DataFlow

Overview

Image Added

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

Technical Rules on Workbench

• Material Movement (ABMMIM03*)

  Provider used for presenting the informations at material document level, could be used by operational reports showing the movements details for a specific period.

  AMDP

  • Controlling Area - If the controlling area is null, get the data from the corresponding attribute of "company code" (c_compcde);
  • Sub-activity 2 - Get the data from the attribute of technical object "Material plant 3" (c_matpnt3);
  • Sub-activity - Get the data from the attribute of technical object "Material plant 3" (c_matpnt3);
  • GBU - Get the data from the attribute of "Sub-activity 2" (c_subact2);
  • Country (GBU Zone) - Get the data from the attribute of "Customer ID" (c_custid);
  • Material conversion - If the corresponding material and unit of measure is not convertible into 'KG' according to the DSO UOMCMAT2, the object is flagged.

  
  

  ABAP ME: ZCL_IMMM_BUSN=>ME_ABIMMM03

  • Valuation type - Treat invalid char;
  • Customer / GBU Zone - Empty if the stocktype not is 'K', 'L', 'M', 'N' or 'O';
  • Vendor - Empty if the stocktype not is 'Q', 'R' or 'S' or stock category is not 'K' or 'Q';
  • Consignation quantity stock (issued) - Stock relevant = 1, transaction key = '100', '101', '104', '105', '106' or '110', application = 'MM', stock category = 'K' or stock category = '' and stock type contain 'LEK';
  • Quantity stock (issued) - Stock relevant = 1, application = 'MM' and transaction key = '100', '101', '104', '105', '106' or '110';
  • Consignation quantity stock (received) - Stock relevant = 1, transaction key = '000', '001', '004', '005', '006' or '010', application = 'MM', stock category = 'K' or stock category = '' and stock type contain 'LEK';
  • Quantity stock (received) - Stock relevant = 1, application = 'MM' and transaction key = '000', '001', '004', '005', '006' or '010';

  Price control (AAMMIM02*)

  Acquisition layer presenting all the prices variation according to the tables MBEWH and MBEW and their respective change date.

  ABAP

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

  AMDP

  • The main purpose of this process is to keep only the Plant, material and valuation type that suffer some change in the unit price between the date coming from load and the previous date available for the same key.
  • The process is able to identify changes at price control, price per unit and/or amount.

  Material stock non cumulative (ABMMIM02*)

  Non cumulative provider to present the stock evolution at quantity and value information.

  AMDP

  • Amount Valuated Stock (inbound / outbound) - Unit price from APMMIM02* based on the same position from posting date multiplied by the quantity according to each material, plant and valuation type. The revaluation is done during the loads from APMMIM02* > ABMMIM02*, considering the difference from the position of the new unit price minus the unit price applied during the previous load from ABMMIM03* > ABMMIM02*.
    • The reference date of previous unit price revaluation is stored in the object Price date (0price_date)

  Material stock - Initialization (ABMMIM01*)

  Provider used to create the balance from the initial stock according to the quantities available in the non cumulative, the process creates a record with the difference of quantities into the first posting date available according to the key in the provider ABMMIM02*.

  AMDP

  • Complement the master data exactly like the treatments done in the provider ABMMIM03* for the objects controlling area, sub-activity, sub-activity 2 and others;
  • It's stored in the provider all those data that is not available in the provider ABMMIM02* or those the quantities doesn't match between the providers.

Reporting

Main queries

Main functionalities

Main key figures

SAP Analytics Cloud Documentation

 SAC IM

2.0 DataFlow

2.1 Overview

Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

2.2 Technical Rules on Workbench

Explanation for the process on the technical side. Can be specific cases or general rules depending on the scope.

Dependencies with other applications

We should have the information where the application is sending or receiving information (e.g. APD open hub) 

Data Loading

Info Providers and objects loaded 

Detail of process chain, list + link between or special event done for the loading

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

Image 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 because it should be performed as a sequential process, due to the balance process based on the pointer from datasource 2lis_03_bx

Image Added

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* with the option for initialization.

Loading frequency

     The stock level (movements and revaluation) are available by update in the process chain PC_MMIM_00 and it is part of the flow follows the D4 frequently loaded data schedule. (it is under PC RCP_MMIC)

     There are 2 main process chains that load the stock cubes, which are

1. Normal time on PC RCP_MMIC - 03a IC Complete Transactional  (3 times / day)
2. Extra time on PC    FI_IC_DELTA_EXTR_HOURLY  - 03b IC Minimun Transactional (additional 3 time / day

Price Control Data load procedure during Financial Closing period:

     Data loads to DSO Price Control (AAMMIM02* - Solvay & Rhodia ) in propagation layer are paused during D1 to D7.

     Process chains PC_MMIM_01 & PC_MMIM_02 are having condition to check D1 to D7 and skip the Info package loads from SAP systems.

     From D7 onwards, Info packages are resumed with regular info package load activity.

Data Quality Control

     If we find any discrepancy with the data in ABMMIM02R/ABMMIM02S, please check for the latest Material unit price in Propagation layer DSO AAMMIM02* - Solvay & Rhodia.

     Perform full data deletion and reload for Plant & Material combination from Propagation layer to Business Transfer layer ABMMIM02R/ABMMIM02S. This activity to be performed after    D7 or Financial closing is completed.

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 criticality, workarounds and resolution plan.>

Roadmap

This multi-provider will be used for the next evolution to combine Rhodia legacy to combine in order to have both legacy in the same report and definition.