| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
The Working Capital BW Reports are part of (WC) application falls under the Finance domain and utilize leverages data sourced from SAP systems associated with , including Receivables, Payables, and Inventories, originating from the SAP Financial (SAP FI) module along with , as well as its submodules AP (Accounts Payables), AR (Accounts Receivables), and GL (General Ledger). It’s a FI oriented solution, mainly based on SAP accounting documents widely enhanced in SAP BW (ex. CO cost object assignment of Vendor postings).It mainly aims at providing GBUs with detailed The aim of this application is to provide detailed information for Payables, Receivables and Inventory data for Industrial WC analysis and piloting, including reconciliation with our official reporting tool Business Financial and Consolidation (BFC). This solution has been in WBP since 2015. |
| Infopanel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Target Users: Finance and Controlling teams also Purchasing and Supply chain colleagues (more than 600 users). | ||||||
| ||||||
For this Application the access is provided based on the BW menu "WCAP - Working Capital Solvay Group" 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 " WCAP - Working Capital Solvay Group" |
| Info | ||
|---|---|---|
| ||
Target Users: Finance and Controlling teams also Purchasing and Supply chain colleagues (more than 600 users). |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
2.0 Business Process
The working| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Working capital is a financial |
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
metric that represents the difference between a company's current assets and its current liabilities. It reflects the company's ability to meet its short-term financial obligations and operational needs. Working capital is a critical measure for assessing a company's financial health and its ability to manage day-to-day operations. Here's how working capital is calculated: Working Capital = Current Assets - Current Liabilities Current Assets: These are assets that are expected to be converted into cash or used up within one year or one operating cycle (whichever is longer). Common examples include cash, accounts receivable (money owed by customers), inventory, and short-term investments. Current Liabilities: These are the company's short-term financial obligations that are expected to be settled within one year or one operating cycle. Examples include accounts payable (money owed to suppliers), short-term loans, and accrued expenses. Accounts Receivables: These are amounts owed to a company by its customers for goods or services that have been delivered or provided but have not yet been paid for. Accounts receivable are typically short-term assets, and companies often have payment terms (e.g., net 30 days) specifying when the customer is expected to settle the outstanding amount. Managing receivables is an important aspect of a company's financial management because it affects cash flow and liquidity. Companies need to strike a balance between offering customers credit terms to encourage sales and ensuring timely collection to maintain healthy cash flow. To effectively manage receivables, businesses often employ credit policies and procedures, credit checks on customers, send invoices promptly, and may even use collection agencies or offer discounts for early payments. Receivables turnover ratios and aging reports are tools commonly used to assess the efficiency of receivables management and to identify potential issues with overdue accounts. To see more detail about the business process in Solvay for Account Receivables please consult the following wiki page Customer Credit & Trade Service Line Knowledge Base. A ccounts Payables: R efers to the amounts of money that a business owes to its suppliers or creditors for goods or services it has received but has not yet paid for. Accounts payables represent a company's short-term liabilities, as these amounts are typically expected to be settled within a relatively short period, often within 30 to 90 days. Managing accounts payables effectively involves ensuring timely payments to suppliers while optimizing cash flow and taking advantage of any early payment discounts that may be available. It's an important aspect of a company's financial management and impacts its relationships with suppliers and creditors. To see more detail about the business process in Solvay for Account Receivables please consult the following wiki page Purchasing Service Line. Inventory: Refers to the goods and materials that a business holds in stock and plans to sell to customers. Inventory is considered a current asset on a company's balance sheet because it is expected to be converted into cash or sold within a relatively short period, typically one year or one operating cycle (whichever is longer). In Inventory data we can check the values for raw materials, WIP products, finish goods, among other fields which allows the users to perform analysis which allow them to have a efficient inventory management since this is essential for optimizing working capital and ensuring that a company has sufficient liquidity to meet its short-term obligations while supporting its sales and production operations. The specific approach to managing inventory will depend on the industry, market demand, and company strategy. |
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) | In this report the users can compare the data from BW with the BFC data from FC pack and BFC Conso regarding Receivables, Payables and Inventories data for one specific period to be able to check and analyze the values and diferences if exists. | Mandatory:
Optional:
| 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. | Mandatory:
Optional:
| 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. | Mandatory:
Optional:
| 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. | Mandatory:
Optional:
| 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 to analyze the total balance for customers and the values overdue and due depending on the calendar selection. | Mandatory:
Optional:
| BW_WBK_WCAP_0009 | BW_QRY_MVFIWC01_0003 |
| WC GBU Solvay Group - Synthesis extract (Core Workbook) | In this report the users can 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. | Mandatory:
Optional:
| 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:
| Mandatory:
Optional:
| BW_WBK_WCAP_0002 | BW_QRY_MVFIWC01_0002 BW_QRY_MVFIWC01_0005 BW_QRY_MVFIWC01_0004 BW_QRY_MVFIWC01_0003 BW_QRY_MVFIWC01_0006 |
| 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. | Mandatory:
Optional:
| BW_WBK_WCAP_0005 | BW_QRY_MVFIWC01_0011 |
2- For Accounting/Legal BFC View
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| NEW WC CICC BFC Interface (Core Workbook) | In 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 and perform already some checks 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. | Mandatory:
Optional:
| 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. | Mandatory:
Optional:
| BW_WBK_WCAP_0003 | BW_QRY_MVFIWC01_0010 BW_QRY_MVFIWC01_0006 |
| WC Detailed FAS transfer (Core Workbook) | Information about the amounts related with Fixed Asset Supplier (CAPEX) in local and EUR currency. | Mandatory:
Optional:
| BW_WBK_WCAP_0017 | BW_QRY_MVFIWC03_0002 |
| WC RCS BFC interface (Core Workbook) | same logic as the workbook for NEW WC CICC BFC Interface the BFC will be manually populated by the users and in here the users can check the following reports:
The rest of the sheets are the values from BFC to be checked and compare the data in the other reports (only applicable for WP1):
| Mandatory:
Optional:
| BW_WBK_WCAP_0001 | BW_QRY_MVFIWC01_0009 |
| WC Solvay Group Annual Overdues interface (Core Workbook) | same logic as the workbook for NEW WC CICC BFC Interface the BFC will be manually populated by the users and in here we have the Receivables aging balances (Legal BFC view) by Company/Activtiy (X04051 key fig.) 1º sheet we have the overdue information to check what will be updated in BFC; 2º sheet it's information regarding the accounts in the scope; 3º sheet the users will populate this with the relevant data to be uploaded in BFC. | Mandatory:
Optional:
| BW_WBK_WCAP_0004 | BW_QRY_MVFIWC01_0009 |
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
For these reports, it’s important to understand some concepts which will allow the user to work with the reports in the same way as the SAP system and BFC tool.| Working Capital Accounts | Components for Payables, Receivables, and Inventory Working Capital (WC) are established based on a BFC Account list, which is maintained in each ERP system within the Table ZZF_BFC_SETACCT - set of accounts by heading, categorized by Family WC. For each Heading (BFC Account), there’s at least 1 corresponding Sets of accounts in which are listed at least 1 GL account (Cf. tr. GS03 - Display Set). Those data are uploaded in BW to update GL Account attributes used in reporting.
| ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Consolidation View | The query takes the integration rate of the company and the partner from the master data of 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. This GBU assignment is different for WP1 and PF1 and it will be explain in detail in the Process Definition section. | ||||||||||||
| Currency Conversion | Key figures are always available in Local (Company) currency, and in some queries in Document currency. | ||||||||||||
| UoM Conversion | In Inventory analysis, UoM can be converted according to alternative UoM managed in Material master data (ex.: L → Kg). | ||||||||||||
| 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. | ||||||||||||
| Customers and Vendors | All Solvay Group Customers/Vendors (internal and external) are also managed both in PRS (PF1_050) and in local ERPs.
Example: Go to FK03 transaction and when the master data is displayed click on "Additional data" and in the 2º tab we can see the PRS vendor code:
Note: For reporting convenience, in BW most of PRS attributes are replicated as Customer/Vendor attributes (incl. PRS Vendor Interco flag). | ||||||||||||
| Trading Partner | Information stored in FI document:
| ||||||||||||
| Balance Calculations | WC figures are mostly open items (balances) calculated in reporting the following way: Open items at Calendar day = entries with: Posting date =< Calendar date and (Clearing date > Calendar date and Clearing date = #) | ||||||||||||
| 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). |
4.2 Process Detail
4.2.1. Report/Process Definition
| Domain | Finance |
|---|---|
| Application | BW reports under WCAP - Working Capital Solvay Group |
| Provider | MVFIWC01 |
| Info | ||
|---|---|---|
| ||
The Working Capital Application has several reports where the users can check the data for Receivables, Payables and Inventories and see the balances to analyze the information with additional assignments in BW and have a better output for the daily/monthly analysis. In this section we will approach:
|
Source of data Anchor Source of data Source of data
| Source of data | |
| Source of data |
Working Capital data is updated from ERPs FI entries, but also from BFC for reconciliation purposes. See below for each source how are the characteristics:
| ERPs | BFC | |
|---|---|---|
| Payables | FI postings on Vendor Payables accounts (K) → BSIK/BSAK FI postings on GL Payables accounts (S) → BKPF/BSEG FI postings on Customer Payables accounts (D)* → BSID/BSAD | Flat Files |
| Receivables | FI postings on Customer Receivables accounts (D) → BSID/BSAD FI postings on GL Receivables accounts (S) → BKPF/BSEG | |
Inventory (WP1/PF1/RHO only) | FI postings on Material Inventory accounts (M) → BKPF/BSEG FI postings on GL Inventory accounts (S) → BKPF/BSEG MM document** → MKPF/MSEG |
- BFC data are updated 1 time a day between D4 and D20; 1 file for closing period (Magnitude-BW-SCA_Month.txt), 1 file for previous one (Magnitude-BW-SCA_Month-1.txt);
- SAP data are updated 3 times a day (6 AM, 12 PM and 6PM French time) + for WP1 4 additional time a day (10 AM, 2PM, 4 PM, 10 PM) during closing period (D-1 to D4).
Reporting Views:
Depending on workbook definition WC data are displayed according 3 different views:
- In Legal BFC/Conso. view, external companies are excluded from display
- In Conso. view, SAP balances of entities which are proportionally integrated (PRS Comp. Conso. Method = 30) are revaluated according corresponding integration rate
- In Legal BFC/Conso. view, entries with internal partner are eliminated from balance calculation
NB: some (Company + Customer/Vendor) combinations, that do not respect those standard elimination rules, are specifically managed as restricted key figures in query definition.
| ERPs | BFC | |
|---|---|---|
| Payables | FI postings on Vendor Payables accounts (K) FI postings on GL Payables accounts (S) FI postings on Customer Payables accounts (D) | PRS Vendor Interco flag = X (master data) PRS TP Interco flag = X (document entry) PRS Customer Interco flag = X (master data) |
| Receivables | FI postings on Customer Receivables accounts (D) FI postings on GL Receivables accounts (S) | PRS Customer Interco flag = X (master data) PRS TP Interco flag = X (document entry) |
| Inventory | FI postings on Material Inventory accounts (M) FI postings on GL Inventory accounts (S) MM document | N/A |
SAP BW High level view Anchor SAP BW High Level view SAP BW High Level view
| SAP BW High Level view | |
| SAP BW High Level view |
To see the data from the source systems see below how the information is organized in the BW perspective:
The cubes where we have the reference “factoring” are specific for data involved in the factoring process according to CAMS which will be explained further in this section.
GBU Assignment Anchor GBU Assignment GBU Assignment
| GBU Assignment | |
| GBU Assignment |
GBU assignment is based on Sub activity 1/2 (1)
- (1) In PF1/PI1 area, original BA can be forced to target value according to exception entries managed in ZZR_REPO_DIV_EXC
- (2) WP1 Receivables assignment
- SD related entries: IECRA issued from COPA derivation rule, based on Distribution Channel + Material Division in counterpart item → IECRA (ex.: 82 + RI → IECRA00006)
- Other entries: IECRA issued from COPA derivation rule, based on Profit Center in counterpart item IECRA (ex.: ZFR3-I0006 → IECRA00006)
NB: in case of several and various counterparts, there’s no split of Customer entry, but an assignment according to the counterpart with the biggest amount
- (3) Profit center is issued from Material master data at Plant level (Cf. MARC)
- (4) BA is issued from T134G according to Material Division (Cf. MARA) and posted Plant
- (5) WP1 Payables assignment
- Vendor entries (K):
- Profit center assignment is performed after split of vendor entries according to CO assignment of counterpart entries (in FI or in related PO item); it can be the Profit center of:
- Assigned Material
- Assigned Cost center,
- Requesting/Responsible Cost center of assigned WBSE…
- Vendor entries (K): CO assignment and split are performed in WP1 when AP data are uploaded in BW thanks to ZWFAT123 update
- General entries (S): same CO assignment w/o split of entries
- (6) In WP1 area, any not assigned entries by IECRA/Profit Center can be forced at FI document item level to target value entered in ZWFAT205
GBU determination from Sub activity 1
GBU determination from Sub activity 2
NB: ZWFAT186 is a « flat » picture of Profit center standard hierarchy.
PF1 ZZF_BFC_DIV_CONV
Receivables Scope Anchor Receivables Scope Receivables Scope
| Receivables Scope | |
| Receivables Scope |
Specific business rules:
- A41100, A49100 and L41160 BFC Accounts related entries;
- Receivables formula calculation including:
- Entries forced as internal
- Acetow (6450) external Customer WVK displayed at 49,9%
- Butachimie external (0560) Customer Invista managed as internal
- Solvay Sodi external (3438) Customers SODASANA and SISECAM managed as internal
- Carryforward Document types S7, S8 and ZU in Italian companies excluded from display
Dedicated workbooks → Queries (1)
- BW_WBK_WCAP_0002 BW - NEW WC Solvay Group GBU (Core Workbook) + BW_WBK_WCAP_0009 BW - NEW WC GBU Solvay Group - BFC vs BW extract (Core Workbook) → BW_QRY_MVFIWC01_0003
- Due/Overdue classification
- L41160 and A49100 related entries are excluded from categorization
- Customer entries are classified as Due/Overdue according to Calculated Net due Date which is not different from Original Net due Date issued from SAP (BSID/BSAD)
- Cash in/out = Customer cleared entries (excluding payment documents). NB: Clearing date is considered as Payment date
- Due/Overdue classification
Dedicated workbooks → Queries (2)
- BW_WBK_WCAP_0012 BW - NEW WC GBU Solvay Group - Rec. Aged balance (Core Workbook) → BW_QRY_MVFIWC01_0012
- Outstanding: whole Receivables balance
- Overdues: Net due date =< Key date
Payables Scope Anchor Payables Scope Payables Scope
| Payables Scope | |
| Payables Scope |
Specific business rules:
- L40100 and A40160 BFC Accounts related entries;
- WP1 Payables entries are net of Investment and Lease open items as reposted during month-end closing process:
- Fixed Asset Suppliers: Vendor and GL entries assigned in BW to an invest. WBSE, or to a PM order assigned in its settlement rules to an invest. WBSE
- Lease Suppliers: Vendor entries assigned in BW to a Lease contract (relevant for IFRS16 valuation)
NB: both are valuated Net of tax
- Payables formula calculation detailed including:
- Entries forced as internal
- Acetow (6450) external Vendor WVK displayed at 49,9%
- Butachimie (0560) external Vendor Invista managed as internal
- Carryforward Document types S7, S8 and ZU in Italian companies excluded from display
Dedicated workbooks → Queries
- BW_WBK_WCAP_0002 BW - NEW WC Solvay Group GBU (Core Workbook) + BW_WBK_WCAP_0008 BW - NEW WC GBU Solvay Group - Payables extract (Core Workbook) → BW_QRY_MVFIWC01_0004
- Due/Overdue classification (1)
- A40160 related entries are excluded from categorization
- Vendor entries are classified as Overdue according to Original. Net due Date directly issued from SAP (BSIK/BSAK)
- Due/Overdue classification (2)
- They are classified as Due according to Net due Date, which is a calculated due date issued from table ZZF_BSEG → For all FI doc. item not maintained in ZZF_BSEG, Net due date = Original. Net due Date, else Net due date <> Original. Net due Date (Cf. entries with Calc.<>Orig. Net due date (Pay.) = X)
NB: for Customer entries which are part of PF1/PI1 Payables balances, there’s no difference between Net due Date and Original. Net due Date
- BW_WBK_WCAP_0005 BW - NEW WC Solvay Group - Payables in Doc/Loc/EUR curr. (Core Workbook) → BW_QRY_MVFIWC01_0011
Factoring Process (CAMS rules) Anchor Factoring Process (CAMS rules) Factoring Process (CAMS rules)
| Factoring Process (CAMS rules) | |
| Factoring Process (CAMS rules) |
In working capital we have the factoring concept, where due to specific conditions we have some cases where the postings are transferred to the CICC company and the data in the SAP systems (PF1/WP1) will be cleared.
- when the invoices are transferred to CICC according to CAMS process are considered to be paid when they are cleared in CICC (PI1 Legal company 0231/4044), and not when they are cleared in the original company (ex. WP1 Affiliate ZFR3) at the time of the transfer.
- FI documents in Affiliate (origin) WP1/PF1 companies and in Legal PI1 companies are linked by a unique factoring contract number managed in table ZZF_BSEG.
For specific business rules:
- In Consolidated reports, data are displayed in an Affiliate point of view:
- For ex. if 4274 company is selected, not only open items in 4274 are displayed, but also cleared items linked to PI1 open items
- In other reports (Legal BFC and Accounting views), they are displayed in Legal company point of view:
- For ex. if 4274 company is selected, only open items in 4274 are displayed
- NB: to get the same whole affiliate point of view as described in previous point, it needs to select 4274 + 0231/4044 Legal companies, and then to filter on 4274 affiliate.
Inventories Scope Anchor Inventories Scope Inventories Scope
| Inventories Scope | |
| Inventories Scope |
Specific business rules (1)
- A31000, A34000, A37000, A39100, A39400 and A39700 BFC Accounts related entries;
- Historical data upload
- Due to volumes of data and for performance purposes, it has been decided to update MM related Inventory data (linked to a Material document) from FI (Cf. M entries) only up to 01/01/2014
- A snapshot has been done on 31/12/2013, based on
- WP1/RHO: MBEW/MBEWH entries
- PF1: PQ1 entries (as stored in ZZMIC_01)
- Technical Material Plant object
- Some characteristics are not the ones entered in SAP transactional data, but are re defined at current date in order to insure consistency between BW data and Stock reports in SAP (Cf. tr. MB5B and MB5L)
- They are managed in a BW compounded technical Material Plant object, including:
- Valuation class: current Class defined in MBEW/MBEWH at Material/Plant/Valuation type level; ex.: Material 14477 / Plant (Val. Area) 0087 → Valuation class Z150
- GL account (and related BFC Account): current account defined in T030 for Transaction BSX and Valuation class; ex.: Valuation class Z150 → 37000100 (A37000)
- Material Division: current Division defined at Material level in MARA
- Material Profit center (and related GBU): current Profit center as defined at Material/Plant level in MARC; ex.: 14477 / 0087 → Profit center 8090-I0534
- Material BA (and related GBU): current BA as defined in T134G at Plant/Division (Cf. MARC) leve
NB: for S entries, GL Account and Profit center/BA are issued from postings
- Inventory formula calculation detailed including:
- PF1 manual entries on MM automatic accounts (Cf. Stock account (BSX) excluded from display, in order to not count twice historical entries uploaded from PQ1 and corresponding S postings uploaded from PF1
- Carryforward Document types S7, S8 and ZU in Italian companies are excluded from display.
Dedicated workbooks → Queries
- BW_WBK_WCAP_0002 BW - NEW WC Solvay Group GBU (Core Workbook) + BW_WBK_WCAP_0007 BW - NEW WC GBU Solvay Group - Inventory extract (Core Workbook) → BW_QRY_MVFIWC01_0005
BFC Scope Anchor BFC Scope BFC Scope
| BFC Scope | |
| BFC Scope |
BFC data are uploaded in BW:
- To perform SAP data quality check when compared to FC pack entries in BFC;
- To get overall conso. figures by enhancing SAP postings with:
- Conso. adjustment postings (manual and automatic) entered directly in BFC w/o correspondence in SAP;
- WC data of conso. companies that are managed out of SAP.
Specific business rules
- Selected Calendar day needs to be last of the month (ex. 30/04/2016)
In 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:
Dedicated workbooks → Queries (1)
- BW_WBK_WCAP_0002 BW - NEW WC Solvay Group GBU (Core Workbook) + BW_WBK_WCAP_0010 BW - NEW WC GBU Solvay Group - BFC vs BW extract (Core Workbook) → BW_QRY_MVFIWC01_0006
- FC Pack field: data issued from SAP (BFC Nature 0LIA01)
- FC Tot Adjust
- FC Manual Adj (1): BFC entries with BFC Nature 1LIA05, 1RET-EX, 1RET50, 1RET90, 1RET91, 1RET95 and 1SOL11 (« spot » manual entries that are normally re integrated in Package in M+1)
- FC Auto Adj (2): BFC entries with BFC Nature 2NRI40, 2NRI50 (in WP1 area, elimination of margin in Inventories)
- FC Top Adj (3): BFC entries with BFC Nature 3TOP10, 3TOP20, 3TOPHISTO, 3TOPSOL and 3TOPGEST (corrections linked to IP % consolidation rate)
- FC Conso = FC Pack + FC Tot Adjust
Intercompany Scope Anchor Intercompany Scope Intercompany Scope
| Intercompany Scope | |
| Intercompany Scope |
Intercompany aged balance
- Comparison in a single workbook of both Receivables and Payables internal postings (Customer and Vendor entries only)
- Dedicated workbooks → Queries
- BW_WBK_INTERCO_0001 Intercompany Aged Balance → BW_QRY_MVFIWC01_0020/0021
- Delay (d) = (selected) calendar day) Net due date
- Possibility to filter AP entries for an entered partner (as a PRS Company code):
List of service invoices
- Counting and valuation by period of Customer documents identifying service invoices in WP1/PF1 area
Dedicated workbooks → Queries
- BW_WBK_INT_0002 BW - List of service invoices (Core Workbook) BW_QRY_MVFIWC03_0010
- WP1: FI Doc. Type RV and Billing type ZLS2, ZG2S, ZS4, ZS5, ZL2B and Z2G + FI Doc. Type DG, DR and RC
- PF1: FI Doc. Type C0, CA, CC, CS and RC
5.0 Non-functional Descriptions
5.1 Usability
as per standards
5.2 Regulatory Compliance
as per standards
5.3 Security
as per standards
5.4 Performance
as per standards
5.5 Reliability
as per standards
5.6 Scalability
as per standards
5.7 Compatibility
as per standards
5.8 Availability
as per standards
5.9 Refresh of the Data
The Working Capital data is updated from ERPs Financial entries, but also from BFC for reconciliation purposes. As such, the following load times exist:
- BFC data is updated 1 time a day between D4 and D20;
- 1 file for closing period (Magnitude-BW-SCA_Month.txt);
- 1 file for the previous one (Magnitude-BW-SCA_Month-1.txt).
- SAP data is updated 3 times a day (6 AM, 12 PM and 6PM French time) + for WP1 4 additional time a day (10 AM, 2PM, 4 PM, 10 PM) during closing period (D-1 to D4)
The load normally takes approximately 90 minutes and when the data is refreshed it uploads only the delta information.
This Workbook combine the several reports in the same place divided by the different sheets:
- Synthesis by Company (same info as WC GBU Solvay Group - Synthesis extract (Core Workbook);
- Synthesis by WC Sub Type (same info as WC GBU Solvay Group - Synthesis extract (Core Workbook);
- Inventory (same info as WC GBU Solvay Group - Inventory extract (Core Workbook);
- Receivables (same info as WC GBU Solvay Group - Receivables extract (Core Workbook);
- Payables (same info as WC GBU Solvay Group - Payables extract (Core Workbook);
- BW vs BFC WC GBU Solvay Group - BFC vs BW extract (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.
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
<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.