cancel
Showing results for 
Search instead for 
Did you mean: 

Difference b/w external & internal bw system for apo dp

Former Member
0 Kudos

Hi,

what are the advantages & disadvantages by using external BW system in implementing apo dp component as well as please provide me for internal also.

Regards,

chinni

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Chinni,

The "internal" BW system plays the following roles:

1) A tool for extracting data from other source systems (e.g.history from SAP ERP). The "internal" BW system has the data extraction capabilities (e.g. capability to extract data from files, SAP source systems, DB Connect, UD Connect, XML, SOAP datasources, XI etc).

2) A data staging area for history. We usually create a history InfoCube in APO. This InfoCube is filled with history from source systems (e.g. SAP ERP). The history is then loaded from InfoCube to the Planning Area using transaction /SAPAPO/TSCUBE.

3) The history InfoCube can also be used to generate Characteristic Value Combinations (CVCs)

3) A place where we store backup of the data in the Planning Area. Usually, we create an InfoCube in which we store a backup of the data of the Planning Area. This is needed, for example, when we need to de-initialize a planning area.

In small implementations, we also execute BeX queries/reports from the "internal" BW system. Usually though, we use an external BW system. It is actually recommended to store the data into an "external" BW System (e.g. an Enterprise DataWarehouse) and do the reporting from there.

The requirements of the APO system and the way it is configured is different from the requirements of a BI system. For example, the APO system might be configured to make sure write access is fast. On the contrary, BW systems are usually configured to make sure that read access is fast.

If you have a external BW system, you can optimize your environment so that it is optimized for OLAP.

Hope this helps.

Answers (0)