Thursday, June 5, 2014

SAP BW 7.4 SP 05 on HANA.

SAP BW on HANA continues to evolve in order to meet the growing challenges imposed on IT by these ever changing market forces.
 
The release of SAP BW running on SAP HANA is a great example of how SAP BW has evolved to ensure organizations continue to leverage  their investment in SAP BW to meet these new  challenge.
 
Key features of SAP BW 7.4. SP 05 on HANA
 
◦Enhanced Data Modeling  
  • ◾Common Eclipse based Modeling Tools
  • ◾BW/HANA Smart Data Access providing the logical EDW
  • ◾Easy integration of external data models with Open ODS Layer
  • ◾Further reduce data layers in BW via Operational Data Provisioning
  • ◾New Composite Provider
  
◦Push down further processing logic to HANA
  • ◾BW Analytic Manager
  • ◾HANA  Analysis Processes
  • ◾BW Transformations
  • ◾PAK (Planning Application Kit) – Pushing down more planning semantics
       
How Does BW running on RDBMS differ from BW running on HANA ?
 
Excellent query performance for improved decision making
 
  • •Performance boost for Data Load processes for decreased data latency
  • •Accelerated In-Memory planning capabilities for faster planning scenarios
  • •Flexible combine EDW with HANA-native data for real-time insights and decision making
  • •Datapersistency layers are cut off and reduced administration efforts
  • •Simplified data modeling and remodeling
 
Characteristic Values > 60 Characters and Extra Long Texts

Extend length for Characteristics values
  • •The maximum output length and attribute length can be <= 250
250 characters applies for the total (compound) length of the key
 
Extra long texts for Characteristics
  • •Long text can be stored as CHAR 60 (standard) or CHAR 1333 (option‘Long text is XL’ set).
  • •No changes on frontends required
  • •Simple switch for existing Characteristics possible
 
BW Integrated Planning

Next level of performance by  pushing down further planning capabilities to HANA
  • •Possibility to implement HANA SQL Script  based user exits to be able to push down ABAP based user exits down to HANA
  • •Distribution of new planning records by key pushed down to HANA
  • •Additional planning functions – Physical delete of planning data records in DSOs rather than just zeroing-out facts
  • •Details about availability of already pushed down elements see SAP note 1637199
Combine the best of three worlds to a unique planning solution (HANA, BPC, BW-IP)

Combines the successful EPM Excel add-in
  • •flexible BPC admin-UI
  • •powerful BW-IP / PAK planning manager
  • •super-fast HANA planning engine
Selected features
  • •Full PAK-model compatibility
  • •Business process flows (BPF)
  • •Work-status
  • •Data auditing
  • •Easy upload scenario

Tuesday, June 3, 2014

Communication from EWM to SAP ERP...

Communication from Extended Warehouse Management (EWM) to SAP ERP uses defined interfaces, and enables distribution, changes to, and confirmation of delivery-relevant data.
In SAP ERP, the interfaces between EWM and SAP ERP are based on deliveries. In EWM, they are based on the following:

●  Inbound delivery notifications and inbound deliveries in the inbound delivery process

●  Outbound delivery orders and outbound deliveries in the outbound delivery process

Where necessary, SAP ERP triggers subsequent communication steps for specific processes.
For more information, see Warehouse Req. - Type Inbound Del. or Outbound Del. Order, Generating a Warehouse Request of the Inbound Delivery Type, Generating a Warehouse Request of Type Outbound Delivery Order.

Communication is asynchronous and uses queued Remote Function Call (qRFC) technology. This technology guarantees serialization of the messages.

INTEGRATION:

The following figure gives you an overview of the functions supported by the interfaces between EWM and SAP ERP:
This graphic is explained in the accompanying text

  1.  Distribution of deliveries
       ○  Send deliveries from SAP ERP to EWM
       ○  Send deliveries from EWM to SAP ERP (for example, for manual inbound deliveries)
  2.  Changes to deliveries
       ○  Send changes from EWM to SAP ERP (for example, confirmation of a pick denial from EWM to SAP ERP)
       ○  Send changes from SAP ERP to EWM (for example, changed ASN from vendor)
  3.  Confirmation of an inbound and outbound delivery split from EWM to SAP ERP
  4.  Send confirmation of deliveries from EWM for follow-on functions in SAP ERP (for example, goods receipt, goods issue, confirmation before goods issue for invoicing before goods issue)
Prerequisites
●  If you are using SAP ERP. Here, you define for each plant and storage location whether you manage your warehouse in a separate, decentralized EWM. EWM receives the requests for goods movements from SAP ERP.
●  Transmit all information to EWM that EWM requires for the goods movements. These include:
    ○  Partner master data (for example, customers, vendors, transportation service providers)
    ○  Location master data (for example, customers, vendors, plants)
    ○  Product master data
●  You have made the Customizing settings for integration with SAP ERP.
    In the Implementation Guide (IMG) for EWM, choose Interfaces → ERP Integration.
Features
    The following functions are available for EWM and SAP ERP for the purpose of processing inbound and outbound deliveries.
●  Processing of Inbound Deliveries
    ○  Receipt of an inbound delivery from SAP ERP to EWM
    ○  Receipt of a change request for inbound deliveries from SAP ERP to EWM
    ○  Notification of changed data before goods receipt from EWM to SAP ERP
    ○  Confirmation of a goods receipt from EWM to SAP ERP
    ○  Notification of a reversal or correction of the goods receipt from EWM to SAP ERP
    ○  Notification of an inbound delivery split from EWM to SAP ERP
●  Processing of Outbound Deliveries
    ○  Receipt of an unchecked outbound delivery from SAP ERP to EWM
    ○  Receipt of a checked outbound delivery from SAP ERP to EWM
    ○  Reporting of an outbound delivery change from EWM to SAP ERP
    ○  Quantity change request from EWM to SAP ERP
    ○  Confirmation of a goods issue from EWM to SAP ERP
    ○  Notification of a reversal of the goods issue from EWM to SAP ERP
    ○  Direct billing or invoicing before goods issue
    ○  Communication of an outbound delivery split from EWM to SAP ERP
For more information, see Processing of Inbound Deliveries, Processing of Outbound Deliveries, and Interfaces for Communication from EWM to SAP ERP.