The objective of the application is to extract from SAP Vault source system Bill of Material data and explode BOM level by level with components data.
Then these data are used for the application BW - DPS - Forecast Vs Booking / Component.
Tool Leader: Lei Shen
IT leader of the application: Lei Shen (PP), Craig Wanamaker (BW)
Name of project: Solstice
PMO Project: 8612 Solstice AERO
Reporting Coordinator: Lei Shen
Number of users: tbd
Critical period: none
Geographical perimeter: worldwide
InfoArea:
This application is linked to the Solstice global project and this specific need was named "DEV47- Other MiniBW request for planning team".
MiniBW (CPX) dedicated platform was created for Aero Requirements about Solstice project.
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/1Y2OmoBqD6VWwpmUPnuiQ6ZFm0hwlPruA
Sheet "Dim_BOM" :
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 SAP Vault source system.
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.
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 Vault source system : DTS_ZBW_MAST_BOM_LEVEL.
The extractor is based on 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 the class, we are using 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.
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 :
Taking the following example for the material 157473 :
Line in yellow is the header line of BOM Head 157473. Product Level = 1 because BOM Head = Product = 157473.
In blue, there are all components of BOM Head 157473, we increment BOM Level and Product Level.
In pink, the previous component 157193 of BOM head 157473 become the BOM Head, we incremente the Product Level.
In brown, it's the header line of BOM Head 157193, BOM Level =1. Others lines corresponds to components of BOM Head 157193, BOM Level = 2.
RSA3 on extractor DTS_ZBW_MAST_BOM_LEVEL for the same example : 157473
BOM data are used in application BW - DPS - Forecast Vs Booking / Component.
There are 2 process chain :
They are part of process chain PC_PP_04 :
PC_PP_04 is part of global RSP_DAILY :
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.
There is a query BW_QRY_CPPPBO01_0001 (BOM Data Reporting) based on composite provider CPPPBO01 (BOM Item Data - Virtual).
This query was used for testing data coming from SAP Vault source system but it is not used and accessible by key users.
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
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