Page tree


Versions Compared

Key

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

Table of Contents
outlinetrue

For more documentation: PCM

1.0

Access Management 


Panel
borderColor#ffffff
titleColor#ffffff
titleBGColor#009EE0#5495FC
titleRoles & Access

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

Role menu for all project costs queriesPSA02

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" 
    Role CodeRole DescriptionExplanation

    ZRZBI_RCS_CAFI_M09

    PS - Project Costs

    A27

    ITC Credit Management Analysis - End User role

    Application role

    ZBI_RCS_

    FI_

    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

    A28

    ITC Credit Management Analysis - RCS/APM role

    Application role

    ZR_RCS_FI_A27

    ITC Credit Management Analysis - End User role

    User role

    ZR_RCS_FI_A28

    ITC Credit Management Analysis - RCS/APM role

    User role

    ZR_RCS_FI_A29

    ITC Credit Management Analysis - Super User role

    User role

    ZR_RCS_FI_A30

    ITC Credit Management Analysis - Key User role

    User role

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

    List of authorization objects mandatory for the application.

    Authorization objectExplanation
    0COMP_CODE;
    CPFCTR1_2ZR_*_CA_P05
    C_COMPCDE
    ;
    __C_
    PMORDER
    AUTHMAZR_*_CA_
    0COMP
    P00
    C_
    CODE
    COMPCDE
    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

    BW catalog of roles: https://docs.google.com/spreadsheets/d/10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I/edit#gid=131158862

    DataFlow

    Overview

    The dataflow can be divided in 3 main steps:

    1. check that no other run are in progress (a) and then extract data from BW to PCM 
      1. Extract master data in full mode to csv files through openhub
      2. Load FIAR and CAMS data into specific DSO build for PCM project (DBFIAR20 and DBFIAR21),then extract to csv through openhub
      3. Load the data from the file via Talend 
    2. treatment on PCM GCP
    3. Load full with deletion DPFIAR13 from Big Query with new data source DTS_FI_PCM_01 by PC_FI_PCM_10. SQL server was replaced by Big Query

    Image Added

    Embedded Google Drive File
    urlhttps://docs.google.com/presentation/d/1_A3-92Qk8JCFssDoDl5KcjEf5JXtLGTeNgKqMFcer1k/edit?usp=sharing
    fullwidthtrue
    height600

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

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

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

    BW to Talend

    DBFIAR20 loading initialisation process

      Image Added

    Big Query to BW

    DPFIAR13 data loading

    Data source DTS_FI_PCM_01 get from remote source GBQ_Predict_Credit and get from table core_perimeter_future_bw (GCP project predict-credit-mgt-v2-prod)

    Image Added

    Report to get back from BigQuery after calculate by Data Science

      Image Added Image Added

    WIth new version 2.0, BW get only 3 key figures

    PRED_NOT_PIM     → K_PFNPI
    PROBA_NOT_PIM  → K_PPNPI
    AMOUNT_EUR      → 0DEB_CRE_LC

    Note: DPFIAR14  is obsolete

    Architecture Overview

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


    Obsolete 

    Image Added

    SQL server was replaced by Big Query and after files are generate, they will be loaded by Talend by Data Engineering team

    Objective of the application

    Provide predictive information on Credit Management.

    • Define which payer is a priority based on its history and the due amount.


    Tool Leader: David TONDA

    IT leader of the application: Guillaume THEVENET

    Name of project: PCM Predictive Credit Management

    PMO Project: 6958 Big Data for Credit Management

    Reporting Coordinator: David TONDA

    Usage information

    Nu mber of users:  tbd

    Critical period: none

    Geographical perimeter: worldwide

    InfoArea:

    • All objects are stored in FIAR infoarea: IA_FMCO_FIAR

      Image Added

    Process chain Display Component:

    • 134 - PROJECT - PCM
      COMP_PCM
      Image Added


    History

    In Mar 2020, the data flow was updated to  PCM 2.0

    In 2021, BW change the source system SDK_PCM (SQL) to BigQuery(#4749200)

    In Feb 2023, Po2 project requires to segregate data of Eco/Sco, therefore, company master data file is modified to add C_AUTHMA(authorization scope) to the openhub OH_PCM_05


    Technical Rules on Workbench

    The whole process can be summarized has follow:

    • Extraction of BW data (master and transactional data) in flat files (csv with "|" separator)
    • copy and loading of these file into a SQL database
    • Calculation of predictive information on SQL side to produce two table which define Priority per Amount & Priority per Payer
    • Loading of these data in BW to be used on standard reporting

    Openhub

    Updated on 12 Mar 2021: 18 Openhub (2 Transactional and 16 Master data)

    Open HubOpen Hub NameSource of Open HubProcess ChainFilenameDetail of file
    OH_PCM_21PCMV2: DBFIAR20DBFIAR20PC_FI_PCM_V2dbfiar20_delta.csvFIAR: Line Item with Delta - PCM - All systems
    OH_PCM_02PCM: GL_ACCOUNTATTRIBUTES 0GL_ACCOUNTPC_FI_PCM_01gl_account_full.csvAttribute of GL account
    OH_PCM_03PCM: C_CUSTIDATTRIBUTES C_CUSTIDPC_FI_PCM_01c_custid_full.csvAttribute of Customer
    OH_PCM_04PCM: COUNTRYATTRIBUTES 0COUNTRYPC_FI_PCM_01country_full.csvAttribute of Country
    OH_PCM_05PCM: C_COMPCDEATTRIBUTES C_COMPCDEPC_FI_PCM_01c_compcde_full.csvAttribute of Company
    OH_PCM_06PCM: C_CST_CA2ATTRIBUTES C_CST_CA2PC_FI_PCM_01c_cst_ca2_full.csvAttribute of Customer credit control area
    OH_PCM_07PCM: TCURRDTS_TCURRPC_FI_PCM_01tcurr_full.csvAttribute of Currency
    OH_PCM_08PCM: DBFIAR21DBFIAR21PC_FI_PCM_01dbfiar21_delta.csvFIAR: Credit blocked - PCM - All systems
    OH_PCM_09PCM: G_CWWE01ATTRIBUTES 0G_CWWE01PC_FI_PCM_01g_cwwe01_full.csvAttribute of sub activity (IECRA)
    OH_PCM_10PCM: 0CLM_CLSP TextsTEXTS 0CSM_USERPC_FI_PCM_010CLM_CLSP_TEXT.csvText of Collection specialist
    OH_PCM_11PCM: C_COMPCDE TextsTEXTS C_COMPCDEPC_FI_PCM_01c_compcde_text.csvText of Company
    OH_PCM_12PCM: C_SALEMP TextsTEXTS C_SALEMPPC_FI_PCM_01c_salemp_text.csvText of Sales employee
    OH_PCM_13PCM: C_PMNTTRM TextsTEXTS C_PMNTTRMPC_FI_PCM_01C_PMNTTRM_TEXT.csvText of payment term
    OH_PCM_14PCM: CPFCTR1_2 TextsTEXTS CPFCTR1_2PC_FI_PCM_01CPFCRT1_2_TEXT.csvText of GBU
    OH_PCM_15PCM: CPFCTR2_2 TextsTEXTS C_FACUBUPC_FI_PCM_01CPFCTR2_2_TEXT.csvText of BFC group of activity
    OH_PCM_16PCM: 0G_CWWE01 TextsTEXTS 0G_CWWE01PC_FI_PCM_010G_CWWE01_TEXT.csvText of  sub activity (IECRA)
    OH_PCM_17PCM: C_PM_MTHD TextsTEXTS C_PM_MTHDPC_FI_PCM_01C_PM_MTHD_TEXT.csvText of payment method
    OH_PCM_18PCM: 0REPR_GROUP TextsTEXTS 0REPR_GROUPPC_FI_PCM_010REPR_GROUP_TEXT.csvText of credit management representatives group


    All master data openhub are loaded in full mode. All extract data from master data except the TCURR one which is connected to a datasource.

    All transactional data openhub are loaded in delta mode. (remark delta is not possible with multiprovider).


    All openhub use a "|" separator because some field already contain ";" in the value and openhub doesn't encapsuPC_FI_PCM_10ate data.

    Image Added

    All openhub use logical file name defined through FILE transaction. All files are stored in the following folder

    Image Added



    DBFIAR20 flow

    Transformations before DBFIAR20 → DSO from other applications:

    Technical Documentation - RTR - FI Working Capital for Solvay Group (WBP)

    Technical Documentation - ITC - Credit Management


    ODSO DBFIAR20 -> DEST OH_PCM_01:

    Delete data where C_LGSYSAF = PF1_020 and C_COMPCAF = 6059.

    ODSO DBFIAR20 -> DEST OH_PCM_21

    Delete data where C_LGSYSAF = PF1_020 and C_COMPCAF = 6059.

    DBFIAR21 flow

    TRSF: ZZV_KPI_CREDITBL2 Rhodia -> DPFIAR05 & TRSF: ZZV_KPI_CREDITBL2 Solvay -> DPFIAR06

    Conversion from time stamp to dates.

    TRSF: DPFIAR06 -> DBFIAR09 & TRSF: DPFIAR05 -> DBFIAR10

    Number of hours to release are the differences between times stamps.

    C_CUSTPRS, C_CUSTPR are an attribute from C_CUSTID.

    C_CST_CAT2 comes from master data C_CST_CAT2 (with help of c_ctr_area and c_custpr).

    C_CRDACC comes from master data C_CST_CAT2 (with help of c_ctr_area and  c_cst_ca2).

    C_COMPCDE comes from master data C_COMPCDE (with help of fields logsys and c_compprs).

    MVFIAR11 flow

    RSDS DTS_PRIORITY_PER_AMOUNT_PRD SDK_PCM -> ODSO DPFIAR14

    DPFIAR14 not loaded since septemeber 2019

    If C_CUSTID, CPFCTR1_2, C_ZONEFI = #, the result is empty.

    C_CUSTPR comes from C_CUSTID

    MVFIAR10 flow

    RSDS DTS_FI_PCM_01 BQFIPCM_01 -> ODSO DPFIAR13

    No specifics rules.

    RSDS DTS_PRIORITY_PER_PAYER_PRD SDK_PCM -> ODSO DPFIAR13

    Not used since june 2021

    C_CST_CA2 comes from C_CUSTID



    Reporting

    QueryDescription
    BW_QRY_MVFIAR10_0001PCM: predictive analytics (GBU)
    BW_QRY_MVFIAR11_0001PCM: predictive analytics (Detail)


    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

    Data Quality Control

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

    PCM: File generation

    PC_FI_PCM_01

    Open hubs for master data

    DBFIAR20

    DBFIAR21

    Daily10 am10 mins

    PCM: Predictive data load

    PC_FI_PCM_10

    DBFIAR13

    DBFIAR14 (at 10.26.2023 → skipped)

    Daily11 am

    2 mins


    Target folder for open hubs

    Image Added


    Record Keeping

    DSO are loaded with full historical data but we only send today - 3 years to SQL server.


    Data Quality Control


    Operational Documentation

    Procedures

    If the service account:bqtobw@predict-credit-mgt-v2-dev.iam.gserviceaccount.com  in Google Cloud Platform is expired, then the configuration of remote source:GBQ_Predict_Credit in BW/HANA should be adapted accordingly.

    1. Copy the new JSON file to the folder defined in gbqadapter_prod.properties on dp agent server (acew1dhcahca1)
    2. Change the KeyFilePath to the folder of the new JSON file (JSON file provide by DataOps team:  dataops@solvay.com )

    Remote source in BW configuration is not required to change.

    Image Added

    The properties file in dp agent server is required to change if the project name or the location to keep the JSON file is changed.  

    The new JSON file must be the same as the detail in the properties file at KeyFilePath

    Image Added

    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 criticity, workarounds and resolution plan.>

    Roadmap

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