General presentation

Objective of the application

The objective of the application is to extract from WP1 SAP systems Recipe data. The goal is to have the link between the production version (Plant@Material) and the activities by product line.

The data are extracted from MAPL, PLKO, PLPO, CRHD tables.

Then data are consumed by Dynasys application by generated flat file.

There is no query developped for the reporting.

Usage information

Nu mber of users:  tbd

Critical period: none

Geographical perimeter: worldwide

InfoArea:

History

This application is linked to a need of Dynasy Tool. Every week a manual extraction is done of Master recipe Data from WP1 SAP system. The goal is to extract these data from SAP to BW and generate automaticaly Master Recipe data by flat file and send this file to Dynasys for import.

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

Reporting documentation drive folder:

https://drive.google.com/drive/folders/18VbVRgRTsredyh89a_qSECY7E0yzSKJJ

Dataflow overview  :

https://drive.google.com/file/d/1u9DaP5-AzjNayHLtwYRACs8Y-xJeQNysj1EdPO1FR1k/view

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Assignment of Task Lists to Materials

ADSO APPPRE01 is loaded by the datasource DTS_ZBW_V_MAPL. This datasource used the view ZBW_V_MAPL on WP1 for the data extraction (Join of MAPL/PLKO and PLAS table).

The mapping between the ADSO and the datasource is direct.

In this ADSO we'll have the link between the Production Version (At Material@Plant level) and the different recipe (0PLNNR, Key for Task list group).

For each recipe we'll have a Base Quantity of produced Material and associated Base Unit of Measure.

There are 2 fields used to filter data during extraction and loading on BW : 

• AEDAT (Modification Date MAPL-AEDAT)
• ANDAT (Creation Date MAPL-ANDAT)

Task List - Operation / Activity

ADSO APPPRE02 is loaded by the datasource DTS_PM_TASK_LIST_OPER_ATTR.

This datasource used the table PLPO on WP1 for the data extraction.

The mapping between the ADSO and the datasource is direct.

In this ADSO we'll have the list of operations (activities) and their duration for each recipe.

There are 2 fields used to filter data during extraction and loading on BW : 

• AEDAT (Modification Date MAPL-AEDAT)
• ANDAT (Creation Date MAPL-ANDAT)

There is also the ADSO ABPPRE01 loaded in delta mode from the previous APPPRE02 (mapping direct).

This one is used for the Dynasys interface (projection of this ADSO is used in a Calculation View).

Link Work Center / Object ID

The master data C_WKCTRID contains the link between the Object ID of the ressource associated to an operation and the work center.

It is loaded by the datasource DTS_ZBW_V_CRHD from WP1 SAP system. This datasource is based on the view CRHD_V1.

Control Key

An operation is associated to a Control Key and for the the Dynasys need we are using a filter on to keep only the Control Key flagged as scheduled.

The information is loaded and stored in the master data C_STEUS (Control Key) from the datasource DTS_ZBW_T430.

This datasource is based on the table T430 (Control Key attributes)

Dependencies with other applications

The Dynasys calculation view CV_DY_RECIPE_CAPA uses projections of data based on following object of Recipe Application :

• ABPPRE01
• APPPRE01
• C_WKCTRID
• C_STEUS

More details here.

The result of the calculation view is loaded in ADSO APDPDY10 & ABDPDY59.

Recipe data are consumed by Dynasys tool using the generated flat file DYS_BW_RECIPE.csv from the ADSO ABDPDY59.

Data loadings

Info providers and objects loaded

Scope of data loaded

Both propagation layer ADSO APPPRE01 & APPPRE02 are loaded by 2 FULL DTPs.

The fisrt one is based on creation date and the second on modification date of the record in respective source table.

We load for each of them from current date to current date - 7.

Note that DTP are different for each objects.

Master Data process chain

Recipe Master Data are loaded by process chain PC_PP_RE_01.

Material Task List & Operation / Activity process chain 

ADSO are loaded by following process chain :

• Propagation Layer : PC_PP_RE_02
• Business Layer : PC_PP_RE_03

Master Chain

A global Master process chain load all the Recipe application :  PC_PP_RE_04

This master chain is part of a global chain with BOM application : PC_RE_01

Today the process chain PC_RE_01 is scheduled at 00:30 (CET).

Loading frequency

Daily loading

Average performance

See below init data loading (full without filters) performed end of June 2021  :

Record Keeping

Reporting

Queries End User Documentation

Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution

Today we have only data from WP1 SAP system, PF1 is planned to be added but rules will be different.