DataFlow

Overview

Image Removed

Embedded Google Drive File

migrated	true
url	https://docs.google.com/presentation/d/1XP-u0TaR0tWYw93x3bD1vEnv4bMvX9uEfAnQBWbYsYk/edit?usp=sharing
fullwidth	true
height	600

Embedded Google Drive File
migrated true url https://docs.google.com/presentation/d/1QFcHWVicoAArMfnyhnZPeqncNJTVs9DN7LNyrH0aBzY/edit?usp=sharing fullwidth true height 600

Embedded Google Drive File
migrated true url https://docs.google.com/presentation/d/1uLyqRaleufC3cFA2JOhfP6h8AHjCFToH227qQjMNbSE/edit?usp=sharing fullwidth true height 600

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

Technical Rules on Workbench

Data is extracted from standard extractors from system WP1 400: 2LIS_17, 0PM_OM_OPA_1 & 2, 0CA_TS_IS_1

Dependencies:

• It shares some extractors (2LIS_17_I3OPER, 0PM_OM_OPA_2) with MECANO.
• Data is consumed by ORACLE by the broadcast of a workbook (BCAST_ORACLE_PM) with PM costs, which is integrated manually by IS PM team.
• Data is loaded in cube CUB_PM for QV dashboard RCS KPI
• Costs data from all three systems (WP1/PF1/RHO) is used in FI cubes

Functional Rules:

• Alternative Labeling is used on Functional Location in the source system. The alternative label is loaded in the master data attributes.

Reporting

• CATALOG - Industrial & Planning Reporting (in the tab Maintenance)

Several topics are covered by BEx reports :

• Work Orders with Maintenance Plan
• Work Orders with Equipment
• Notifications by Status and Causes
• Planned and Actual duration on Operations
• Work Orders and Operations by Status and Priority
• Monthly Costs
• Functional Location and Equipment Attributes
• Consumption of Materials on Work Orders
• Work Orders Costs by Vendor
• MTBF (Mean Time Between Failure)
• Backlog on Operations

Broadcast

• BCAST_ORACLE_PM (Weekly) : Extraction of actual costs year to date for current year send to PM IS Team for Chalampé plant, and the data is loaded manually in ORACLE Hyperion by PM Team.
• RCS_KPI_PM_ALL (Monthly) : Extraction of KPI PM. It has been unscheduled on SEP 2015 after a usage survey from IS Reporting Team and is not running anymore.

Image Removed

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 

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

Data loadings

Info providers and objects loaded

Infoproviers and Master data are grouped in the Application Area AREA_PM.

Process Chains included in the Global RSP_DAILY Process Chain:

• ZPC_MD_ATTR_RCS (For shared master data attributes and texts)
• RCS_PM_KPI (Load Cubes for RCS KPI application used by QV dashboard)
• RSP_PM
• RSP_PM_ACETOW (Load PM Costs data from RHO system for FI cubes)
• RSP_PM_SOLVAY (Load PM Costs data & Commitments and orders distribution rules from PF1 system for FI cubes)
• PC_PM_01

Others Process Chains:

• PC_PM_ORDER_WEEKLY
• PM_BACKLOG

Loading frequency

• Daily loadings Monday to Friday
• Weekly loadings for PC_PM_ORDER_WEEKLY & PM_BACKLOG

Average performance

The main process chain RSP_PM run in about one and a half hours.

PM Extractors (2LIS_17) are set up in delta with a delta queue. Costs on PM orders are loaded in full mode.

Historization

We keep all the data in the DSO and Cubes. Archiving is done on Source System.

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