General presentation

Objective of the application

EHS stands for Environment, Health and Safety. The Goal of EHS is to protect employees, the public, the environment and to comply with applicable laws and protect the Company's reputation. EHS departments, of some companies are responsible for environmental protection, occupational health and safety. 

This application described below concerns one of EHS goals : Reporting for Substance Volume Tracking (SVT)

In many countries, regulations state that, above a certain quantity of chemicals and other hazardous substances, you must register with the authorities the maximum quantities of these substances that you plan to purchase, import, produce, sell, or export within a certain period. Substance volume tracking helps you to comply with the relevant regulations by recording the quantities of substances needing to be tracked that you purchase, import, produce, sell, or export. By comparing the recorded quantities with the limit values, the system can warn you in good time before a limit value is exceeded

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

Usage information

Around 90 users, worldwide. Each country can only report on its data.

History

2014 - SVT Roll Out Asia/Turkey => KT document "SVT RO // Knowledge Transfer" => https://drive.google.com/open?id=1yWblSq3wGJGdm-T7D97nWF3I7Ufeawe-HYb91RmZ26Q

2015 - SVT Roll Out Europe/USA/Canada => KT document "EHS-SVT-Documentation" => https://drive.google.com/open?id=1W-NDge82ePPYy4fBiMhr57DVYeBxzRsuyPxjK1ZWQuM

other usefull link

WIKI EHS : https://sites.google.com/a/solvay.com/wiki-ehs-support => access to ask to Vincent Desthieux or Marie Flourie

SVT Asie - Initial Specifications : https://drive.google.com/drive/folders/0B0ImB7CVmt8kSzFwazBDNmlXQjQ

SVT Asie - Mockup (Convergence Project) : https://drive.google.com/open?id=0B0RFolMcqblIfllIN2xHSnR6Sm00T2E4UXZhdjhEd1ZNMC1tUGJDc29tRVFLU2p1SEhaZmc

SVT Roll Out Asia/Turkey - Knowledge Transfer (SVT Solution before deploiement US/CA/EU) : https://drive.google.com/open?id=1yWblSq3wGJGdm-T7D97nWF3I7Ufeawe-HYb91RmZ26Q

Roles & Access

Roles and access

Usefull to know :

1- Menu Roles ZR_RCS_CA_M40 “EHS – Substance Volume Tracking Asia” and ZR_RCS_CA_M36 “EHS – Substance Volume Tracking North America” are now obsolete.

There are replaced by ZR_RCS_CA_M48.

2- Perimeter roles ZBI_RCS_EHS_P06 to ZBI_RCS_EHS_P12 are obsolete because Authorization Team has decided to use naming ZBI_xx_EHS_P06 (xx = country)

3- Perimeter roles ZR_RCS_EHS_P06 to P09 and P11, P13 to P15  are obsolete because old naming.

Usefull to know concerning BUTA Chimie (Company Code ZFR9) : 

A filter on C_PLANT from authorization has been added in all SVT queries :

• variable V_AUT_C_PLANT_0001 for EU report as the Plant is a selection criteria

• variable V_C_PLANT_0001 for all other as the Plant is not a selection citeria

The C_PLANT will have to be removed in object ZBI_SVT (Application Role ZR_RCS_EHS_A07) 

 Following perimeter role will have to be managed for all EHS SVT users :

• For all plants, except BUTA, use perimeter role ZR_TOUT_CA_P02 / object ZTOUTCAP02

• • For BUTA plants, use perimeter role ZR_7866_CA_P02 / object Z7866CAP02

The BUTA data will have to be loaded in cube REACH (SVT Analysis - EU (Rhodia) / CREHS06).

Usefull current authorization matrix

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

Authorization objects

List of autorisation objects mandatory for the application.

Dataflow overview

The dataflow is in the following document : EHS-SVT-Documentation https://drive.google.com/open?id=1W-NDge82ePPYy4fBiMhr57DVYeBxzRsuyPxjK1ZWQuM

Old Dataflow:

Generic dataflow

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

Scenario Determination (C_SCEN)

Unit conversions

The Unit conversion is done in the Bex queries (Quantity Conversion Type), depending on reports

• Reporting in pound (LB) for US
• Reporting in kilogram (KG) for Canada
• Reporting in Ton (TO) for all others

Transactionnal data are stored in material base unit, except of SPRINT Reception quantities (PO Unit)

• if base unit / po unit is managed in dimension MASS, conversion within table T006 works well

• if base unit / po unit is not managed in dimension MASS, conversions for KG/LB/TO have to be managed on ERP side (MM03 / Alternative Conversion).

Example : production done on unit KRE; other used units 1KG, M2, M3, KN3...

There are many "special" units on Solvay ERP.

Important : 

Quantities are not converted when loading data, and are not store into cubes (The conversion is done when running the report)

So, if a conversion is missing for a material ask the material referent to 

1- manage the conversion on ERP Side by managed the material master (MM03) / unit of measure tab

2- the day after, when the DSO UOMCMAT2 is filled, the conversion is applied in the reports. It applies to whole data without any reloading.

For manual loadings, ouside of current loading: be careful with large extraction on those loadings, job can use a lot of memories on the system and generate locks and dumps. 

It is better to launch those loadings after or before closing periods. If not possible to wait,  load on a few month time perimeter only, and not a long period.

With short time execution, loadings are OK and there is no issues.

MasterData Threshold Limit (C_THRHLD) & Attributs and descriptions

 Attributs were loaded from a flat file (by Jonathan in mai 2014)

Text were filled manually for Asia, and Reach.

ABAP programs & functions

ZBW_EHS001 - EHS - SVT - Selective Deletion on DPEHS006 Based on year

This program deletes data on DSOs  and ADSO identified (not necessarily on DPEHS006 - program's text should be changed) in the selection criterium.

It deletes data regarding the variables values in the Global Filter (C_GLBFILT) for Stream EHS, and Rule DATA* for old dataflow, or for new dataflow Stream EHS_SVT Rule DATA_LOAD.

This program is used in the main process chain with following variants

At execution, on selection screen, we choose data to delete: Japan, Australia or other. 

If it concerns new dataflow, "Generic Dataflow ?" should be selected.

It it concerns TSCA dataflow, used in a specific process chains (PC_EHS_SVT_GENFLW_TSCA, PC_EHS_SVT_OLD_FLW_TSCA), "TSCA dataflow must be selected.

It it concerns ADSO of propagation layer, "ADSO Propa" must be selected.

ZBW_EHS002 EHS-SVT Determination of time intervals for loadings

This program updates variables in  the Global Filter (C_GLBFILT) for Stream EHS, and Rule DATA*

The intervals of months are determined using the current date (SY-DATUM).

Notice that if variable exist in C_GLBFILT but is not checked in the program, the variable will be updated to inactive (attribute C_ACTIVE changed to 'N'). 

Caution : if the option 'Do not update MD Global Filter' is set, values will have to be modified manually in the masterdata when changing year

This program is used in the main process chain with following variants

This program is not used on generic dataflow

ZBW_EHS003 - EHS - SVT - Selective Deletion on DPEHS008 and DSO_EHS5 about compositions data based on current year

This program deletes data in business DSOs identified in the selection criterium.

It deletes data regarding the current year based on actual date (sy-datum).

This program is used in the main process chain with following variants:

This program is not used on generic dataflow

ZBW_EHS001_GET_COMPOSITION  - Get Composition Data

This function is used in transformation loading DSO_EHSR (for RCS) and DBEHS005 (for Solvay) which are Flow data with compositions

It read the composition/regulatory list from DSOs DPEHS00800  (for Solvay)  or DSO_EHS5 (for RCS)

Import parameters :

• Material (C_MATNR2)

• Calendar Year (CALYEAR)

• Country key (COUNTRY)

• Source System (LOGSYS)

This program is not used on generic dataflow

Dependencies with other applications

EHS SVT is adding EHS information on transactional data : Purchasing (Application SPRINT), Production, Sales (OBAS)

Data loadings

Info providers and objects loaded

Main Chains

Slave Chains

Other Chains

Loading frequency

The application is done weekly on saturdays at 10 am and wednesday at 10:00am

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

Currently data from 2012 to current year

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

For EHS SVT, queries have been developped, but for each query, an analysis workbook has been settled => only one access mode.

All queries/workbooks are published in an unique role menu “EHS – Substance Volume Tracking” (ZR_RCS_CA_M48)

New Query: SVT Report-Notification of nanomaterials Europe (core query) => BW_QRY_MPR_EHS07_EU_0002

NB : Following queries  are not yet available as workbook (not part of convergence project), a freshdesk has to be created by the Business Team.

• EHS - Imported Material without Composition (Core query) => BW_QRY_MPR_EHS02_0005
• EHS - Imports List by Material (Core query) => BW_QRY_MPR_EHS02_0004
• EHS - Imports list from GTS (Core query) => BW_QRY_MPR_EHS02_0002
• EHS - Imports List by Substance (Core query) => BW_QRY_MPR_EHS02_0006

All reports have following common filtrers

• Country of Origin (C_CNTRY_O) = autorisation

• Tracking Flag (C_TRCKFLG) = 'Y'

• Component Type Exclusion (C_IMPFLG) = 'N'

• Material Exclusion Flag (C_EXCLUSI) = 'N'

• Chemical reaction <> 0 'NO'

All reports have following condition 

• Quantites PRO >= 0
  
  

 Here are the different filters for each report

Main functionalities

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

Broadcast

The broadcast are run every Wednesday and Saturday, via the chain PC_EHS_014, which is included in weekly main chain PC_EHS_005(Saturday) and PC_EHS_NA_001 (Wednesday)

 For Broadcast diffusion, it has been decided to split broadcast by company code using Bursting option for Broadcast

Link to bursting documentation https://docs.google.com/document/d/15DaFZFEcYsfZc98zzlox-J3QaCYbbGsMTd7GxbSHOMM/edit#heading=h.fct6jj0qa4s

Availables broadcast

ONLY the US BroadCast is available.

Other broadcasts will be implemented later by BW maintenance team, via freshdesk process.

US Broadcast rules

Aim : hold alert for the first expedition, for a tracked substance, a company code, a destination country within the same year.

Alert limited to :

• regulatory list US_T12B

• scenario EXP

• country of origin US + PR, GU, VI, AS , MP

• country of destination (ship to) diffrent from US = US + PR, GU, VI, AS , MP

Additional rule :

The delivery creation date has to be the same year as goods issue date.

Other info for futur broadcast

For other broadcast, another rule will be used to define a threshold for each regulatory list.

 Stream EHS / Rule SVT_LIMIT : One threshold by regulatory list

 To harmonize threshold, all should be set to 80% except Turkey which is 100%

No threshold for reg list ZUS_T12B (threshold = 1st expedition)

Maintenance

Known bugs

See freshdesk for current bugs and evolutions

Recurring procedure

Reloading Japan & Korean usages

  => see Japan & Korean usage paragraph 

Reloading data for a specific year

The chain PC_EHS_MAIN_HIST_LOAD / EHS - Master Chain Hist Load can be used to reload data without using global filters values, and without reload referentials Dsos.

DSOs deletion are included in the chain.

Global filters C_GLBFILT has to be settled previously

=> stream EHS / rule DATA*

Reloading historical reference for Composition / regulatory list (DSO_EHS5 for Rhodia side / DPEHS008 for Solvay side)

Composition/Regulatory list are not historized by year in system sources RCS nor Solvay (only current situation), whereas in BW we need to freeze the composition by year.

For every loading, we consider that extracted data corresponds to the current year.

caution : this procedure has never been done. "Real" historical composition data can not be re-determine. In case of a reloading you will only use the current composition, and associate it to the wanted year.

If the current compositions have to be applied to a previous year, you have to :

• delete the wanted year in the DSO (in case of a mistake, the "real historical composition can not be re-determined)
• change the global filter for Stream EHS / Rule = wanted DSO
  First line has to be activated with Active = Y
  Second line has to be filled low = wanted year and Active = Y
  
• Run IP and DTP to load the wanted DSO
• Do not forget to change the global filter afterwards
  First line has to be desactivated with Active = N
  Second line has to be desactivated also with Active = N

Broadcast

If you need to add/change a google group for existing broadcast :

Enter/Modify

• google group id

• google group email

C_Group : Google Group (BCast SVT)

This masterdata is used to store Google Group / E-mail adresse

Caution : only Solvay email addresses

If you need to add/change link company code/google group :

Enter/Modify

• stream EHS

• rule SVT_CC_GRP

C_GLBFILT : (Global Filter)

Low contains CompanyCode\source system,\regulatory list

example 4290\PF1_020\ZUS_T12B

High contains the corresponding google group id

Legal Entities  identified for 2015 

Legal Entities added in 2016 - UR 343945 - add 6062 / ZFR3 - added the 20/01/2016, so applied for 2016 alerts only

Planned Evolution

Broadcast for other countriies

See also freshdesk for other evolutions