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 (C_MATPLNT-CPFCTR1_2 )
Plant (C_PLANT)

Authorization objects

List of autorisation objects mandatory for the application.

Authorization object

Explanation

GBU (C_MATPLNT-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)

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 from RCS. NO_LOAD to avoid loadings
IMEP	RCS_DEL	Period (YYYYPPP) to delete in RCS DSO/Cube. NO_DEL to avoid

Main Chains

Process Chain	Code	Type	Frequency	Comments
		MAIN

Sub Chains

Process Chain	Code	Type	Frequency	Comments

Other Chains

Process Chain	Code	Type	Frequency	Comments

Loading frequency

Detail of frequency : monthly; weekly or else

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

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

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

List the most important and complex queries only with a link to the documentation

Main functionalities

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

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

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