You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

General presentation

Objective of the application

Tool Leader + IT leader of the application: 

Usage information

History

Roles & Access

Roles and access

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

Role CodeRole DescriptionExplanation
ZR_RCS_CA_M731CT - COSTA TransactionsRole to have access to transaction ZBW_CUST_COSTA 






Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation






Dataflow overview

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

Percentage inflation

Zero Based Budgeting

Resp. Cost Center Determination

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.

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


Rules & Explanations

Dependencies with other applications

Data loadings

Info providers and objects loaded

Loading frequency

Average performance


Key FigureEstimation
~ Average Process Chain Runtime
~ Average nb of rows loaded per load
~ Total nb of rows loaded (if full)
~ Average Runtime for 10k lines

Record Keeping

Reporting

Queries End User Documentation

Unit test for program ZBW_COSTA_RCC:

https://docs.google.com/document/d/1lG0t9k2MadMawaTrYvtFDmwJ1Twzbp3jcjF1VJ-XC1g/edit?usp=sharing

Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution


  • No labels