Technical Architecture on Applying Customized Logic on SAP BPC (7.5 & 10)

[Former Member]

Scenario:

The user who is authorized to plan material price unvaryingly for all the materials enters plan data irrespective of the companies. While the user submits the data, the BPC Application (BW Cube) is updated based on master data (members) of “Material” dimension and the materials with respective price for the appropriate month/year entered in the planning screen.

The data is updated in the application only for the company codes maintained for specific materials in the ‘Material Dimension’ (P_MATERIAL) and the master data of ‘Material’ is designed accordingly.

Technical Flow

The overall technical process flow involved in updating a Planning application is depicted below:

Design of Material Dimension

The below snap shot reflects the design of “Material” dimension and the main attributes considered are: ID, ENTITY & MATERIAL

Master Data:

In this scenario, Entity and Material Number are maintained separately and used to create ID for each material (Compounding of Entity & Material No). The user authorized to plan for pricing the materials could see all the materials and plan accordingly. But when he/she submits planned data, the BADI implementation logic written on UJR_WRITE_BACK gets triggered and the Planning application is updated with Material with its corresponding Entity (Transaction Data).

In the above shown scenario, Natural Gas will be updated for the companies (Entitiy) 1002, 1003, 1004 and 1005 & Nitrogen is updated for 1002, 1003, 1004, 1005, 1006 and 1008.