The objective of the application is to extract from WP1 SAP system Bill of Material data and explode BOM level by level with components data.
Then data are consumed by Dynasys application by generated flat file.
Tool Leader: Lei Shen
IT leader of the application: Lei Shen (PP), Craig Wanamaker (BW)
Reporting Coordinator: Lei Shen
Number of users: tbd
Critical period: none
Geographical perimeter: worldwide
InfoArea:
This application is linked to a need of Dynasy Tool. Every month a manually extract is done of BOM Data from ERP SAP system. The goal is to extract these data from SAP to BW and generate automaticaly BOM data level by level 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 |
|---|---|
https://drive.google.com/drive/folders/18VbVRgRTsredyh89a_qSECY7E0yzSKJJ
Dataflow overview :
BOM Number master data (C_BOMNUM) is loaded by the datasource DTS_ZBW_V_MAST_STKO.
The Datasource is based on table MAST (Material to BOM Link) and STKO (BOM Header) from WP1 SAP source system => View ZBW_V_MAST_STKO
In view ZBW_V_MAST_STKO, we keep only entries from STKO with BOM Status (STLST) is not equal to 2 (inactive BOM) and BOM usage (STLAN from MAST) is equal to '1' (Production).
There are 2 fields used to filter data during extraction and loading on BW :
For more explanations, see part Data Loading.
BOM Item master data (C_BOMITM) is loaded by the datasource DTS_ZBW_EXTRACT_BOM_ITEM.
The datasource is based on specific function module ZBW_EXTRACT_BOM_ITEM.
In this function module we call the standard function CSAP_MAT_BOM_ITEM_SELECT to extract each item for a given material/plant.
There are 2 fields used to filter data during extraction and loading on BW :
For more explanations, see part Data Loading.
The most important need of this dataflow is to extract (and explode) all BOM items and components for a given product.
A specific BW extractor has been developed to build the Bill of Material from SAP WP1 source system : DTS_ZBW_MAST_BOM_LEVEL.
There are 2 fields used to filter data during extraction and loading on BW :
For more explanations, see part Data Loading.
The extractor is based on view ZBW_V_MAST and in particular from MAST table to keep all Bill of material to explode and the class ZDTS_ZBW_MAST_BOM_LEVEL is used to extand the datasource adding new fields.
In view ZBW_V_MAST, we keep only entries from STKO with BOM Usage (STLTY) = M (Material) and BOM Status (STLST) is not equal to 2 (inactive BOM).
In the class, we use the standard function module 'CS_BOM_EXPL_MAT_V2' to build the Bill of material and BOM level. The function module is used as recursive function, as long as BOM exists and have to be explode. We filter records from MAST to have only data with BOM usage (STLAN) is equal to '1' (Production).
Today we only explode BOM at level 1 (Master material and its components at first level).
The equivalent to explode BOM level by level on SAP side is T-CODE CS11.
See below, main fields determined or calculated in the class :
BOM quantities and component quantities are converted in KG between propagation and business layer.
Moreover, quantities are recalculated in order to have a BOM Base quantity equal to 1 KG, Component quantities are updated accordingly.
There are 3 fields stored in BOM Propagation and Business ADSO with a system extension :
For more explanations see : BW OTC - Supply Chain- DPS (WBP)
BOM data are used by Dynasys tool (consumed by generated flat file).
ADSO ABDPDY50 is loaded by composite provider CPPPBO01.
Dynasys flat file is generated by reading ABDPDY50 data.
Detail of process chain, list + link between or special event done for the loading
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
| 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 |
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
Extract BOM data from PF1 SAP source system.