This application used the data from Working Capital application (FI) and the Project Costs applications (PS), you can see more details in the functional documentation for the respectives applications. The objective of this application is to allow BFC Capex vs BW project reporting (PeC and Cash) data reconciliation: it mainly means providing a detailed view of all BFC CAPEX components (PeC/AuC, PeC/FXA, Fixed Asset Supplier, and Lease debt), to be available on a wide range of axes also shared with BW PeC and Cash solution. This fine analysis grid of CAPEX should allow to:
|
For these queries the access is provided based on the BW menu and it's done via Service one. |
Target Users: Controlling teams. |
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 31.08.2023 | Inês Vilares | Initial draft |
|
CAPEX stands for "Capital Expenditure." It refers to the money a company spends to acquire, upgrade, or maintain physical assets such as buildings, machinery, equipment, vehicles, or technology infrastructure. Capital expenditures are typically made with the expectation that they will provide benefits to the company over an extended period, often several years. Key points about CAPEX include:
In this way, it's important to perform several analysis for CAPEX data to provide long-term value and benefits to the company. CAPEX Calculation: CAPEX = PeC + FA Supplier + Lease debts
In here we will have the information from the investments projects and lease contracts (and related with the vendor values this is excluded from WC to be in this scope for the CAPEX analysis). |
For this application find below all the workbooks available: I need to review the reports with Pierre it's not the same as in the documentation
CAPEX Invest. Projects
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| CAPEX BFC data - Invest. (Core Workbook) | This report show the values for the YTD for each month and the amounts for each month. The structure contains all the BFC accounts related with the investment data for CAPEX. | Mandatory:
Optional:
| BW_WBK_CX_0011 | BW_QRY_MVFICX01_0011 |
| CAPEX FA adjust. analysis L40800 (Core Workbook) | This report shows the data related with the values from SAP FI data for the Projects and compare this data with the information from the BFC Heading L40800 (closing - open values) for the Fixed Asset Supliers. | Mandatory:
Optional:
| BW_WBK_CX_0009 | BW_QRY_MVFICX01_0009 |
| CAPEX Invest. Project to BFC synthesis (Core Workbook) | Mandatory:
Optional:
| BW_WBK_CX_0018 | BW_QRY_MVFICX01_0018 | |
| CAPEX Invest. Project vs FI analysis (Core Wrokbook) | BW_WBK_CX_0014 |
CAPEX Lease Contracts
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| CAPEX Lease B/S by Flows (Core Workbook) | BW_WBK_CX_0016 | |||
| CAPEX Lease BFC Interface (Core Workbook) | BW_WBK_CX_0015 | |||
| CAPEX Lease Colmar check (Core Workbook) | BW_WBK_CX_0023 | |||
| CAPEX Lease Debt/RoU based on RE Act./Plan. Cash flow (Core Workbook) | BW_WBK_CX_0019 | |||
| CAPEX Lease Future Cash flow for Budgeting (Core Workbook) | BW_WBK_CX_0020 | |||
| CAPEX Lease GL extract for KPI automation (Core Workflow) | BW_WBK_CX_0001 | |||
| CAPEX Lease REFX RoU (Core Workbook) | BW_WBK_CX_0017 | |||
| CAPEX Lease Rolling Future Cash flow for L6605 (Core Workbook) | BW_WBK_CX_0022 |
fg
| Consolidation View | The query takes the integration rate of the company and the partner from a table managed by GAR (Group Accounting Reporting).
The formula to retrieve the consolidated sales is in line with BFC: Consolidated Sales = Amount * Max [ 0, Integration Rate of CY (tingsoc) - Integration Rate of Partner (tingpart) ] Internal Sales = Amount * Min [ Integration Rate of CY (tingsoc), Integration Rate of Partner (tingpart) ] The integration rate of the partner is managed on the TRADING PARTNER. For specific cases some external customer must be considered as internal for certain company code (joint venture for example) . For cases the Partner integration rate is taken at the crossing Sold To/Company code. 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. WP1 Logic: (to be completed) PF1 Logic: (to be completed) |
| Exchange Rate | All the PS queries use the same type of currency conversion:
This means that each document will be converted with the rate available for the posting date of that document. IE : Documents posted in January will be converted with the January rate, even if you run the report in february. Depending on the key figure, the "Period" will be different : Budget : the date will be the start of the project (WBS Creation date) Commitments : Rate available at the theoretical reception date if the date is in the past, or current rate if date in the future. Plan : Rate available at the month of the plan data. PEC : Rate available at the reception date. Cash – Payments : Rate available at the invoice reception date. Cash – Down payment : Rate available at the down payment posting date.Cash – Non-Purchase requests (Stocks, Hours) : Rate available at the cost reception date |
| BFC Headings | This is the correspondent account in the BFC official reporting tool for Solvay to report the values. |
| BFC Flows | This indicates the type of movement performed in SAP and how we will allocate this to the respective accounts in BFC tool. Example: we can have flow for acquision, retirement, open values, closing values, etc. |
| Annual Closing | Each end of year, the main BW master data (about the structure) which are not time-dependent need to be frozen = no more loading from ECC or flat file on these main master data. To avoid the impact of the new evolution scheduled for next year on the yearly closing a freeze is applied to block the loading to allow the yearly closing period with the same scope done for the year and not with inputs for next year, for some master data, the loading are freeze in the middle of December until end of January. So when there is a new organization, historical data is restated in BW (not in SAP and BFC). |
| Domain | Finance |
|---|---|
| Application | BW reports under CX - CAPEX Analysis |
| Provider | MVFICX01 |
The CAPEX Application was built for different reasons but the main reason it was because exist some issues with the Project Costs solution and the CAPEX solution allow the users to justify and correct sometimes the figures that we have for the investment projects making a link on what we have in Project Cost, in FI and in BFC data. The Project Costs application we don't have any link to the BFC data so this CAPEX application facilitate this reconcilation between BFC CAPEX vs BW PeC and Cash data. In this section we will approach: |
Integration in a single reporting tool of 3 kinds of data to be compared, in Rhodia (WP1) and Solvay Legacy (PF1) area:


The information in BW is coming from the Working Capital (FI) scope and Project Costs (PS) scope where in here we use the cubes information to fill the Multiprovider with the respective data for CAPEX information. |
CAPEX analysis in BW.xlsx ask Pierre
| Structure | Data information |
|---|---|
| PeC | A20*** and A21*** postings with BFC Flow F20, F23 and F53 (Acquisition) |
| FA Supplier | L40800 YtD and Monthly variation (= F99 closing value - RS100 opening value) |
| Lease Detbs | L16810/L56010 YtD and Monthly variation (= F99 - RS100) |
For reporting convenience:
Calculation for CAPEX: |
YtD and Monthly comparison of BFC CAPEX data vs SAP CAPEX FI postings
| BFC Field | Description | BFC Nature |
|---|---|---|
BFC Pack | It's the data coming from SAP to BFC tool | OLIA01 |
BFC Adjt | Postings made only in BFC side | <> OLIA01 |
| BFC Conso | Its the information which will show the final figures for the group to the stakeholders and it's the BFC Pack + BFC Adjt | - |
BFC vs FI comparisons should be done only in Conso. View; balances are supposed to be equal |
| Structure (FI data) | Data information | Notes |
|---|---|---|
| PeC | A20*** and A21*** assigned GL account YtD/Monthly balances with FI Conso. tr. type F20, F23 and F53 (WP1) or 120, 125, 275, Y01 and Y42 (PF1 and PI1) Acquisition | Since the flows in PF1 and PI1 as a different flow number exist a link between PF1 Conso. tr. type and BFC flows which is managed in ZZF_BFC_AA. |
| FA Supplier | L40800 assigned GL account YtD and Monthly variation (closing value - opening value) | |
| Lease Detbs | L16810/L56010 assigned GL account YtD and Monthly variation (closing value - opening value) | For reporting convenience:
|
In SAP when we have the vendor invoices the amounts are posted in a reconciliation account (ex: WP1 account 40100100) as a daily basis process. In here we have the amounts for the different scopes (no assigment if it's a vendor value or a FAS or a lease vendor).
In the month end closing process, exist in SAP a program to reallocate/transfer these values as a restatement in a specific G/L vendor account (ex: WP1 account 4080300) to have only the values correspondent to the investment projects with the Net of tax amount.
This program exist in WP1, PF1 and PI1 and as we know, in BW we also have a logic to do the same process for the assignment to know where the amounts belongs on a vendor perspective (payables, lease or investment). confirm only the assignment is perform in BW based on the info from 40100100 account.
This logic in BW side it's much more accurate comparing with the SAP program since we can have some differences which BW as the correct assignment and the SAP program don't. This is something that it's happening a long time ago and the proposal was to use the data from BW logic and transfer to SAP and in this way they can use that this data in SAP and fill the BFC with more accurate data.
Only in PI1 system use this BW logic, WP1 and PF1 they use the SAP program logic
Summarize:
| System | Assignment | Result |
|---|---|---|
| WP1 | the postings with the correct assignment are made by the SAP program | BFC data <> BW data |
| PF1 | the postings with the correct assignment are made by the SAP program | BFC data <> BW data |
| PI1 | the postings with the correct assignment are made by the load of data from BW side (in PI1 is different since to have the posting for FAS we calculate the FAS data in BW side and we sent the result as a file to PI1 and then a program run in 1 PI1 but based on BW information) | BFC data = BW data |
This can explain some differences between BW and BFC data.
5.5 Reliability
5.6 Scalability
5.7 Compatibility
5.8 Availability
5.9 Refresh of the Data
BFC data Loads:
The loads to BW it's once per day during the closing time (D+3 until D+20).
FI Data loads:
From WP1: 7 times a day during month-end closing (D-1 until D+4), otherwise 3 times a day
From PF1: 3 times a day