The Working Capital BW Reports are part of the Finance domain and utilize data sourced from SAP systems associated with Receivables, Payables, and Inventories originating from the Financial (FI) module along with submodules AP, AR, and GL.
It’s a FI oriented solution, mainly based on SAP accounting documents widely enhanced in BW (ex. CO assignment of Vendor postings).
It mainly aims at providing GBUs with detailed Payables, Receivables and Inventory data for Industrial WC analysis and piloting, including reconciliation with BFC. This solution has been in WBP since 2015.
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 08.08.2023 | Inês Vilares | Initial draft |
| Data Product Type |
|
| Technologies |
|
Data Sources Note: list of all applications and various environment |
|
2.0 Business Process
The working capital is a financial indicator used to measure the Free Cash Flow of the enterprise. - To be completed
It is equal to the sum of:
- Value of the stocks
- Value of the customer receivables
- Value of the vendor payables
For this, the users can check on the SAP side the data for Receivables, Payables and Inventories but not with a high level view for all the dimensions in the same place or to have detail view for each part of the Working Capital with some additional information which is important for their analysis on a daily and monthly basis, as example to have aview of the values by GBU which only exists in BFC and BW side or for the factoring concept where with the transfer of the documents in the source systems they lose information and in BW it’s possible to track this easily.
3.0 Application Feature Overview
For this application find below all the workbooks available:
1- For GBU Conso. View
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| WC GBU Solvay Group - BFC vs BW extract (Core Workbook) | Report to compare the data from BW with the BFC data from FC pack. The user can compare the Receivables, Payables and Inventories data for one specific period and see the values to be able to check the final values for BFC Conso and BW and analyze the diferences if exists. | BW_WBK_WCAP_0010 | BW_QRY_MVFIWC01_0006 | |
| WC GBU Solvay Group - Inventory extract (Core Workbook) | It's possible to see detail information for Inventories such as material division,, material group, PIF code, plant among others and analyze the Total Stock value, Total Stock Quantity and Unit price for different months. | BW_WBK_WCAP_0007 | BW_QRY_MVFIWC01_0005 | |
| WC GBU Solvay Group - Payables extract (Core Workbook) | It's possible to see detail information for Payables such as vendor number, PRS vendor number, name, among other fields that is possible to add to analyze the total balance for vendors and the values overdue and due depending on the calendar selection. | BW_WBK_WCAP_0008 | BW_QRY_MVFIWC01_0004 | |
| WC GBU Solvay Group - Rec. Aged balance (Core Workbook) | The report allows the users to see the total balance of the accounts and the overdue values information by aging until >180 days. | BW_WBK_WCAP_0012 | BW_QRY_MVFIWC01_0012 | |
| WC GBU Solvay Group - Receivables extract (Core Workbook) | It's possible to see detail information for Receivables such as customer number, PRS customer number, name, among other fields that is possible to add to analyze the total balance for customers and the values overdue and due depending on the calendar selection. | BW_WBK_WCAP_0009 | BW_QRY_MVFIWC01_0003 | |
| WC GBU Solvay Group - Synthesis extract (Core Workbook) | Report to check the total balance for Receivables, Payables and Inventories data for one specific period and also to check the amounts for Overdue and Due information by Company in the 1º sheet and by WC Sub Type in the 2º sheet. | BW_WBK_WCAP_0006 | BW_QRY_MVFIWC01_0002 | |
| WC GBU Solvay Group (Core Workbook) | This Workbook combine the several reports in the same place divided by the different sheets:
| BW_WBK_WCAP_0002 | BW_QRY_MVFIWC01_0002 | |
| WC Solvay Group - Payables in Doc/Loc/EUR curr. (Core Workbook) | Shows the list of all vendors and the total balance in Document currency, Local currency and EUR currency. | BW_WBK_WCAP_0005 | BW_QRY_MVFIWC01_0011 |
2- For Accounting/Legal BFC View
| Reports | Definition | BW Workbook Query | Query Technical Name |
|---|---|---|---|
| NEW WC CICC BFC Interface (Core Workbook) | some cases, BFC is manually populated by users thanks to dedicated workbooks in which WC data can be checked and formatted in a way compliant with BFC. In this Workbook we can see the values with the BFC layout for WC for CICC companies in the 1º, 2º ad 3º sheets based in the existent sheets with the Headings from BFC. The user populate the data in these sheets and this will be uploaded in BFC side. | BW_WBK_WCAP_0013 | BW_QRY_MVFIWC01_0009 |
| WC Accounting Solvay Group (Core Workbook) | Balance information for receivables, payables and inventories where we can analyze the values by accounting view or legal view. Intercompany and Lease/FAS amounts are possible to check and the measures can be checked for last year period, the period selected and the previous period from the selection. | BW_WBK_WCAP_0003 | BW_QRY_MVFIWC01_0010 |
| WC Detailed FAS transfer (Core Workbook) | Information about the amounts related with Fixed Asset Supplier (CAPEX) | BW_WBK_WCAP_0017 | BW_QRY_MVFIWC03_0002 |
| WC RCS BFC interface (Core Workbook) | BW_WBK_WCAP_0001 | BW_QRY_MVFIWC01_0009 | |
| WC Solvay Group Annual Overdues interface (Core Workbook) | BW_WBK_WCAP_0004 |
Notes:
1- The folder WCAP - Working Capital in Accounting (not conso.) view - This is a report for companies which already left Solvay Group but they are working with the system PF1 or WP1 (agreement with Solvay for this).
2- Due to volume of data and for performance purposes, lowest level of detail in postings (including FI Doc. number) is not available in workbooks. Nevertheless, this lowest level of detail can be reached from each of them by selecting jump standard function (Based on BW_QRY_MVFIWC03_0001):
4.0 Functional Specification
4.1 General Data/Calculations
This section will approach the concepts/definitions that will be used in all the reports and required to understand the data from the reports.
Could be specific fields, closing activities, additional information to work and understand the reports.
4.2 Process Detail
4.2.1. Report/Process Definition
| Domain | <insert name> |
|---|---|
| Application | >insert name> |
| Provider | <insert name> |
| Existing Documentation | <insert link> |
This section represents the process with detail information for the application. Can include specific or special cases, complex logics , calculations, flows, among others.
4.2.2. KPI's/Calculations/Indicators
Indicators available:
- XXXX
- XXXX
Indicatores/KPI's | Definition | Calculation/Extraction of data |
|---|---|---|
Can be a field, a program, something that was created or the report | What are we looking for ? Why has this KPI been created/developed? What is the goal of monitoring this data ? | How is the calculation, or if it's a program what are the steps or how the data is extracted if it's by files |
5.0 Non-functional Descriptions
Please populate the relevant section and delete those that are not applicable.
5.1 Usability
Usability is about the ease with which a User can learn to start using the solution and the ease with which they can use the system. In addition to ease of learning and ease of use, usability also includes areas such as ease of recall, error avoidance and handling, accessibility among others e.g., 99% of metadata entry Users who have use the Maintenance Dashboard should be able to change filters, extract etc., when required. Maintenance data will be centrally stored in the Google Cloud platform, which will be available to other applications e.g., and Dashboards if needed.
5.2 Regulatory Compliance
Software systems must comply with legal and regulatory e.g., GDPR requirements, this can change depending on country, organisation industry and / or region. The software systems must be secure from unauthorized access. The Maintenance Dashboard will comply with Solvay’s regulations and compliance e.g., access only granted to authorized Users.
5.3 Security
Security refers to essential aspects that assure a solution and its components will be protected against unauthorized access or malware attacks. Important considerations related to security aspects of a system are User authentication, User authorization or User access privileges, data theft, malware attacks, data encryption, and maintaining audit trails, e.g., only Users with administrator access shall be able to create new accounts and assign data access privileges to the new accounts e.g.,
- All data will be encrypted in the dashboard
- Only authorised Users / Administrative Users will be able to access data.
- Maintenance data will be split between either SCO or ECO, and Users will only have authority to one Entity data.
5.4 Performance
Performance defines how fast a software system or a particular section of it responds to certain User actions under a certain workload. In most cases, this metric explains how long a User must wait before the target operation happens e.g., the page renders, a transaction is processed, etc., given the overall number of Users now. Performance requirements may describe background processes invisible to Users, e.g., backup and speed of data transfers.
5.5 Reliability
Reliability is the ability of a solution or its component to perform its required functions without failure under predefined conditions for a specified time / period. Reliability can possibly be specified in terms of average time system runs before failure occurs, percentage of operations completed successfully within a time / period, maximum acceptable failure probability, or number of failures within a period. Reliability aspects are in reference to (but not limited to) evaluation of the system to be considered as reliable, classification of reliability defining failures vs. regular failures, and the impact of failure on business operations. The Maintenance Dashboard will display data from the previous refresh of data.
5.6 Scalability
Scalability refers to the degree to which a solution can evolve to handle increased amounts of work. The increased amount of work could be in terms of the user base, transactions, data, network traffic, or other factors e.g., the system should be able to handle an additional load of a maximum of 5,000 Users every month for the next 6 months without any noticeable performance impacts.
5.7 Compatibility
Interoperability is the degree to which the solution is compatible with other components. It is a measure of how effectively the system interoperates with other software systems and how easily it integrates with external hardware devices.
Interoperability aspects to be discussed during elicitation are in reference to (but not limited to) software systems to be interfaced with along with data / messages to be exchanged and any standard data formats, hardware components to be integrated with, and any standard communication protocols to be followed e.g., Order Management system will push the order file into a secured file transfer protocol server from where it will be loaded into the system through a daily job. To guarantee between Google Cloud platform and SAP BW Queries e.g., BW_QRY_MVPMOR01_0002, Solvay has introduced a new tool called Xtract (Xtract).
5.8 Availability
Availability is the degree to which the solution is operable and accessible when required. It is a measure of time during which the system is fully operational e.g., available for use and sometimes included as a Service Level Agreement (SLA) considering its criticality to the business, e.g., the system shall be at least 99% available on weekdays between 09:00 to 18:30 Central European Time (CET).
5.9 Refresh of the Data
Frequency, data, and time of the data refresh in the data product.