Show TOC

Process documentationHistorical Data Capture with SAP ERP

 

You use this process to generate a demand history based on data from SAP ERP.

To get the historical data, the system loads order data from the Sales (SD) component of SAP ERP and stock transfer data from the Materials Management (MM) component of SAP ERP into the Business Intelligence system in SAP Supply Chain Management (SAP SCM).

The system processes this raw data according to the requirements of Service Parts Planning (SPP) and consolidates it as a demand history.

Caution Caution

If you work with enhancement package (EHP) 2 for SAP ERP 6.0, and create a sales order in SAP ERP SD, the system automatically calls the global availability check (GATP). GATP provides the ERP system with all required information about the location (for example, whether it is a customer-facing location, or the first stockholding location). If you change a sales order in SAP ERP SD, the system does not always automatically call GATP, so information about the location may not be provided. If the information about the location is not supplied, SAP Supply Chain Management (SAP SCM) does not take changes in this sales order into account when capturing historical data.

End of the caution.

Recommendation Recommendation

If you make changes to a sales order in SAP ERP SD, we recommend that you manually call GATP afterwards.

End of the recommendation.

Note Note

If you work with releases of SAP ERP higher than enhancement package 2, this recommendation does not apply.

End of the note.

Prerequisites

  • You have made the settings for historical capture and maintenance. For more information, see Settings for Historical Data Capture and Maintenance.

  • In the demand history, SAP Service Parts Planning (SPP) requires fields (at least FACELOC, FLOCTYPE, STOCKLOC, and SLOCTYPE) from sales orders that do not exist in releases of SAP ERP earlier than enhancement package (EHP) 2.

    To make the required fields available in enhancement package (EHP) 2 for SAP ERP 6.0 or higher, you have activated the business function Integration of SCM and ERP (SCM_GEN_01) in transaction SFW5. For more information, see SAP Help Portal at http://help.sap.comInformation published on SAP site, under Start of the navigation path SAP ERP Next navigation step SAP ERP Central Component Next navigation step SAP ERP Enhancement Packages Next navigation step ERP Central Component Enhancement Package 4 Next navigation step Business Functions (SAP Enhancement Package 4 for SAP ERP 6.0) Next navigation step Business Functions in SAP ERP Next navigation step Enterprise Business Functions Next navigation step Cross-Application Enterprise Business Functions Next navigation step Integration of SCM and ERP End of the navigation path.

    To make the required fields available in SAP ERP releases before enhancement package (EHP) 2 for SAP ERP 6.0, you have followed the approach described for the UEPOS and EZEIT fields. For more information, see Manually Enhancing DataSource 2LIS_11_VASCL.

  • To load order data from SAP ERP SD, you have maintained DataSource 2LIS_11_VASCL in SAP ERP and replicated it to the BI system of SAP SCM. There you have mapped this DataSource to InfoSource 2LIS_11_VASCL.

    To load stock transfer data from SAP ERP SD, you have maintained DataSource 2LIS_02_SCL in SAP ERP and replicated it to the BI system of SAP SCM. There you have mapped this DataSource to InfoSource 2LIS_02_SCL.

    For each of the InfoSources 2LIS_11_VASCL and 2LIS_02_SCL, you have created and executed an InfoPackage with the update mode Initialization of the Delta Method and created an InfoPackage with the update mode Delta Update and scheduled it as a background job.

    For more information about DataSources, see the SAP Library for SAP NetWeaver under Start of the navigation path SAP NetWeaver Library Next navigation step SAP NetWeaver by Key Capability Next navigation step Information Integration by Key Capability Next navigation step Business Intelligence Next navigation step Data Warehousing Next navigation step Data Acquisition Next navigation step Data Extraction from SAP Source System Next navigation step DataSource Next navigation step Transferring BI Content DataSources into Active Version End of the navigation path.

    For more information about InfoPackages, see the SAP Library for SAP NetWeaver under Start of the navigation path SAP NetWeaver Library Next navigation step SAP NetWeaver by Key Capability Next navigation step Information Integration by Key Capability Next navigation step Business Intelligence Next navigation step Data Warehousing Next navigation step Data Warehouse Management Next navigation step Scheduler Next navigation step Creating InfoPackages End of the navigation path.

  • If you want to load data from SAP ERP SD and you work with enhancement package (EHP) 2 for SAP ERP 6.0, you have manually added the UEPOS and EZEIT fields to DataSource 2LIS_11_VASCL. For more information, see Manually Enhancing DataSource 2LIS_11_VASCL.

    Note Note

    If you work with releases of SAP ERP higher than enhancement package 2, this manual enhancement is not required.

    End of the note.

  • If you load order data from SAP ERP SD, you have transferred and activated DataStore object 9ASDDAT. The system then generates InfoSource 89ASDDAT.

    If you load stock transfer data from SAP ERP MM, you have transferred and activated DataStore object 9APURDAT. The system then generates InfoSource 89APURDAT.

    For each of the InfoSources89ASDDAT and 89APURDAT, you have created and executed an InfoPackage with the update mode Initialization of the Delta Method as well as created an InfoPackage with the update mode Delta Update and scheduled it as a background job.

  • If you want to load order data via a CSV file, you have transferred and activated InfoSource 9ASD_CSVLOAD.

    If you want to load stock transfer data via a CSV file, you have transferred and activated InfoSource 9APUR_CSVLOAD.

    For each of the InfoSources 9ASD_CSVLOAD and 9APUR_CSVLOAD, you have created a source and an InfoPackage with update mode Full Update.

Process

  1. When you load order data from SAP ERP SD, the system extracts the data from SAP ERP SD and saves it in DataStore object 9ASDDAT. InfoSource 89ASDDAT takes its data from this DataStore object.

    When you load stock transfer data from SAP ERP MM, the system extracts the stock transfer data from SAP ERP MM and saves it in DataStore object 9APURDAT. InfoSource 89APURDAT takes its data from this DataStore object.

  2. The system uses update rules to process and check the data.

    For more information, see Update Rules for Historical Data Capture.

    The system saves the processed and checked data together with the raw data in the DataStore object 9ARAWDAT and as demand history in the InfoCube 9ADEMAND.

  3. The system captures the demand history in the InfoCube 9ADEMAND as follows:

    • The system aggregates the demand in weeks.

    • The system aggregates the demand in months.

    • The system aggregates the demand in posting periods.

    • The system aggregates the demand along the BOD.

      In doing so the system captures both the demand history of a product at each stockholding location and at each entry location. However, the system only uses the demand history of the stockholding location for forecasting.

  4. The system creates the yearly demand history that both phase-out planning and surplus and obsolescence planning require. To do so, the system uses the data in the InfoCube 9ADEMAND and extracts it into the InfoCube 9ADEMANN. For more information, see Historical Data Capture in Years.

As an alternative to the above process, you can also load sales and stock transfer orders from a flat file (CSV file). The following graphics show the data flow if you load data from a CSV file:

In the above case the system loads order data from a CSV file via InfoSource 9ASD_CSVLOAD. The system then proceeds as described in steps 2 to 4.

In the above case the system loads stock transfer data from a CSV file via InfoSource 9APUR_CSVLOAD. The system then proceeds as described in steps 2 to 4.

In the above case the system loads order data from a CSV file via InfoSource 9ASDDAT_CSV. The system applies update rules to the data in the InfoSource and saves the order data in DataStore object 9ASDDAT. InfoSource 89ASDDAT takes its data from this DataStore object. The system then proceeds as described in steps 2 to 4.

In the above case the system loads stock transfer data from a CSV file via InfoSource 9APURDAT_CSV. The system applies update rules to the data in the InfoSource and saves the stock transfer data in DataStore object 9APURDAT. InfoSource 89APURDAT takes its data from this DataStore object. The system then proceeds as described in steps 2 to 4.

For more information about how you load data using a CSV file, see the SAP Library for SAP NetWeaver under Start of the navigation path SAP NetWeaver Library Next navigation step SAP NetWeaver by Key Capabilities Next navigation step Information Integration by Key Capabilities Next navigation step Business Intelligence Next navigation step Data Warehousing Next navigation step Data Acquisition Next navigation step Transferring Data from Flat Files End of the navigation path.