1.0 Overview
The P&L (Profit and Loss) application it’s part of the Finance domain using data from SAP systems, non-ERP system and BFC (Business Financial Consolidation) information based on data from COPA (Controlling - Profitability Analysis) a component from SAP CO (Controlling) module. The aim of this application is to give a P&L reporting adapted to Soda Ash GBU requirements. It is based on the corporated P&L query and offered special axis and calculation for Soda Ash. |
For this Application the access is provided based on the BW menu "PL - Profit and Loss" and it's done via Service one. Fill the form In SAP system select the "WBP - BW Business Warehouse" In WBP - BW Business Warehouse : Select the Business Role select the "PL - Profit and Loss" |
Target Users: Soda Ash controllers. |
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 14.12.2023 | Inês Vilares | Initial draft |
|
2.0 Business Process
The base is the same for the Profit and Loss application in the functional documentation. We can see in that documentation the logic for the P&L.
For this application this was built in 2018 and the need was to provide a dedicated report only for GBU SD .This report is a separate report from the P&L reports.
This new report:
- is based for main Part on P&L datas;
- will construct Soda Ash business axis that are not existing in ERp or in actual BI reports;
- SD BU;
- Origin.
- retreat some functional flow :
- redetermination of internal or external amounts
- reallocation of transport cost between SD BU for specific flow
- recalculate some lines of the P&L (internal sales and COGS ) for specifics flows
On a monthly basis the business needs to analyzed the logistic costs and to verify the origin information to be able to see in more detail the flows associated to Soda Ash and the impact of the values in the P&L.
The Origin/Sourcing field will provide details on where the Soda Ash is produced (for example, it can be in Europe or North America), distinguishing whether the material is synthetic or natural.
The Scope field categorizes whether it is internal or external and further checks are conducted for these flows (for example, if it is Europe to Europe or Europe intra BICAR).
3.0 Application Feature Overview
For this scope we only have one query:
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| BW P&L by BU - Monthly Query (Soda Ash) (Core Query) | This report shows the values with the P&L structure with the additional information for some fields required for Soda Ash to see the amounts and quantities in detail for the flows/operations with Soda Ash (external and internal). | Mandatory:
Optional:
| N.A | BW_QRY_MVCOPA07_0001 |
4.0 Functional Specification
4.1 General Data/Calculations
The base is the same for the Profit and Loss application in the functional documentation. We can see in that documentation the logic for the P&L.
4.2 Process Detail
4.2.1. Report/Process Definition
| Domain | Finance |
|---|---|
| Application | NA since it's only a query |
| Provider | MVCOPA07 |
SAP BW High Level View
To see the data from the source systems see below how the information is organized in the BW perspective:
General Requirements:
Assuming that BW is the selected tool it is recommended creating a separate model/cube in BW although fed by the existing BW P&L one.
Reasons:
- The calculations are done at an aggregated level and cannot be made for a detailed level
- The BFC R1000 / R15400 headings cancellation (aggregated level) involve complex cross data checks.
- The request is complex and it involves some performance risks.
- The new axis of BU SD is too complex to build in the existing P&L impacting the whole model volumetry → side effects in other GBUs
Macro process
We have the specifications for each step in the functional specification done in 2018.
5.0 Non-functional Descriptions
5.1 Usability
as per standard.
5.2 Regulatory Compliance
as per standard.
5.3 Security
as per standard.
5.4 Performance
as per standard.
5.5 Reliability
as per standard.
5.6 Scalability
as per standard.
5.7 Compatibility
as per standard.
5.8 Availability
as per standard.
5.9 Refresh of the Data
The load for this report it's for working days around 3 a.m.