General presentation

Objective of the application

You can find documentation on the existing data flow here (solvay link) or here (syesqo link).


The objective of this new composite provider CPPURM04 "BOM explosion with quantities (intermediates)" is to have in a single data flow the BOM and their intermediates..

He's composed by WP1 data (ABPURM02 - BOM explosion (WP1)) and new adso, explained below, for PF1 data (ABPURM04 - BOM explosion "Intermediates" (PF1)).


Dataflow overview

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

For PF1 aDSO ABPURM04, the data come from aDSO APPUPRIC loaded by datasource DTS_CO_PRICE_RM linked to table ZCO_PRICE_RM in PF1 (this table is generated with program ZCO_PRICE_SIMULATION in PF1).


The DTP DTP: APPUPRIC -> ABPURM04 - Delta contain semantic group on LOGSYS, FISCPER, C_PLANT and C_MATNR2.

In transformation TRSF: APPUPRIC -> ABPURM04 some rules are applied:

Start routine: 

End routine:

To resume, the logic is: 1) find the intermediate product on imep data (abcopp01) in function of the finished material / plant in BOM data (ABPURM04).

2) Is in intermediates product / plant are found, add them it in BOM data.

3) search again on IMEP data but not with BOM data, but with intermediates product and plant found previously.



Dependencies with other applications

Dependencies with:


Data loadings

Loading frequency

aDSO ABPURM04 is loaded in process chain PC_COPC_BOM_PF1




Reporting

Query DE_BW_QRY_CPPURM04_0001 "BOM explosion with quantities (Intermediates)" is used by Xtract to build the PCF dashboard.


Filters:

Key figures, rows and free characteristics:

With "PERC" = NODIM("[K_MENGECK] Quantity" / "[K_LOT_FP] Lot Size" * 100)

Raw material quantity = NODIM("[K_MENGECK] Quantity").


Maintenance


Planned Evolution

Finish the calcul of the intermediate product for cases where the plant of the intermediate is not the same as plant from finished material.