Provide "Make or Buy" information in the SpP Raw Material process to deliver a Manufacturing adjusted cost.
This information is provided by Finance or Controlling and based on several calculations on their side, and therefore not available in SAP.
The indicator "Usage factor" must be manually populated by the Business at Material Group / Finished Product / Raw Material / Plant level for the 4 rolling quarters to come.
Tool Leader + IT leader of the application: Name of project or main leader for the application + reporting coodinator
How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site
Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information
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_M78 | Forward Looking ICM - Raw Material | Role Menu |
| ZBI_RCS_CO_A06 | Forward Looking ICM - Raw Material | Authorization objects |
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
| V_CPFCTR1_2_0006 | CPFCTR1_2 |
| V_C_PLANT_0012 | C_PLANT |
| V_C_AUTHMA_0001 | C_PLANT__C_AUTHMA |
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
The Critical Raw Material Master Data C_FLRMAT is used to identify the “Make or Buy” Products.
The source of this information is located in PF1 system for SpP, where the table ZFI_ICM_CRITIC is populated by Business through transaction ZCRIT.
The field “Critical flag” (C_FLRMATF) is used to identify “Make or Buy” Products as follows:
“I” : Critical Internal
“E” : Critical External
The BW data flow logic is based on an intermediate buffer ADSO, allowing the save of the previously input value from Business, and the update from the latest data coming from DTS_CV_FMCO_MORB_SPP
The chronology is the following
The Planning ADSO is then source of the Manufacturing data flow, where the quantity from the BOM will be replaced by the usage factor from the workbook and multiplied by the price in the Raw Material Forecast calculation.
Therefore, the Raw Material Forecast price must have been confirmed before the "Make or Buy" process.
The datasource is based on calculation view CV_FMCO_MORB_SPP
First step - join between C_FLRMAT (filter flag 'I' or 'E') with ABCOPRIC (BOM DSO for SPP) based on the Raw Material (BOM component) to get finished product (C_MATNR2)
Then a join with C_MATNR2 master data to get Material Group
Workbook layout
ALCOPC16 FL - Raw Mat Make or Buy - MG
The Aggregation Level is encapsulating the Composite Provider, with the exact same output structure.
All characteristics and key figures of the ADSO are selected to guarantee the Planning functionalities in the query/workbook.
CPCOPC14 FL - Raw Mat Make or Buy - MG
The Composite Provider is encapsulating the Planning ADSO, with the exact same output structure.
The navigational attribute C_PLANT__C_AUTHMA is added to handle authorizations on Scope in the query.
Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...
PC_COPC_15 - COPC: TD - D - RMAT Make or Buy (Mat Group)
Detail of frequency : monthly; weekly or else
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
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