Functional Specification Document:
Describe in a few words the content of application + link with functional or technical specifications (google links) done with during the project or linked with PPMO
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_M69 | MS - Model S | Role for queries and workbook |
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
| C_COMPCDE__C_AUTHMA | Query authorization object |
| CPFCTR1_2 | Query authorization object |
| C_COMPCDE__C_MNGAREA | Query authorization object |
| C_COMPPRS | Query authorization object |
The principal thing to know here it's about the way to extract the data.
The goal is to extract and stock in APCOMS01 "Quantity Total Stock" 0TOTALSTCK from ABMMIC01. Info object 0TOTALSTCK is not physically stored in invenotry DSO. The only way to extract the key figure is to use a query as datasource (BW_QRY_ABMMIC01_0001).
In query BW_QRY_ABMMIC01_0001 we used a variable "V_CALMONTH11" based on class ZCL_BIU001_V_0CALMONTH_0031.
The class determine the month to load from current date and more or less x month(s). To know the number of months to add or removre from current date, the class read master data global filter (C_GLBFILT) on stream "STOCK_LOG":
Normally, by default the month to load in ADSO APCOMS01 is current month - 1. To load other month it's necessary to change fields "low" and / or "hight" in master data.
It's in ADSO APCOMS01 where we define by default C_SOURCE = LOGISTIC. We will use this field in filters to extract data from caclulation views to separate LOGISTIC data and WORKING CAPITAL (equal TRANSIT) data.
Load ADSO ABCOMS01 and calculate key figuress for Model S.
Last step is to caculate all key figures for Model S report, It's done in transformation TRSF: APCOMS04 -> ADSO ABCOMS01.
In start routine, we delete some lines according to their company code or plant. Company code and plant to exclude are defined in master data global filter (C_GLBFILT) in stream "MODEL S" and rule "PLANT" or "COMPCDE":
During the loading, the transformation will convert the unit and currencies key figures with help of conversion type UOM_MATNR2 (units) and CTK_MODELS (currencies).
In end routine, we use key figures previously converted to create new ones:
Mains data sources:
Logistic data: ADSO ABMMIC01 - "Material stock".
Transit data: DBFIGL13 - "IM from FIGL: Line Items for G/L Acct (S) - Rhodia Level 2".
Integrated Margin data: ODS_PCP4 - "CCR: Integrated margin".
| Process Chain - Technical Name | Process Chain - Description | Starter | Comment |
|---|---|---|---|
| PC_CO_MS_0006 | MS: TD - M - Model S - Global | Event: Z_EVT_PC_CO_MS_0006 triggered in process chain PC_INT_MARGIN | |
| PC_CO_MS_0003 | MS: TD - M - Model S Propagation APCOMS01 | External start only (via API or metachain) | Sub Chain of PC_CO_MS_0006. Load ADSO APCOMS01 with query BW_QRY_ABMMIC01_0001 in source. |
| PC_CO_MS_0004 | MS: TD - M - Model S Propagation - APCOMS04 | External start only (via API or metachain) | Sub Chain of PC_CO_MS_0006 |
| PC_CO_MS_0005 | MS: TD - M - Model S Businesss | External start only (via API or metachain) | Sub Chain of PC_CO_MS_0006 |
| PC_CO_MS_0001 | MS: TD - D - Shift of Months: Models S (Propagation Layer) | External start only (via API or metachain) |
The loading is done after the process chain PC_INT_MARGIN - "Integrated Margin 2" normally once a month in the 3th workday.
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.
BW_QRY_ABMMIC01_0001 - BW - Material Stock for extract model S (Core Query)
BW_QRY_CPCOMS01_0001 - Stock margin elimination report (Core Query)
BW_QRY_CPCOMS01_0002 - Stock Margin Elimination report 2 (Core Query)
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