Access Management 


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

Role CodeRole DescriptionExplanation

ZR_RCS_CA_M09

PS - Project Costs

Role menu for all project costs queries

ZBI_RCS_PS_A02

Project Costs and Structures Analysis - End User role

Application Role:

    • End User rights
    • gives access to infoproviders of Infoarea "AREA_PSCO"
    • BI Analysis Authorization "ZBI_PS" ("*" for authorization objects not relevant for the application)

ZBI_RCS_CO_A21

CBS Project costs Reporting Analysis - End User role

Application Role:

    • End User rights
    • gives access to infoproviders of Infoarea "AREA_F_CO_CBS_PS"
    • Gives access to multiprovider:MPR_PS014
    • BI Analysis Authorization "ZBI_CBS_PC" 

List of authorization objects mandatory for the application.

Authorization objectExplanation
0COMP_CODE;C_COMPCDE;C_PMORDER__0COMP_CODECompany, role: ZR_*_CA_P01
0PROFIT_CTR__CPFCTR1_2; 0PROFIT_CTR__C_PFCTR1;CPFCTR1_2;C_AGRITM__CPFCTR1_2;
C_ASSET2__C_PFCTR1;C_ASSET__C_PFCTR1;C_MATPLNT__CPFCTR1_2;
C_MATPLNT__C_PFCTR1;C_MATPNT2__CPFCTR1_2;C_PFCTR1;
C_PMORDER__C_PFCTR1;C_PMORDR__C_PFCTR1;C_PRDEQUI__CPFCTR1_2;
C_RECONTR__CPFCTR1_2;C_RESP_CC__CPFCTR1_2;C_SUBACT2__CPFCTR1_2
C_TECMAT__CPFCTR1_2;C_WBS_EL2__CPFCTR1_2;C_WBS_EL2__C_ZSECT;C_WBS_ELE__CPFCTR1_2;
C_WBS_ELE__C_ZSECT;C_ZSECT		GBU, role: ZR_*_CA_P05
C_FAMIL;C_WBS_EL2__C_FAMIL;C_WBS_ELE__C_FAMILFamily, role: ZR_*_CA_P04

DataFlow

Overview

Technical Rules on Workbench

MPR_IC001 - Material stock / movement

CUB_IC001 - Material stock

Transformation: ODS_IC01 -> CUB_IC001

Key figures rules explained in document "Inventory Management - documentation" in sheet "stock quantities/values".

0GL_ACCOUNT is defined in function of 0VAL_CLASS:

C_MATPUVT (Material Plant Unit Price by Valuation Type): concatenation between  PLANT - MATERIAL - VALUATION TYPE. 

TRCS IFS_2LIS_03_BF -> ODSO ODS_IC01

0VAL_TYPE / 0SHIP_TO / C_EXIDV / : remove strange characters with module function "ZF_INVALID_CHARACTERS".

RSDS 2LIS_03_BF WP1_400 -> TRCS IFS_2LIS_03_BF

0VENDOR comes from master data 0PLANT (field LIFNR) in function of BWART (movement type), SHKZG (Debit/Credit) and SOBKZ (Receiving plant). For more detail check the routines.

Transformation: ODS_IC02 -> CUB_IC001

Sames rules as Transformation: ODS_IC01 -> CUB_IC001

TRCS IFS_2LIS_03_UM -> ODSO ODS_IC02

Delete records whene STOCKCAT = V or STOCKTYPE = V.

CUB_PP02 - Production Planning In/Out Material

TRSF: DTS_SCM_MD04 -> CUB_PP02 (ECC6)

C_PRODORD: equal field DEL12 (MRP element number) if DELKZ (MRP elmnt ind.) equal 'BR' or 'FE' or 'AR'.

0VENDOR: if DELKZ (MRP elmnt ind.) equal 'PA' or 'BA' or 'BE' and if field PLUMI (Plus/minus) = '+' and field WERKS (Plant) <> field WRK02 (Producing plant) then read master data PLANT and take field LFINR.

0COMP_CODE: if field werks (plant) is not empty, reand master data PLANT and take the field BURKS associated.

0SOLD_TO: if DELKZ (MRP elmnt ind.) equal 'U1' or 'U2' or 'U3' or 'U4' and if field PLUMI (Plus/minus) = '-' read master data PLANT with field WRK02 (Producing plant) and take field KUNNR associated.

When DELKZ (MRP elmnt ind.) equal 'VJ' and if PLUMI (Plus/minus) = '-' 0SOLD_TO equal source field KUNWE (Ship-To Party).

C_RESWK (Supplying (issuing) plant in case of stock transport order): if DELKZ (MRP elmnt ind.) equal 'PA' or 'BA' or 'BE' and if field PLUMI (Plus/minus) = '+' then C_RESWK = source field WRK02 (Producing plant).

0MOVE_PLANT (Receiving Plant/Issuing Plant): if DELKZ (MRP elmnt ind.) equal 'U1' or 'U2' or 'U3' or 'U4' and if field PLUMI (Plus/minus) = '-' read master data PLANT with field WRK02 (Producing plant) and take field KUNNR associated.

When DELKZ (MRP elmnt ind.) equal 'VJ' and if PLUMI (Plus/minus) = '-' → read master data PLANT with source field  ZZVKORG (Sales Org.) or KUNWE (Ship-To Party) and take the  plant associated from master data.

CUB_PP01 - Production Planning MAD

TRSF: DTS_SCM_MD04 -> CUB_PP01 (ECC6)

For C_PRODORD, 0COMP_CODE, 0MOVE_PLANT, 0SOLD_TO and C_RESWK → same tules as TRSF: DTS_SCM_MD04 -> CUB_PP02 (ECC6).

C_NEWMON (GR Month) & C_NEWDATE (Goods Receipt Date):

        • If field PLUMI = '+', module function DATE_CONVERT_TO_FACTORYDATE is used to convert the source field date DAT00 (Planned date) with calendar 'BE'. Then date after conversion minus source field  WEBAZ (GR proc. time). Then we use again a module fonction  FACTORYDATE_CONVERT_TO_DATE (with alendar BE).
        • If field PLUMI <> '+' we just use the result of module function DATE_CONVERT_TO_FACTORYDATE is used to convert the source field date DAT00 (Planned date) with calendar 'BE'.

CUB_IC002 - Material movements

Transformation: ODS_IC01 -> CUB_IC002

Start routine: delete records where company code is liste in master data global filter:

CUB_COPC1 - Material Prices

Transformation: 0COPC_O01 -> CUB_COPC1

RSDS 0CO_PC_ACT_05 WP1_400 -> ODSO 0COPC_O01


CUB_CAP - Capacity Planning - Weekly

RSDS DTS_DPS_CAPACITY WP1_400 -> CUBE CUB_CAP


CUB_CAPM - Capacity Planning - Monthly

RSDS DTS_DPS_CAPACITY WP1_400 -> CUBE CUB_CAPM


Reporting

Dependencies with other applications

We should have the information where the application is sending or receiving information (e.g. APD open hub) 

Data Loading

Info Providers and objects loaded 

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

Main Process ChainFinal Provider LoadingFrequencyTime startDuration
















Data Quality Control


Operational Documentation

Procedures

<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>

Scheduling

<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>

Monitoring

<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>

Error Handling

<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>

Known Bugs

<List the existing bugs, its criticity, workarounds and resolution plan.>

Roadmap

<List past & future evolutions for the application (including links to MED/FSD/TSD)>