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 offers a set of reports about EHS specifications and documents.

Assessment Report FFS: https://drive.google.com/open?id=1GMdZG9r5NZTGLFTTp-R0dIg9AGv5vYcNDOksMO204_A

Shared Pure Sub BUR: https://drive.google.com/open?id=1-LzduYSYn6ZepXOemnTzB5nsC8fbYpOsGs9AtCgfJQU

Report Shipping FFS: https://drive.google.com/open?id=1335-xQFGQLE4V1QMHN-rTDzQkDVq3lhEJJCb8LSxH2Y

Tool Leader + IT leader of the application: 

Reporting Coordinator: Célia Gonzalez-Roux

Usage information

Around 50 users. Some reports are only for the use of the EHS Admin team (Role menu EHS - Admin).

History

Roles & Access

Roles and access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Authorization objects

Link to the BW Catalog of role

https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I

Dataflow overview

Reporting documentation drive folder:

https://drive.google.com/open?id=0B03hryo6pwqdTUtSSldyOXB0U1k

Functional and Technical rules

Rules & Explanations

Assessments dataflow:

SAP system logs all the changes that are made within the Specification Management (changes on substances properties, compositions…). This flow extracts these changes, that are updated in the table EST_CHANGE_DOCS using the program RC1_CHANGE_DOCS_GET.

Data model:

Zone determination (R1)

General case: the zone is obtained from the characteristics (C_ATWRT) attribute.

Special case: if the modification type is "Delete" and the characteritic value is empty, the zone is obtained from the Value Assignement Type (C_ESTCAT) attribute.

PURE_SUB determination when LIST_SUB inheritance (R2)

Some data are managed at LIST_SUB level and transfer to the PURE_SUB by inheritance link. In that case, the modification recovered in EST_CHANGE_DOCS table is at LIST_SUB level but not at PURE_SUB level. 

 In order to recover the LIST_SUB modifications at PURE_SUB level, the inheritance link are extracted into BW (DSO_EHSG). Each modification at LIST_SUB level is duplicated for each corresponding PURE_SUB. The LIST_SUB specification is kept in infoobject EHS_SPEC and the PURE_SUB specification in infoobject C_SPEC2. The flag "Inherited data" (C_SUBFLG) is filled.

Modification type (R3)

TODO

Instance ID determination (R3)

The instance ID on the lines concerning changes on characteristics value or usage is not filled in the table EST_CHANGE_DOCS. That is why the instance ID is determined in the extractor from ESTVA table. However, if the instance is deleted, the corresponding record is first flagged as "deleted" in the tables and then is physically removed from ESTVA. In consequence, to be able to retrieve the instance ID when the instance is deleted, we have to find it in the logs concerning ESTVA table changes => this is done by a look up in the propagation layer DSO DPEHS01 where tabname = "ESTVA".

Datasources customer exit:

• DTS_ZEST_CHANGE_DOCS (R4): 
  - determination of the instance (zzord) from table ESTVA. If this instance can't be determined because it was deleted from the table, a look up is done in BW (cf. Instance ID determination (R3))
  - determination of the usages (zzusage) from table ESTDU. If there are several usages, they are concatenated in the same field. The usages are not determined for lines with tabname = "ESTVA" or "ESTCAT" when they are deleted.

Legal and Standard Compositions dataflow:

Master Data dataflow:

Characteristic (C_ATWRT):

Attributes: 

C_ATWRT attributes are loading from a flat file.

The file contains 2 informations :

• Magnitude Geographie / Zone (C_ZONE): it contains 

The file loading is not scheduled.

Flat files :

Value Assignment Type : 

Characteristic : 

Dependencies with other applications

Data loadings

Info providers and objects loaded

Loading frequency

Average performance

Record Keeping

Reporting

Queries End User Documentation

Main queries

Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution