Access Management 

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. 

DTP: filter to exclude materials 102283, 104123, 104740, 105984, 105985, 105986, 107266, 111400, 120707, 139210.

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.

DTP: filter to exclude materials 102283, 104123, 104740, 105984, 105985, 105986, 107266, 111400, 120707, 139210. Snapshot = DAY or DAY_AP or SOIP1 or SOIP2.

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

DTP: filter to exclude materials 102283, 104123, 104740, 105984, 105985, 105986, 107266, 111400, 120707, 139210. Snapshot = DAY or DAY_AP or SOIP1 or SOIP2.

CUB_IC002 - Material movements

Transformation: ODS_IC01 -> CUB_IC002

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

C_BAUGR (Material number of higher-level assembly): if C_BAUGR is empty and C_PRODORD (Manufacturing Order) is not empty, take the C_MATNR from master data C_PRODORD.

C_LIP01S (Product line 01 Higher Level): if C_PRODORD (Manufacturing Order) is not empty, take the C_LIP01 (Product line 01) from master data C_PRODORD.

C_LPRODS (Product Line 00 Higher Level): if C_PRODORD (Manufacturing Order) is not empty, take the C_LIPROD (Product line 00) from master data C_PRODORD.

C_PRODS (Commercial Product higher level): if C_PRODORD (Manufacturing Order) is not empty, take the C_PROD (Commercial Product / Material Group) from master data C_PRODORD.

DTP: filter to exclude materials 102283, 104123, 104740, 105984, 105985, 105986, 107266, 111400, 120707, 139210.

CUB_COPC1 - Material Prices

Transformation: 0COPC_O01 -> CUB_COPC1

BASE_UOM comes from master data C_MATNR.

DTP: filter to include materials 102283, 104123, 104740, 105984, 105985, 105986, 107266, 111400, 120707, 139210 and currency type  not equal 10. Group semantic on MATERIAL / PLANT / VAL_TYPE / FISCPER3 / FISCYEAR / PRICE_TYPE / FISCVARNT / VAL_CLASS / VALUATION / STLMT_CTRL / PRICE_CTRL / COMP_CODE / MAT_PLANT

CUB_CAP - Capacity Planning - Weekly & CUB_CAPM - Capacity Planning - Monthly

RSDS DTS_DPS_CAPACITY WP1_400 -> CUBE CUB_CAP &  RSDS DTS_DPS_CAPACITY WP1_400 -> CUBE CUB_CAPM

Delete data where: 

• • • KBEASOLL (Proc. Schd.) is empty
    • FSTAD (Earliest start) is lower than date of loading.

C_MATNR = 'DUMMY' for each week / workcenter

k_capav is calculated in end routine in function of the calweek and also the date, plant and workcenter (with module function "Z_WBW_READ_KAZY").

DTP: filter on snapshot = LTP or DAY (depends of DTP) + group semantic on WERKS and MDV01.

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

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