Data, Analytics & AI Platform

Page tree


Versions Compared

Old Version 2

changes.mady.by.user Karen Oppong

Saved on

compared with

New Version Current

changes.mady.by.user POLOSSON-ext, Damien

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Content Zone

Table of Contents
outlinetrue

Access Management

1.0 Access Management 

Application Role:

  • End User rights
  • gives access to infoproviders of Infoarea "AREA_F_CO_CBS_PS"
  • Gives access to multiprovider:MPR_PS014
    • 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 Code

    Role Description

    Explanation

    ZR

    ZBI_RCS_

    CA

    SD_

    M09

    PS - Project Costs

    Role menu for all project costs queries

    ZBI_RCS_PS_A02

    Project Costs and Structures Analysis - End User role

    Application Role:

      • End User rights
      • 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

    A01

    Application role for Global Sales project / SD data / Orderbook

    Role for the application

    ZR_RCS_CA_M49

    SD - Sales and Distribution

    Role menu for the application

    BI Analysis Authorization "ZBI_CBS_PC" 

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

    List of authorization objects mandatory for the application.

    Authorization object

    Explanation

    0COMP_CODE;

    CPFCTR1_2

    GBU

    C_COMPCDE

    ;

    Legal company

    C_

    PMORDER__0COMP_CODE
    		Company, role: ZR_*_CA_P01
    0PROFIT_CTR__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

    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) 

    SAL_OF

    Sales office

    WARNING: For the PO part the notion of sales offices doesn't exist. The restriction in sales offices will not be considered for the reports PO and PO+SO.

    Data flow

    Overview

    Data Admin - Customer


    This workbook works directly with Customer's Master-Data, whether or not the customer has sales.
    It is possible to control the GBR(*) customer Corporate group, even if the customer still has no sales in SAP. This report works directly with master data and for that reason the GBU can't be used in prompts (GBU defined only when the customer has sales).

    Data Admin - Customer Group

    This report retrieves all customers' groups (Corporate and GBU), for customers with sales in SAP. It is possible to be refreshed by GBU.

    Data Admin - End Use


    This report provides data to control the mapping done for 2 axis recorded in GBR(*) and was developed to help the data mapping for the CRM Analytics tool (depending of the GBU’s decision to use it or not).
    The axis are:

    • CORPORATE END USE
    • GBU Customer Group (Group, Sub-Group, Account Type, Customer Classification)

    Both are available in the BW WBP reports and in the CRM Analytics.

    Tabs in the report:

    • END USE and SALES
    • END USE link
    • END USE axis
    • Application
    • Market
    • Segment

    For the Billing date we suggest to use always 1 year period.
    For the END USE mapping always use the Corporate end use TO LINK, to identify easily the customers and products to update in Quikload (GBR).

    Data Admin - Material not converted


    It’s not possible to convert sales unit into prompted quantity unit (PUQ) when that conversion don't exist in SAP.
    After choosing the PUQ the report retrieves all materials that are not converted in that unit.

    Data flow

    Please see the data flow of the multiprovider MVSDAD01(MP: Data Admin (Global Sales) - with GBU) generated from Performer Suite.

    Please see the data flow of the multiprovider MVSDAD02(MP: Data Admin (Global Sales) - without GBU) generated from Performer Suite.

    Please see the data flow of the multiprovider MVSDSO44(MP: Global Sales (Global Sales)) generated from Performer Suite.

    Please see the data flow of the multiprovider CPSDSO54(MP: Order book, Forecast & historical (PO & SO)) generated from Performer Suite.

    Reporting

    Workbook


    Query


    Data Admin - Customer Corporate GroupBW_WBK_SD_CPSDSO54_0001Customer Corporate GroupsBW_QRY_CPSDSO54_0009
    Data Admin - Customer GroupBW_WBK_SD_ADM_0002GBR - Corporate Group (core query)

    BW_QRY_MVSDAD02_0009

    GBR - GBU Customer Group (core query)

    BW_QRY_MVSDAD01_0008

    Historical Data: Sales Orders (Core query)

    BW_QRY_MVSDSO44_SD0002

    Data Admin - Customer Master DataBW_WBK_MVSDAD02_0005GBR - Customer Master data (core query)

    BW_QRY_MVSDAD02_0005

    Data Admin - Material Master DataBW_WBK_MVSDAD02_0006GBR - Material Master Data (core query)

    BW_QRY_MVSDAD02_0006

    Data Admin - End UseBW_WBK_SD_ADM_0001GBR - End Use Link (core query)

    BW_QRY_MVSDAD01_0001

    GBR - End Use Axis (core query)

    BW_QRY_MVSDAD01_0002

    BW - GBR - End Use Ship to Link (core query)

    BW_QRY_MVSDAD01_0010

    Historical Data: Sales Orders (Core query)

    BW_QRY_MVSDSO44_SD0002

    Data Admin - Material not ConvertedBW_WBK_MVSDSO44_SD0009Data Admin: Material not converted (Core query)

    BW_QRY_MVSDSO44_SD0009

    Data Admin - Ship-to KABW_WBK_MVSDSO44_SD0002_ADMINHistorical Data: Sales Orders (Core query)

    BW_QRY_MVSDSO44_SD0002

    Data loading

    Main Process ChainFinal Info ProviderFrequencyStart TimeDuration
    PC_GLOBAL_SALES_MAINCRSDSO41, 42...Daily~1:30am CET~3.5h
    PC_SD_MAINCRSDSO01, 02...Daily~2:00am CET~1h
    PC_GL_SALES_MAIN_POCRSDSO51, 52...Daily~6:00am CET~1h
    PC_OBAS_TRANSFERS_MAINCRSDSO11, 12...Daily~6:00am CET~0.5h


    Data Quality Controls

    Data comes from SAP system. To compare data between BW and sources systems, check propagation layers.

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

    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


    Powered by Atlassian Confluence and Brikit Theme Press