Collect and Transfer Demand History (SAP Library - Supply Chain Planning Interfaces (LO-SCI))

Collect and Transfer Demand History

Prerequisites

Demand history can be transferred to the external system through two programs:

RMCPMANU

This program transfers demand history stored in the information structure S125. The user specifies the history’s version, start date and finish date, and the program gives all the data entered within that period.

RBDMCCOP

This program can be used for any information structure. Given a specific time period, the program compares the data records in the version ‘000’ with a designated version (usually version ‘CTR’),and only sends out those data entries which are different in the new version. After the data transfer, the designated version gets updated to version ‘000’ so that the next execution of this program can follow the same logic. Only the initial data transfer sends over all the data within the specified period when the designated version has no data in that period.

The menu path for this program is: Logistics ® Central Functions ® SCP Interfaces ® DP/DRP Interface ® Send info structure

RBDMCCOP reduces data traffic significantly. But demand history data is usually aggregated according to the combination of characteristic values in the external system. If the original data records are not maintained in the external system at the lowest level, the new updates sent over by RBDMCCOP will not be aggregated and the external system will have the incorrect amount.

Configuration for SIS
Procedure

S125 is provided in the DRP interface as a standard information structure to collect demand history. After analyzing your business process, you need to check out whether the settings of S125 (characteristic values and update rules) satisfy your business needs. You probably need to set up your own information structure because of the special requirements, but you can use S125 as a reference for your setup. If in the integration design S125 is the only information structure the external system accepts, you need to populate data into S125 by copy management. Depending on the customer requirements, the following configuration steps may be or may not be needed.

Set up information structure. Menu path: IMG ® Logistics General ® Logistics Information System ® Logistics Data Warehouse ® Data Basis ® Information Structures ® Maintian Self-defined Information Structures

Enable the LIP message for the information structure. Menu Path: IMG ® Production ® Sales & Operations Planning ® Functions ® Application Link Enabling (ALE)

Maintain update group, statistics groups, etc. Menu path: IMG ® Logistics General ® Logistics Information system ® Logistics Data Warehouse ® Updating ® Updating Control ® Settings: Sales

The R/3 System uses update groups to link together statistics groups and sales areas. The R/3 System comes with several pre-configured statistics groups. The statistics groups and sales area together determine the update group. It is the update group that determines the information structure to be updated. The S125 information structure comes pre-configured to use an existing update group (000001). It is necessary to maintain statistics groups for both materials and customers. If you are creating your own information structure, you should coordinate with other LIS configurations and probably use the existing update group 000001.

Configure and generate the update rules. Formulas and requirements may be used. Menu path: IMG ® Logistics General ® Logistics Information System ® Logistics Data Warehouse ® Updating ® Updating Definition ® Specific Definition Using Update Rules

Activate update rules. You can define the periodicity here. Menu path: IMG ® Logistics General ® Logistics Information System ® Logistics Data Warehouse ® Updating ® Updating Control ® Activate Update

Use copy management if necessary. Menu path: IMG ® Logistics General ® Logistics Iinformation System ® Logistics Data Warehouse ® Data Basis ® Tools ® Copy Management