General presentation
Objective of the application
P&L
P&L application provides reports fully aligned with BFC structure (BFC Headings) down to REBIT/REBITDA able to analyze P&L starting from the BFC view (Company/Activity) and ability to drill down to Customer Material level.
A profit and loss statement (P&L) is a financial statement that summarizes the revenues, costs and expenses incurred during a specific period of time, usually a fiscal quarter or year.
These records provide information about a company's ability – or lack thereof – to generate profit by increasing revenue, reducing costs, or both.
It was done in 2 phases :
Phase 1 : COPA model of Rhodia legacy (RCS)
Phase 2 :
- Solvay legacy (PQ1)
- BFC Data
- CICC
- Below Gross Margin
- Non ERP companies
IM
Integrated Margin is linked with P&L data and providers BW and BO reports with details of the calculation of the integrated costs
Reporting coordinator is Sandrine Micollet.
Usage information
More than 500 users have access to WC applications. Those users are worldwide and most of them are controllers.
History
P&L was done in 2015 and IM in 2016
Roles & Access
Roles and access
| Role Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M432 | P&L – Upload Data - Non-ERP ZPL_FILE | Role menu for non ERP |
| ZR_RCS_CA_M12 | PL - P&L Reporting | Role menu |
| ZBI_RCS_FI_A33 | P & L – Profit and Loss - End User role | End user role |
Authorisation objects
Link to the BW Catalog of role
https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I
Dataflow presentation
Overview
P&L
WP1
BFC
Non ERP
PQ1
IM
Reporting documentation drive folder:
https://drive.google.com/open?id=0B_p_Afe8sjVlN1J3YzYzdE8taDg
https://drive.google.com/open?id=0B_p_Afe8sjVlTEVnc3NjdDV5U0U
Query documentation folder:
Functional and Technical rules on Workbench + Reporting
Rules & Explanations
Functional rules
Rhodia legacy
COPA module is the ancestor of BW
COPA is divided in “tight” perimeters (in customizing, in VV list, for certain characteristics, for BW data sources) : Operating concern
The lines of the ERP data (COPA value fields from WP1 system) must be translated in BFC account. This translation should be dynamic.
Historic data have be recalcuted with the new allocation Value Field / BFC Account
Historic views are avaible in BFC (not restated)
Value Fields
Value Fields are the lowest key figures in COPA module (For BCS sourcing)
Value Fields are the central elements of the BFC account determination
- P&L analysis is based on BFC Account with a detail by Value Field. For now, it is not useful to have an analysis directly by value field
The organization determination must be as flexible and as dynamic as possible. We had to consider 2 cases:
- CASE A : COPA line items with Material and Distribution Channel valids
- CASE B : COPA line items with Material empty and/or Distribution Channel empty
Solvay legacy data
Existing application in PQ1 with a lot of intelligence
Easier to load from PQ1 than redoing what has already been done
BFC Data
Loaded by flat files
3 levels:
Version 1: Total P&L
Version 2: Interco Sales
Version 3 : Third Party
Another DSO for data without version
CICC
Loaded by BFC flat files
Only for CICC companies
Below Gross Margin
Loaded by BFC flat files only for companies loaded in Non ERP
Non ERP companies
Some companies are in Solvay group but don’t use RCS of Solvay ERP : companies belonging to NOVECARE or SODA GBU
Systems involved
Rhodia ERP WP1
Solvay BW PQ1
BFC (flat files)
- Flat files for Non ERP
Organisation
BFC GBU
BFC Group of Activities
BFC Activity
Technical rules
P&L WP1
We have 2 steps in the business layer.
From the propagation layer, we transpose data from DPCOPA01 to DBCOPA01.
In DPCOPA01, each value field is in a dedicated key figures. Objective of the transposition, we have 1 key figure and 1 field in key (called Value Field) to identify them.
After the transposition, we split data in 2 target DSO: DBCOPA02 and DBCOPA03.
As we have common rules for both DSO, we use an Info source to have those rules inside an unique transformation.
BFC
BFC Data comes from extraction sent by Marie-Yolande KUCZYNSKI
- Every day between 3rd and 20th day + 25th day of the month at 3:30AM (FR)
- In TXT format
- In /BW/exploit/PandL
The file loaded by cancel and replace (using recordmode to delete active records) to propagation layer. For this part, we don’t respect LSA methodology.
All business rules calculated between propa DSO DPCOPA02 and Info source
- Easier for maintenance
- Very simple business rules
- Only exclusion of data between info source and business layer
For business and reporting layers, we load by Delete + Full.
From the BFC File, we also load 2 other targets :
- CICC system
- Companies not working on ERP : only a part of P&L
Those targets are in business layer.
We load them by Delete + Full for current and previous months : determination in process chains to update TVARVC table
We do selective deletion using programs and loading with selections in DTP
The time reference could be changed manually. There is a written procedure for that
The reporting layer is loaded by deletion and full loading.
Non-ERP
We needed a solution for companies not working on ERP. We have created a specific transaction : ZPL_FILE
The transaction is based on program : ZBW_PL_PC
With this transaction, user can load excel file for
- Customer master data
- Material master data
- Non-ERP transactional data
The transaction available in SOLIA portal. For information, it's better to use IE and not Chrome
We have created a new authorization object (C_SRSYST) to be sure that users can only load data for companies they have access to.
We test user’s authorizations with DPAUTH01 DSO
For master data, we can display content of master data in the screen and also save it in an excel file
For master data and transactional data, user can load excel file.
We control content of the file to be sure that there is no error (missing field or incorrect value)
Once data is loaded:
- Save file in csv in /BW/exploit/PandL
- Execute process chain
- By event
- Load file to PSA
- Manage “delta queue” is several loadings at the same time
- Another process chains to load from PSA to BW Info provider
- 1 for Master data
- 1 for DSO and cubes
- Process chain runs 3 times a day (managed in Global filter master data)
PQ1
Common rules:
In business layer, we filter to keep posting on account types S (G/L Account) and M (Materials)
Rhodia legacy rules:
We continue to use ODSFIGL3. This DSO is very huge so it would have been to long to load other DSO and it would be to heavy in WBP system.
A split of data is done between propagation and business DSO (ODSFIGL1 and ODSFIGL3), in the start routine of the transformation.
The split is also done in WP1 system, in ZWFAT143 table. This table is filled in WP1 when the data source 0FI_GL_4 is launched. The data are retrieved in ODSFIGL2.
Integrated Margin (IM)
Common rules:
Dependencies with other applications
No dependencies
Data loadings
Info providers and objects loaded
List on info providers inside the technical cockpit.
Loading frequency
WP1 and BFC are loaded daily at 1h30 am (french time)
Non ERP is loaded 3 times a day
PQ1 loading: on demand from PQ1 system
Average performance
WP1: 1h40 for P&L and IM
BFC: 10 min
Non ERP: 5 min
PQ1: 10min for GM and 1h for PCA
Record Keeping
We keep all records.
Reporting
Queries End User Documentation
All the reporting is available throught workbooks in the role "PL - P&L Reporting" ZR_RCS_CA_M12
Query documentation:
Main queries
There are several queries but the main ones are:
BW_QRY_MVCOPA01_0001 BW P&L Query
BW_QRY_MVCOPA01_0002 BW P&L - Monthly Query
BW_QRY_MVCOPA01_0003 BW P&L Reconciliation Query
BW_QRY_MVCOPA01_0005 BW Integrated Contribution Margin Query
All queries use structures for key figures. There are many key figures, using calculated and restricted key figures inside.
Main functionnalities
Jump query available
Broadcast
No broadcast
Maintenance
Known bugs
No known bug
Recurring procedure
P&L : Non ERP transaction
https://drive.google.com/open?id=1gF426ok7VvnF1-idij_FCsMt7HMYQuY4LiN34CseSZs
P&L : Time reference for CICC and GM flat files
https://drive.google.com/open?id=1cqPl_gkWdFubpTRyxbSaJtsa4iv8m4uH-bRT8dGOyoY
IM: No Delta - Delete and full for current and previous months.
For manual full loading, DBCOPA20 and DBCOPA23 must be loaded month by month
Program for LER determination
https://drive.google.com/open?id=1pEJTKs37dEloE7HGiY9lVsPf0crLoxxbzVN9oN33cr8
Program for LER info providers
https://drive.google.com/open?id=1-54NzGz63dagA-UyyIIoNgK8fwmzo-e-YAnASxInwjo
Planned Evolution
PQ1 data flow will be removed and replaced by PF1 system (project SPS)
File loaded by cancel and replace (using recordmode to delete active records) to propagation layer
For this part, we don’t respect LSA methodology
All business rules calculated between propa DSO DPCOPA02 and Info source
Easier for maintenance
Very simple business rules
Only exclusion of data between info source and business layer
We load by Delete + Full
Reporting layer
- We load by Delete + Full
Data loading
Save file in csv in /BW/exploit/PandL
Execute process chain
By event
Load file to PSA
Manage “delta queue” is several loadings at the same time
Another process chain to load from PSA to BW Info provider
Master data
DSO and cubes
Process chain runs 3 times a day (managed in Global filter master data)