Entering content frame

Process documentation Sales Scheduling Agreement Processing Locate the document in its SAP Library structure

Purpose

In the SAP Business Information Warehouse (SAP BW) you can evaluate data on sales scheduling agreement items that are planned in SAP APO.

As well as sales scheduling agreements planned in APO (APO sales scheduling agreements), sales orders from SAP R/3 can also be included in the evaluation.

For example, you can evaluate

        How reliably customer requirements were confirmed, in other words, whether they were confirmed fully or partially

        How reliably deliveries were made for customer requirements, in other words, whether deliveries were made on time for confirmed customer requirements

Background documentation

The following InfoCubes, which until now, only took sales orders into account, can also be filled with data from APO sales scheduling agreements:

         Sales: Overview (0SD_C03)

         Service Level Order Quantities (0SD_C11)

         Backorders (0SD_C14)

Integration

APO Release

as of APO 4.0

Plug-In Release

as of PI 2004.1

OLTP Release

as of SAP R/3 Enterprise Core 4.70

BW Release

BI 3.3 Add-On

 

To carry out evaluations that take into account sales scheduling agreements you must be working with SAP APO 4.0 and a SAP R/3 system with Plug-In PI 2004.1.

Depending on the process, the data comes from different data source/source systems:

       If a sales scheduling agreement item is planned in SAP APO movement data, for example, required, confirmed, open and original quantities, comes from SAP APO. The item data, such as material, division or sold-to party comes from SAP R/3.

       Order and movement data for sales orders and order and movement data for deliveries for sales orders and sales scheduling agreements planned in SAP APO comes from SAP R/3.

Features

The evaluation of customer requirements from sales order and APO sales scheduling agreements can be carried out for schedule lines or for releases.

Schedule Line Based Evaluation of Requirements from Sales Orders and Sales Scheduling Agreements

The following graphic represents how data on customer requirements and deliveries from the R/3 system is combined with order data for sales scheduling agreements from the APO system.

 

This graphic is explained in the accompanying text

 

This graphic is explained in the accompanying text

ODS Objects

The ODS object Assignment of Deliveries to Requirements (0CDS_DS07) is the central InfoProvider in the information flow, in which requirements and confirmed requirements from sales scheduling agreements and sales orders planned in SAP APO are compared with deliveries that have been made, on the basis of the delivery date.

The InfoProvider Assignment of Deliveries to Requirements (0CDS_DS07) is filled from the ODS objects

        Schedule Lines for Sales Scheduling Agreements 0CDS_DS01

In the update rule of the requirement data from APO sales scheduling agreements of the ODS object Scheduling lines for Sales Scheduling Agreements (0CDS_DS01) in the ODS object Assignment of Deliveries to Requirements (0CDS_DS07) data, that has been transferred from SAP R/3 to SAP BW on document item level (for example, sold-to party and material) is read in from the ODS object Sales Scheduling Agreement Items (0CDS_DS02).

        Sales Scheduling Agreement Items 0CDS_DS02

The ODS object Sales Scheduling Agreement Items (0CDS_DS02) can only be filled with data about sales scheduling agreement items that are also planned in SAP APO. 

Therefore, the contents of the characteristic Sales Scheduling Agreement Item Planned in SAP APO (0APOPLANNED) is checked in the update rule of the ODS objects from the InfoSource Order Item Data (2LIS_11_VAITM). The system checks whether the transferred document is planned in SAP APO. If so, it is updated in the ODS object.

        Deliveries 0CDS_DS05

In the update rule of the deliveries in the ODS object Deliveries (0CDS_DS05) the system checks, within the start routine whether the delivery to be updated from source system to the InfoProvider contains a reference to a preceding document that is contained in either one or both of the ODS objects Sales Orders (0CDS_DS04) or Sales Scheduling Agreement Items (0CDS_DS02). The document is only transferred to the ODS object if the result of the check is positive.

        Sales Orders 0CDS_DS04

The ODS object Sales Orders is filled from the InfoSources Order Schedule Lines (2LIS_11_VASCL) for the original quantities and Sales and Shipping Consumption Data for Schedule Lines (2LIS_11_V_SCL) for the open quantities.

Because the InfoSource Sales and Shipping: Consumption Data for Schedule Lines (2LIS_11_V_SCL), which is used to update open quantities, only updates open quantities from confirmed schedule lines, the key figure Open Requirement Quantity (0APOOPREQ) of the ODS objects Assignment of Deliveries to Requirements (0CDS_DS07) is not updated for sales orders. This affects the calculation of key figures that are based on the open requirement quantity.

Background documentation

Whereas the ODS object Schedule Lines for Sales Scheduling Agreements (0CDS_DS01) is filled from SAP APO from the InfoSource Due Delivery Schedules and Confirmations (0APO_PPDS_CDS_1), the other ODS objects mentioned above are filled using InfoSources from SAP R/3.

 

The correction quantities for sales scheduling agreements from ODS object 0CDS_DS06 are used to synchronize cumulative delivered quantities from deliveries from SAP R/3 with cumulative quantities from requirements, (from SAP APO), for which deliveries have been made. When the correction quantities are being calculated the deliveries from the ODS object Deliveries (0CDS_DS05) are accessed, within the update rule, in order to determine cumulative delivered quantities dynamically.

For more information on the ODS object 0CDS_DS06 and an example of the calculation of correction quantities, see Correction Quantities for Sales Scheduling Agreements.

InfoCubes

The following InfoCubes are filled from the ODS object Assignment of Deliveries to Requirements (0CDS_DS07):

        Service Level Order Schedule Lines 0CDS_C01

        Fulfillment Using Confirmations and Deliveries 0CDS_C02

        Service Level Order Quantities 0SD_C11

In the update rules for Service Level Order Quantities (0SD_C11) and Service Level Order Schedule Lines (0CDS_C01) as well as Fulfillment Using Confirmations and Deliveries (0CDS_C02) the correction quantity are read in from the ODS object Correction Quantities 0CDS_DS06.

        Backorders 0SD_C14

Process Chain

The data flow described can be initialized using the process chain 0APO_PPDS_CDS_INIT_P01 (Initial Data Loading) and updated in the process chain 0APO_PPDS_CDS_DELTA_P02 (Delta Data Loading) in the Delta process.

The purpose of the process chains is to fill the ODS object Assignment of Deliveries to Requirements (0CDS_DS07) (that is, the data flow beneath the ODS object in the graphic) as well as the initialization and Delta update of the InfoCube Fulfillment Using Confirmations and Deliveries (0CDS_C02).

The filling of the InfoCubes 0CDS_C01, 0SD_C11 and 0SD_C14 is not part of the process chain. These InfoCubes cannot be filled with data from the ODS object 0CDS_DS07 in the Delta process, but only by full update.

For more information, see Initial Data Load – Sales Scheduling Agreement Processing and Delta Data Load – Scheduling Agreement Processing.

 

Order-Based Evaluation of Requirements from the Sales Scheduling Agreements

The InfoCube Sales: Overview (0SD_C03), which, until now, you could use to evaluate sales orders in Sales and Distribution has been enhanced.

The following graphic illustrates how the InfoCube Sales: Overview is filled:

 

This graphic is explained in the accompanying text

 

As well as the method of filling the InfoCube Sales: Overview (0SD_C03) using R/3 InfoSources that has existed up to now, (on the left, in gray in the graphic) as of SAP BI Content 3.3 Add-On you can also fill the InfoCube with data on APO sales scheduling agreements (on the right, in blue in the graphic).

The InfoCube Sales: Overview (0SD_C03) is filled

        from SAP R/3 from the following InfoSources:

        Order: Item Data 2_LIS_11_VAITM

        Consumption Item Data 2_LIS_11_V_ITM

        Delivery Header Data 2LIS_12_VCHDR

        Delivery Item Data 2LIS_12_VCITM

        Billing Document Header Data 2LIS_13_VDHDR

        Billing Document Item Data 2LIS_13_VDITM

        From SAP APO using the ODS object Order Receipt for Sales Scheduling Agreements (0CDS_DS03), that is filled with data from SAP APO using the InfoSource Due Delivery Schedules and Confirmations (0APO_PPDS_CDS_1)

In the update rule of the requirement data from APO sales scheduling agreements of the ODS object Order Receipt for Sales Scheduling Agreements (0CDS_DS03) in the InfoCube Sales: Overview (0SD_C03), data, that has been transferred from SAP R/3 to SAP BW on document item level (for example, sold-to party and material) is read in from the ODS object Sales Scheduling Agreement Items (0CDS_DS02). This ODS object can only be filled with data on APO sales scheduling agreements. Therefore, the contents of the characteristic Sales Scheduling Agreement Item Planned in SAP APO (0APOPLANNED) is checked in the update rule of the ODS objects from the InfoSource Order Item Data (2LIS_11_VAITM). The system checks whether the transferred document is planned in SAP APO. If so, it is updated in the ODS object.

 

Background documentation

In contrast to the ODS object Schedule Lines for Sales Scheduling Agreements (0CDS_DS01) the ODS object Order Receipt for Sales Scheduling Agreements (0CDS_DS03) is not updated on the level of the schedule line but on the level of the release. This is achieved by using the fields Release Date and Release Time as the key.

Queries

In the role Sales Scheduling Agreement Processing (SAP_BW_CDS_ORDER) you can use the following queries:

        Service Level Order Schedule Lines (uses InfoCube Service Level Order Schedule Lines 0CDS_C01)

Example

For example, the query Service Level Order Schedule Lines (0CDS_C01_Q0001) can be used to determine for how many schedule lines from sales orders and from APO sales scheduling agreements deliveries have been made punctually, too early, or too late for selected sold-to parties and materials. The comparison between order dates and delivery dates is carried out on the basis of calendar days.

        Fulfillment Using Deliveries (uses InfoCube Fulfillment Using Deliveries and Confirmations 0CDS_C02)

Example

The query Fulfillment Using Deliveries (0CDS_C02_Q0001) can be used to determine at what times there was a backlog of deliveries to a certain sold-to party for a certain material or at what times there was an overdelivery.

When the query is called the system asks the user to enter the sold-to party and materials and the evaluation period for which the data should be requested from the InfoCube.

The user can also define tolerance values for the over/underdelivery of the requirement and the confirmed requirements that are relevant for highlighting certain situations in the display. Depending on the tolerance value defined, the values of individual key figures are highlighted either in green (situation OK), yellow (critical) or red (especially critical). The key figures displayed describe the state of the over or underdelivery, partly in the form of a quantity (absolute over/underdelivery) partly in the form of a relation. The cumulative quantities from the deliveries made and the requirements that are determined for the evaluation period are used to calculate the relative under or overdelivery.

        Fulfillment Using Confirmations (uses InfoCube Fulfillment Using Deliveries and Confirmations 0CDS_C02)

Example

The query Fulfillment Using Confirmations (0CDS_C02_Q0002) can be used to determine at what times there was a backlog of confirmations of a customer requirement for a certain material and a certain sold-to party or at what times there was a surplus confirmation.

When the query is called the system asks the user to enter the sold-to party and materials and the evaluation period for which the data should be requested from the InfoCube.

In addition the user can define tolerance values for the surplus/shortage confirmation of the requirement. The key figures displayed describe, on the one hand, an absolute surplus or shortage confirmation and on the other, the relative surplus or shortage confirmation which the system calculates using the cumulative quantities from the confirmed quantities and requirement quantities for the evaluation period.

For more information, see Service Level Order Schedule Lines, Fulfillment Using Confirmations and Fulfillment Using Deliveries.

 

 

For more information on analyzing sales orders, see Structure linkOrder Fulfillment.

For more information about sales scheduling agreements planned in SAP APO see the SAP Help Portal under SAP Cross-Industry Solutions mySupply Chain Management SAP Supply Chain Management SAP SCM SAP Advanced Planning and Optimization (SAP APO) Production Planning and Detailed Scheduling (PP/DS) External Procurement Collaborative Management of Delivery Schedules Link to external website  Delivery Schedule Processing for Sales Scheduling Agreements (SCM-APO-PPS-CDS).

 

Leaving content frame