Page tree


Access Management 


Roles & Access

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

Role CodeRole DescriptionExplanation

ZR_RCS_CA_M68

PaPM – CBS - Load Driver data for PaPM

Role menu for ZBW_PAPM

ZR_RCS_CA_M71

PaPM – CBS - Snap Shot creation for PaPM Data

Role menu for ZBW_PAPM_VER

ZBI_RCS_PAPM_A01 PAPM - CBS Invoicing - ECOEnd user role
ZBI_RCS_PAPM_A01_PO2 PAPM - CBS InvoicingEnd user role
ZBI_RCS_PAPM_A02  PAPM - Segmented P&L - ECOEnd user role
ZBI_RCS_PAPM_A03 PAPM - CBS Invoicing - SCOEnd user role
ZBI_RCS_PAPM_A04PAPM - Segmented P&L - SCOEnd user role
Authorization Objects

List of authorization objects mandatory for the application.

Authorization objectExplanation
C_AUTHMAAuthorization scope : ZR_*_CA_P00

Background:

The inter-company service charges and cost allocation process for Solvay’s Corporate and Business Services (CBS) is time consuming, manually maintained, lacks appropriate technology enablement and is controlled across multiple functions.

We need a process to automate the data loading process to remove the drawback of manual process.

Objective

The objective of application is to allow users loading data from excel files with validation of content. 

History

The project was started in May/2016 and was in go-live in June/2016. It was requested by CBS project manager Nathalie Delahousse and approved bt Sandrine Micollet,

Link about the specifications :

CBS Database - support for inter-company invoicing


DataFlow

Overview


Technical Rules on Workbench

CPCBSI01

The calculation view CV_RH_FI_COST_ANALYIS used in CPCUBFC02 as a part of source for composite provider CPCBSI01 is based on composite provider CPCUBFC01 with GBU fixed cost cubes (documentaion here).


RSDS DTS_FF_PAPM_001 PC_FILE -> ADSO ABCBSI01

Module function  BAPI_CURRENCY_CONV_TO_INTERNAL is used to convert the currencies for key figures K_GRFNCO, K_COGOCA, K_DEPRE2, K_COTRAN and K_SALECO.


ADSO ABCBSI01 -> ADSO ABCBSI02

Start routine: select low field from master data global filter with stream = PAPM, rule = VERSION and c_glbfilt = 001

Field routine:

C_PAPMVER (PaPM Version) → determined from master data global filter with value retrieved in start routine.

C_COMPPRS, C_BFCCOMP, C_ZONE and 0COUNTRY come from master data c_compcde.

C_FUNCT_1, C_FUNCT_2, C_FUNCT_3, C_FUNCT_4 come from master data c_costctr.

C_CELTHF1, C_CELTHF2, C_CELTHF3 come from master data 0COSTELEMNT.

CPCBSI02

ADSO APCBSI01 -> ADSO APCBSI04

Start routine: select low field from master data global filter with stream = PAPM, rule = VERSION and c_glbfilt = 001

Field routine:

C_PAPMVER (PaPM Version) → determined from master data global filter with value retrieved in start routine.

CPCBSI03

ADSO APCBSI02 -> ADSO APCBSI05

Start routine: select low field from master data global filter with stream = PAPM, rule = VERSION and c_glbfilt = 001

Field routine:

C_PAPMVER (PaPM Version) → determined from master data global filter with value retrieved in start routine.


ZBW_PAPM

We can create authorization object to restrict access to users for Transaction code ZBW_PAPM.

We can also restrict access at granular level for all users, example  at company code or controlling are etc..

For driver data available for PaPM, we can display data available in BW in the screen.
We control the content of the file to be sure that there is no error (missing field or incorrect values).

Once data is loaded:

  • The file is saved as csv in /exploit/BW/PaPM in BW server
  • The previously loaded data in BW staging is deleted
  • The info-packages are executed to load the new flat file previewed and checked by user in respective PSAs.
  • The process chains are executed
    • By schedule (hourly with abap condition looking time in global filter).
    • Manage “delta queue” is several loadings at the same time
  • Three other process chains to load from PSA to BW Info provider
    • For all 3 driver data
    • Loads data in respective ADSOs
    • Process chain runs twice a day (managed in Global filter master data)

An ABAP program was developed to help user loading flat file for all three driver data required for PaPM application.

We have created a specific transaction  :  Z BW_PAPM  to run the ABAP program

The program technical name is              :  ZBW_CBS_INT_COMP_INV  

The program title/description is             :   Load CBS PaPM Data - 3 Drivers and Transactional source

With this transaction, user can load excel file for

    • CBS-PAPM-Driver1-Amount.

    • CBS-PAPM-Driver2-Head Count

    • Master data Driver MD

The transaction is available in SOLIA portal. For information, it's better to use IE and not Chrome


Below there is a list of entries in global filter used to support the program to do several activities, like: check authorizations, upload flat file, check company code, run process chain, etc.


 


Lay-out of files

CBS-PAPM-Driver 1-Amount (APCBSI01)

Flat file driver 01 structure :  Advanced DSO APCBSI01

Info-Object

Description

Type

Size

Key

Business rules and Comment

c_compprs

PRS Company code

CHAR4Ynot empty and exists

C_PCDRV01

PAPM Driver Code

CHAR20Ynot empty and exists

K_CCDR01

PAPM Value Company code driver 01

AMNT23N

Not empty.

length 16

Loaded with process chain  PC_CBS_PAPM_001.


CBS-PAPM-Driver 2- HeadCount (APCBSI02)

Flat file driver 02 structure :  Advanced DSO APCBSI02

Info-Object

Description

Type

Size

Key

Business rules and Comment

c_compprs

PRS Company code

CHAR4Ynot empty and exists

c_zzsite 

PaPM  Site

NUMB6Ynot empty and exists

C_PCDRV01

PAPM Driver Code

CHAR20Ynot empty and exists

K_HCDR02

PAPM Nb Headcount per company Driver 02

NUMB16Nlength 8, decimals 16,'.' for decimals, with sign

Loaded with process chain  PC_CBS_PAPM_002.


Master data Driver MD (C_PCDRV01)


Load text for master data C_PCDRV01. File loaded in AL11 repository "/exploit/BW/PaPM/papm_text_driver.csv

Process chain  PC_CBS_PAPM_004.


ZBW_PAPM_VER

Linked to program ZBW_CBS_INT_COMP_INV_VER.

The goal is to display or save PAPM version. The saving is done with the execution if process chain PC_CBS_PAPM_SNAP_SHOT:



Reporting

Main queries

BW_QRY_CPCBSI01_0001 - PAPM BW Transactional data with version



BW_QRY_CPCBSI03_0001 - PAPM Driver headcount with version


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

Main Process ChainFinal Provider LoadingFrequencyTime startDuration

PC_CBS_PAPM_001

PC CBS PaPM - Driver 1 Amount

APCBSI01On demand - event ZEVT_PC_CBS_PAPM_001 on program ZBW_CBS_INT_COMP_INV (transaction Z BW_PAPM)

PC_CBS_PAPM_002

PC CBS PaPM - Driver 2 Head Count

APCBSI02

On demand - event ZEVT_PC_CBS_PAPM_002 on program ZBW_CBS_INT_COMP_INV (transaction Z BW_PAPM)



PC_CBS_PAPM_003

PC CBS PaPM - Transactional data

ABCBSI015th working day of the month 8 am2 mins

PC_CBS_PAPM_004

PC CBS PaPM : Text Driver C_PCDRV01

C_PCDRV01On demand - event ZEVT_PC_CBS_PAPM_004 on program ZBW_CBS_INT_COMP_INV (transaction Z BW_PAPM)

PC_CBS_PAPM_SNAP_SHOT

PC CBS PaPM - Snap-shot of Version Data

ABCBSI02

ABCBSI04

ABCBSI05

On demand - event PC_CBS_PAPM_SNAP_SHOT on program ZBW_CBS_INT_COMP_INV_VER (transaction ZBW_PAPM_VER)



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

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