| Table of Contents |
|---|
General presentation
Objective of the application
CBS stands for 'Corporate Business Services'
CBS is a dedicated Reporting tool built on SAP BW module. It allow to analyse Functions fixed costs on cost centers and on project.
Usage information
Around 200 users have access to CBS applications. Those users are worldwide and most of them are function controllers.
History
Project done in 2012. It was the first project in BW mixing data from WP1 and PF1/PI1 systems.
Roles & Access
Roles and access
|
Access Management
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
List of application role + menu role and explanation if we have several applications role with specials rules.
CBS is part of the Controlling application (Info Area AREA_F_CO in BW) |
...
| Panel |
|---|
...
Authorization objects
MPR_FC001:
...
|
...
| |||||||
List of authorization objects mandatory for the application.
|
|
...
See also file maintained by Authorization team : BW Catalog of Roles / link: |
DataFlow
...
Overview
| Widget Connector | ||
|---|---|---|
|
| Widget Connector | ||
|---|---|---|
|
List of cubes MPR_FC001:
| Cube | Description | Last month where new data was loaded in cube (updated at 09.19.2023) |
|---|---|---|
| CUB_FC007 | Fixed costs Analysis (External data) | 06.2021 |
| CUB_FC002 | Fixed costs Analysis Acetow | 12.2017 |
| CUB_FC004 | Fixed costs Analysis CICC | 09.2023 |
| CUB_FC003 | Fixed costs Analysis PIM | - |
| CUB_FC006 | Fixed costs Analysis Rhodia | 09.2023 |
| CUB_FC005 | Fixed costs Analysis Solvay | 09.2023 |
...
List of provider MPR_FC002:
| Cube | Description | Last month where new data was loaded in cube (updated at 09.19.2023) |
|---|---|---|
| ODSACCA9 | Cost Center: Actual Costs through Delta Extraction Rhodia S | 01.2014 |
| ODS_CCA9 | Cost Centers: Actual Costs Through Delta Extraction | 09.2023 |
| ODS8CCA9 | Cost Centers: Actual Costs Through Delta Extraction - Acetow | 02.2019 |
| ODS7CCA9 | Cost Centers: Actual Costs Through Delta Extraction - CICC | 09.2019 |
| ODS6CCA9 | Cost Centers: Actual Costs Through Delta Extraction - Solvay | 09.2023 |
| ODS_OPA6 | ODS_OPA6Orders: Actual Costs Through Delta Extraction | 09.2023 |
| ODS8OPA6 | Orders: Actual Costs Through Delta Extraction - Acetow | 02.2019 |
| ODS7OPA6 | Orders: Actual Costs Through Delta Extraction - CICC | 01.2013 |
| ODS6OPA6 | Orders: Actual Costs Through Delta Extraction - Solvay | 09.2023 |
| ODS_WBS6 | WBS Element - Actual Costs trough Delta Extraction | 09.2023 |
| ODS6WBS6 | WBS Element - Actual Costs trough Delta Extraction - Solvay | 09.2023 |
Functional and Technical rules on Workbench + Reporting
Rules & Explanations
Objective of the application
CBS stands for 'Corporate Business Services'
CBS is a dedicated Reporting tool built on SAP BW module. It allow to analyse Functions fixed costs on cost centers and on project.
History
Project done in 2012. It was the first project in BW mixing data from WP1 and PF1/PI1 systems.
Technical Rules on Workbench
Master data management
In the beginning of the project, we discovered that some objects may have same values but can be totally different in the ERP systems.
...
We can specific the company code by table TVARVC and maintain the list via tcode TVARVC in WP1:
BW and ERP systems
- WBD (BW Development) is linked to WD1 (RCS development), DI1 (CICC development), DF1 (Solvay development), TS2 (Acetow Test)
- WBQ (BW Quality) is linked to WQ1 (RCS quality), QI1 (CICC quality), QF1 (Solvay quality) and TS2 (Acetow Test)
- WBP (BW Production) is linked to WP1 (RCS Production), PI1 (CICC Production), PF1 (Solvay Production), RHO (Acetow Production)
- PIM system is not used anymore
Reporting
Queries End User Documentation
Link to user guide
https://drive.google.com/file/d/1h4RMrmL5MR0plRCW0aqKelxvNKrVw-7J/view
Main queries
Dependencies with other applications
CBS applications is dependant with
- FC2 Fixed Costs (obsolete) now replaced by FC GBU Fixed costs
- PS / CAPEX Project costs (common DSO)
- CO Profitability (comme DSO ODS_OPA06)
Data
...
loading
Info providers and objects loaded
MPR_FC001
| Process chain | Provider loaded | Frequency | Time start | Duration |
|---|---|---|---|---|
| PC_FC_CYTEC_003 | CUB_FC007 | At demand (transaction) | ||
| RSP_COOM_OTHER | CUB_FC005 CUB_FC002 | Daily (not week-end) | 2:30 am | 15 min |
| RSV_COOM_CCA_OTHER | CUB_FC005 CUB_FC002 CUB_FC004 | Daily (not saturday) | 2:00 am | 15 min |
| PC_FC_D4 | CUB_FC006 | Working Day 2, 3 and 4 | 1 pm 8 pm | 5 min |
| RSP_COOM | CUB_FC006 | Daily (not saturday) | 1:15 am | 20 min |
| RPC_FC2_BUDGET_1 | CUB_FC006 | Wednesday | 7 am | 1h30 |
| PC_FIXED_COST_BUDGET | CUB_FC006 | Working Day 2, 3 and 4 | 1 pm 8 pm | 5 min |
MPR_FC002:
| Process chain | Provider loaded | Frequency | Time start | Duration |
|---|---|---|---|---|
| PC_FC_D4 | ODS_CCA9 ODS_OPA6 | Working Day 2, 3 and 4 | 1 pm 8 pm | 5 min |
| RSV_COOM_CCA | ODS_CCA9 | daily 1:30 am | 10min | |
| RSV_COOM_CCA_OTHER | ODS6CCA9 ODS6OPA6 | Daily (not saturday) | 2:00 am | 15 min |
| RSP_COOM | ODS_OPA6 ODS_WBS6 | Daily (not week-end) | 2:30 am | 15 min |
| RSP_COOM_OTHER | ODS6WBS6 | Daily (not week-end) | 2:30 am | 15 min |
Record Keeping
We have data since beginning of 2012 and we never made clean-up.
Reporting
Queries End User Documentation
Link to user guide
https://drive.google.com/open?id=0B_p_Afe8sjVlZ0pxa1psVEFwNDQ
Main queries
Main functionnalities
Jump query available
Broadcast
No broadcast
Maintenance
Known bugs
No known bug
Recurring procedure
No recurring procedure
...
Main functionnalities
Jump query available
Data Quality Control
Data come from SAP system. To compare data between BW and sources systems, check propagation layers.
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
<List the existing bugs, its criticity, workarounds and resolution plan.>
Roadmap
<List past & future evolutions for the application (including links to MED/FSD/TSD)>

