The objective of the application is to extract from WP1 SAP systems Recipe data. The goal is to have the link between the production version (Plant@Material) and the activities by product line.
The data are extracted from MAPL, PLKO, PLPO, CRHD tables.
Then data are consumed by Dynasys application by generated flat file.
There is no query developped for the reporting.
Number of users: tbd
Critical period: none
Geographical perimeter: worldwide
InfoArea:
This application is linked to a need of Dynasy Tool. Every week a manual extraction is done of Master recipe Data from WP1 SAP system. The goal is to extract these data from SAP to BW and generate automaticaly Master Recipe data by flat file and send this file to Dynasys for import.
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
Reporting documentation drive folder:
https://drive.google.com/drive/folders/18VbVRgRTsredyh89a_qSECY7E0yzSKJJ
Dataflow overview :
https://docs.google.com/presentation/d/1L7nBbAchsWPnGthA0j1ks0Jl8utmKoh0uwDeUtNJKAc/edit#slide=id.p1
ADSO APPPRE01 is loaded by the datasource DTS_ZBW_V_MAPL. This datasource used the view ZBW_V_MAPL on WP1 for the data extraction (Join of MAPL/PLKO and PLAS table).
The mapping between the ADSO and the datasource is direct.
In this ADSO we'll have the link between the Production Version (At Material@Plant level) and the different recipe (0PLNNR, Key for Task list group).
For each recipe we'll have a Base Quantity of produced Material and associated Base Unit of Measure.
There are 2 fields used to filter data during extraction and loading on BW :
ADSO APPPRE02 is loaded by the datasource DTS_PM_TASK_LIST_OPER_ATTR This datasource used the table PLPO on WP1 for the data extraction.
The mapping between the ADSO and the datasource is direct.
In this ADSO we'll have the list of operations (activities) and their duration for each recipe.
There are 2 fields used to filter data during extraction and loading on BW :
There is also the ADSO ABPPRE01 loaded in delta mode from the previous APPPRE02 (mapping direct).
This one is used for the Dynasys interface (projection of this ADSO is used in a Calculation View).
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 master data C_WKCTRID contains the link between the Object ID of the ressource associated to an operation and the work center.
It is loaded by the datasource DTS_ZBW_V_CRHD from WP1 SAP system. This datasource is based on the view CRHD_V1.
An operation is associated to a Control Key and for the the Dynasys need we are using a filter on to keep only the Control Key flagged as scheduled.
The information is loaded and stored in the master data C_STEUS (Control Key) from the datasource DTS_ZBW_T430.
This datasource is based on the table T430 (Control Key attributes)
The Dynasys calculation view CV_DY_RECIPE_DATA uses projections of data based on following object of Recipe Application :
The result of the calculation view is loaded in ADSO APDPDY10 & ABDPDY59.
Recipe data are consumed by Dynasys tool using the generated flat file DYS_BW_RECIPE.csv from the ADSO ABDPDY59.
Both propagation layer ADSO APPPRE01 & APPPRE02 are loaded by 2 FULL DTPs.
The fisrt one is based on creation date and the second on modification date of the record in respective source table.
We load for each of them from current date to current date - 7.
Note that DTP are different for each objects.
Recipe Master Data are loaded by process chain PC_PP_RE_01.
ADSO are loaded by following process chain :
A global Master process chain load all the Recipe application : PC_PP_RE_04
This master chain is part of a global chain with BOM application : PC_RE_01
Today the process chain PC_RE_01 is scheduled at 00:30 (CET).
Daily loading
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
See below init data loading (full without filters) performed end of June 2021 :
| ADSO | Nb records | Time |
|---|---|---|
| APPPRE01 | 942.546 | 18m 9s |
| APPPRE02 | 1.356.968 | 6m 46s |
Record Keeping
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
List the most important and complex queries only with a link to the documentation
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Today we have only data from WP1 SAP system, PF1 is planned to be added but rules will be different.
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016