General presentation

Objective of the application

ARTIST tool is composed of 3 BW reports whose aim are to:

Provide to GBU’s Product Stewardship team automatically updated relevant reports (volumes + REACH data), intended to facilitate REACH audits performed either internally or by national enforcement bodies

Help GBU’s Product Stewardship team to identify easily missing REACH information on Raw Materials and on Marketed Products which are bought or manufactured, based on effective volumes and flows

Consolidate in SAP-EHS (CG02 transaction) all information giving the REACH regulatory status for any Solvay substance, especially :

Legal Entity
CLP notification
REACH pre-registration and registration status

as well as basic REACH information of couple (Raw Materials;supplier).

Wiki EHS support: https://sites.google.com/a/solvay.com/wiki-ehs-support/wiki/reach-reports-artist

Reporting Coordinator: Célia Gonzalez-Roux

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

Role Code

Role Description

Explanation

ZR_RCS_CA_M38

EHS Reach - ARTIST Reports

Role menu for ARTIST reports

ZBI_RCS_EHS_A02

Environment, Health and Safety Analysis - End User Role

Application Role:

End User rights
gives access to infoproviders of Infoarea "AREA_EHSTR" (EHS - Transactional Data)
BI Analysis Authorization "ZBI_EHS" ("*" for authorization objects not relevant for the application)

Authorization objects

Link to the BW Catalog of role

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

Dataflow overview

Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.

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

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

Detail of process chain, list + link between or special event done for the loading

Loading frequency

Detail of frequency : monthly; weekly or else

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

Key Figure	Estimation
~ 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

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

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

List the most important and complex queries only with a link to the documentation

Main functionalities

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

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

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