PERPRODLOCLOCFR POC creation issue

[former_member653425]

Dear All,

We are facing a typical issue on POC creation

We have a KF1@PERPRODLOCLOCFR which is copied from COPY/DISAGG operator from KF2@PERPRODLOC.

The issue is with the generation of POC at PERPRODLOCLOCFR since we do not have any other stored KF at this level.

We have decided to create a DUMMY KF i.e DUMMY@PERPRODLOCLOCFR and Load all POC combination for PROD , LOC and LOCFR. through the manual load. but this not a permanent solution for newly created MDTs

Do we have any other methods to generate the POC?

Br,

Sandeep

[lingaiahvanam · Accepted solution]

Hi,

You can create another key figure and KF3@PERPRODLOCLOCFR as stored and run the COPY/DISAGG operator copy from KF1@PERPRODLOCLOCFR to KF3@PERPRODLOCLOCFR key figure. Once again run copy operator from KF3@PERPRODLOCLOCFR to KF2@PERPRODLOC to store the data.

Make sure that the following conditions to reviewed during disaggregation operator copy functions.

https://help.sap.com/viewer/bf99e931b8d44aafb4e306ec3602cbdd/2002/en-US/b2fdf555fe5e7b43e10000000a44...

KF1 is a stored key figure with base planning level product-customer, and KF2 is a stored key figure with base planning level product-location.

If you define the DISAGG operator to copy and disaggregate the values from KF1 to KF2 at the aggregation level of PRDID, then the DISAGG operator reads the key figures values of KF1 at the aggregation level of product, then disaggregates and writes the values to KF2 at product-location level.

Note

• The source key figure can be calculated or stored, but the target key figure must be stored.
• Disaggregation works even if the source key figure cannot be calculated at the base planning level of the target key figure.
• If the disaggregation operator is used for version key figures, both source and target key figures must be added to the version.

Best Regards,

Lingaiah