...
| Panel | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
List of application role + menu role and explanation if we have several applications role with specials rules.
|
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
DataFlow
...
Overview
https://drive.google.com/open?id=1BiVUn_ILyg-EXmJm-I7Rgd7OA2k8Q1HMtbI_8Tj9kycfile/d/1De8PXqJ4-roA9qB8_j20Rh6Gmyjvro4PRcE3uVRukXs/view
MVCOPA01 (WBP)
For multiprovider MVCOPA01, not all cubes aossciated associated are used for integrated margin report.
Only the providers vith with IM in red are concerned:
WP1
Updated dataflow after Solstice update (Rules are unchanged except for the Solstice split)
...
Infoprovider Name | Infoprovider Techname | Source System | Source Infoprovider Name | Source Inforprovider Techname |
|---|---|---|---|---|
CCR: Integrated margin | ODS_PCP4 | WBP_400 | CCR: Integrated margin first-calculation (Direct Update) | ODS_PCP6 |
CCR: Integrated margin first-calculation (Direct Update) | ODS_PCP6 | WBP_400 | Updated by ABAP Program | 1) Z_M_INT |
CCR: Product Cost Items (Market Margin) | DSO_PCP1 | WP1_400 | Cost components | DTS_KEKO_CKIS |
CCR: Released Costs Estimates (Market Margin) | DSO_PCP3 | WP1_400 | Product Cost Planning: Released Calculations | 0CO_PC_PCP_02 |
Purchase Price (Market Margin) | DSO_PCP2 | DW2 | Database: DW2 Table: GL_COST_PURCHASE | 6DB_GL_COST_PURCHASE |
Some e xplanations on P&L wiki page .
...
Here is an exemple of file to upload: https://drive.google.com/drive/folders/1UAeGGSXjEh1f4QlDOM0kU16m_5qfI96dnwvtjMl0l6yXPGJI4uHdwKa0C7BtfTpq
The transformation into ODS_PCP4 is similar to the one from ODS_PCP6: it is direct mapping except the conversion of the lot size in Kilogram.
...
In scope of project 8612 - Soltice we put in place a link between WBP and CPX system to take into account the vault data in calculation of Integrated Margin.
...
RSP_COPCP_MONTHLY to load the source of data and PC_INT_MARGIN to retreive result of IM from CPX (in dso ABDSOPCP1) and calcul the IM in WBP side.
...
More details about the split here:
https://docsdrive.google.com/documentfile/d/1QbjsKm0qxUuWNk2E7gntCDq1NIirYi8huKzaSJRp9zU/edit#1aI-ptjt44Whj_oJYnwz-AYQBHUuiOUIi_GOV0dhOvDU/view#
1 - transfert from WBP to CPX:
...
At the end of process chain RSP_COPCP_MONTHLY there is a process "Remote process chain" to launch process chain PC_CO_PC_MM_04 in CPX.
2 - calculation of IM in CPX:
...
ZBW_M_INT in CPX is a copy Z_M_INT in WBP, so if there is a change in Z_M_INT it may be helpful to make the same change in ZBW_M_INT.
3 - Transfert the result of IM in CPX to WBP and take it into account in the calculation of IM in WBP:
...
Webmethods load data from CPX with a flat file and this flat file is loaded in DSO AADSOPCP1 → APDSOPCP1 → ABDSOPCP1 and ABDSOPCP2 for historical save.
Data from DSO ABDSOPCP1 are loaded in ODS_PCP1, like that we have the source from WBP (WP1) and CPX (WPX) to calculate the IM.
Embedded Google Drive File docid 1Y7FttO49cNfmRlNunysT46CaQpjm0JioYl8E7ymcWLU Between DSO APDSOPCP1 and ABDSOPCP1 we transpose the data to adapt the source to the next target (ODS_PCP1). Some values of ABDSOPCP1 are defined in master dat global filter (C_GLBFILT) on stream "DSO_PCP1"
In program Z_M_INT we calcul the Integrated Duty and the Integrated Freight with data from CPX (assigned in cost component 400 and 500 in loading of DSO ABDSOPCP1) (this calculation is not done in CPX side with prorgam ZBW_M_INT).
...
Data Quality Control
Data come from SAP system. To compare data between BW and sources systems, check propagation layers.
Operational Documentation
Procedures
<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>
Scheduling
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
Monitoring
<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>
Error Handling
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
Known Bugs
<List the existing bugs, its criticity, workarounds and resolution plan.>
Roadmap
<List past & future evolutions for the application (including links to MED/FSD/TSD)>