Best Practices for Managing Master Data Across Scenarios in SAP PaPM (Pillar 2 Use Case)

[kastolia]

Hi Community,

We are currently working on a Pillar 2 implementation in SAP PaPM and have encountered a challenge regarding the handling of subsidiary master data across multiple process instances (scenarios).

Our requirement is the following:

• The list of subsidiaries should be maintained in a central master table (editable only by authorized users).

• When a new process instance is created, this master list should be automatically loaded into the instance-specific input table.

• The user should be able to make changes to the data (e.g., modify validity, add/remove companies) within their scenario, without impacting the master list or other scenarios.

• Each new scenario must always start from the original master list, regardless of changes made in other instances.

We would like to hear how others have handled this - especially:

• How do you technically ensure that each new scenario fetches the master data without affecting or being affected by previous ones?

• How do you structure your tables and functions to prevent overwriting or duplication?

• Any lessons learned or pitfalls to avoid?

Looking forward to your thoughts and experiences!

#sappapm 

[ZYT]

Hi @kastolia ,

  I believe the requirements you described can be effectively addressed through a well-structured data flow and the strategic use of a writer of library type. Here’s a streamlined approach you could consider:

1. Establish a central master table in a controlled environment, ensuring edit access is restricted to authorized users only. This safeguards data integrity at the source.
2. Develop a custom library in SAP HANA Cloud Explorer that handles the logic to replicate or transform the master data to meet the structure and business rules of your input table.
3. Configure a writer of library type within the PaPM Universal Model to integrate this library and enable seamless interaction with the target data structures.
4. Define a dedicated activity in your process to execute the writer, ensuring automated, reliable data replication within your operational workflow.

  I hope this provides clarity. If you need further details, please feel free to reach out. We’re also planning to release a sample content in UM in this year to demonstrate this approach in action.

Thanks and best regards,

[Sotiris_X]

Hey @ZYT

Could you please clarify whether the solution you outlined regarding the use of SAP HANA Cloud Explorer and the writer of library type is applicable to an on-premise setup of SAP PaPM? If it is not applicable, could you suggest an alternative solution for achieving similar outcomes in the on-premise version?

Thank you.

[ZYT]

Hi @Sotiris_X, for PaPM on-premise/ PCE you may consider to use RFA of HANA external procedure type. You may refer to Thomas' blog for more details: https://community.sap.com/t5/financial-management-blog-posts-by-sap/papm-how-to-embed-an-sap-hana-st...