Objectives

Access Management 

DataFlow

...

Overview 

Image RemovedImage Added

https://drive.google.com/open?id=1BiVUn_ILyg-EXmJm-I7Rgd7OA2k8Q1HMtbI_8Tj9kyc/file/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:lref-gdrive-embedded-file

WP1

Updated dataflow after Solstice update (Rules are unchanged except for the Solstice split)

...

PQ1 flows are kept only for historical data, they are replaced by PF1 flows since 01.2018.

PF1:

NON ERP:

Infoarea & Infoprovider

Technical

...

Rules on Workbench

Integrated Margin for EP & PI

KT file.

Some

...

explanations on P&L

...

Technical Documentation - RTR - Profit and Loss (P&L) + Integrated Margin (IM) (WBP)#IntegratedMargin(IM)wiki page .

Data Update Conditions for DSO_PCP1 from DTS_KEKO_CKIS

Data Source: DTS_KEKO_CKIS
Source System: WP1_400
Data Flow Version: BI 7.0
Transformation: RSDS DTS_KEKO_CKIS WP1_400 -> ODSO DSO_PCP1 (0K1O4SUXOC9DPNTS7R3JSO0DRSOF0BY9)
Start Routine: This start routine is to do 2 main tasks.
1) It is to delete all records where the amount and quantity is equal to zero.

...

Data Update Conditions for DSO_PCP3 from 0CO_PC_PCP_02

Data Source: 0CO_PC_PCP_02

Source System: WP1_400

Data Flow Version: BI 7.0

Transformation: RSDS 0CO_PC_PCP_02 WP1_400 -> ODSO DSO_PCP3 (0CY1UWMKPVWXUI74VIAPF3V2S12PIYQ1)

Start Routine: This start routine is to do 2 main tasks.

...

Data Update Conditions for DSO_PCP2 from 6DB_GL_COST_PURCHASE

Data Source: 6DB_GL_COST_PURCHASE

Source System: DW2

Data Flow Version: BI 7.0
Transformation: RSDS 6DB_GL_COST_PURCHASE DW2 -> ODSO DSO_PCP2 (07G0MUNSUYM2GSSZ09F9Q6CC9OF3LCOZ)
There are 3 individual rountines in this transformation to divide the following key figure values that are of currencies Korean Won (KRW) and Japanese Yen (JPY) by 100.

...

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.

...

Read more information in :
https://drive.google.com/open?id=0BwtAGBKWM-z-cWdzQ0QyTTFpRHM 

Data Loading

Info Providers and objects loaded 

...

DSO_PCP2

DSO_PCP1 / ODS_PCP1

...

PC_CO_PC_MM_04 (CPX)

...

Update with project 8612 - Solstice (CPX)

BW - CO - Integrated Margin

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.

To do that, we have three steps:

1 - Transfert source data from WBP to CPX.

2 - Calculation of IM in CPX side with data from WBP and WPX.

3 - Transfert the result of IM in CPX to WBP and take it into account in the calculation of IM in WBP.

CPX data flow

DSO correspondance WBP - CPX :

...

ODS_MARM

Details:

To put in place these three steps we had to split the chain RSP_COPCP_MONTHLY in two chains:

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://docs.google.com/document/d/1QbjsKm0qxUuWNk2E7gntCDq1NIirYi8huKzaSJRp9zU/edit#

1 - transfert from WBP to CPX:

We use datasource from WBP dso to load data in CPX side.

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:

The principle is similar to what we done in WBP. We load data from WPX and WPB in ABDSOPCP1 and after we execute program ZBW_M_INT to calculate the Integrated Margin. All is done in meta chain PC_CO_PC_MM_04 (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:

After the calcultion of IM in CPX, a webmethods will sent a flat file with results (/exploit/BW/Integrated_Margin/OH_COMM01.CSV) in WBP and execute the chain PC_INT_MARGIN to load dso DSO ABDSOPCP1 with data from CPX, and after load this in ODS_PCP1 and do the calculation of IM.

If an error occurs in CPX system or with WebMethods, there is a process chain PC_INT_MARGIN_TEST (Integrated Margin - test if Integrated Margin 2 is scheduled) which runs every D+3 at 1 a.m. to check if PC_INT_MARGIN is running or not:

If not, we can suppose there was a problem and we force the execution of process chain PC_INT_MARGIN.

Image Removed

If yes, there is no problem, it's not necessary to force the execution of PC_INT_MARGIN.

Image Removed

The calculation of IM has same principle than before, there are two things that change with CPX data.

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.

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).

Simple/Integrated/Market Margin

  The Simple Margin  is the margin done between each transaction.
o Ex : Simple Margin from A to B = 10. Simple Margin from B to End Customer = 10.

  The Integrated Margin  is the cumulated margin from the beginning of the chain.
o Ex : Integrated Margin at A = 10 (same as simple margin since nothing before that)

Integrated Margin at B = 20 because it “integrates” the margins done before.

The idea of integrated margin is to give you, when we sell goods to a customer an idea of the overall margin done at  Solvay level, not only the vision at the last entity.
(For example you could have a negative margin between B and end customer, but a large margin between A and B so  the group is still getting a good margin).

Unfortunately it’s not possible in the system to simply cumulate the simple margins, so instead the BO system  recalculates all the cumulated costs and based on that recalculates the integrated margins :

Basically : Integrated Margin at B = (Sales B to EndCust) – B Costs – A Costs

The “Market Margin” is specifically used for the cases of sales between EP and PI GBU  inside a legal entity.

Both GBU want to be able to distinguish their own margins, but the normal system doesn’t allow them to do this  because usually there is no invoice between them : EP and PI are in the same entity and sometimes even the  same plant, so they cannot create invoices.

To solve this BO has a system where EP/PI can upload a “Market Price” agreed between them. The “Market Margin”  will therefore be recalculated taking this “Market Price” when there is a transfer of goods between EP and PI.

Update with project 8612 - Solstice (CPX)

BW - CO - Integrated Margin

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.

To do that, we have three steps:

1 - Transfert source data from WBP to CPX.

2 - Calculation of IM in CPX side with data from WBP and WPX.

3 - Transfert the result of IM in CPX to WBP and take it into account in the calculation of IM in WBP.

CPX data flow

DSO correspondance WBP - CPX :

Details:

To put in place these three steps we had to split the chain RSP_COPCP_MONTHLY in two chains:

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://drive.google.com/file/d/1aI-ptjt44Whj_oJYnwz-AYQBHUuiOUIi_GOV0dhOvDU/view#

1 - transfert from WBP to CPX:

We use datasource from WBP dso to load data in CPX side.

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:

The principle is similar to what we done in WBP. We load data from WPX and WPB in ABDSOPCP1 and after we execute program ZBW_M_INT to calculate the Integrated Margin. All is done in meta chain  PC_CO_PC_MM_04 (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:

After the calcultion of IM in CPX, a webmethods will sent a flat file with results (/exploit/BW/Integrated_Margin/OH_COMM01.CSV) in WBP and execute the chain PC_INT_MARGIN to load dso DSO ABDSOPCP1 with data from CPX, and after load this in ODS_PCP1 and do the calculation of IM.

If an error occurs in CPX system or with WebMethods, there is a process chain PC_INT_MARGIN_TEST (Integrated Margin - test if Integrated Margin 2 is scheduled) which runs every D+3 at 1 a.m. to check if PC_INT_MARGIN is running or not:

If not, we can suppose there was a problem and we force the execution of process chain PC_INT_MARGIN.

Image Added

If yes, there is no problem, it's not necessary to force the execution of PC_INT_MARGIN.

Image Added

The calculation of IM has same principle than before, there are two things that change with CPX data.

• 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).

Image Added

Reporting

Technical Documentation - RTR - Profit and Loss (P&L) + Integrated Margin (IM) (WBP)

Dependencies with other applications

Data Loading

Info Providers and objects loaded 

 Image Removed