Access Management 

DataFlow

Overview

Technical documentation for dataflows : https://drive.google.com/open?id=0B-KST39ThPrUeUVDb0FRNVNQckU

Technical Rules on Workbench

Below objects should be loaded previously before load GTBU in the following sequence:

1. Master Data C_PMORDR (Work Orders Master Data)
2. DSO ODS_PM04 (Work Orders / Operations)

For transformations between propagation and business layer C_COMPDE comes from master data C_PMORDR if a correspondance is found, else c_compcde is empty. C_WORKCTR and C_PLANT come from C_PM_OP2.

There are also seletives deletion in the start routines.

Each transformations (except for DSO_PM11) have similar structures rules (with some specificities, for more detail check directly in routines):

During the first package loading, an internal table is filled with data in source package.

Then during the next packages, we check if the new record added already exist in internal table but with different keys. If it's the case, the line is added in ITB_ SCAFFOLDING. If not the line is added but with key figures at 0 (or null) and some key fields (C_GTBUSH & C_INONUM & C_INOREF) empties or the lines is not loaded.

Key figures have differents rules in function of a specific field.

Reporting

• List of BEx Reports & Workbooks : CATALOG - Industrial & Planning Reporting (in the tab Maintenance, Category = GTBU)

Main queries

Main functionnalities

The files generate data for BW in the export tab. Indicators are registered in the files with a key. After confirmation of the file, a night job (on WP1: PM_T00400_EU; on PF1: ZZI_020_TA_GTBU_EXTRAC_BW) for program ZWPMT00400 add data in tables ZWPMT007 and ZWPMT019 for the extraction. We can check the files uploaded by suppliers in the SAP transaction. In BW, the key relate to the KF.

The application is based on three datasources based on SAP tables:

• DTS_ZBW_ZWPMT007
• DTS_ZBW_ZWPMT019
• DTS_PMESLL

Main dimensions for the data:

• C_GTBUUID Unique log file identifier for GTBU
• C_PMORDR PM Work Order

• C_EQUNR Equipment number

• C_LBLNI Entry sheet number

• C_SEDAT Service entry sheet creation date

• C_SCITKEY Equipment item key

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 

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

• Ticket #17365: A new data has been added in the definition sheet for Scaffolding. The users want to add it in BW reports.