This application allows 4 kinds of data reporting :
Tool Leader + IT leader of the application: Functionally this application is shared between Indus/RTR/OTC/PtP, but it's overall the owner is PtP. Current Reporting Coordinator is Duarte Costa.
| It's important to note that the PP (Production Planning) and IM (Stocks) applications are very linked since they share data and share the same info-area AREA_MMIC. See "Dependencies" paragraph for more info. |
The tool is used by several types and areas of users :
Used worldwide by hundreds of users.
Only has RCS data.
Created before 2006. No significant changes since on the dataflow.
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M03 | IM Stocks | Menu role |
ZR_RCS_IM_A01 | Stock Analysis - Super User Role | Should no longer be given - Gives user access to query creation on area AREA_MD, AREA_MMIC |
| ZR_RCS_IM_A02 | Stock Analysis - End User Role | Gives user access to queries on area AREA_MD, AREA_MMIC |
| ZR_RCS_IM_A03 | Stock Analysis - Key User Role | Gives user access to queries on area AREA_MD, AREA_MMIC + Access to add/remove items from menu ZR_RCS_CA_M03 |
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
| Company Code | Company of the plant which holds the material |
Reporting documentation drive folder:
https://drive.google.com/drive/folders/1NsKbz-S0FtzMddWjNuOdlbd5QgYWU73d
Exemple of dataflow overview :
Template Application name DataFlow
Detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way
The stocks application is very linked to the PP Production planning --> The PP application also uses the MPR_IC001 cube.
For queries in that cube, the distinction between what goes to PP and what goes to IM is :
| Code | Name | Explanation |
|---|---|---|
| CUB_COPC1 | Material Prices | Contains the monthly individual material prices (Moving Average and Standard). Used for the MAP alert query and broadcasts |
| CUB_IC002 | Material movements | Contains the material movements from ODS_IC002. Used only by the VS (Value Stream) application and may be removed if VS is decommissioned. |
| CUB_IC001 | Material stock | Cube to report the stock levels - Here the key figures are cumulative and use both the material movements + revaluations to get the correct values. |
| MPR_IC001 | Material stock / movement | MPR which combines the material movements, the stock levels and several PP infoproviders - Although it was used in the past for stocks queries, only PP queries should be created on it. Use MPR_IC004 for stock queries related to stock level and material movements. |
| MPR_IC004 | Stock Movements | This replaces the MPR_IC001. MPR_IC001 should only be used for PP queries. |
| DSOENTPR | Enterprise Product (PEP Source Sys) | Used to copy from the BO GBR univers database the Ent Grp and Sub-group material master data |
| DSR_IC01 | Material Movement - APD ( Direct Update ) | ?? - Data loaded from a query via APD - Used for EHS (REACH) - Not part of the stocks application |
| DSR_IC02 | Material Movement - APD - REACH ( Direct Update ) | ?? - Data loaded from a query via APD - Used for EHS (REACH) - Not part of the stocks application |
| 0COPC_O01 | Material Prices | Contains the monthly individual material prices (Moving Average and Standard). ODS for the CUB_COPC1 cube. |
| ODS_IC01 | Material movements | Contains all the material documents - All the inventory movements with historical values |
| DSOPLTPR | Plant Product (PEP Source Sys) | Used to copy from the BO GBR univers database the Operational Asset and Sub-group material master data |
| ODS_IC02 | Revaluations | Contains the revaluation documents - This is used to update the material movement values so that the stocks levels (in CUB_IC001) are correct with the end of month values. |
| DSO_IC07 | Variance in Stock Between BW & RCS | Loads data from the WP1_400 system in order to, when necessary, compare the ERP stock values with the BW stock values. Used only to check for mistakes. Usually after january 1st. |
Appart from the standard master data used in the stocks, there are a few which are important for queries to work properly :
The stock level / stock movements part of the flow follows the D4 frequently loaded data schedule.
The material prices part of the flow is on a daily full update (Note though that the extractor, in full, only provides current, previous and last december periods data)
C_MATPUVT has to be loaded manually on january each year to update the unit price.
if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
All history MUST be kept : the stocks level queries are all using cumulative key figures so it's necessary to keep all documents.
See documentation in the public wiki : IM - Stocks (WBP)
See list of queries in the public wiki documentation :
The most important thing to understand in this application is the different between the infoproviders with cumulative key figures and those without.
The ODS_IC01, ODS_IC02, CUB_IC002 for example are not using cumulative key figures : When you filter on january, you will see the documents posted in january. These are used to report on the activity (movements) on a given period.
The CUB_IC001 uses special cumulative key figures : When you filter on january, you won't get the documents posted in january but a cumulative value of all the documents posted since the beginning up to and including January. This is to report on the stock level at a given date.
The main broadcasts are :
In the past we had sometimes issues on the 1st of January each year due to a few documents not being correctly loaded in the delta.
Note that the stock level cube (CUB_IC001) is VERY sensitive to loading errors : if a document is missing on day D, it will affect ALL the results after day D since all the key figures are cumulative.
As of 25/07/2016 there is no consolidated stock application with all ERPs, but Anon, Kasemvilas is working on adding the PF1 data into a new inventory dataflow.