General presentation

Objective of the application

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

Usage information

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

History

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

Roles & Access

Roles and access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Authorization objects

List of autorisation objects mandatory for the application.

Dataflow overview

Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

Functional and Technical rules on Workbench + Reporting

Flat files loading - Transaction ZBW_CUST_COSTA

Order Capex Opex

• Program: ZBW_COSTA_ORDER_CAPEX_OPEX
• Process chain: PC_CT_TR_03
• Infoprovider: APCOCT09 → CPCOCT06
• Query: BW_QRY_CPCOCT06_0001 + QV_BW_QRY_CPCOCT06_0001
• Flat file format: https://drive.google.com/file/d/17S7GBSYr4PdUoIKgFM_55WUXNZ30Mj_5/view?usp=sharing

Percentage inflation

• Program: ZBW_COSTA_INFLATION
• Process chain: PC_CT_TR_04
• Infoprovider: APCOCT11 → CPCOCT06
• Query: BW_QRY_CPCOCT06_0002 + QV_BW_QRY_CPCOCT06_0002
• Flat file format: https://drive.google.com/file/d/1ohjO7Frob67lfLQeTBI5YV1TAKlRz9MO/view?usp=sharing

Zero Based Budgeting

• Program: ZBW_COSTA_C_CTSBPKG_ZBB
• Process chain: PC_CT_TR_05
• Infoprovider: APCOCT13 → CPCOCT06
• Query: BW_QRY_CPCOCT06_0003 + QV_BW_QRY_CPCOCT06_0003
• Flat file format: https://drive.google.com/file/d/1m-KAKYcZaj0EW5-DWsYnxeovxS733nQH/view?usp=sharing

Resp. Cost Center Determination

• Program: ZBW_COSTA_RCC
• Process chain: PC_CT_RCC_01
• Infoprovider: APCOCT15
• Query:
• Flat file format:  https://docs.google.com/spreadsheets/d/1vqYWqegl4sTGUZTg-lPb6o1N5XzWKx7midspUa3ZGik/edit#gid=0

Rules & Explanations

Cluster GBU

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).

Group of function

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).

• C_FUNCT_2 = level 4 in Z013ZCBS_GRP (without controlling area).
• C_FUNCT_2__C_GRPFUNC = Level 3 in Z013ZCBS_GRP.
• C_FUNCT_2__C_GBUFUNC = Level 2 in Z013ZCBS_GRP.

2) Load attributes C_GRPFUNC & C_GBUFUNC in master data C_COSTCTR (with look up on C_FUNCT_2)

Cost package derivation from:

Material Group

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).

Segment

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.

Cost Element:

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.

Investment Reason for PM Order

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:

• Developments are done in transformtions:
  • Transf: 0COORDER_ATTR -> C_COORDER
  • Transf: 0COORDER_ATTR -> C_COORDER Solvay
• The filters used are defined in master data global filter we stream "C_COORDER".
• By default the period to read adso ABCOCT01 is current month -1. But it's possible to make the look-up with several month with definition of period in master data global filter: 

Start routine:

1. Define all filters.
2. Do a select in internal table to take data from adso APCOCT01 or APCOCT02 with filters on CALMONTH, C_PSOBJTY, C_DESTTY and C_PTOBJTY.
3. Aggregation with keys LOGSYS /BIC/C_PSOBJ /BIC/C_PTOBJ BIC/C_WBS_EL2 of data from DSO ABCOCT0* in internal table sorted by ascending.
4. Search the attributes C_INV_REA & C_GEN_REA in master data C_WBS_EL2 for all entries of internal table.
5. Create new table to have PSOBJ (coorder) and WBS_EL2 + Attributes in same table.
6. Select current GEN_REA, INV_REA, ORD_TYP from master data C_COORDER to be able to keep current data if nothing was found in dso ABCOCT01 or C_WBS_EL2

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.

ANAPLAN/F2G SCOPE

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.

https://drive.google.com/file/d/1gm7dEVDqkwav53t70qyF9hPcTdlgGQG1/view?usp=sharing

To do that, it's necessary to define the rule of exclusion in a table: ZCOSTA_ANAPLAN

This table could be maintened with SM30 or transaction ZMAINT_COSTA_ANAPLAN.

We use this table in calculations views CV_FMCO_CO_CT_UNION_COSTS_TRANSPARENCY & CV_FMCO_CO_CT_UNION_COSTS_TRANSPARENCY_DEST.

To apply the exclusion flag anaplan or F2G:

• We do a projection of table ZCOSTA_ANAPLAN, filtered on one type of C_CTEXR_A or C_CTEXR_F.
• Create a full outer join with costa data and ZCOSTA_ANAPLAN on the necessary field(s) to find which records match with the filter, if there is a match we add a new column with the C_CTEXR_A or F.
• Repeat the join for each type of filter.

• At the end we can define a global column for exclusion flag and exclusion reason (anaplan and F2G).

Level 5 - Responsible Cost center

Level 5 responsible cost center is retreived in CV_FMCO_CO_CT_UNION_COSTS_TRANSPARENCY & CV_FMCO_CO_CT_UNION_COSTS_TRANSPARENCY_DEST.

1 - Projection of adso APCOCT18 where L5 are stored.

2 - Join with costa (co_area, c_resp_cc) to have calday (calculated with the first day of the costa period) from costa data in same line of L5.

3 - Projection of L5 with filter on L5 date from and L5 date to with help of calday.

4 - Rank to take only one L5 by co_area, c_resp_cc and date.

5 - Join to add the L5 in costa table with join on CO_AREA, C_RESP_CC and CALDAY.

GBU Global

In calculations views

The global GBU is calculated in fuction of C_MAGNITU or C_RESP_CC:

If we don't have GBU in attribute of C_MAGNITU (destination GBU) we use GBU from C_RESP_CC (origin GBU).

Rule in calculation view: if(isnull("C_MAGNITU__CPFCTR1_2") OR "C_MAGNITU__CPFCTR1_2" = '',"C_RESP_CC___CPFCTR1_2","C_MAGNITU__CPFCTR1_2")

Dependencies with other applications

Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...

Data loadings

Info providers and objects loaded

Detail of process chain, list + link between or special event done for the loading

Loading frequency

Detail of frequency : monthly; weekly or else

Average performance

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

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

Queries End User Documentation

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

Main queries

List the most important and complex queries only with a link to the documentation

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

List recurring procedures

Planned Evolution

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