Access Management 

DataFlow

Overview

Technical Rules on Workbench

Rules & Explanations

Main documentation:

Preparation

Kickoff

Project Quality Plan

Design Validation

Design

Functional Specification

Map of Datasources

Profiles Management

Queries Definition

Technical documentation

Deployment

E Learning

Rule to take the GBU code

Read the field C_SUBACT2 (profit center) from master data C_MATPNT3 using plant and material as key.

      SELECT  logsys
              /bic/c_plant
              /bic/c_matpnt3
              /bic/c_pfctr1
              /bic/c_subact2
              co_area
          INTO  TABLE itb_matpnt2
          FROM  /bic/pc_matpnt3
         FOR ALL ENTRIES IN itb_dpsdtr02
          WHERE /bic/c_plant   = itb_dpsdtr02-c_plant
            AND /bic/c_matpnt3 = itb_dpsdtr02-c_matpnt2
            AND logsys         = itb_dpsdtr02-logsys
            AND objvers        = 'A'.

        READ TABLE itb_matpnt2 INTO itb_matpnt2_w
          WITH TABLE KEY logsys    = <result_fields>-logsys
                         c_plant   = <result_fields>-/bic/c_plant
                         c_matpnt2 = itb_dpsdtr02_w-c_matpnt2.
        IF sy-subrc = 0.
          <result_fields>-/bic/c_pfctr1    = itb_matpnt2_w-c_pfctr1.
          <result_fields>-/bic/c_subact2 = itb_matpnt2_w-c_subact2.
          <result_fields>-co_area           = itb_matpnt2_w-co_area.

Rule to determine the partner code

        IF itb_dpsdtr02_w-c_vendid  IS NOT INITIAL.
          <result_fields>-/bic/c_pnty3py     = 'VEND'.
          <result_fields>-/bic/c_3rparty  = itb_dpsdtr02_w-c_vendid.
          SHIFT <result_fields>-/bic/c_3rparty LEFT DELETING LEADING '0'          .
        ENDIF.
        IF itb_dpsdtr02_w-c_shiptid   IS NOT INITIAL.
          <result_fields>-/bic/c_pnty3py     = 'CUST'.
          <result_fields>-/bic/c_3rparty  = itb_dpsdtr02_w-c_shiptid.
          SHIFT <result_fields>-/bic/c_3rparty LEFT DELETING LEADING '0'          .
        ENDIF.

Rule to determine the departure and destination code

        IF itb_dpsdtr02_w-c_dpnode2   IS NOT INITIAL.

          <result_fields>-/bic/c_pntydp   = 'NODE'.
          <result_fields>-/bic/c_pntdp2    = itb_dpsdtr02_w-c_dpnode2.
        ENDIF.
        IF itb_dpsdtr02_w-c_dpshpn2  IS NOT INITIAL.
          <result_fields>-/bic/c_pntydp   = 'SHIPP'.
          w_shppnt   = itb_dpsdtr02_w-c_dpshpn2.
          <result_fields>-/bic/c_pntdp2    = w_shppnt.
        ENDIF.
        IF itb_dpsdtr02_w-c_dpplnt2  IS NOT INITIAL.
          <result_fields>-/bic/c_pntydp   = 'PLANT'.
          <result_fields>-/bic/c_pntdp2    = itb_dpsdtr02_w-c_dpplnt2.
        ENDIF.
        IF itb_dpsdtr02_w-c_dpvend2   IS NOT INITIAL.
          <result_fields>-/bic/c_pntydp   = 'VEND'.
          <result_fields>-/bic/c_pntdp2    = itb_dpsdtr02_w-c_dpvend2.
          SHIFT <result_fields>-/bic/c_pntdp2 LEFT DELETING LEADING '0'.
        ENDIF.
        IF itb_dpsdtr02_w-c_dpcust2   IS NOT INITIAL.
          <result_fields>-/bic/c_pntydp   = 'CUST'.
          <result_fields>-/bic/c_pntdp2    = itb_dpsdtr02_w-c_dpcust2.
          SHIFT <result_fields>-/bic/c_pntdp2 LEFT DELETING LEADING '0'.
        ENDIF. 

Rule to determine the reference month

        IF itb_dpsdtr01_w-dtcomplact IS NOT INITIAL.    " (shipment completion date)
          <result_fields>-rstt_rmnth = itb_dpsdtr01_w-dtcomplact(6).
        ELSE.
          IF itb_dpsdtr01_w-dtcompl_pl IS NOT INITIAL.
            <result_fields>-rstt_rmnth = itb_dpsdtr01_w-dtcompl_pl(6).     " (shipment planned completion date)
          ELSE.
            <result_fields>-rstt_rmnth = itb_dpsdtr01_w-erdat(6).     " (shipment creation date)
          ENDIF.
        ENDIF.

Unit conversions

The Unit conversion is done in the Bex queries (Quantity Conversion Type), after user chooses the unit conversion on reports

Transactionnal data are stored in sales 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).

There are many "special" units on Solvay ERP, ie: 1KG, 1TN, VKG, KRE, 

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.

The conversion type created by TIERS queries is QCT_MATNR4 (see below the setup for it).

BW Quantity Conversion

BW Updated Qty Unit by Material

Currency conversion

 
 The reports are all based on amounts in Local Currency Those amounts come directly from RCS/PF1. If user selects a currency in the prompt the query will convert, otherwise it will return the values in local currency. 

 The X rate considered is the Daily Month Average (M) rate (table managed by finance team, source ECB - European Central Bank) based on Document creation date.

• See private documentation on BW Currency Conversion

The current available rates applied to ALL data (even past data) independently of the date.

We applied conversion type Curr Conv based on M shpcst creation - CTK_MTIERS (see setup below) :
 

BW Currency Conversion

Determination of manual price change of shipment cost

The manual price change (C_MPROK1) is from the Shipment cost sub-items as below:
VFSI - MPROK in PF1 and WP1

Dependencies with other applications

• It shares extractors (2LIS_08TRTK, 2LIS_08TRTLP, 2LIS_08TRFKZ) with the legacy TR application for WP1 and PF1.
• It was created some master data in order to have the attributes shared with several applications: shipment doc, delivery doc and shipment cost item doc.
• Data is consumed by Qlikview dashboard. The loadings in QV are daily. It runs a fixed scheduled, the loadings must be finished when the next start.
• There is an integration with SPRINT (purchase schedule lines) to store there the service purchases (freight)
• There are links between TIERS and Value Stream and Industrial dashboard (both for Rhodia legacy)

• There is an integration with SPRINT to store the profit center (C_SUBACT2) for purchase services

Rhodia PO schedule lines (DB_PUSL1)

Solvay PO schedule lines (DB_PUSL2)

• There is an integration with Value Stream to store there the cost of transports

Rhodia CUB_VS (value stream)

• There is an integration with Industrial dashboard to store there the cost of transports

Rhodia CUB_DIPL (industrial dashboard)

Info areas

Master Data

Propagation Layer

Business Layer

Reporting Layer

Virtual Layer

Multi provider

1 - MVSDTR01 - Shipm & Delivery & Cost & Cond & PO/Inv (Sol&Rho)

Data Flow

Dimensions

Key figures

2 - MVSDTR02 - TR Vir: Shipment Events (Solvay & Rhodia)

Data Flow

Dimensions

Key figures

Main KPI calculations

Main functionalities

• E Learning - user guide
• Leaflet Impression
• Q&A Synthesis
• WeLearn Course Description

Main datasources based on SAP tables

• 2lis_08TRTK    – Shipment Header

• 2lis_08TRTLP  – Shipment & Deliveries

• 2lis_08TRFKZ  – Shipment Costs
• DTS_TRKONV   – Shipment Conditions
• DTS_TRFI_ESSR – Invoices & Purchases History
• DTS_TRFI_VFKP – Invoices & Purchases Issues

Main dimensions for the data

• C_POINT2   –  Connection Point (it can be a customer, vendor, plant, node point or shipping point)

• C_3RPARTY  –  3rd Party (Cust / Vend) - it cab be a vendor or a customer

• C_ROUTE     –  Route
• C_SHIPNU2   –  Shipment Number
• C_SHCSTI2   –  Shipment Cost item
• C_DELITM2   –  Delivery Item
• C_CNDTYP2  – Condition Type
• C_SHPTP_2   –  Shipping Type
• C_SHPMTP2   – Shipment Type
• C_SHCITTY   –  Item category shipment costs 
• C_VTADD01   –  Ship. Shipping Line 
• C_SHIPCD2   –  Shipping conditions
• 0TRZONE    –  Transportation Zone 
• C_TRPPNT2   –  Transportation planning point 
• C_VSTGA   –  Event Reason f.deviation
• C_EVTTYP   –  Event Type

Reporting

Main queries

1 - Shipment cost details analysis

• Technical Name: BW_QRY_MVSDTR01_0010
• Propose a detailed analysis of shipment cost accruals, detailled by materials. Make shipment costs accruals understandable.
• Allows benchmarking between materials, between customers.
• Gives some possibilities of drill down to get details on a macro figure.
• Public: sites log managers / GBU log process teams, base for Qlikview reportings

Configuration

First Result

2 - Shipment cost vs invoice analysis 

• Technical Name: BW_QRY_MVSDTR01_0011
• Propose advanced cost analysis functionalities including invoice / accrual comparision and other ratios that can't be available at material level.
• Detect / evaluate unbilled payables.
• Audit tarif calculation
• Public: finance / controlling, sites & GBU logistics managers, data log and support teams

Configuration

First Result

3 - Shipment status and events 

• Technical Name: BW_QRY_MVSDTR01_0012

• Propose tracking of events on shipments. without cost considerations.
• Propose a reporting on volumetry : number of files (delivery or shipment) per flow, average value on some indicators...
• Load plan of shipping points

• Public: LOG data and support teams, GBUs sites log managers and sites operations supervisors, Transport managers

Configuration

First Result

4 - CO²  Emissions

• Technical Name: BW_QRY_MVSDTR01_0013
• The propose is to show the calculations about quantity of carbonic gase that is released in atmosphere considering all the shipments by zone
• Public: users that manage the environment effects and reports to governments

Configuration

First Result

5 - Shipment Events 

• Technical Name : BW_QRY_MVSDTR02_0001

• The propose is to show the events (problems) involving the hauliers that happened during the logistic process 
• Public: GBUs sites log managers and sites operations supervisors, transport managers

Configuration

First Result

Queries used to load QV applications

Matrix between queries and info objects

For more details about each query please click in following link: TIERS: Reporting Solution

Dependencies with other applications

We should have the information where the application is sending or receiving information (e.g. APD open hub) 

Data Loading

Info Providers and objects loaded 

1 - Main Process Chain

This process chain is responsible to trigger and syncronize all TIERS processes chains for Solvay and Rhodia. It is scheduled to run every workday inside the Daily process chain (RSP_DAILY) after general master data PC, around 3AM (French time).

•  PC_SD_TIERS_001: SD TIERS Daily Main PC

2 - Propagation Layer

 This process chain is responsible to run the loads between source system and first layer in BW.

• PC_SD_TIERS_020 à SD TIERS Daily Solvay Propagation PC
• PC_SD_TIERS_010 à SD TIERS Daily Rhodia Propagation PC

3 - Business Layer

 This process chain is responsible to load the second and third layers from propagation layer.

• PC_SD_TIERS_021 à SD TIERS Daily Solvay Business Rule PC
• PC_SD_TIERS_011 à SD TIERS Daily Rhodia Business Rule PC

4 - Master data

 This process chain is responsible to load all the master data attributes in BW.

• PC_SD_TIERS_MD_022 à SD TIERS Daily Solvay Master Data PC
• PC_SD_TIERS_MD_002 à SD TIERS Daily Rhodia Master Data PC

5 - Text & maintenance

 This process chain is responsible to load all the master data texts in BW.

• PC_SD_TIERS_MD_TEXT022 à SD TIERS Daily Solvay Text PC
• PC_SD_TIERS_MD_TEXT002 à SD TIERS Daily Rhodia Text PC
• PC_SD_TIERS_DELETE à SD TIERS Daily Deletion PSA/Change Log

Loading frequency

Daily inside the daily process chain

Average performance & monitoring

Daily process chain is loaded in 2 hours with around 30k lines in DELTA mode for a total of 10M lines in cubes. 

See below an extract of 1 month of monitoring

For details about application load monitoring, click in following link: Application Monitoring

Record Keeping

User defined that 3 full years stored is enough to be maintained in BW.

There is no automatic process to remove historical data, so any request about historical deletion should be done by user using Freshdesk ticket.

Data Quality Control

Operational Documentation

Procedures

<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>

Scheduling

<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>

Monitoring

<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>

Error Handling

<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>

Known Bugs

<List the existing bugs, its criticality, workarounds and resolution plan.>

Roadmap

<List past & future evolutions for the application (including links to MED/FSD/TSD>