(warning)     (warning)     (warning)     (warning)

The new wiki link for this data flow is here:

Technical Documentation - PAPM/CBS invoicing 

Please update the new doc there and no longer here.

(warning)    (warning)     (warning)     (warning)



General presentation

List of contacts

Objective of the application

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. 

Tool Leader + IT leader of the application: Name of project or main leader for the application + reporting coodinator

Usage information

Around 4 users worldwide.

How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site

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

Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information

Roles & Access

Roles and access

Toe Be Confirmed

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

Role CodeRole DescriptionExplanation
 TBC







Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation
 TBC




Dataflow overview

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

Functional and Technical rules on Workbench + Reporting

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:

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  :  ZBW_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

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

Rules & Explanations

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.

Global Filter Stream (Application)Global Filter RuleGlobal FilterGlobal Filter DescriptionGlobal Filter SignGlobal Filter OptionGlobal Filter Low ValueGlobal Filter Hight ValueGlobal Filter Active
PAPMAMNT1FILE NAME

CBS-PAPM-Driver1-Amount.xlsY
PAPMAMNT2DELTA QUEUE

0
Y
PAPMAMNT3COUNTER OF LOADING
19
Y
PAPMAUTHGR1AuthorizationIEQZR_CBS_PAPM_FILE_UPLOADY
PAPMAUTHGR2AuthorizationIEQZR_CBS_PAPM_FILE_UPLOAD_TCODEY
PAPMCADR1FILE NAME

CBS-PAPM-Driver3-CADRE.xlsY
PAPMCADR2DELTA QUEUE

0
Y
PAPMCADR3COUNTER OF LOADING
9
Y
PAPMCOAREA1Controlling areaIEQZCYT
Y
PAPMCOMPCDE1Company CodeIEQ7008USDY
PAPMCOMPCDE2Company CodeIEQ7764EURY
PAPMHDCN1FILE NAME

CBS-PAPM-Driver2-HC.xlsY
PAPMHDCN2DELTA QUEUE

0
Y
PAPMHDCN3COUNTER OF LOADING
17
Y
PAPMLOGSYS1Source SystemIEQZCBSPAPMUPLDY
PAPMPAPM_RUN1Identify current run for CY process chain (11,...,15)IEQ12
Y
PAPMPAPM_STIME1START TIME ALLOWED for PAPM LoadingIEQ11LOADY
PAPMPAPM_STIME2START TIME ALLOWED for PAPM LoadingIEQ15LOADY
PAPMSENDMAIL1Send emailIEQThanga.Muthu-ext@solvay.comY
PAPMTIME1REFERENCE TIME FOR PAPM LOADIEQ12
Y
PAPMTYPE1REFERENCE TYPE FOR PAPM LOADIEQNO_LOAD
Y
PAPMUNIXAMNT1Unix for Driver 1- AmountIEQ/exploit/BW/PaPM/Driver_1_AmountY
PAPMUNIXCADR1Unix for Driver 3 for cadreIEQ/exploit/BW/PaPM/Driver_3_CadreY
PAPMUNIXHDCN1Unix for Driver 2 for HeadCountIEQ/exploit/BW/PaPM/Driver_2_HeadCountY


There is an ABAP condition ZBW_UPDATE_GLB_FILTER used to define the hours that the process should be executed based on global filter rule PAPM_STIME,  twice a day @11 Hours and 15 Hours.



Lay-out of files


CBS-PAPM-Driver 1-Amount

Flat file driver 01 structure :  Advanced DSO APCOPA01

Info-ObjectDescriptionTypeSizeKeyBusiness rules and Comment

0FISCVARNT

Fiscal year variant

CHAR2YAlways K4

0FISCPER

Fiscal year / period

NUMC7YYYYYMMM

0LOGSYS

source system

CHAR10Ncheck against global filter

C_COMPCDE

Company code

CHAR4Ncheck with C_COMPCDE

C_CCDR01

PAPM Company Code Driver 01

CHAR250NFree Description

K_CCDR01

PAPM Value Company code driver 01

AMNT23Nlength 17, decimals 3,'.' for decimals, with sign(Unit 0CURRENCY)

0CURRENCY

Currency key

CUKY5NCheck against Currency key table /BI0/SCURRENCY


CBS-PAPM-Driver 2- HeadCount


Flat file driver 02 structure :  Advanced DSO APCOPA02



Info-ObjectDescriptionTypeSizeKeyBusiness rules and Comment

0FISCVARNT

Fiscal year variant

CHAR2YAlways K4

0FISCPER

Fiscal year / period

NUMC7YYYYYMMM

0LOGSYS

source system

CHAR10Ncheck against global filter

C_COMPCDE

Company code

CHAR4Ncheck with C_COMPCDE

C_SITEDR2

PAPM Site driver 2

CHAR250NFree Description

C_CCDR02

PAPM Company code Driver 02

CHAR250NFree Description

K_HCDR02

PAPM Nb Headcount per company Driver 02

NUMB23Nlength 16, decimals 16,'.' for decimals, with sign


CBS-PAPM-Driver 3-Cadre and All

Flat file driver 03 structure :  Advanced DSO APCOPA03


Info-ObjectDescriptionTypeSizeKeyBusiness rules and Comment

0FISCVARNT

Fiscal year variant

CHAR2YAlways K4

0FISCPER

Fiscal year / period

NUMC7YYYYYMMM

0LOGSYS

source system

CHAR10Ncheck against global filter

C_COMPCDE

Company code

CHAR4Ncheck with C_COMPCDE

K_CDDR03

PAPM Value Company code driver 03

NUMB23Nlength 16, decimals 16,'.' for decimals, with sign

K_ALLDR03

PAPM All Head count cadre and no cadre diver 03

NUMB23Nlength 16, decimals 16,'.' for decimals, with sign

Detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way

Dependencies with other applications

Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...

Data loadings

Info providers and objects loaded

Data Load process Steps and Process Chains

Step 1: Initializing/Deleting Data from previous loads through application(PCs trigerred thro' event trigger)

  1.  PC_CBS_PAPM_001A  -  PC CBS PaPM - Driver 1 Amount Del PSA              - Event Trigerred  -  PC_CBS_PAPM_001A
  2.  PC_CBS_PAPM_002A  -  PC CBS PaPM - Driver 2 Head Count Del PSA       - Event Trigerred   -  PC_CBS_PAPM_002A
  3.  PC_CBS_PAPM_003A  -  PC CBS PaPM - Driver 3 Cadre Del PSA                 - Event Trigerred   -  PC_CBS_PAPM_003A

Step 2: Flat File loading for New Driver KPIs and data-flows

   


Step 3 : Load data to aDSOs through main process chain

The main process chain to load all three driver data on a daily basis from PSA to ADSO is as below

  1. PC_CBS_PAPM - CBS: Global PC PaPM PC_CBS_PAPM Change 


Local Process chains to load all three driver data through the application to PSA and Events

  1. PC_CBS_PAPM_001  -  PC CBS PaPM - Driver 1 Amount    
  2. PC_CBS_PAPM_002  -  PC CBS PaPM - Driver 2 Head Count 
  3. PC_CBS_PAPM_003  -  PC CBS PaPM - Driver 3 Cadre

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

Loading frequency

       1. Data Loading to PSA by user : 

           Adhoc when users use the application

      2. Data Loading to PSA for reporting:

           Twice daily at 11 hours and 15 hours

Process Chain Details

1. PC_CBS_PAPM_001A  -  PC CBS PaPM - Driver 1 Amount Del PSA              - Event Trigerred  -  PC_CBS_PAPM_001A


2. PC_CBS_PAPM_002A  -  PC CBS PaPM - Driver 2 Head Count Del PSA       - Event Trigerred   -  PC_CBS_PAPM_002A



3.PC_CBS_PAPM_003A  -  PC CBS PaPM - Driver 3 Cadre Del PSA                 - Event Trigerred   -  PC_CBS_PAPM_003A

4. PC_CBS_PAPM_001  -  PC CBS PaPM - Driver 1 Amount    - run in main Process chain


5. PC_CBS_PAPM_002  -  PC CBS PaPM - Driver 2 Head Count  -  run in main Process chain


6. PC_CBS_PAPM_003  -  PC CBS PaPM - Driver 3 Cadre - run in main Process chain


Main Chain


Data-loading Layers





Transformations

1.DTS_FF_PAPM_002 PC_FILE -> ADSO APCBSI01


2. DTS_FF_PAPM_003 PC_FILE -> ADSO APCBSI02


3. DTS_FF_PAPM_004 PC_FILE -> ADSO APCBSI03



Average performance

if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application


Key FigureEstimation
~ Average Process Chain Runtime
~ Average nb of rows loaded per load
~ Total nb of rows loaded (if full)
~ Average Runtime for 10k lines

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

Queries End User Documentation

Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.


Main queries

BW_QRY_CPCBSI01_0001 PAPM BW Transactional data with version

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

List recurring procedures

Planned Evolution

Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016