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's target cost, actual cost, the variance for each cost item in process order, the 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

Around 400 users worldwide.

Access to ZIMEP_FILE transaction for Flat File Integration is limited to Yoram Vandijk. In the short- to mid-term, access should be extended to a handful of users.

History

2018.04.25:

• Creation of C_ORIMAP3, in reference to C_MATPNT3, to collect Origin Group from PF1 table MBEW.
• Evolution of Main IMEP flow (CRCOPP01/04). Data is no longer separated by Index1, but in current data (CRCOPP01, M & M-1) and history (CRCOPP04, M-2 and older).
• Update of associated Process Chains to take this change into account.
• Creation of Program ZBW_IMEP004 to delete history data from DBCOPP01 after they have been moved to DBCOPP04.
• Update on how Real Factors are calculated in DSO DBCOPP10.

2018.03:

• Implementation of Cost Centers postings (CRCOPP06) & Cost Centers SKF postings (CRCOPP07) flows.
• Implementation of Cost Center Postings Budget Import (CRCOPP08) flows.
• Creation of Process Chains PC_CO_IMEP_32/33/34/35/36, for CC Posting Budget Import.
• Update of ZBW_IMEP002 to integrate CC Posting Budget Flat Files.
• Creation of C_CELTHX5, 5th and last level of XCS-ALL hierarchy in 0COSTELMNT.

2018.01:

• Creation of Process Chains PC_CO_IMEP_28/29/30, collecting Standard Key Figure Attributes and Texts from PF1.
• Implementation of Business Rules and Selective Deletion in InfoProviders for ZBW_IMEP002.
• Update of Flat File Integration structure - removed obsolete InfoProviders.

2017.12.21:

• Creation of C_KSTRG4 (Cost Object Hierarchy) and C_ETABR3 (R/3 Establishment)
• Implementation of new flows for above MDs
• Update of C_MATPNT2 to include above MDs as attributes
• Update of Flat File Integration structure

2017.11.21:

• Separation of Process Chains for daily loading for Current Month (events XXX) and Previous Month (events XXX_PREV_MTH) Loadings
• Implementation of Material Ledger Costing Split
• Implementation of Origin Split & Origin Group
• Implementation of Cost Element Group

Roles & Access

Roles and access

Authorization objects

List of authorization 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

PF1

Flat Files & WP1

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)

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

Table TKKH2 / Origin Group Texts in CO Object

This table exists on system PF1 and contains texts for Origin Group.

View ZBW_V_TKKH2 / Origin Group Texts

This view exist on system PF1 and references table:

View ZBW_V_CKPX / Cost Objects Hierarchies

This view exist on system PF1 and references tables:

• CKPE / CO-PC Cost Object Hierarchy: Individual Objects
• CKPH / Master Record: Cost Object ID Number
• CKPHT / Texts for CKPH

View contains all levels of Cost Object Hierarchy as attributes, as well as the associated texts.

View is filtered on CKPHT Language = English. (obsolete)

Tables are filled from table KKPHIE. (To be confirmed)

View ZBW_V_ETABR3 / Establishment Texts

This view exist on system PF1 and references tables:

At datasource level (PF1/WP1)

For PF1 only:

• DataSource DTS_ZBW_V_TKKH2, based on view ZBW_V_TKKH2, returns Origin Group Texts.
• DataSource DTS_ZBW_V_CKPX, based on view ZBW_V_CKPX, returns Cost Object Attributes & Texts.
• DataSource DTS_ZBW_V_ETABR3, based on view ZBW_V_ETABR3, returns R/3 Establishment Texts.

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)

Cost Element Texts (0COSTELMNT) & Statistical Key Figure (0STKEYFIG)

Some Cost Elements do not fit the standard format for this Master Data - coded on 6 characters, they stand for Statistical Key Figures that are not used.

Because these Cost Elements do not exist in hierarchy CHEFXCS-ALL, values for attributes C_CELTHX1/2/3/4/5 are collected through Flat File flow based on DataSource DTS_FMCO_0COSTELMNT_01.

Statistical Key Figures are loaded using generic datasources 0STKEYFIG_ATTR (Attributes) and 0STKEYFIG_TEXT (Texts).

Texts from Statistical Key Figures are then copied in Cost Element texts.

Generic datasources exist in SOLVAY PF1 Dataflow only.

At business level (WBP)

GBU (CPFCTR1_2)

The GBU available for reporting is BFC Global Business Unit (CPFCTR1_2)

• For RCS WP1 data, the GBU is taken from the Profit Center (Navigational attribut 0PROFIT_CTR__CPFCTR1_2)

• For Solvay PF1 data, the GBU is calculated at Business Level following below rule
  
  Case 1: Profit Center (0PROFIT_CTR) & Company Code (C_COMPCDE)are filled

  Case 1a: Profit Center is 10 characters long + starting with 'F' + plant is filled

  • Concatenate Profit Center, Company Code, Plant
  • Read MasterData Technical Business Area (C_TECHBA) and get GBU (CPFCTR1_2)

  Case 1b: Profit Center on 5 positions starting by 'D' 

  • Concatenate '00000', Profit Center, Company Code
  • Read MasterData Technical Business Area (C_TECHBA) and get GBU (CPFCTR1_2)

   Case 2 : Plant (C_PLANT) & Material (C_MATPNT2) are filled

  • Read MasterData Material Plant (C_MATPNT2) and get Profit Center (0PROFIT_CTR)
  • Then apply Case 1a and Case 1b

   Case 3: Controlling Area (0CO_AREA), Cost Center (C_COSTCTR) are filled

  • Read MasterData Cost Center (C_COSTCTR) and get GBU (CPFCTR1_2)

Exclude activity and Balancing movements (C_EXACBMO)

The flag is set to 'X' when :

• cost element, first 2 positions = '98'.
• index 1 = '9' and origin, first 2 positions = 'KL'.

This rule is settled in transformation at Business Level for SOLVAY PF1 only

The flag is set to 'P' (Produced Component) when Index1 = 3 and Origin exists as an Index1 = 1 Material in the source package.

This allows users to filter out lines where a component of a Material already exists as a Material, to avoid counting the associated key figures twice.

This rule is settled in transformation at Business Level for both SOLVAY PF1 and RCS WP1.

Material Ledger Costs Split (K_MLWRT)

For SOLVAY PF1 (DBCOPP01/04) and Flat Files (DBCOPP03), Material Ledger Costs are split between 3 components:

• Material Ledger Fixed Costs (K_ML_FC)
• Material Ledger Variable Costs (K_ML_VC)
• Material Ledger Dependencies (K_ML_DEP)

From Flat File, for index1 = 3 or index1 = 9, we check that K_MLWRT is not null.

At all times, K_MLWRT = K_ML_FC + K_ML_VC + K_ML_DEP.

The same split has been added to RCS WP1 (DBCOPP02/05) for MultiProvider assignment, based on Cost Component Group 0CCOMPGRP.

Origin Split (C_ORIGIN)

In DBCOPP01/04 (SOLVAY PF1), Origin details have been split between 5 infoObjects:

• Origin Activity Type (C_ORICACT)
• Origin Cost Center (C_ORICCTR)
• Origin Order (C_ORICORD)
• Origin WBS Element (C_ORICWBS)
• Origin Material (C_ORIMAT)

Their value is dependent on the Index1 value and C_ORIGIN structure:

• For index1 = 1 or 3, C_ORIMAT = C_ORIGIN+12(18). For index1 = 5 or 7, it is the same but first we check that LOGSYS/C_ORIGIN exists as C_MATNR2.
• For index 1 = 5 or 7, C_ORICACT = 0ACTTYPE (Activity Type) and C_ORICCTR = C_COSTCTR (Cost Center)
• For index1 = 9, depending on the first 2 characters of C_ORIGIN:
  • When 'KL', C_ORICCTR = C_ORIGIN+6(10) / C_ORICACT = C_ORIGIN+16(6)
  • When 'KS', C_ORICCTR = C_ORIGIN+6(10)
  • When 'OR', C_ORICORD = C_ORIGIN+2(12)
  • When 'PR', C_ORICWBS = C_WBS_EL2 where C_WBS_EL2__C_OBJNR = C_ORIGIN+0(10)
  • When '00', C_ORIMAT = C_MATNR2

The same split has been applied to DBCOPP02/05 (RCS WP1), with simplified rules:

• For Index1 = 1 or 2 or 3, C_ORIMAT = C_ORIGIN+12(18).
• For index 1 = 5, C_ORICACT = 0ACTTYPE (Activity Type) and C_ORICCTR = C_COSTCTR (Cost Center)

Origin Texts

Origin Texts are collected from PF1 and WP1. Loads are included in Main Chains and thus happen daily on Current Month (and Previous Month from 01 to 08 of each month).

Because of a large amount of missing texts, a corrective DTP runs every day to collect texts from other Master Data, once more based on the first 2 characters of C_ORIGIN:

• When 'KL', Short Text from C_COSTCTR & ' / ' & Medium Text from 0ACTTYPE
• When 'KS', Medium Text from C_COSTCTR
• When 'OR', Short Text from C_COORDER
• When 'PR', Medium Text from C_WBS_EL2
• When '00', Medium Text from C_MATNR2

There is also a special case where text exists but must be replaced: If INDEX1 = 5 and Text begins with 'ATY', apply the same text as 'KL' Origins.

Origin Group (C_HRKFT)

Origin Group is collected as a subchain of CO Key Subnumber (C_COKSNB)

Origin Group Texts are collected from SOLVAY PF1 by datasource DTS_ZBW_V_TKKH2.

Origin Group is also collected as attribute of C_ORIMAP3, infoobject created in reference to C_MATPNT3 and identical to C_ORIMAT in our data. That Origin Group, C_ORIMAP3__C_HRKFT, is collected from SOLVAY PF1 by datasource DTS_MBEW_01.

Total Actual Quantity Conversion

Total Actual Quantity is converted to fill the values of the following attributes of Activities DSOs (DBCOPP04 for SOLVAY PF1, DBCOPP05 for RCS WP1):

• Total Actual Quantity Standard (K_ACQTSTD)
• Total Actual Quantity in EP (K_ACQTYEP)
• Total Actual Quantity in Scope 1 in CO2 (K_AQT1CO2)
• Total Actual Quantity in Scope 2 in CO2 (K_AQT2CO2)
• Total Actual Quantity in Scope 3 in CO2 (K_AQT3CO2)

Conversion is based on Real Factors DSOs (DBCOPP10 for PF1, DBCOPP11 for WP1) and ZBW_V_CO2_COEFFS DSOs (DBCOPP07 for PF1, DBCOPP08 for WP1).

If coefficient Real Factor Conversion (K_RFACONV) exists in Real Factors DSO, TAQ Standard and TAQ in EP are calculated using that coefficient. Otherwise, they are calculated using Local To Standard UoM Conversion (K_UOMCONV) and Primary Energy Coefficient (K_ENGCOEF), respectively, from ZBW_V_CO2_COEFFS DSO.

TAQ in CO2 are always calculated using coefficients CO2 Emission Scope (K_CO2EMI1/2/3) from ZBW_V_CO2_COEFFS DSO if they exist.

Master Data Cost Element (0COSTELMNT)

CHEFXCS-ALL Hierarchy Levels are stored in Master Data Cost Element, in attributes C_CELTHX1 to C_CELTHX5.

Levels are stored as follow:

Hierarchy Level 1 is always "XCS-ALL" and thus not stored.

Dependencies with other applications

(None known)

Data loadings

Info providers and objects loaded

Global Filters (C_GLBFILT) used in Chains

ABAP Programs used in Chains

Further explanations for program ZBW_IMEP001

Further explanations for program ZBW_IMEP002

Interface

User must first indicate whether he is loading a Planned Data Budget File (Target: CRCOPP03, Event/Process Chain launched: PC_CO_IMEP_15) or a Cost Center Postings Budget File (Target: CRCOPP08, Event/Process Chain launched: PC_CO_IMEP_32). Only one type of file can be loaded at once, and both types have different format.

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.

Preview is color-coded: green entries are correct, while yellow ones return warnings and red ones return one or more errors.

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

If errors and warnings exists, they will be listed with a description of the error at the end of each line.

Once the file content is checked and all errors corrected, the user can load the file to BW application server (AL11) and raise the event associated with the type of import they chose by clicking on "Load file" icon.

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

 The event PC_CO_IMEP_32 triggers the process chain PC_CO_IMEP_32 - "IMEP: META - T - Main (CC postings) (Flat Files)".

Either process chain will load the user's file data into IMEP BW application.

 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 forms:

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, only for Planned Data Budget Files:

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

• BUSINESS RULE 1. VERSION VALUE - IMEP_BR1 (Rejection Code)
  BFR06 (Budget Forecast) or Byy (Yearly Budget, where yy between 00 and 99)

• BUSINESS RULE 2. FISCAL YEAR VALUE - IMEP_BR2
  Year, between 1900 and 2999

• BUSINESS RULE 3. PERIODVALUE - IMEP_BR3
  Month, between 01 and 12

• BUSINESS RULE 4. INDEX VALUE - IMEP_BR4
  Index is 1 (Produced material), 3 (BOM Component) or 9 (SKF/Direct Posting)

• BUSINESS RULE 5. COST OBJECT EXISTS - IMEP_BR5
  Check DSO DBCOPP13 for Cost Object. Empty Cost Object is accepted too.

• BUSINESS RULE 6. COST ELEMENT EXISTS - RK14_2
  Check Master Data 0COSTELMNT for Cost Element with Controlling Area CHEF and Level 1 Hierarchy XCS-ALL

• BUSINESS RULE 7. COST CENTER

  • BUSINESS RULE 7.1. COST CENTER MANDATORY FOR INDEX 9 - RK3_1

  • BUSINESS RULE 7.2. COST CENTER EXISTS - RK3_2
    Check Master Data C_COSTCTR for Cost Center with Controlling Area CHEF

• BUSINESS RULE 8. ORIGIN

  • BUSINESS RULE 8.1. ORIGIN MANDATORY FOR INDEX 3 - IMEP_BR8_1

  • BUSINESS RULE 8.2. ORIGIN EXISTS (as MATERIAL) - IMEP_BR8_2
    Check Master Data C_MATNR2 for Origin with Source System PF1_020

• BUSINESS RULE 9. UNIT EXISTS - RD12_2
  Check Master Data 0UNIT for Unit

• BUSINESS RULE 10. CURRENCY EXISTS - RD11_2
  Check Master Data 0CURRENCY for Currency.

• BUSINESS RULE 11. KEY FIGURES VALUES - IMEP_BR11
  For index 3 and 9, check that Material Ledger Costs are not null (Sum of Fixed Costs, Variable Costs and Dependencies)

• BUSINESS RULE 12. DUPLICATE ENTRIES (WARNING) - RD14

f230-check_file_cc: Check content of the file as follow, only for Cost Center Postings Budget Files:

Info: Business Rules sharing the same name are identical in both "check_file" forms.

• BUSINESS RULE 1. VERSION VALUE - IMEP_BR1 (Rejection Code)
  BFR06 (Budget Forecast) or Byy (Yearly Budget, where yy between 00 and 99)

• BUSINESS RULE 2. FISCAL YEAR VALUE - IMEP_BR2
  Year, between 1900 and 2999

• BUSINESS RULE 3. PERIOD VALUE - IMEP_BR3
  Month, between 01 and 12

• BUSINESS RULE 6. COST ELEMENT EXISTS - RK14_2
  Check Master Data 0COSTELMNT for Cost Element with Controlling Area CHEF and Level 1 Hierarchy XCS-ALL

• BUSINESS RULE 7. COST CENTER

  • BUSINESS RULE 7.2. COST CENTER EXISTS - RK3_2
    Check Master Data C_COSTCTR for Cost Center with Controlling Area CHEF

  • BUSINESS RULE 7.3. PARTNER COST CENTER EXISTS -  IMEP_BR7_3
    Check Master Data C_COSTCTR for Cost Center with Controlling Area CHEF

• BUSINESS RULE 9. UNIT EXISTS - RD12_2
  Check Master Data 0UNIT for Unit

• BUSINESS RULE 10. CURRENCY EXISTS - RD11_2
  Check Master Data 0CURRENCY for Currency.

• BUSINESS RULE 12. DUPLICATE ENTRIES (WARNING) - RD14

• BUSINESS RULE 13: PARTNER ORDER EXISTS - IMEP_BR13
  Check Master Data C_COORDER for Cost Order with Source System %F1_020
• BUSINESS RULE 14: PARTNER WBSE EXISTS - RK27_2
  Check Master Data C_WBS_EL2 for WBS Element with Source System %F1_020

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/IMEP_flat_file.csv".
• Filename consumed by process chain PC_CO_IMEP_32 is hardcoded in this form:  "/exploit/BW/IMEP/IMEP_cc_flat_file.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 once the program's operations are complete.

f453-send_email_data: Send an email after data loading.

f463-delete-obsolete-data: Selective deletion of data in either DPCOPP03/DBCOPP03/CRCOPP03 or DPCOPP04/DBCOPP14/CRCOPP08 based on Version (C_VERSF) and Fiscal Period (0FISCPER).

Program Log

f500-display_log: Display log.

Further explanations for program ZBW_IMEP003

Further explanations for program ZBW_IMEP004

All DSOs and Cubes listed in the program variant will be cleared of all M-2 data and older, leaving only Current and Previous Month.

Main Chains

SAP events detail

PF1:

Z1C_RUNDMC_KOST for current month update

Z1C_RUNDMC_KOST_PREV_MTH for previous month update

WP1:

ZWPP_RUNDMC_KOST for current month update

ZWPP_RUNDMC_KOST_PREV_MTH for previous month update

Flat Files:

PC_CO_IMEP_15 for every Budget update

PC_CO_IMEP_32 for every CC Postings update

No chain runs on Sunday.

Sub  Chains

Loading frequency

IMEP is loaded daily. Previous month is loaded from 01 to 08 only while Current month is loaded from 09 to the end of month.

Events on Solvay ECC (PF1) and RCS (WP1) start BW Process Chains. These events are not expected to run on Sundays.

Flat Files (Excel file) can be loaded manually in transaction ZIMEP_FILE, at will.

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

Business requires 3 years of historical data in addition to current year. (Y to Y-3)

Cubes contain data since 2017. Historical data beyond this is stored in Propagation/Business level.

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

Older data are deleted from DSOs/Cubes at the end of the RCS and Solvay process chains (PC_CO_IMEP_01/08/20/25).

Data availability for go live (01.2017)

From Solvay PF1 : 2014 + 2015 + 2016

From RCS WP1: 2015 + 2016 (2014 was not available anymore as year was archived in WP1)

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

Reload data on a given period

1. Update data in C_GLBFILT (Stream = IMEP). You need to change the period in ***_LOAD and ***_DEL to the period you are using. 
   Depending on what you are reloading, *** is either SOLV or RCS:
   
2. The previous step is usually done by program ZBW_IMEP003 when the Process Chain starts. Thus, you need to disable the variant used in the PC to keep the period entered manually.
   To do so, open the Process Chain you will use for the reload (PC_CO_IMEP_01 for Solvay and PC_CO_IMEP_08 for RCS) and check the first program.
   Variant will always be ZVAR_PER_***:
   
   Open the variant to Change it, check the "Initialization?" button:
   
   Save and leave. Don't forget to come back to uncheck the button once you are done.
3. Run the Process Chain using Function Module (SE37) RSPC_API_CHAIN_START, keep an eye on the process.

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