This application is part of the Finance domain and its based on SAP CO Order postings, including Actual postings and Commitments from 2015 and describe the Environmental & Rehabilitation (ER) expenses.
For these queries the access is provided based on the BW menu and it's done via Service one.
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 15.09.2023 | Inês Vilares | Initial draft |
| Data Product Type |
|
| Technologies |
|
Data Sources Note: list of all applications and various environment |
|
2.0 Business Process
To be checked
3.0 Application Feature Overview
For this application find below all the workbooks available:
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
BW - Environ. & Rehab. database (Core Workbook) | This report shows the amounts regarding the costs with the environmental and rehabilition expenses for all orders in the scope for the following measures:
| Mandatory:
Optional:
| BW_WBK_ER_0002 | BW_QRY_MVCOOP01_0002 |
| BW - Environ. & Rehabilition expenses analysis (Core Workbook) | This workbook contains the same information as the "BW - Environ. & Rehab. database (Core Workbook)" splitted by time frequency:
| Mandatory:
Optional:
| BW_WBK_ER_0001 | BW_QRY_MVCOOP01_0001 |
4.0 Functional Specification
4.1 General Data/Calculations
For these reports, it’s important to understand some concepts which will allow the user to work with the reports and analyze the data.
| Consolidation View | The query takes the integration rate of the company and the partner from a table managed by GAR.
In this way, the user has 4 options:
|
|---|---|
| GBU Assignment | The concept for GBU doesn't exist in SAP but it’s a requirement to have in BW since in BFC we have this definition. This GBU assignment is different for WP1 and PF1 and it will be explain in detail in the Process Definition section. |
| PRS Concept | The PRS is one dedicated SAP environment (based on PF1) whose aim is to unify some structural information as Master Data information for customers, vendors, company codes, etc. For this, depending on each master data we are referring to, we have specific tables created to maintain the data and have the configuration from source systems to BFC definition and alignment. |
| BFC site | Order attribute entered as External number in SAP Ex.: LIVOU, HALIF, LILLE… NB: relevant for authorizations |
| Orders | Posted object in SAP CO document Ex.: 900100 CUBAT-BIOSOL PROJECT (WP1), 5900160 THOROF-GROUNDWATER (PF1)… NB: codification is quite different between WP1 and PF1 areas |
| Order Type | Are used to categorize various cost objects and represent specific business processes within the Controlling module. These order types are used for cost tracking, budgeting, and monitoring purposes. For this scope the order attribute entered in SAP to distinguish Recurring (Y998) and Non Recurring (Y999) Environmental Cash-out orders. |
| Object class | Order attribute entered in SAP to distinguish CAPEX (invest.) from OPEX Ex.: OC |
| Cost element | Posted P&L account in SAP CO document Ex.: 98300207 MAINTENANCE (WP1), 6122040000 Waste treatment (PF1) NB: codification is quite different between WP1 and PF1 areas |
| 1/2/3 - CE grouping | Hierarchy based on Cost elements and Object class combinations: 1 - CE grouping: ER (Environmental & Rehabilitation) 2 - CE grouping: Z-ENVEXP (expenses) and Z-ENVREV (revenues) 3 - CE grouping: Z-DISMT, Z-ENVLEG, Z-REMEDO… |
| Period | Derived from Posting date (Actual) or Scheduled delivery date (Commitments) in SAP CO document Ex.: 1, 2… |
| PO number/item | Number of PO document and item in SAP, including text of item Ex.: 4502341051/20 Zone I site investig, 4201086557/20 PINCEL RETROPROJ PT… |
| Profit Center | Order attribute entered in SAP (to determine GBU in WP1 area) Ex.: 8090-I0534 0087 Silica (WP1), CBLT 5835 - Bollate com (PF1)… NB: codification is quite different between WP1 and PF1 areas |
| Resp. cost center | Order attribute entered in SAP Ex.: 6068-4886 Environmental Provis (WP1), XF14700000 REGULATORY ENVIR.SAF (PF1)… NB: codification is quite different between WP1 and PF1 areas |
| Vendor | Vendor entered in SAP PO header Ex.: 55171 ETABLISSEMENTS KAISER (WP1), 2110192 THE BRIGGS COMPANY (PF1)… NB: codification is quite different between WP1 and PF1 areas |
4.2 Process Detail
4.2.1. Report/Process Definition
| Domain | Finance |
|---|---|
| Application | BW reports under ER - Environmental & Rehabilition expenses analysis |
| Provider | MVCOOP01 |
BW - Environ. & Rehab. database (Core Workbook)
As mentioned this workbook show all the information for the ER scope based on the order types Y998 and Y999 in only one report/sheet.
check object class and flat file
BW - Environ. & Rehabilition expenses analysis (Core Workbook)
This workbook contains the same information as the "BW - Environ. & Rehab. database (Core Workbook)" splitted by time frequency:
Periodic View
- Only periods up to Fiscal year/Period entered in prompt are displayed (followings are empty);
- Commitments are only shown in reporting if period entered in prompt is the current one (otherwise, corresponding columns are empty); this is the whole amount of current Commitments, not dependent from Fiscal year/Period entered in prompt;
- Amounts in CO area curr. can be converted in EUR if entered in prompt;
- YtD calculation is the sump of amounts from January to Fiscal year/Period entered in prompt; YtD variance calculation is based on CO area / EUR currency.
Selected Quarter View
- P1Q is the 1rst month of quarter defined according to Fiscal year/Period entered in query prompt, P2Q the 2nd and P3Q the 3rd
ex.: for 05.2015 = 2nd quarter of 2015 → P1Q = 04.2015, PQ2 = 05.2015 and P3Q = # (empty); - Commitments: idem Periodic view;
- Amounts in CO area curr. conversion in EUR: idem Periodic view;
- YtD calculation/variance: idem Periodic view
Quarterly View
- Q1 is the 1rst quarter of the year defined according to Fiscal year/Period entered in prompt, Q2 the 2nd, Q3 the 3rd and Q4 the 4th. Only quarters less or equal than the one derived from Fiscal year / Period entered by user are valuated;
i.e.: for 05.2015 entry = 2nd quarter 2015 → Q1 = 01 to 03.2015, Q2 = 04 to 05.2015, Q3 = # (empty) and Q4 = # (empty); - Commitments: idem Periodic view;
- Amounts in CO area curr. conversion in EUR: idem Periodic view;
- YtD calculation/variance: idem Periodic view
5.0 Non-functional Descriptions
5.1 Usability
5.2 Regulatory Compliance
5.3 Security
5.4 Performance
5.5 Reliability
5.6 Scalability
5.7 Compatibility
5.8 Availability
5.9 Refresh of the Data
The data load is once per day in the early morning..