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_M731 | CT - COSTA Transactions | Role to have access to transaction ZBW_CUST_COSTA |
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
Clusters and sub clusters come from PF1_050, datasource DTS_BW_REPO_BU_CLU_SCLU. This datasource uses module function ZFM_BW_REPO_BU_CLU_SCLU).
We extract data into adso APCOCT14 and then load the attributes and textes in master data CPFCTR1_2, C_CLUSTER & C_SUBCLUS (loadings done in process chain PC_CT_MD_01).
Goal:
Add in master data C_COSTCTR two attributes: group function and GBU function extracted from hierarchy Z013ZCBS_GRP (WP1 system). The link between cost center and hierarchy is C_FUNCT_2 (attribute from cost center and level 4 in hierarchy Z013ZCBS_GRP).
Steps:
1) Extract Z013ZCBS_GRP hierarchy in master data C_FUNCT_2 where: (done in process chain PC_CT_MD_01).
2) Load attributes C_GRPFUNC & C_GBUFUNC in master data C_COSTCTR (with look up on C_FUNCT_2)
In adso APCOCT04 we use data from master data C_MAT_GRP to determine cost sub package (C_CTSBPKG).
This loading is done in process chain PC_CT_TR_01 (process skipped for the moment because values in master data C_MAT_GRP are not ok, so data loaded by flat file).
In adso APCOCT05 we use data from master data C_SEGT to determine cost sub package (C_CTSBPKG).
This loading is done in process chain PC_CT_TR_01.
In adso APCOCT06 we use data from adso APCOCT16 (only landscape ERPSOLV and ERPRCS) to determine cost sub package (C_CTSBPKG) associated to cost element.
For the moment there is no process chain to load this dso, for the moment there is another transformation and dtp to load the adso with flat file.
Goal: in master data c_coorder add three new attributes C_GEN_REA & C_INV_REA & C_ORD_TYP
C_GEN_REA & C_INV_REA come from C_WBS_EL2 and C_WBS_EL2 comes from dso ABCOCT01 & ABCOCT02.
Main rules:
Start routine:
End routine:
If C_COORDER___0ORDCATEG = 30 feed C_INV_REA & C_GEN_REA & C_ORDR_TYP
Else feed only C_ORDR_TYP
If nothing was found, no change, keep the current attributes in master data C_COORDER.
In scope of Costa data, it's necessary to define which data are for COSTA, F2G or ANAPLAN. The idea is to exclude some records not in scope of ANAPLAN or F2G.
To do that, it's necessary to define the rule of exclusion in a table: ZCOSTA_ANAPLAN
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
Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...
Detail of process chain, list + link between or special event done for the loading
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.
Unit test for program ZBW_COSTA_RCC:
https://docs.google.com/document/d/1lG0t9k2MadMawaTrYvtFDmwJ1Twzbp3jcjF1VJ-XC1g/edit?usp=sharing
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