https://wiki.scn.sap.com/wiki/display/SCM/Planning+Version+Copy+in+SCM+APO

Source : https://blogs.sap.com/2015/01/02/data-extraction-from-planning-area-to-backup-info-cube/

Introduction

A planning area as we know is one of the most important areas in both Demand (DP) and Supply Network Planning (SNP). It basically defines the area where most of the planning activities take place grouping together both characteristics and key figures under a single domain.

In order to maintain the data consistency and to avoid loss of data, it is generally a good practice to take backup of the data in planning area to Info cube.

In this document, we will see how data can be backed up from Planning Area in step wise manner. For illustration purpose, have taken SNP Planning Area however process remains same for both DP and SNP – only major difference being in SNP, export DataSources can be generated for the SNP aggregates and not for MPOS like in Demand Planning. We would see the same further ahead in the document.

1. Create Planning Area

Planning area is created – TESTSNP. Here we have copied the standard planning area 9ASNP02 and created our own custom planning area. Configuration Steps for SNP Planning Area is discussed in detail in the following document –

SNP Configuration Steps for Planning Area and Planning Book/Data View

Creation of Backup Cube

Navigate to the Created Planning Area in the above step and from menu Select Extras – Data Extraction Tools as shown below –

Same can be achieved by the below transaction also –

Transaction – /SAPAPO/SDP_EXTR

Here, we need to select Data backup and then Generate Infocube from Planning Area in next screen. After that we need to provide the name of Infocube and Infoarea as shown below –

Above step will create Infocube with name SNPBACKUP. After creation of backup Infocube, we can see the same in transaction RSA1 – here we can edit/create new dimensions (basically to partition the data) and remove unwanted characteristics/key-figures which we do not want to save in cube.

3. Create Data Source

In order to create the Data Source, we need to again the same path as described in step 2.

Transaction – /SAPAPO/SDP_EXTR

Here, we need to select Generate Data Source and then provide the name of the data Source. 9A is prefixed to the name given by us for Data Source by the system automatically.

In the next screen, we need to select the Aggregate on which we want to base the Data Source. In case of DP Planning Area, we can base the Data Source on the MPOS while this is not the case with SNP. This also means that only the characteristics or characteristics combination contained in these aggregates can be used in the InfoSource, transfer structure and transfer rules. Also For an SNP aggregate, only the key figures assigned to it can be extracted. So, it is an important decision to select the Aggregate on which one wants to base the Data Source as per business requirement. Here, we have selected the aggregate 9AMALA (9AMATNR, 9ATRNAME).

Also while creation of Data Source, there is this indicator as highlighted above which gives one the flexibility to avoid the system from transferring data records cube if all key figures in the data record have the value zero. This can drastically reduce the volume of information that the system transfers, and as a result improve performance.

Once the Data Source is generated, we can replicate the Data Source and then it will appear in transaction RSA1. Then we need to activate the Data Source as shown below

4. Create Transformation

In the above steps, we have created the backup cube for planning area to store the data and also Data Source for Planning Area. Now, we need to link the both and this is achieved by Transformation. It connects the objects in Source to corresponding objects in target.

Transaction – RSA1

Select the Infocube – Right click create transformation. In next screen, we need to provide source and target for this transformation to link. After validation of all linkages, we then activate the transformation as shown below –

In Transformation one also has option to define various Formulas, Rules etc. basically to define how the data needs to be mapped to the target field.

5. Create Data Transfer Package(DTP)

Transaction – RSA1

In Transformation, we defined the mapping between source and target objects; however extraction and update are defined using DTP.

Within DTP, there is option of defining the type of Extraction – Full/Delta, package size, filter criteria, Update Mode, Processing Mode and Error Handling Mechanism. All these options can be defined as per business requirement.

6. Create Infopackage

Transaction – RSA1

Infopackage would help in extracting the data from source and loads it to PSA. Data from PSA to the target is taken by DTP as described above.

Once Infopackage is created, we have defined all the objects which would be needed to extract the data from SNP Planning Area and store it into Backup cube. Final structure in RSA1 would look like below –

Summary –

In this document, we saw how data from planning area can be stored in Infocube via data Source, Transformation, DTP and Infopackage. Also, one can automate these steps via process chain and have it scheduled on Daily/Weekly basis as per requirement.

• – RSA1 – Créer les key figures dans un catalogue d’info objects
• RSA1 – Créer les charactéristiques et attributs
• – /SAPAPO/MSDP_ADMIN – Créer la Planning object structure regroupant charactéristiques et attributs
• /SAPAPO/MSDP_ADMIN – Créer (ou copier) la planning area en référence à la POS, et lui attribuer les Key figures
• /SAPAPO/SDP94 – Créer un planning book/dataview affichant les key figures
• /SAPAPO/TSOBJ – Transporter planning books et Macros