You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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)

Tool Leader + IT leader of the application: 

Usage information

History

Roles & Access

Roles and access

Role CodeRole DescriptionExplanation
ZR_RCS_CA_MxxIMEP - Integrated Manufacturing & Energy Performance Gives access to queries & workbooks IMEP (Manufacturing & Energy reports)
ZBI_RCS_IMEP_A01

IMEP - Integrated Manufacturing & Energy Performance (IMEP)

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

  •  GBU (C_MATPLNT-CPFCTR1_2 )
  •  Plant (C_PLANT)
  • Company Code (C_COMPCDE)

Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation
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"

Company Code (C_COMPCDE)

ZR_*_CA_P01

ZR_ZFR9_CA_P01 => BUTACHIMIE - ( ZFR9) (ex 0560)

ZR_TOUT_CA_P01 => All Companies "Solvay"

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

Dataflow overview

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

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

 

Dependencies with other applications

Data loadings

Info providers and objects loaded

Loading frequency

Average performance

 

Key FigureEstimation
~ 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

Reporting

Queries End User Documentation

 

Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution

 

  • No labels