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

Authorization objects

List of autorisation objects mandatory for the application.

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

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)

Datasource : DTS_ZBW_V_ZWPPMCKOST based on view ZBW_V_ZWPPMCKOST

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) 

Cost Component Structure (0CCOMPSTRUC)

The Cost Component Structure id is not unique on PF1 (on WP1, only id Z1 is used), and the id is not part of source table ZWPPMCKOST.

The append ZEXTRA_FIELDS has been added to extract structure of the data source (ZOXDF10019). Fields belonging to the append are field within class ZDTS_ZBW_V_ZWPPMCKOST.

To get the information :

• by default set id to 'Z1' except for exception managed in table TCK07 'Costing Variants for Organizational Units'
• Exceptions for certain company codes (BUKRS)
  • ignore value '++++'
  • keep only one valid record by company code (the latest)

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

ABAP Programs used in Chains

Further examplation for program ZBW_IMEP001

Further examplation for program ZBW_IMEP002

Interface

The user can choose an Excel flat file from his local computer by using the "File to load" browser.

Once the file is choosen, the user can preview the content to be uploaded from his selected file by clicking on "Preview" icon.

 Once the file is choosen, the user can start the content checking of the file by clicking on "Check file" icon.

Once the file content is checked, the user can load the file to BW application server (AL11) and raise the event PC_CO_IMEP_15 by clicking on "Load file" icon.

 The event PC_CO_IMEP_15 triggers the process chain PC_CO_IMEP_15 - "IMEP: META - T - Main (Non-SAP Plant Flat Files)".

This process chain load the Non-SAP Plant data from user's file into IMEP BW application.

 The user can view the history of loaded files by clicking  on "History" icon.

 The user can exit the program by clicking on "Exit" icon.

Source Code

Report ZBW_IMEP002 contains several distinct parts:

Interface

Selection screen.

Import File

f200-import_file:  Import the XLS file from user's workstation.

f210-upload_excel:  Convert the XLS file in Internal table.

f220-check_file: Check content of the file as follow:

For more details, see file ZWPPMCKOST_table structure & contents_QF1.xlsx.

• BUSINESS RULE 1 : SOURCE SYSTEM
  • BUSINESS RULE 1.1 : SOURCE SYSTEM NOT FILLED
  • BUSINESS RULE 1.2 : SOURCE SYSTEM NOT AUTHORIZED
    
• BUSINESS RULE 2 : PLANT
• BUSINESS RULE 3 : FISCAL YEAR PERIOD
  • BUSINESS RULE 3.1 : FISCAL YEAR PERIOD NOT FILLED
  • BUSINESS RULE 3.2 : FISCAL YEAR PERIOD NOT EXISTING
• BUSINESS RULE 4 : PROFIT CENTER
  • BUSINESS RULE 4.1 : PROFIT CENTER NOT FILLED
  • BUSINESS RULE 4.2 : PROFIT CENTER NOT EXISTING
  • BUSINESS RULE 4.3 : PROFIT CENTER SHOULD HAVE 10 CHARACTERS
• BUSINESS RULE 5 : MATERIAL INCORRECT
  • BUSINESS RULE 5.1 : MATERIAL SHOULD HAVE 18 CHARACTERS
• BUSINESS RULE 6 : QTY UNIT
  • BUSINESS RULE 6.1 : QTY UNIT MISSING
  • BUSINESS RULE 6.2 : QTY UNIT NOT EXISTING
• BUSINESS RULE 7 : KEY FIGURE NOT IN THE GOOD FORMAT
• BUSINESS RULE 8 : DUPLICATED ENTRIES (NO ERROR BUT WARNING)

Program Output

f300-output_preview: Generate ALV grid to show Converted data from Excel.

f310-output_check: Generate ALV grid to show Converted data from Excel after check.

Program Load

f400-load_pchain: Check if process chain is already in progress.

f413-csv_file_data: Import Customer file in ALL11.

• Filename consumed by process chain PC_CO_IMEP_15 is hardcoded in this form:  "/exploit/BW/IMEP/non-sap_plant.csv".
• Flat file integrated manually by user, is saved as follow: '/exploit/BW/IMEP/' w_file '_' sy-sysid '_' sy-uname '.csv'.
• Where w_file is the filename on user's local pc, sy-sysid is the BW environment and sy-uname is the user name which is running the program.

f423-filename_data: Update Global filter master data with new file name.

f433-savelog_data: Update log after loading (DSO DBCOPP09 - "IMEP - Log Import (Non-SAP Plant) ( Direct Update )").

f440-finish_message: Pop-up message at the end.

f453-send_email_data: Send an email after data loading.

Program Log

f500-display_log: Display log.

Main Chains

Sub  Chains

Other Chains

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

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.

IMEP Glossary :

Main queries

Main functionalities

"Special" KPIs

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 

PC_CO_IMEP_15