Loading Data From APO SCM 5.0 to BW 7.0

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

Loading Data from APO SCM 5.0 to

BW 7.0

Applies to:

SAP BI 7.0, SCM 5.0. For more information, visit the EDW homepage

Summary

This paper will provide a step by step process to load data from APO Demand Planning to SAP BW.

Author: Geetanjali Deshpande

Company: L&T Infotech

Created on: 2 May 2011

Author Bio

Geetanjali Deshpande is SAP BI Consultant with 4.5 years experience in SAP BI implementation, Support and Enhancement projects. SAP expertise includes extensive knowledge of SAP BI and its integration with other SAP and non-SAP systems.

http://www.sdn.sap.com/irj/sdn/edw

Loading Data from APO SCM 5.0 to BW 7.0


© 2011 SAP AG 2

Table of Contents

Business Scenario: ............................................................................................................................................. 3

Process to Create Data Source in APO ............................................................................................................. 3

Step 1: ............................................................................................................................................................. 3

Step 2: ............................................................................................................................................................. 4

Step 3: ............................................................................................................................................................. 4

Step 4: ............................................................................................................................................................. 5 No Extraction of Data Records without Key Fig Values: .............................................................................................. 6

Package Size: .............................................................................................................................................................. 7

Parallel Processing Profile ........................................................................................................................................... 7

Step 5: ............................................................................................................................................................. 8

Experience Sharing: ........................................................................................................................................... 8

Related Content .................................................................................................................................................. 9

Disclaimer and Liability Notice .......................................................................................................................... 10



© 2011 SAP AG 3

Business Scenario:

Consider the following business scenario: A company is using APO Demand Planning (DP) to create a forecast of market demand for its products. The company is using SAP R/3 as a transactional system and SAP BW for reporting. To monitor the forecasting accuracy, the forecast should be tracked against the actual shipments. We can have such monitory reports in SAP BW. For such reports we would need to load the APO Demand Planning data to the SAP BW and then we can create a report to show the comparison of forecasts against the actual shipments. This paper will provide you step by step process to extract data from APO Demand Planning to SAP (earlier know as BI) BW 7.0

Process to Create Data Source in APO

To load data to SAP BW, we need to create a data source in APO system.

Step 1:

Login to APO system and open the SAP menu. Go to “Administration of Demand Planning and Supply” as shown below:



© 2011 SAP AG 4

Step 2:

This will take you to the S&DP Administration screen as shown below:

Here you will find the list of all the planning areas created in the system for Demand Planning. Double click on the Planning Area for which you want to create a Data Source.

Step 3:

After double clicking on a particular Planning Area, following screen will appear. Here go to Extras -> Data Extraction Tools



© 2011 SAP AG 5

Step 4:

By selecting above option following screen will appear:

Here click on the Generate DataSource and then the system will ask for the DataSource name and other settings.



© 2011 SAP AG 6

Note: The DataSource generated will by default have name starting with “9A”. This is as per the SAP standard naming conventions.

The various settings that we can do on this screen are:

No Extraction of Data Records without Key Fig Values:

Set this indicator if you want to prevent the system from transferring data records to InfoObjects in the Business Information Warehouse if all key figures in the data record have the value zero. Depending on your data this can drastically reduce the volume of information that the system transfers, and as a result improve performance.



© 2011 SAP AG 7

Package Size:

In the lower box you specify how many data records are transferred in one package. When transferring large data volumes it is essential that the data is split into packages to avoid memory problems. When the source system has finished reading the data packages, it is transferred to BW and processed further. In this box it is possible to change the default for all data extraction in the system or just the value for the current planning area.

Parallel Processing Profile



© 2011 SAP AG 8

You can also enter a parallel processing profile that you have previously created in Customizing (Demand Planning -> Profiles -> Maintain Parallel Processing Profile). This determines how and if the reading and transfer of the packages is split into parallel processes. As such the block sizes that you enter in the parallel processing profile should be significantly smaller than the package sizes above.

Step 5:

With the following options we can test, transport or replicate the DataSource.

Experience Sharing:

We can create multiple DataSources for a single Planning Area to meet the data extraction requirements.

We can enhance this DataSource to add custom logic for extraction from Planning Area in the same way as in SAP R/3 using BADI development,

We can create standard as well as remote access enabled DataSources based on Planning Area to meet the reporting requirements.

The Remote Enabled DataSource can be used with Virtual Cubes to report the Planning Area data as it is in BI at real time. The standard extractors can be used for periodic loading of Planning Area data to SAP BW.



© 2011 SAP AG 9

Related Content

Demand Planning

Enhancing DataSource

Data Warehousing

For more information, visit the EDW homepage

http://help.sap.com/saphelp_scm40/helpdata/en/8a/9d6937089c2556e10000009b38f889/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/EN/d9/f622392ab1f708e10000000a11402f/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/EN/43/477945f03530d9e10000000a11466f/frameset.htm

http://www.sdn.sap.com/irj/sdn/edw



© 2011 SAP AG 10

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Loading Data From APO SCM 5.0 to BW 7.0

Documents

Transcript of Loading Data From APO SCM 5.0 to BW 7.0