...

All aDSO above the acquisition layer (basically a provider with the same fileds from datasource) uses an infosource in the link to become easier the implementation of different type of code: AMDP (recommend for look up at db level) and ABAP (better in treatments at row level).

The integrated price has a flow similar to standard price (APMMIM01*) using a cross look up information with material movements available. The flow has as origin the data from the tables in model S, that are aggregated by plant, material, batch e period before the creation of the revaluation process. 

Image Added

Functional and Technical rules on Workbench + Reporting

...

• Valuation type - Treat invalid char;
• Calendar day - Convert the timestamp into date, if timestamp is null, concatenate the information from year, month and day 01. If the date keeps initial, the entire record is removed from flow;
• Price variation - If the total value is not initial (not valuated stock), check the price condition (S - Standard or V - Average) to assign the corresponding value.
• The record is only stored by the delta process if the date is bigger than the last one stored for the same key (material, plant and valuation type). This avoid the check done by the post process done in the propagation layer, when the process checks the variance of price between days.

Material movements - Price (APMMIM02* / APMMIM04*)

Propagation layer used to present the difference of unit price among the calendar days. 

...

CPIMMM01 has 3 main datasource loading and all the process is available in the process chain PC_MMIM_00.

Image RemovedImage Added

1. 2LIS_03_BF movement document. Load movement stock data coming from the classical DSOs Rhodia (ODS_IC01) and Solvay (DPMMIC03) 
2. DTS_MBEW_0001 - price definition according to the material, plant and valuation type
3. DTS_CO_PC_ACT_5_H - historical price according to the end of month position.
4. Model S tables provide data for integration (finance) price.

The INIT process is quite different The INIT process is quite different because it should be performed as a sequential process, due to the balance process based on the pointer from datasource 2lis_03_bx

...

1. ODS_IC01 → ABIMMM03R / DPMMIC03 → ABIMMM03S - Load and activate. Preferably filtering in several full loads split by CALYEAR due to the amount of data during the activation.
2. Run IP for DTS_CO_PC_ACT_5_H, DTS_MBEW_001 and 2LIS_03_BF (requires setup table)
3. DTS_CO_PC_ACT_5_H → AAMMIM02R / AAMMIM02S - Load data
4. DTS_MBEW_001 →  AAMMIM02R / AAMMIM02S - Load data from delta (Avg. price), full last requisition (Std. Price) and activate data.
5. AAMMIM02R → APMMIM01R / AAMMIM02S → APMMIM01S - Load data and activate data.
6. ABCOMS01 / ABCOMS04 → APMMIM05R - Load data and activate data.
7. ABCOMS02 / ABCOMS03 → APMMIM05S - Load data and activate data.
8. APMMIM05R → APMMIM04R - Load data and activate data.
9. APMMIM05S → APMMIM04S - Load data and activate data.
10. ABIMMM03R → ABMMIM02R / ABMMIM02S → ABMMIM02S - Load and activate. Preferably filtering in several full loads split by CALYEAR due to the amount of data during the activation.
11. AAMMIM01R → ABMMIM01R / AAMMIM01S → ABMMIM01S - Load data, do not need to activate.
12. ABMMIM01R → ABMMIM02R / ABMMIM01S → ABMMIM02S - Load and activate.
13. APMMIM01R → ABMMIM02R / APMMIM01S → ABMMIM02S - Load and activate. Preferably filtering in several full loads split by CALMONTH due to the amount of data during the activation.
14. APMMIM04R → ABMMIM02R / APMMIM04S → ABMMIM02S - Load and activate. Preferably filtering in several full loads split by CALMONTH due to the amount of data during the activation.
15. Run delta DTP from APMMIM01* and ABIMMM03* Run delta DTP from APMMIM01* and ABIMMM03* with the option for initialization.

...

Main functionalities

...

Main functionalities

Main key figures

SAP Analytics Cloud Documentation

 SAC IM

Broadcast

N/a

Maintenance

N/a

...