SALES AND DISTRIBUTION (SAP HANA-OPTIMIZED)

This documentation describes the SAP HANA-optimized BI Content objects that you can use to analyze data from SAP ERP Sales and Distribution.

The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW running on SAP HANA.

You can use the SAP HANA-optimized BI Content for Sales and Distribution to analyze sales order data, delivery data, billing data, condition data, and delivery service data.

InfoArea Delivery Service – SAP HANA-optimized (/IMO/SDDLV) contains the MultiProvider SD-DLV: Service Level (/IMO/SD_M11) and SD-DLV: Backorders (/IMO/SD_M51), which enables you to analyze delivery service quality and backorders.

Unlike the existing InfoCube for Backorder reporting (0SD_C14), MultiProvider SD-DLV: Backorders(/IMO/SD_M51) enables reporting at a more granular level without the need to load the data into an InfoCube. This is made possible by the backorder key figures being calculated at runtime in the SAP HANA Information model. MultiProvider SD-DLV: Backorders (/IMO/SD_M51) only supports current backorders. If a historic view of the backorder data is needed, a separate InfoCube has to be created and loaded with the required time granularity.

Prerequisites

See Prerequisites.

Features

Data is supplied by the following DataSources:

• 2LIS_11_VAHDR: Sales Document Header Data
• 2LIS_11_VASTH: Sales Document Header Status
• 2LIS_11_VAITM: Sales Document Item Data
• 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data
• 2LIS_11_VAKON: Order Condition Data
• 2LIS_11_V_SSL: Sales Document: Order Delivery
• 2LIS_12_VCHDR: Delivery Header Data
• 2LIS_12_VCITM: Delivery Item Data
• 2LIS_13_VDHDR: Billing Document Header Data
• 2LIS_13_VDITM: Billing Document Item Data
• 2LIS_13_VDKON: Billing Condition Data

SAP delivers the following example BEx queries on top of MultiProviders Sales Overview (/IMO/SD_M10),Delivery (/IMO/SD_M20), Conditions (/IMO/SD_M40), SD-DLV: Service Level (/IMO/SD_M50), and SD-DLV: Backorders (/IMO/SD_D51):

• Incoming Orders (/IMO/SD_M10_Q0001)
• Open Orders (/IMO/SD_M10_Q0002)
• Sales Order and Sales Revenue from last 12 Months (/IMO/SD_M10_Q0003)
• Order, Delivery and Sales Quantities (/IMO/SD_M10_Q0004)
• Expected Incoming Orders Based on Open Quotations (/IMO/SD_M10_Q0005)
• Delivery Overview (/IMO/SD_M20_Q0001)
• Billing Overview (/IMO/SD_M30_Q0001)
• Ratio of Credit Memos to Billing Documents (/IMO/SD_M30_Q0002)
• Condition Value per Customer (/IMO/SD_M40_Q0001)
• Delivery Performance (/IMO/SD_M50_Q0001)
• Perfect Order Fulfillment (/IMO/SD_M50_Q0003)
• Returns (/IMO/SD_M50_Q0002)
• Backorders: Overview (/IMO/SD_M51_Q0001)
• Backorders: Open Order Quantity (/IMO/SD_M51_Q0002)

You can track changes to amounts and quantities for sales documents over a specified time period for the following DataStore objects:

• SD: Sales Document Item Data (/IMO/SD_D11)
• SD: Sales-Shipping Allocation Item Data (/IMO/SD_D16)
• SD: Delivery Item Data (/IMO/SD_D21)
• SD: Billing Document Item Data (/IMO/SD_D31)

These changes are tracked using InfoObject Statistics Date as Calendar Day (0ST_UP_DTE). All key figures are updated using aggregation type “Summation”.

 Note

If you also want to track changes based on characteristics, such as the material group or route, you must add the corresponding characteristics to the key part of the DSOs. A total of 16 key fields are supported. If you want to track more characteristics, you need to use an InfoCube instead of the DSO (for example 0SD_C03 –Sales Overview).

 Note

If you want to report on the basis of the creation date, rather than tracking the changes to sales documents, you need to make the following changes to adapt the content:

• Move characteristic 0CALDAY from the key part of DSO to the data part
• Update all time characteristics using characteristic 0CREATEDON (instead of 0ST_UP_DTE) in BW transformations
• Change the aggregation type for all key figures to “Overwrite”

Integration

Generic InfoObjects

The following generic InfoObjects are filled for the new SAP HANA-optimized BI Content:

• Generic Customer (0GN_CUSTOM)
• Product (0PRODUCT)
• Sales Category (0GN_CAT_SAL)
• Location (0GN_LOCATIO)

SD-Specific Logic Used in Transformations

InfoObject	Logic
0DEB_CRED Credit/Debit Postings (C/D)	Differentiates between debit and credit postings. The following sales document categories (0DOC_CATEG =VBTYP) generate credit postings in the DSO: For sales order processing: Credit memo request (VBTYP = K) Returns (VBTYP = H) For delivery processing: Return delivery (VBTYP = T) For Invoice processing: Credit memo (VBTYP = O) Cancelled invoice (VBTYP = N) Internal consumption (credit) (VBTYP = 6) All other sales document categories generate debit postings in the DSO.
0DOC_CLASS Document classification: Order/Delivery/Invoice	Classifies documents as order, delivery, or invoicing (billing) documents: O = Order D = Delivery I = Invoice

Data Flow

Overview

Overview: Delivery Service

Overview: Backorders

Related Content

The following content is not part of SAP product documentation. For more information, see the followingdisclaimer  .

SAP Community Network (SCN)

• ABAP Development
• Java Development
• Business Process Management and Composition
• Business Rules Management
• Process Integration (PI) & SOA Middleware
• B2B Integration
• SAP Netweaver Portal
• User Interface Technology
• SAP Netweaver Business Warehouse
• Web Dynpro ABAP
• Web Dynpro Java
• Composite Applications
• Security
• SAP Netweaver Application Server
• SAP Netweaver Administrator
• Enterprise Services Repository (ESR)
• SAP Netweaver Business Client

Source: Sales and Distribution ON SAP HANA