Page tree


Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
outlinetrue

1.0

Access Management 


Role menu for all project costs queries
Panel
borderColor#ffffff
titleColor#ffffff
titleBGColor#009EE0
titleRoles & Access

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

Role CodeRole DescriptionExplanation
ZR_RCS_CA_
M09
M072

PS - Project Costs

TR - Transportation costs Newrole menu
ZBI_RCS_
PS
TR_
A02Project Costs and Structures Analysis
A08

New Transport  Costs Analysis

- End User

roleApplication

Role

:
  • End User rights
  • role menu for TIERS, gives access to

    infoproviders of Infoarea "AREA_PSCO"
  • BI Analysis Authorization "ZBI_PS" ("*" for authorization objects not relevant for the application)
  • ZBI_RCS_CO_A21

    CBS Project costs Reporting Analysis - End User role

    Application Role:

  • End User rights
  • gives access to infoproviders of Infoarea "AREA_F_CO_CBS_PS"
  • Gives access to multiprovider:MPR_PS014
  • BI Analysis Authorization "ZBI_CBS_PC" 

    all cubes under infoarea IA_SD_TR*

    Authorization Object ZBI_TR2 / Authorization on Company Code

    This role has to be used with the role menu transportation costs

    ZP2_RCS_TR_A08

    Transportation Costs Analysis TIERS - End User Role

    Linked to authorization role ZP2_TR2

    NB: The role menu ZR_RCS_ALL_MENU "Role composite with all role Menu and perimeters" gives access to all role menu. When asking for a new role menu, do not forget it is added to that one.

    NB: ZBI_RCS_TR_A02 & ZR_RCS_TR_A02 are obsolete

    Image Added

    Image Added

    Image Added

    Panel
    borderColor#ffffff
    titleColor#ffffff
    titleBGColor#009EE0
    titleAuthorization Objects

    List of authorization objects mandatory for the application.

    Authorization objectExplanation
    0COMP_CODE;

    C_COMPCDE

    ;

    C_

    PMORDER

    SHCSTI2__

    0COMP_CODECompany, role:

    C_COMPCDE

    ZTOUTCAP01 => All Companies "Solvay"

    ZR_*_CA_P01

    0PROFIT

    ZR_

    CTR

    ZFR3_CA_P01 => Analysis company Rhodia Opérations ( ZFR3)

    CPFCTR1_2
    ; 0PROFIT_CTR__C_PFCTR1;CPFCTR1_2;C_AGRITM__CPFCTR1_2;
    C_ASSET2__C_PFCTR1;C_ASSET__C_PFCTR1;C_MATPLNT__CPFCTR1_2;
    C_MATPLNT__C_PFCTR1;C_MATPNT2__CPFCTR1_2;C_PFCTR1;
    C_PMORDER__C_PFCTR1;C_PMORDR__C_PFCTR1;C_PRDEQUI__CPFCTR1_2;
    C_RECONTR__CPFCTR1_2;C_RESP_CC__CPFCTR1_2;C_SUBACT2__CPFCTR1_2
    C_TECMAT__CPFCTR1_2;C_WBS_EL2__CPFCTR1_2;C_WBS_EL2__C_ZSECT;C_WBS_ELE__CPFCTR1_2;
    C_WBS_ELE__C_ZSECT;C_ZSECT
    GBU, role: ZR_*_CA_P05
    C_FAMIL;C_WBS_EL2__C_FAMIL;C_WBS_ELE__C_FAMILFamily, role: ZR_*_CA_P04
    GBU, role: ZR_*_CA_P05
    C_COMPCDE__C_AUTHMAAuthorization scope role: ZR_*_CA_P00

    See also file maintained by Authorization team : 

    DataFlow

    Overview

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/presentation/d/1vGhaf14nZ4In_iudZ3OURh0uiuE-1cwk1V5Teebdpus/edit?usp=sharing
    fullwidthtrue
    height600

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/presentation/d/1RtpPCUE7RHx0ZNlRVhTxEcOfKgzg-l7uJQ6BzXXik3U/edit?usp=sharing
    fullwidthtrue
    height600

    Technical Rules on Workbench

    Rules & Explanations

    Main documentation:

    Preparation

    Kickoff

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/presentation/d/1EcBnprCcrjUyFV1L4KDWq-QoeQmvY4hrPvYL2EJPgO4/edit#slide=id.p4
    fullwidthtrue
    height600

    Project Quality Plan

    Embedded Google Drive File
    migratedtrue
    urlhttps://drive.google.com/file/d/0B46EYtJzPsZ-YTRHRlhTWEtWQW8/view?resourcekey=0-_MW23kVWMZOTSPCXYM4u4Q
    fullwidthtrue
    height600

    Design Validation

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/presentation/d/1buvi6M5KrDk5Ll3917sEr-52ujLgT5ZY5R0_Ws94gpM/edit#slide=id.p4
    fullwidthtrue
    height600

    Design

    Functional Specification

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/document/d/1EByARR5UOqBQ9ZOP6Xwf_Ol7ylPXrcpVo0P1iK6287c/edit
    fullwidthtrue
    height600

    Map of Datasources

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/spreadsheets/d/1JNOj5lzgzK9U3AGYjxwxdNH_vtgRG3KM3ZsEoEWkVQU/edit
    fullwidthtrue
    height600

    Profiles Management

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/presentation/d/1UAsa0rCdnEabItHTulE6VKo95-txq46zpiLj_xBYU2Y/edit#slide=id.gc3efd81a5_0_0
    fullwidthtrue
    height600

    Queries Definition

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/spreadsheets/d/1cSJqjkLnZ-OX5pOLV8UxfZDIUuUW8EH2D8TLUjTjzas/edit#gid=0
    fullwidthtrue
    height600

    Technical documentation

    Embedded Google Drive File
    migratedtrue
    urlhttps://docs.google.com/document/d/1E9_Z1BWfKZcLS9d_l6kSHGs84LhLORv2Dqt61xAqcu8/edit
    fullwidthtrue
    height600

    Deployment

    E Learning

    Embedded Google Drive File
    migratedtrue
    urlhttps://drive.google.com/file/d/0B46EYtJzPsZ-MGpzQjFmRnB0c0k/view?resourcekey=0-jc-PGiMleMqlk7oOGgemkQ
    fullwidthtrue
    height600

    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).

    Image Added

    Image Added

     

    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.

     

    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) :
     Image Added

    Image Added

    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


    Image Added

    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)Image Added

    Solvay PO schedule lines (DB_PUSL2)Image Added

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

    Rhodia CUB_VS (value stream)
    Image Added

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

    Rhodia CUB_DIPL (industrial dashboard)

    Image Added


    Info areas

    Image Added

    Master Data

    Image Added

    Propagation Layer

    Image Added

    Business Layer

    Image Added

    Reporting Layer

    Image Added

    Virtual Layer

    Image Added

    Multi provider

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

    Image Added

     

    Data Flow

    Image Added

     

    Dimensions

    Image Added

    Image Added

    Key figures

    Image Added

    Image Added

     

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

    Data Flow

    Image Added

    Dimensions

    Image Added

    Key figures

    Image Added

     

    Main KPI calculations

    Image Added

    Main functionalities

    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

    QueryName
    BW_QRY_MVSDTR01_0010BW - Shipment costs detailed analysis TIERS (Core Query)
    BW_QRY_MVSDTR01_0011BW - Accrual Costs vs Invoice analysis TIERS (Core Query)
    BW_QRY_MVSDTR01_0012BW - Shipment status and events TIERS (Core query)
    BW_QRY_MVSDTR01_0013BW - CO²  Emissions TIERS (core query)
    BW_QRY_MVSDTR01_0014BW - Shipment costs analysis by delivery ( for DYNASYS)
    BW_QRY_MVSDTR01_0020BW - Forward Reject Services Analysis (Core query)
    BW_QRY_MVSDTR01_0021BW-Overwiew of DG Shipment status and events-TIERS
    BW_QRY_MVSDTR01_9000BW - TR - ZV23 Vehicle Control at Production Plant
    BW_QRY_MVSDTR01_9998BW - Shipment costs detailed analysis Vendors TIERS
    BW_QRY_MVSDTR01_9999BW - Shipment costs detailed analysis TIERS
    BW_QRY_MVSDTR01_BCST_0001BW -Shipment costs detailed analysis TIERS Broadcast Query
    BW_QRY_MVSDTR01_BCST_0002BW- Shipment Status and Events Broadcast query
    BW_QRY_MVSDTR02_0001BW - Shipment Events TIERS (Core Query)
    QVEPSC_BW_QRY_MVSDTR01_0001BW - Shipment Costs Analysis for E&P TIERS - Qlikview (
    QVNVSC_BW_QRY_MVSDTR01_0001BW - Shipment Costs Analysis for Novecare TIERS - Qlikview (
    QVPISC_BW_QRY_MVSDTR01_0001BW - Shipment Costs Analysis for P&I TIERS - Qlikview (Core)
    QVSBS_BW_QRY_MVSDTR01_0001BW - SBS OTC Shipment Costs TIERS (QV SBS KPI)
    QVSCE_BW_QRY_MVSDTR01_0010BW - Economics part of activity SCE (Core Query)
    QVSCE_BW_QRY_MVSDTR01_0011BW - Acc. Costs vs Invoice Analysis TIERS (Core Qry for QV)
    QVSCE_BW_QRY_MVSDTR01_0012BW - Activity Haulier Evaluation SCE (core query)
    QVSCE_BW_QRY_MVSDTR01_0013BW - CO² Footprint SCE (QV Query)
    NameDescription
    BW_CKF_MVSDTR01_0001No of Containers
    BW_CKF_MVSDTR01_0002Distance (SUM ship)
    BW_CKF_MVSDTR01_0003Gross W. dels. (SUM del item)
    BW_CKF_MVSDTR01_0004Net W, dels. (SUM del item)
    BW_CKF_MVSDTR01_0005Gross W, dels. (SUM delivery)
    BW_CKF_MVSDTR01_0006Net W, dels. (SUM delivery)
    BW_CKF_MVSDTR01_0007Gross W, dels. (SUM ship)
    BW_CKF_MVSDTR01_0008Net W, dels. (SUM ship)
    BW_CKF_MVSDTR01_0010No of handling units (MAX delitem)
    BW_CKF_MVSDTR01_0011No of handling units
    BW_CKF_MVSDTR01_0014Detailed Shpt. condition value
    BW_CKF_MVSDTR01_0015Invoiced Value
    BW_CKF_MVSDTR01_0016Accrual, Net value shipment
    BW_CKF_MVSDTR01_0017# Ship Relevant for SADH below 30 min
    BW_CKF_MVSDTR01_0018# Ship Relevant for SADH
    BW_CKF_MVSDTR01_0020Distance (SUM stage)
    BW_CKF_MVSDTR01_0021No of Shipments
    BW_CKF_MVSDTR01_0023No of handling units (MAX stage)
    BW_CKF_MVSDTR01_0024No of Stages (by detail)
    BW_CKF_MVSDTR01_0025No of Stages (by Stage)
    BW_CKF_MVSDTR01_0026No of Stages
    BW_CKF_MVSDTR01_0027No of Delivery Items
    BW_CKF_MVSDTR01_0028No of Deliveries
    BW_CKF_MVSDTR01_0032CO² Emission Factor
    BW_CKF_MVSDTR01_0040#Ship Relevant for Loading duration
    BW_CKF_MVSDTR01_0041#Ship Relevant for Queue time
    BW_CKF_MVSDTR01_0042#Ship Relevant for On Site duration
    BW_CKF_MVSDTR01_0045Number of HOTS
    BW_CKF_MVSDTR01_0046#Ship Relevant for booking leadtime
    BW_CKF_MVSDTR01_0052Net W. dels in VKG (SUM del item)
    BW_CKF_MVSDTR01_0053Net W. dels in VKG (SUM delivery)
    BW_CKF_MVSDTR01_0054Net W. dels in VKG (SUM ship)
    BW_CKF_MVSDTR01_0055Net W. dels in VTN (SUM del item)
    BW_CKF_MVSDTR01_0056Net W. dels in VTN (SUM delivery)
    BW_CKF_MVSDTR01_0057Net W. dels in VTN (SUM ship)
    BW_CKF_MVSDTR01_0070Gross W. dels. (MAX stage)
    BW_CKF_MVSDTR01_0071Net W. dels. (MAX stage)
    BW_CKF_MVSDTR01_0072Net W. dels in VKG (MAX stage)
    BW_CKF_MVSDTR01_0073Net W. dels in VTN (MAX stage)
    BW_CKF_MVSDTR01_0081Distance (max delivery)
    BW_CKF_MVSDTR01_0082Distance (max delitem)
    BW_CKF_MVSDTR01_0090Loading Duration (Days)
    BW_CKF_MVSDTR01_0091Transit time (Days)
    BW_CKF_MVSDTR01_0092Booking leadtime (Days)
    BW_CKF_MVSDTR01_0093HOTD delay (in days)
    BW_CKF_MVSDTR01_0094HOTS delay (in days)
    BW_CKF_MVSDTR01_0095On site duration (Days)
    BW_CKF_MVSDTR01_0096Queue time at plant (Days)
    BW_CKF_MVSDTR01_0097Planned Transp Time (Days)
    BW_CKF_MVSDTR01_0098SADH in min (by ship)


    BW_RKF_MVSDTR01_0001Number of Legs
    BW_RKF_MVSDTR01_0002Extra-costs accrual CP


    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

    Image AddedImage AddedImage AddedImage AddedImage Added 

    First Result

    Image Added

    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

     Image AddedImage AddedImage AddedImage AddedImage Added 

     

    First Result

    Image Added


    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

    Image AddedImage AddedImage AddedImage Added      Image Added

    First Result


    Image Added

    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


    Image AddedImage AddedImage AddedImage Added


    First Result

    Image Added

    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


    Image Added  Image AddedImage AddedImage Added

    First Result

    Image Added


    Queries used to load QV applications

     Image Added


    Matrix between queries and info objects

    Query descriptionCost deatailed analysisAccrual vs invoiceStatuses and eventsEvent reportingCO2 Footprint
    Technical nameMVSDTR01_0010MVSDTR01_0011MVSDTR01_0012MVSDTR002_0001MVSDTR01_0013

    General "Core entry keys"

    COMPANYCOMPANYCOMPANYCOMPANYCOMPANY
    PROMPT UNITPROMPT UNITPROMPT UNIT
    PROMPT UNIT
    PROMPT CURRENCYPROMPT CURRENCY


    System originSystem originSystem originSystem originSystem origin
    BFC GBUBFC GBUBFC GBUBFC GBUBFC GBU
    Site (PUSITE) - C-PSITESite (PUSITE)Site (PUSITE)Site (PUSITE)Site (PUSITE)
    Actual completion Year / MonthActual completion Year / MonthActual completion Year / MonthActual completion Year / MonthActual completion Year / Month
    Shipment departure countryShipment departure countryShipment departure countryShipment departure countryShipment departure country
    Shipment destination countryShipment destination countryShipment destination countryShipment destination countryShipment destination country
    Forwd. AgentForwd. AgentForwd. AgentForwd. Agent

    Query Specific axes

    Product Hierarchy



    Material plant



    Bulk / PackedPO numberRouteEvent typeZone
    3RD PartyShpiment cost item categoryDG classEvent reason for deviation
    Shpiment cost item category



    Transportation ModeTransportation ModeTransportation ModeTransportation ModeTransportation Mode

    For those who want to detail

    PlantPlantPlantPlantPlant
    Departure Geo ZoneDeparture Geo ZoneDeparture Geo ZoneDeparture Geo ZoneDeparture Geo Zone
    Transportation planning pointTransportation planning pointTransportation planning pointTransportation planning pointTransportation planning point
    Planed completion datePlaned completion datePlaned completion datePlaned completion datePlaned completion date
    Actual completion dateActual completion dateActual completion dateActual completion dateActual completion date
    Shipment numberShipment numberShipment numberShipment numberShipment number
    Shipping conditionShipping conditionShipping conditionShipping conditionShipping condition
    Shipment typeShipment typeShipment typeShipment typeShipment type



    "By default" shown Measures (among those available)












    Accrual Net value shipment (CP)Accrual Net value shipment (CP)Gross weightNb of eventGross Weight
    Gross Weight (PU)Invoiced value (CP)Nb of shipmentsEvent durationDistance
    Net Weight (PU)Net weight (PU)Nb of containers
    CO2 Tons
    Cost per Unit (Net)Gross Weight (PU)Nb of deliveries

    Cost per unit (Gross)Cost per unit (Net)Nb of HU


    Cost per unit (Gross)# ship relevant for loading duration


    Invoice - accrual Gap# ship relevant for On site duration


    Provisionning accuracy# ship relevant for Queue time



    # ship relevant for Trnasit time



    Average loading duration

    Keep all others as optionalKeep all others as optionalAverage On site duration



    Average Queue time



    Average Transit duration



    % OTD



    % OTS



    Average distance

    "By default" shown Rows (among those available)



    Source sytemSource SystemSource sytemSource SystemSource system
    Site (CPLANT PSITE)Site (CPLANT PSITE)Site (CPLANT PSITE)Site (CPLANT PSITE)Site
    Shipment destination CountryForward agentForward agentForward agentShip Shipping type



    Event type



    Event reason
    All navigational attributes :




    OrganizationSource systemSource systemSource systemSource systemSource system

    BFC GBUBFC GBUBFC GBUBFC GBUBFC GBU

    PlantPlantPlantPlantPlant

    Site (Plant C-PSite)Site (Plant C-PSite)Site (Plant C-PSite)Site (Plant C-PSite)Site (Plant C-PSite)

    Company codeCompany codeCompany codeCompany codeCompany code
    ShipmentShipment numberShipment numberShipment numberShipment number

    Departure countryDeparture countryDeparture countryDeparture country

    Destination countryDestination countryDestination countryDestination country

    Forwarding agentForwarding agentForwarding agentForwarding agent

    Transportation planning pointTransportation planning pointTransportation planning pointTransportation planning point

    Actual Completion dateActual Completion dateActual Completion dateActual Completion date

    Actual completion date (Month) YYYY/MMActual completion date (Month) YYYY/MMActual completion date (Month) YYYY/MMActual completion date (Month) YYYY/MM

    Actual completion date (Quarter) YYYY/QActual completion date (Quarter) YYYY/QActual completion date (Quarter) YYYY/QActual completion date (Quarter) YYYY/Q

    Actual completion date Year (YYYY)Actual completion date Year (YYYY)Actual completion date Year (YYYY)Actual completion date Year (YYYY)

    Actual date for Start of shipmentActual date for Start of shipmentActual date for Start of shipmentActual date for Start of shipment

    Planned shipment completion datePlanned shipment completion datePlanned shipment completion datePlanned shipment completion date

    Planned shipment completion date (YYYY-MM)




    Shipment destination pointShipment destination pointShipment destination pointShipment destination point

    Shipment destination point typeShipment destination point typeShipment destination point typeShipment destination point type

    Shipment departure pointShipment departure pointShipment departure pointShipment departure point

    Shipment departure point typeShipment departure point typeShipment departure point typeShipment departure point type

    RouteRouteRoute


    Shipment packaging materialShipment packaging materialShipment packaging material


    Shipment shipping typeShipment shipping typeShipment shipping type


    Transportation modeTransportation modeTransportation modeTransportation modeTransportation mode



    Departure point - TR zone




    Departure point - Zip code




    Destination point TR zone




    Destination point Zip code



    Shipment Shipping lineShipment Shipping line

    Shipment stageShip Stage sequence numberShip Stage sequence numberShip Stage sequence number


    Ship stage departure pointShip stage departure pointShip stage departure point


    Ship stage departure point typeShip stage departure point typeShip stage departure point type


    Ship stage destination pointShip stage destination pointShip stage destination point


    Shipment stage destination point typeShipment stage destination point typeShipment stage destination point type


    Leg indicatorLeg indicatorLeg indicator

    DeliveryDelivery




    Delivery Item




    Delivery distribution channel




    Material




    Material plant




    DG class
    DG class


    UN number
    UN number


    3rd Party
    3rd Party


    3rd Party type
    3rd Party type




    3rd partry - TRzone




    3rd party - Location




    3rd party - Zip code


    Transportation group (Bulk / Packed)
    Transportation group (Bulk / Packed)


    Transportation group detail
    Transportation group detail


    Material hierarchy
    Material hierarchy

    Shipment x deliveryShipping conditionShipping conditionShipping condition

    Shipment cost itemShipment cost numberShipment cost number



    Item numberItem number



    Service agentService agent



    Shipment cost item categoryShipment cost item category



    Shipment cost posting dateShipment cost posting date



    Shipment cost posting date - Month (YYYY/MM)Shipment cost posting date - Month (YYYY/MM)




    PO Number




    Invoice Number


    Cost conditionCondition typeCondition type


    Event


    Event actual start date (day)




    Event actual end date (day)


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

    2.0 DataFlow

    2.1 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

    2.2 Technical Rules on Workbench

    Explanation for the process on the technical side. Can be specific cases or general rules depending on the scope.

    2.2

    Dependencies with other applications

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

    3.0

    Data Loading

    3.1

    Info Providers and objects loaded 

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

    Main Process ChainFinal Provider LoadingFrequencyTime startDuration

    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

     Image Added   

    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

    Image Added


    Key Figure

    Estimation

    Key Figure

    Estimation

    ~ Average Process Chain Runtime90 to 120 minutes
    ~ Average nb of rows loaded per load

    Shipment Header: Solvay 6K, Rhodia 2K

    Shipment&Deliveries: Solvay 40K, Rhodia 10K

    Shipment Costs: Solvay 9K, Rhodia 4K

    Shipment&Purchases: Solvay 110K, Rhodia 24K

    Shipment Conditions: Solvay 32K, Rhodia 152K

    1.200K records (all providers)

    ~ Total nb of rows loaded (if full)

    Data is stored since 2014

    Propagation Layer - Solvay 20.000K, Rhodia 10.000K

    Business Layer - Solvay 15.000K, Rhodia 8.000K

    Reporting - Solvay 15.000K, Rhodia 8.000K

    Master data - Solvay 11.000K, Rhodia 5.000K

    ~ Average Runtime for 10k lines30 minutes


    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>