Products without composition requirements

Objective

The composition of every raw material, semi finished and finished good has to be described in Composition Database. This is a pre-requisite in order to assess its regulatory compliance.

Raw materials may have a lower ratio comparing with the BU/Enterprises because it’s often difficult to get the whole composition from the suppliers.

The KPI should measure:

1. - Number of products without a composition in Compo Database

B - Percentage of products without a composition in Compo Database.

Calculation

1. 1. - Number of products without composition

A2 - Number of products which have a composition exclusively made of the 'Unknown' or 'Undefined' components.
"Undefined" corresponds to specification code "100000000000" and "Unknown" to "100000000001".

B - See A1 divided by the total number of products

Selections:

Remove from KPI data:

• Products which have a NAM PROD (language EN) with OBS are not taken into account.

• Authorizations group ALL.

Frequency

Process chain is started monthly every 1st day.

Target

Product with composition at 100% requirements

Objective

For a product, the sum of its components should be equal to 100 %.

Raw materials may have a lower ratio comparing with the BU/Enterprises because it’s often difficult to get the whole composition from the suppliers.

The KPI should measure:

1. - Number of products which composition is fully described in Compo Database.
   B - Percentage of products which composition is fully described in Compo Database

Calculation

1. 1. - Number of products having a 100% composition.
      A2 - Number of products having a 99.9% composition.
      A3 - Number of products having 99.9% composition * ithout 'Unknown' or 'Undefined'* component.

B - See A divided by the total number of products.

Selections :

Remove from KPI data:

• Products which have a NAM PROD (language EN) with * BS* are not taken into account.
• Authorizations group ALL.

Frequency

Process Chain is started monthly every 1st day.

Target

Number of 'GPP' Products without Dangerous Goods Master Data requierements

Extract from meeting minutes - 2009, 22 of september

> W8.2.2 : Number of products without DG Master data
> - Split by BU - Material being linked to commercial product
> - Only active materials (criterion ?)

How to access data

Get active materials (without deletion flag) with ‘DG indicator profile’ = ‘GPP’. Then get the related PROD_COM and BU.

MM03 – Material Master Date, Basic Data 2 view:

For each of the materials, verify that a Dangerous Goods Master Data exists for IMDG regulation, and that this master data is released and active at time of extraction (control on validity period to be done).

DGP3 – Dangerous Goods Master

Technically
(Use Product Axis to get Material data (MM) and commercial product data (EH&S)

1. Get materials from MARA table with LVORM <> ‘X’ (Deletion flag) and PROFL = ‘GPP’ (DG Indicator Profile).
2. Get corresponding PRCO{{footnote}}PRCO is built by concatenating 'PRCO' and 'MARA-WRKST (Basic Material)/footnote and BU also : access to ESTRH with SUBID = PRCO number to get AUTHGRP (Authorisation – meaning : BU)
3. For each of these materials, verify that a Dangerous Goods Master Data exists in DGTMD table.
   There are two controls to do :

• no DG Master data exists, whatever the regulation is
• no DG Master data exists for IMDG regulation

Access to DGTMD should be done considering :
o Material (MATNR) :come from material master data previously accessed
o Deletion Flag (DELFLG) : should be blank
o Valid-From Date (VALFR) : should be inferor to current date
o Valid-To Date(VALTO) : should be superior to current data
o Dangerous Goods Regulation (LWDG) : (according case – IMDG or others)
o Processing Status for Basic Data and Master Data (DGWOS) = ‘10’ (Released)

Suggestion of BW dashboard

• Number of materials which will be displayed in ‘No Reg’ column will be the number of materials with NO DG Master Data AT ALL (not even one regulation.)
• Number of materials which will be displayed in ‘No IMDG’ column will be the number of materials with no IMDG Dangerous Goods Master Data

Dataflow overview

Technical details

Extractor

The extractor is based on Standard Extractor called 0EHS_SPEC_MAT, with no enhancement n SAP ECC (RCS).

Detailed data : DSO_EHS01

The DSO EHS01 is used to store all data loaded from RCS as snapshot, so monthly all data available in RCS is loaded in order to keep the history in BW.

Transformation: RSDS 0EHS_SPEC_MAT WQ1_260 -> TRCS IFS_EHS_SPEC_MAT

The transformation is used to convert all Fields into InfoObject and the only one business rule used is to get the current day and set it as “Last Change On”.

Transformation: IFS_EHS_SPEC_MAT -> DSO_EHS1

The main business rules in this transformation are to consolidate all necessary data from Master Data and convert all data to the necessary formats.

In the start routine the code is getting below data in order to be used in the routines conversion:

• From Material Master Data the related Commercial product
• From Specification Master Data the related Authorization

In the conversion routines:

• Routines rules:
  Specification routine is used to check in Material Master Data if the specification contains the correct code or is the commercial product. The commercial product begins with “PRCO”. The idea is to clean unnecessary codes.
  Commercial Product routine gets the Commercial Product from Material Master Data.
  Authorization is get from Specification Master Data linked by Commercial Product from Material Master Data.
• Time Conversion rules:
  Calendar Month is taken from Last Change On
• Direct Assignments:
  For all other InfoObjects

Transformation : DSO_EHS1 -> DSO_EHS1

The main business rule in this transformation is to clean the Specification not assigned, so in the start routine the data is checked if there is no Specification and, if there is any other records with the same condition if yes, a new record is added with the option Delete assigned (Record Mode = “D”).

Aggregated data : DSO_EHS02

The DSO EHS02 is used to store the aggregated data with respective flags and metrics to be used in the reports.

Transformation: ODSO DSO_EHS1 -> ODSO DSO_EHS2

The transformation is used to aggregate the detailed data to the necessary level and delete unnecessary data from the report.

In the Start Routine the data deleted are:

• Authorization group = “ALL”
• Commercial Products with description like “* BS*” (Obsolete) for language “EN” (English).

In the routines:

• The Calendar month is set to previous one
• The flag for Commercial Product without Composition is set when the Specification is not assigned or start with “PRCO” with means that is value is the Commercial code, not the Specification (Composition).

Transformation: ODSO DSO_EHS2 -> ODSO DSO_EHS2

As the data is aggregated in DSO_EHS2, the transformation is used to set all missing flags.

In the Start Routine the DSO_EHS1 data is get to be used in the routines.

In the routines:

• The Flag for Specification at 100% (C_SPEC100) check if the key figure EHS_SPMA is 100 and if the Commercial product has composition, /BIC/C_PRCWCOM assigned
• The Flag for Specification at 99,9 to 100% (C_SPEC099) check if the key figure EHS_SPMA is grater than 99,9 and if the Commercial product has composition, /BIC/C_PRCWCOM assigned
• The Flag Unknown or Undefined (C_UNKNOW) check in ODS_EHS1 if the composition there is at least one record with these classification
• The Flag Only Unknown or Undefined (C_UNKNOW2) check in ODS_EHS1 if the composition there is only record with these classification

Detailed data : DSO_EHS3

In order to freeze the data related to KPI a DSO was created and snapshots from these data are stored.

Transformation: RSDS DTS_EHS_GPPWP1_400 --> ODSO DSO_EHS3

The business in this transformation can be divided in groups:

• Replacement fields to InfoObjects, simple rule “from to”.
• Commercial Product (C_PROD) assignment using a populated table in Start Routine using C_MATNR Master Data

Detailed data : DSO_EHS4

In order to frozen the data related to KPI, a DSO was created and Snapshots from these data is stored.

Transformation: IOJC C_MATNR -> ODSO DSO_EHS3

The business in this transformation can be divided in groups:

• Replacement fields to InfoObjects, simple rule “from to” for C_MATNR and C_PROD.
• 0CALMONTH is set to previous month
• EHS_AUTH is got from Commercial Product Master Data
• C_IMDG_FG and C_NORG_FG is got from DSO_EHS3

Summarized data: Infoprovider CUB_EHS03

Transformation: ODSO DSO_EHS2 -> CUBE CUB_EHS01

Transformation: ODSO DSO_EHS4 -> CUBE CUB_EHS01

Reporting area : Multiprovider MPR_EHS01

The MultiProvider MPR_EHS01 was created to be used for all reports and to prepare the application to use extra InfoCubes or any other InfoProviders

Exploitation

Necessary objects to load EHS KPI

error
To be done : original document in Eroom has information about the PP Objects not EHS
/error

Source system

Only one source system is used in this application : RCS Production WP1_400

Global filter

The global filter is used to filter out all unnecessary data, the load process check in this Master Data what is the Reference Date to clean the data. This process is to avoid unnecessary data in the Objects improving the load and report performance.

Global process chain

In case of loading error

If there are errors in the process chain no special actions should be done. The procedures to crrect are the standard ones.

Access authorizations

The security will be through BEx (Business Explorer Role). All users should have access to this role : ZR_RCS_KPI_A01

Queries

All queries can be found in the menu role ZR_RCS_KPI_A01.

• *

  Appendix

Comments and essential facts

Important tests

InfoCube Design
SAP recommends tha all dimensions not line item for performences purposes should be represent less than 20% of the fact table. In TCODE SE38, the ABAP report : SAP_INFOCUBE_DESIGNS show the design.