Roles & Access

Dataflow overview

User Requirements

Segmented P&L Prestudy

Dataflow overview :

Technical Detailled Specification - 11490 - PR00097 Segmented P&L - Data extraction to PAPM

STEP 1 : BW dataflow for PAPM extraction:

ADSO ABCOPA08 - P&L Snapshot (Solvay)

ADSO ABCOPA09 - P&L Snapshot (Rhodia)

STEP 4: Calculation view used to extract data to PAPM :

Solvay.IA_FMCO.IA_FMCO_CO.IA_FMCO_COPA/CV_FMCO_COPA_PL_SNAPSHOT_PAPM

Transaction Type Enhancement in P&L BW data flow:

1. Calculation view using CPCOPA01 data : Solvay.IA_FMCO.IA_FMCO_CO.IA_FMCO_COPA/CV_FMCO_COPA_PL_TP_TRTYPE
2. Composite Provider using the CV data: CPCOPA04
3. Jump P&L Query BW_QRY_CPCOPA04_0001 (available from Main P&L Query BW_QRY_MVCOPA01_0001)

Technical Detailled Specification - 11490 - Segmented P&L - Batch enhancement

General presentation

Objective of the application

Name : Segmented P&L in PAPM

Project ID : 11490

Description : BW a solution based on existing P&L reporting layers, that can be used to fuel Segmented P&L application to be built in PAPM

PaPM = Profitability and Performance Management is a native SAP HANA solution that maintains and executes complex calculations, rules and simulations. With no set data model, it is highly flexible and enables you to create high-speed profitability and cost analysis with minimal IT involvement. In Solvay, we have 2 main parts, which are CBS and P&L segmentation. This wiki will focus on P&L segmentation. PaPM is an application that is installed on top of a BW server. It is taken care of by the PaPM team (Carl Zeng). BW data in ADSO that will serve as a datasource of the future SEGMENTED P&L application built on PAPM tool.

Tool Leader + IT leader of the application:  

Usage information

History

Created in 2022

Technical rules on Workbench

Rules & Explanations

The main subject the implementation of a “database” (BW ADSO) that will serve as a datasource of the future SEGMENTED P&L application built on PAPM tool  

The source of data will be the current BW P&L application.
For audit reason, the new Segmented P&L need to have Organisation structure freezed at the end of each month . Following the previous PAPM CBS project we Will do “SnapShots” of P&L data in dedicated ADSO. 
By storing organisational structures in Snapshot ADSO we will be able to provide the situation of SOLVAY at each end of month.

Those ADSO will not have to be emptied and recharged unless we will lose this historical vision.
Transaction Type (TP): This key information for Segmented P&L process in PAPM is coming from BW COPA, but must be restated in a new TP in BW.
The restatement is based on a new specific (ZCOPA_TP_DERIV) derivation table, including the Manufacturing Plant in its key.
Consequently, this Manufacturing Plant has also to be defined in BW with the same Business rules already set up in the Model S BW solution (see below).

Nature of Data

The source of data is P&L data at LEGAL view , standard costs (no IM costs) in Company Code Currency 
Considering this need we can feed the new Database directly from P&L item items DSO

Only PF1 and WP1 is used by PAPM Segmented P&L in first version (NON ERP , CICC and BFC are not take into account)

This application provides Sales quantities in KG and VKG  based on Material master data conversion unit (as it is done in P&l Queries). The conversion is done at the moment of PapM loading.

This conversion is processed dynamically in both calculation views ( CV_FMCO_COPA_PL_SNAPSHOT_PAPM & CV_FMCO_COPA_PL_TP_TRTYPE )

using CPUOMCMAT2 DSO UOM Material conversion rates : (first conversion to material UOM, then to KG and VKG)

This application provides amount at P&L element (value field) +OCDE  Activity (for PF1) and also store the BFC account at the moment of snapshot. We don't need to provide any KPI of P&L .
This application extracts all data of P&L (above and below REBIDTA)

Manufacturing Plant

In the Model S, the Manufacturing plant is defined either from the Batch attributes, either from the Material/Plant attributes (see the Production plant issued from corresponding Special Procurement Key) for WP1 or Profit center for PF1.
All those info have to send from BW to PAPM where the Manufacturing Plant will defined the same way it is already in the BW Model S solution.
Remark : manufacturing Plant could be a plant of another ERP. So we have to introduce the Source System of Manufacturing plant.
Up to now only PF1 data in BW are available at Batch level; on WP1 side, even if the Batch info is available in CO PA entries, it is not updated in BW.
Current P&L model in BW has been enhanced with the Batch for WP1 source.
NB: in order to ensure consistency of the whole P&L solution, the batch has also been added in the Integrated Margin objects (DSOs).

This Manufacturing plant determination is processed in the Calculation views (steps 4 and 7 of BW dataflow for PAPM overview) with the following rules : 

This dynamic determination is implemented at the beginning of the 2 following calculation views :

CV_FMCO_COPA_PL_SNAPSHOT_PAPM & CV_FMCO_COPA_PL_TP_TRTYPE

Transaction Type Enhancement

Both origin Transaction Type (TP) (see ZZWWE16 from WP1 / ZZWWTPT from PF1) and restated TP are available in Snapshot ADSOs, but also in core P&L query Jump (no need to provide the restated TP in other P&L queries based on cubes)
By construction Enhanced TP from PAPM ADSO could be different from P&L query Jump (GBU and Material division are dynamic)
The restated TP determination has to be automatic: whenever the derivation table is updated, restated TPs are in all entries (including past ones) in Snapshot ADSOs and in P&L query Jump.
ZCOPA_TP_DERIV derivation table is maintained in BW with a key allowing a join from ADSO Snapshot to get TP restated.

Example of data in restatement table ZCOPA_TP_DERIV:

This table can be maintained in SM30 using transaction ZSEGPL (see below). 

The view ZCOPA_TP_DERIV_V is based on the restatement table and displays descriptions for several fields.

The content of this parameter table is retrieved in the calculation views : CV_FMCO_COPA_PL_SNAPSHOT_PAPM & CV_FMCO_COPA_PL_TP_TRTYPE

Access to the table is done multiple times in the CV with different keys in order to allow several combination for TP restatement:

Here are some explanation of how the restatement table is working:

The data inserted must follow one these possible 7 patterns / combinations to be considered:

Other combination's visualization where X = field with value :

For fields Division, Material, Sold to and Country : 

- a specific value will match with the corresponding value in COPA data
- '#' will match with Unassigned values in COPA data
- a blank field will match with all values

For other fields:

- a specific value will match with the corresponding value in COPA data
- '#' and a blank field will match with Unassigned values in COPA data

Example of the first combination, with all fields filled in:

Example of the third combination, with a defined value for Sold to Party and Country, and all values accepted for Material and Division:

If an entry in the restatement table does not match any of the 7 predefined patterns, then it will be ignored and will not be applied.
Example: 

The combination with fields Division, Material and Country with blank values and Sold to Party filled with value is not supported. This entry will be ignored.

N.B.: The read priority of the restatement table is done in this combination order : pattern 1, then pattern 2 , then pattern 3,... then pattern 7.  
If a COPA data can match several lines in the restatement table: then only the prior combination will apply (if it matches both pattern 2 and 6, then only pattern 2 will apply for TR Type restatement).

N.B.2: If no TP transaction type can be dertemined, it will be assigned the same value as the Transaction Type from the P&L COPA source data.

Please find HERE the test document for this calculation view detailling several case examples.

Snapshot Mechanism

Snapshots are done automatically each month on M-1 (for all the perimeter except a list of Authorization Scopes)  and also can be done manually through the specific transaction ZSEGPL

In the Manual transaction user can select :
- a list of Companies or plants 
- a range of Months 
- a list of authorization Scope to exclude
- a list of Sold To 

When user do a manual snapshot the program overwrites the perimeter of selection in Snapshot aDSO
The list of authorization Scope (attribute of Company code) take into account in the snapshot could change by users
A BW query based on Snapshot aDSO has been developped by PAPM team (Carl Zeng).
We have to feed the new snapshot ADSO since 2021 but the data must be stored for 10 years  

BW specific transaction ZSEGPL for manual Snapshot gives also access to :
Input screen for Authorization scope exclusion
Input screen for TP derivation values
File path for TP Derivation table loading

See Detailed infos & Model sheets

ZSEGPL Main transaction

Uses program ZBW_SEGPL_MAIN: Main program of transaction ZSEGPL

ZSEGPL_AUT: Maintenance table for Authorization scope

Allows to manually maintain data in table ZCOPA_SNPSHT_AUT.

This table contains the list of Authorization scope to be excluded from snapshots.

ZSEGPL_FIL: Import flat file for Restatement table 

Program ZBW_SEGPL_FILE : Called in transaction ZSEGPL to upload flat file for Restatment table

Here is an example of the expected file format: BW Derivation Table Example 1.xlsx

Key user in charge of flat file loading : Tiago Costa

Some Business rules are being checked before flat file data integration:

In case of data quality rejection, all details are displayed in the transaction:

In case of no data rejection, a success message pops up:

Tests examples are available HERE.

ZSEGPL_SNP: Manual Snapshot

Uses program ZBW_SEGPL_SNAP: Called in transaction ZSEGPL to trigger manual snapshot reload

The manual snapshot perimeter can be updated through this transaction.

Reload scope is stored in TVARV table with NAME field = Z_SEGPL_CALMONTH / Z_SEGPL_COMPCDE / Z_SEGPL_PLANT / Z_SEGPL_SOLDTO

These values are then used during manual snapshot : during the selective deletion of DSO ABCOPA08 & ABCOPA09 and in DTP executed filters.

Snapshot is then triggered by run the Process chain TD - T - Manual Snapshot PC_COPA_PL_48.

ZSEGPL_TPD: Manual Maintenance of Restatement table

Reporting

Main queries

New Jump P&L Query BW_QRY_CPCOPA04_0001 (available from Main P&L Query BW_QRY_MVCOPA01_0001)

This new query is a copy of the original Jump Query BW_QRY_CPCOPA01_0001 with the new restated TP Type.

Dependencies with other applications

Data loadings

Info providers and objects loaded

Loading frequency

Monthly process chain : PC_COPA_PL_47 (TD - M - CPCOPA01 Snapshots) : Scheduled every month on the 4th working day at 10am

Manual snapshot Process chain : PC_COPA_PL_48 (TD - T - Manual Snapshot) : triggered using ZSEGPL transaction

Average performance

Data Quality Control

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

Several issues have been encountered during the Project phase.

All have been either explained or corrected.

All informations are available in the Issue List in BW Part Document

Roadmap