1827752 - Planning Object Structure Persistence Changes on SAP HANA

Symptom

In the SCM on SAP HANA system, a different kind of persistence is required for planning object structures (POS) than previously in SCM systems on non SAP HANA databases. In the original design, BW InfoCubes were used for this purpose. With the changes contained in the related notes, DSOs (DataStore objects) are used.
This means that existing POS structures must be migrated before you use Demand Planning, Supply Network Planning, Service Parts Planning, and Supply Network Collaboration in the SCM on HANA scenario. After the migration, newly created planning object structures are also created as DSOs in the Business Warehouse.

Other Terms

POS, Planning Object Structure, Aggregate, HANA, DSO, InfoCube, Migration,
9ADCBAS, 9ADPBAS, 9ASNPBAS, 9ASNPSA, 9ATPVSOB, 9ADFC01, 9AINVM1, 9ASLIM, 9ASLIW, 9ASLIY

Reason and Prerequisites

Prerequisite: your SCM system is installed on a SAP HANA database.

Reasons:

• In the current design, each POS InfoCube has a key figure (9APLOBJ) for storing the planning object GUID for each characteristic value combination (CVC). In a SCM on SAP HANA system, where the POS InfoCubes are migrated to DSOs, this key figure is replaced by a characteristic 9APLOBJC and stored as a data field in the DSO.

           Usage of 9APLOBJ key figure is limited, therefore we switch to a supported usage to store the planning object GUID for characteristic value combinations by using a characteristic InfoObject 9APLOBJC.

• Usage of aggregate InfoCube persistence became obsolete in BW on SAP HANA, because aggregates do not improve performance if the SAP HANA database is used as persistence.

• POS InfoCubes with the current design cannot be converted to In-Memory InfoCubes (SAP HANA Optimized InfoCubes).

Solution

The solution does not result in any functional change in the applications. Planning object structures work as before functionally. However, this is a mandatory post-migration step of SCM on HANA migration which is valid from Support Package 2 of SAP Enhancement Package 2 for SAP SCM 7.0.

1. Install the relevant support package for your application component, as follows:

• For SAP SCM: SAP Enhancement Package 2 for SAP SCM 7.0, version for SAP HANA, SP02

• For SAP SNC: SAP Enhancement Package 2 for SAP SCM 7.0, version for SAP HANA, SP02

2. Execute the POS DSO migration report as described in the attachment of SAP Note 1818080.

Header Data

Released On	10.05.2013 09:32:18
Release Status	Released for Customer
Component	SCM-BAS-POS Planning Object Structure
Other Components	SCM-APO-FCS Demand Planning SCM-APO-SNP Supply Network Planning (SNP) SCM-ICH-IMO Inventory Monitor
Priority	Correction with high priority
Category	Consulting