General presentation

Objective of the application

i-MEP stands for Integrated Manufacturing & Energy Performance

The I-MEP application provides to business the possibility to analyze the production target cost / actual cost / variance for each cost item in process order / cost collector, and to determine energy consumption and CO2 emission during production process.

BI manufacturing reports will replace house solutions :

on RCS (WP1) : programs ZWPP40A/B/C
on Solvay (PF1) : program Z1K_MATCOST (Prix de Revient)

Describe in a few words the content of application + link with functional or technical specifications (google links) done with during the project or linked with PPMO

Tool Leader + IT leader of the application: Name of project or main leader for the application + reporting coodinator

Usage information

How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site

History

Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information

Roles & Access

Roles and access

Role Code

Role Description

Explanation

ZR_RCS_CA_M55

IMEP - Integrated Manufacturing & Energy Performance

Gives access to queries & workbooks IMEP (Manufacturing & Energy reports)

ZBI_RCS_IMEP_A01

IMEP - Integrated Manufacturing & Energy Performance

Gives access to InfoArea IA_FMCO_CO_IMEP* and all authorization relevant objects except

GBU (CPFCTR1_2 )
Plant (C_PLANT)

Authorization object ZBI_IMEP

Authorization objects

List of autorisation objects mandatory for the application.

Authorization object

Explanation

GBU (CPFCTR1_2 )

ZR_*_CA_P05

Plant (C_PLANT)

ZR_*_CA_P02

ZR_7866_CA_P02 => Plant 7866 - Chalampé (ex 7027) - (Cie ZFR9)

ZR_TOUT_CA_P02 => All Plants "Solvay"

See also file maintained by Authorization team : BW Catalog of Roles / link: https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I

Dataflow overview

https://drive.google.com/open?id=18v4PEvS10Q4RmofZBDuuuTiyTqO9anDL3x-Bcxvnv2s

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Source tables

Table ZWPPMCKOST / i-MEP extraction table

This table exists on both systems PF1/WP1, but the structure is slightly different.

Following additional fields exists for PF1 table, but not for WP1 table : append ZWPPMCKOST_EXTRA

Process Chain	Code
Code établissement DSI	ETABL
Code édition	EDITI
Libellé de la ligne d'édition	LIBLI
Type: Fix/Var/Dep	FVD
Cost collector for production process PROCNR	PKOSA
Material Ledger Cost	MLWRT

This table is filled via program XXX and contains only the values for the previous period (The table is emptied before each loading)

to be completed

Table ZZX_CO2_COEFFS / Energy and CO2 Emission Coeffcients

This table exists on both systems PF1/WP1, and is filled manually by Energy Carbon team

to be completed

At datasource level (PF1/WP1)

Controlling Area (0CO_AREA)

The controlling area is unique on PF1 ( value CHEF), but not on WP1 ( Z006, Z025, Z026...)

The controlling Area is not available on ECC side specific tables, but, in order to match the BI referential, this information is necessary to get referential attribut and texts (example 'Cost Center' C_COSTCTR, 'Profit Center' C_PFT_CTR)

To get the information extractor are based on specific view with follow the business rule given :

- A plant belongs to a single company code (link found in table T001K where 'Valuation Area' (BWKEY) corresponds to the plant (WERKS)

- A company code belongs to a single controlling area (link found in table TKA02 / field 'Business Area' (GSBER) is always empty)

Add datasource names and view names

At business level (WBP)

At reporting level (WBP)

GBU (CPFCTR1_2)

The GBU available for reporting is BFC Global Business Unit (CPFCTR1_2) found on Cost Center

Detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way

Dependencies with other applications

Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...

Data loadings

Info providers and objects loaded

Global Filters (C_GLBFILT) used in Chains

Stream	Rule	Explanation
IMEP	RCS_LOAD	Period (YYYYPPP) to load, RCS. NO_LOAD to avoid loadings Do not change active flag (Active = Y) This variable is used in decision block
IMEP	RCS_DEL	Period (YYYYPPP) to delete, RCS DSO/Cube. NO_DEL to avoid Do not change active flag (Active = Y)
IMEP	RCS_HISTO	Counter 1 = Number of Year to keep in all DSOs/Cubes RCS Counter 2 = Delete all data in all DSOs/Cubes RCS older than The counter 1 is entered manually, it is a number of years to keep in all DSOs and Cubes. If '3' is entered, 3 full years + current year are kept. The counter 2 is determined within program ZBW_IMEP001 depending of the loaded period and the counter 1. Example : we are the 01/08/2016, the period 007.2016 is loaded. As the counter 1 is '3', the calculated counter 2 is 001.2013. All period previous to 001.2013 will be deleted via the main process chain
IMEP	SOLV_LOAD	same explanation than for RCS'ones
IMEP	SOLV_DEL	same explanation than for RCS'ones
IMEP	SOLV_HISTO	same explanation than for RCS'ones

ABAP Programs used in Chains

Program

Variant

Explanation

ZBW_DELDIM

ZVAR_IMEP_01
ZVAR_IMEP_02
ZVAR_IMEP_03
ZVAR_IMEP_04
ZVAR_IMEP_05
ZVAR_IMEP_06

Existing program, reused to clean cube dimensions. It delete unused dimension elements

ZBW_IMEP001

ZVAR_DEL_RCS
ZVAR_DEL_SOLV
ZVAR_OBS_RCS
ZVAR_OBS_SOLV
ZVAR_PER_RCS
ZVAR_PER_SOLV

Program created for the projet to :

Determine period to load from source system (and period to delete, obsolete periods)
Delete exercice/period (previously to new load)
Delete obsolete periods (to keep a constant perimeter of data)

Further examplation for program ZBW_IMEP001 :

$TECHNO - BI TEAM > BW RTR - i-MEP (WBP) /!\ Obsolete /!\ > image2016-8-4 10:10:6.png$

Main Chains

Process Chain

Code

Type

Frequency

Comments

IMEP: META - T - Main (Solvay)

PC_CO_IMEP_01

MAIN

D1 to D4

This chain is starting when event xxx is received from Solvay PF1.

Global Filter IMEP/SOLV_LOAD is used in the decision bock.

IMEP: META - T - Main (RCS)

PC_CO_IMEP_08

MAIN

D1 to D4

This chain is starting when event xxx is received from RCS WP1.

Global Filter IMEP/RCS_LOAD is used in the decision bock.

Sub Chains

Process Chain	Code	Type	Comments
IMEP: MD - Referential & Conversion factors (Solvay)	PC_CO_IMEP_02	subchain	Data requiered for Business Rules
IMEP: TD - Delete period in targets before loading (Solvay)	PC_CO_IMEP_03	subchain	Before loading a period, the same period has to be deleted from targets (DSO/Cubes) Global Filter IMEP/SOLV_DEL is used
IMEP: TD - Propagation (Solvay)	PC_CO_IMEP_04	subchain	Global Filter IMEP/SOLV_LOAD is used to limit the InfoPackage
IMEP: TD - Business (Solvay)	PC_CO_IMEP_05	subchain
IMEP: TD - Reporting (Solvay)	PC_CO_IMEP_06	subchain
IMEP: MD - Texts	PC_CO_IMEP_07	subchain	This load could be done ones a week or ones a month
IMEP: MD - Referential & Conversion factors (RCS)	PC_CO_IMEP_09	subchain	Data requiered for Business Rules
IMEP: TD - Delete period in targets before loading (RCS)	PC_CO_IMEP_10	subchain	Before loading a period, the same period has to be deleted from targets (DSO/Cubes) Global Filter IMEP/RCS_DEL is used
IMEP: TD - Propagation (RCS)	PC_CO_IMEP_11		Global Filter IMEP/RCS_LOAD is used to limit the InfoPackage
IMEP: TD - Business (RCS)	PC_CO_IMEP_12
IMEP: TD - Reporting (RCS)	PC_CO_IMEP_13

Other Chains

Process Chain	Code	Type	Frequency	Comments

Loading frequency

IMEP is loaded daily from D1 to D4 only.

Events on Solvay ECC (PF1) and RCS (WP1) starts BW Process Chains.

In Process Chains we also check that we are between D1 and D4 (programme ZBW_IMEP001).

Average performance

if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application

Key Figure	Estimation
~ Average Process Chain Runtime
~ Average nb of rows loaded per load
~ Total nb of rows loaded (if full)
~ Average Runtime for 10k lines

Record Keeping

3 years plus current year is asked by business.

Older data are deleted from DSOs/Cubes at the end of the process chains RCS and Solvay.

The number of years to keep can be maintained in Global Filter masterdata (Stream IMEP / Rule RCS_HISTO or SOLV_HISTO/ Counter '001'

Reporting

Queries End User Documentation

Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.

Main queries

Report	Type	Comment	Link to documentation
MANUFACTURING - Local Core Query	QRY	Manufacturing report will be used to display all the characteristic and key figures loaded from the ZWPP40x program. This report will display key figures only on company code currencies and local base unit of measure.	https://drive.google.com/open?id=14wAf4AjUgq2jcQko5A2AyEYY_pd2evwVokizwSomUPQ
MANUFACTURING - Consolidation Core Query	QRY	Manufacturing report will be used to display all the characteristic and key figures loaded from the ZWPP40x program. This report will provide the possibility to display unit of measure and currency in a consolidate target unit.	https://drive.google.com/open?id=1-UP2e782f6PX1huigJezI6_rLRnVWskAQp5YonjgNG0
ENERGY - Energy Expense (Core Query)	QRY	Report will display the energy purchase information	https://drive.google.com/open?id=0BzmDyGNrfxu2Q0R0YzNBcXRhQ3M
ENERGY - Primary Energy and Emission report (Core Query)	QRY	Report will display the primary energy consumption	https://drive.google.com/open?id=0BzmDyGNrfxu2aE1WeEtFS0xjek0
ENERGY - Interface Production Report (Core Query)	QRY	3 reports will be used to provide source data to the EPS system. As this is a temporary solution, the reports will be executed manually by the users. No automation process will be implemented	https://drive.google.com/open?id=0BzmDyGNrfxu2QkFrMWhMNHlLZE0
ENERGY - Interface Cost Production Report (Core Query)	QRY	3 reports will be used to provide source data to the EPS system. As this is a temporary solution, the reports will be executed manually by the users. No automation process will be implemented	https://drive.google.com/open?id=0BzmDyGNrfxu2Yms3bjlmOWx2b2M
ENERGY - Interface Consumption Quantity Report (Core Query)	QRY	3 reports will be used to provide source data to the EPS system. As this is a temporary solution, the reports will be executed manually by the users. No automation process will be implemented	https://drive.google.com/open?id=0BzmDyGNrfxu2VFNNNWxOa29HVWs
MANUFACTURING - Reconciliation (Workbook)	WB	Manufacturing data reconciliation workbook will be created to compare VC, FC, DEP key figures between the P&L – legal view report and the manufacturing report.

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

No broadcast

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

List recurring procedures

Planned Evolution

Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016