| borderColor | #ededed |
|---|---|
| titleColor | #ffffff |
| titleBGColor | #009EE0 |
| title | Business Context and Application Overview |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Describe the key User profiles that exist for the application. General role/Viewer role: Approver role: |
| Info | ||
|---|---|---|
| ||
Target Users: As examples: Controllers / Accountants |
| |
The ITC application regroups all the reports that will permit to the credit managers to follow there customer portfolio. The different reports will present data about :
There are two main parts : the ITC reports with the global view of the customer situation, and the FSCM (Financial Supply Chain Management) reports to assure the follow up of the customers (dispute and promise to pay). |
VERSION
DATE
MODIFIED BY
DESCRIPTION
0.01
dd.mm.yyyy
<Insert name>
Initial draft
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Data Product Type |
| |||||||
| Technologies |
| |||||||
Data Sources Note: list of all applications and various environment |
|
| ||||||
For this Application the access is provided based on the BW menu "ITC - Credit Management" 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 "ITC - Credit Management". |
| Info | ||
|---|---|---|
| ||
Target Users: Credit Management Community (Risk and Collection), Controllers, Collection Team, Short Payment Team (Only one query => Dispute Follow up for Short Payment) and Sales Team |
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 17.10.2023 | Inês Vilares | Initial draft |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
2.0 Business Process
Credit management in SAP involves the processes and tools used to assess and control credit risk associated with customers and business partners. It is a crucial component of the SAP Financial Accounting (FI) and Sales and Distribution (SD) modules, which allows organizations to evaluate the creditworthiness of their customers, set credit limits, monitor outstanding receivables, and ensure the timely collection of payments. Here are some key aspects of credit management in SAP:
- Credit Check: SAP enables businesses to perform real-time credit checks on customers during the order-to-cash process. This ensures that orders are not processed for customers who have exceeded their credit limits or have overdue payments.
- Credit Scoring: Credit scoring models can be configured within SAP to assign risk scores to customers based on their payment history and other relevant factors. These scores help in making informed credit decisions.
- Credit Limits: Organizations can define and manage credit limits for each customer, limiting the amount of credit they can extend. SAP can automatically block or release orders based on these credit limits.
- Dunning Procedures: SAP allows the automation of dunning processes, which involve sending reminders and notifications to customers with overdue payments. The severity and frequency of dunning letters can be configured.
- Dispute Management: SAP provides tools to manage and resolve payment disputes and discrepancies with customers. It helps streamline the dispute resolution process.
- Credit Reporting: Credit management in SAP offers reporting and analytics to track the creditworthiness of customers and the overall credit risk of the organization. These reports assist in making data-driven credit decisions.
- Collections Management: SAP Collections Management is part of the broader credit management process, helping organizations prioritize and manage collections activities efficiently.
Efficient credit management in SAP is vital for maintaining a healthy cash flow, reducing bad debt, and ensuring a stable financial position. It allows organizations to balance the need for sales and growth with the necessity of minimizing credit risk.
In the context of SAP, "FSCM" stands for "Financial Supply Chain Management." It is a set of applications and tools within SAP designed to help organizations manage various financial aspects of their supply chain and improve their overall financial processes. FSCM encompasses various modules and functionalities that address different aspects of financial supply chain management, including credit management, collections management, dispute management, and cash and liquidity management.
Key components of SAP FSCM include:
- SAP Credit Management: Helps organizations assess and manage the creditworthiness of their customers, set credit limits, and reduce credit risk.
- SAP Collections Management: Supports efficient collections processes by providing tools for prioritizing and tracking customer collections, as well as automating dunning and follow-up procedures.
- SAP Dispute Management: Enables organizations to handle and resolve disputes with customers or vendors, improving dispute visibility and resolution.
- SAP Biller Direct: Offers a self-service portal for customers to view and pay their invoices online, enhancing the billing and payment process.
- SAP Treasury and Risk Management: Provides tools for managing cash and liquidity, mitigating financial risks, and optimizing cash flows.
SAP FSCM is designed to streamline financial processes, reduce credit risk, enhance cash flow, and improve customer relationships, ultimately contributing to better financial supply chain management.
The Solvay credit management area defined is SOLV.
For Solvay exist a lot of processes and teams involve in the credit management and FSCM scope. In the following link we have more informatin about these areas https://wiki.solvay.com/display/public/SBSOTC/CCT+Domains+-+Operating+Procedures.
3.0 Application Feature Overview
For this application find below all the workbooks available:
Folder: ITC Credit Management
1.Credit Mgt Reporting
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| Credit Mgt - Aged Balanced (Core Workbook) | This report reflects the total balance per customer and the total of overdues for the calendar day selected. It's also possible to see the amounts for the different ranges in overdue: Overdue 0-4 days; Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0016 | BW_QRY_MVFIAR01_0006 |
| Credit Mgt - Anticipated payments (Core Workbook) | This report has the total amount in local and EUR currency for the customers (legal) by company code and the result between the Due Date minus the Clearing Date. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0012 | BW_QRY_MVFIAR02_0005 |
| Credit Mgt - Blocked Orders | This report has 3 sheets:
| Mandatory:
Optional:
| BW_WBK_ITC_0001 | BW_QRY_MVFIAR03_0001 BW_QRY_MVFIAR03_0002 |
| Credit Mgt - Credit Exposure & Payment Perf. (Core Workbook) | Check with the BAO - Ellon will check this Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0004 | BW_QRY_MVFIAR01_0009 BW_QRY_MVFIAR01_0006 BW_QRY_MVFIAR01_0008 BW_QRY_IFRFIAR01_0001 |
| Credit Mgt - Credit exposure (core Workbook) | This report shows the total values per customer and GBU for the outstanding balance and other KPI's for the credit management scope like exposure, global credit limit, credit line %, etc). Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0018 | BW_QRY_MVFIAR01_0008 |
| Credit Mgt - Credit Management Workbook (Core Workbook) | It provides an overall view on Credit Performance. It covers main Credit KPIs to report global performance for Solvay Group, a GBU or a specific GBU perimeter (eg. Geographical or Entity), a Region. Several sheets are in place for the diffeent analysis as Global Trends, Top 20 for overdues or ratings, Aged balance and DSO analysis by zone, company code and activity, doubtful detailed. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0008 | BW_QRY_MVFIAR01_0006 BW_QRY_MVFIAR01_0002 BW_QRY_MVFIAR01_0001 BW_QRY_MVFIAR01_0003 BW_QRY_MVFIAR01_0007 |
| Credit Mgt - Customer Payment Terms (Core Workbook) | This report provides information by customer and the payment terms to analyze some data related with the payment terms (gap in days, number of payment days, number of customer and % with high duration). Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0006 | BW_QRY_MVFIAR01_0011 |
| Credit Mgt - Customer Portfolio Scan (Core Workbook) | This report it's by customer and the users can check the values for the outstanding for the selected period and the possibility to select previous for comparison, overdue total amount and % and the advance payments amounts. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0002 | BW_QRY_MVFIAR01_0002 |
| Credit Mgt - Customer review date & activation | This report shows different sheets with the review dates and exceeded for 1-30 days and > 30 day. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0005 | BW_QRY_C_CST_CA2_0002 BW_QRY_C_CST_CA2_0001 BW_QRY_MVFIAR04_0001 |
| Credit Mgt - Detailed aged balance (Core Workbook) | This report reflects the total balance per customer and the total of overdues for the calendar day selected. It's also possible to see the amounts for the different ranges in overdue and due:
Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0023 | BW_QRY_MVFIAR02_0003 |
| Credit Mgt - Detailed Open/Cleared items (Core Workbook) | This report shows by default a view with the FI document numbers with detail dates and the total amount in the different currencies. In here the user can see in detail all the information for the open and cleared items. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0021 | BW_QRY_MVFIAR02_0001 |
| Credit Mgt - Doubtful cust. (Core Workbook) | This report shows the values per customer for the total outstanding, doubtful and write down value and percentage. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0013 | BW_QRY_MVFIAR01_0003 |
| Credit Mgt - DSO (Core Workbook) | This report shows per customer the amounts for the measures Turnover, Outstanding, Not yet due, DSO and the Best DSO for the calendar day selected and previous months. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0011 | BW_QRY_MVFIAR01_0001 |
| Credit Mgt - Global Credit Exposure (Core Workbook) | In here we have two sheets with the following information:
Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0003 | BW_QRY_MVFIAR01_0008 BW_QRY_MVFIAR05_0001 |
| Credit Mgt - Internal control (Core Workbook) | For this reports we have 3 sheets for analysis based in the customer credit management information and we can see:
Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0010 | BW_QRY_MVFIAR01_0012 BW_QRY_MVFIAR01_0014 BW_QRY_MVFIAR01_0015 |
| Credit Mgt - Payment perf. (Core workbook) | Ths report it's possible to analyze per customer the amounts for Total Cleared and Payment perf. on last 6 months %. In the Total Cleared values the uses can check in more detail the following measures:
Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0019 | BW_QRY_MVFIAR01_0009 |
| Credit Mgt - Process Expert Workbook) | In here exist several sheets where we can see different analysis to provide an overall view on Credit Performance of Solvay Group and All GBUs. It covers main Credit KPI's o report global performance for Solvay Group, providing detailed figures and performance ranking for GBUs. Sheets:
Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0007 | BW_QRY_MVFIAR01_0006 BW_QRY_MVFIAR01_0002 BW_QRY_MVFIAR01_0001 |
| Credit Mgt - Risk Distribuiton (Core Workbook) | This report shows the amounts for Total Outstanding, Total Overdue, Overdue % and Nb of PRS Custo Credit for the calendar day sleected and previous periods. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0017 | BW_QRY_MVFIAR01_0007 |
| Credit Mgt - Weighted Paymt terms & delays (Core Workbook) | This report is defined in Conso. view as all the other Credit Mgt reports, meaning in WP1/PF1/PI1 area and after Intercos eliminations It includes factoring entries that can be seen both in Legal/Affiliate (origin) Company points of view. 1) Cash in follow up
2) Open items follow up
Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0028 | BW_QRY_MVFIAR02_0007 |
| Credit Mgt - WP1 Credit Exposure (Core Workbook) | This report presents the information for the customer and document level to see measures as the credit limit, the expected shipments and the respective cumulative amount to check the credit exposure for each customer. | Mandatory:
Optional:
| BW_WBK_ITC_0027 | BW_QRY_CPFIAR10_0001 |
| Credit Mgt - WP1 Weighted Aver. Days Paid (Core Workbook) | In this report the user can check the values related with the Agreed Paymt Terms Days, Real Paymt Terms Days, Amount Loc./Target curr., Weighted amount Loc./Target curr. and Days Slow. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_0026 | BW_QRY_MVFIAR02_0006 |
2.FSCM - Cash Collection Reporting (Dispute & Promise to Pay)
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| BW - PCM - by GBU (Core Workbook) | This report is used more focus for the PCM it's not expected for the users to work with this in AfO. Default values:
| Optional:
| BW_WBK_PCM_0001 | BW_QRY_MVFIAR10_0001 |
| BW - WISE - Cash Collection Piloting Report (Core Workbook) | This report it's a master data regarding the dunning block associated to the customer and we can see information as Dunning Level, Dunning Clerk, Last dunned and Coll. Specialist by default but more fields can be added. Default values:
| Optional:
| BW_WBK_FSCM_0001 | BW_QRY_MVWISE03_0001 |
| BW - WISE - Cash Collection Statistics Report (Core Workbook) | In this report the users can check the values related with the disputes. In here we can see the following analysis:
Default values:
| Mandatory:
Optional:
| BW_WBK_FSCM_0005 | BW_QRY_MVWISE04_0002 BW_QRY_MVWISE04_0003 BW_QRY_MVWISE04_0004 BW_QRY_MVWISE04_0005 |
| BW - WISE - Dispute Follow up wth CLM Org. Info (Core wbk) | This report it's a follow up on the disputes. The users can check the Total Amount, the Overdue ranges from 1-4 days until Overdue > 90 days, Amount Credited and Disputed Amount. Default values:
| Mandatory:
Optional:
| BW_WBK_FSCM_0003 | BW_QRY_MVWISE02_0003 |
| BW - WISE - Dunning Level Report (Core workbook) | In here we have a table with the information for the customer number, name, company code and the related data for the dunning block, level, clerk and Coll. Specialist. Default values:
| Optional:
| BW_WBK_FSCM_0004 | BW_QRY_MVWISE03_0001 |
| BW - WISE - Scenario Collection Piloting Report (Core wbk) | In this report we have two sheets to perform the following analysis:
Default values:
| Optional:
| BW_WBK_FSCM_0002 | BW_QRY_MVWISE02_0001 BW_QRY_MVWISE02_0002 |
3.Credit Mgt Without Consolidation Rules
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| Credit Mgt - Aged Balance in acct. view (Core Workbook) | This report reflects the total balance per customer and the total of overdues for the calendar day selected. It's also possible to see the amounts for the different ranges in overdue:
Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_7006 | BW_QRY_MVFIAR01_7006 |
| Credit Mgt - Doubtful cust. in acct. view (Core WorkBook) | In this report we can see the total balance and the doubtfull amounts per customer. It's also possible to add more measures to compare with previous months. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_7003 | BW_QRY_MVFIAR01_7003 |
| Credit Mgt - DSO in acct. view (Core WorkBook) | This report shows the DSO amounts for the month selected and previous months to perform a comparison between them per customer. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_7001 | BW_QRY_MVFIAR01_7001 |
| Credit Mgt - Overdue in acct. view (Core Workbook) | This report has the outstanding values, the total of overdues and the % of overdues for the selected calendar day and the previous months per customer. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_7002 | BW_QRY_MVFIAR01_7002 |
| Credit Mgt - Risk Distribution in acct' view (Core Workbook) | This report shows for each rating the total amounts for the Outstanding, Total Overdues, % of Overdues and how many PRS cusomers are. The values can be analyzed for the month selected or previous months. Default values:
| Mandatory:
Optional:
| BW_WBK_ITC_7007 | BW_QRY_MVFIAR01_7007 |
| Credit Mgt - Workbook without Solvay Conso rules (Core Workbook) | This report has several sheets where we can see different analysis based in different queries. Sheets:
| Mandatory:
Optional:
| BW_WBK_ITC_7008 | BW_QRY_MVFIAR01_7001 BW_QRY_MVFIAR01_7002 BW_QRY_MVFIAR01_7003 BW_QRY_MVFIAR01_7006 BW_QRY_MVFIAR01_7007 BW_QRY_MVFIAR01_7008 |
Folder: ITC Credit Management - Non Solvay
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| Credit Mgt - Workbook without Solvay Conso Rules (Core Workbook) | This report has several sheets where we can see different analysis based in different queries. Sheets:
| Mandatory:
Optional:
| BW_WBK_ITC_7008 | BW_QRY_MVFIAR01_7001 BW_QRY_MVFIAR01_7002 BW_QRY_MVFIAR01_7003 BW_QRY_MVFIAR01_7006 BW_QRY_MVFIAR01_7007 BW_QRY_MVFIAR01_7008 |
Folder: ITC Credit Management AR Payments - To be completed we need to investigate the queries associated to this and if exist dependencies.
For this folder we don't have any workbook but exist some queries for this scope.
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
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/or BFC tool.
| 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 2 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 we have the explanation in detail in the Process Definition section in the Working Capital Functional Documentation. |
| Outstanding | Sum of documents in the customer account (excluded doubtful and advance payment) |
| Overdue | Refers to a situation where a payment or financial obligation has not been met by the agreed-upon due date. It is used to indicate that a payment or a task is past its scheduled or expected payment date. It's essential to monitor and manage outstanding payments or tasks to ensure timely settlement and compliance with financial agreements and deadlines. |
| Not yet due | Refers to a situation where a payment or financial obligation has not reached its scheduled or expected due date. In other words, the payment or task is still within the agreed-upon time frame and has not yet become overdue. |
| Doubtfull | Where there is uncertainty or concern about the likelihood of receiving payment on a debt or account receivable. It suggests that there are doubts about the debtor's ability or willingness to fulfill their financial obligations, such as repaying a loan or settling an invoice. When an account or debt is categorized as "doubtful," it implies that there is a significant level of uncertainty regarding the collectibility of the amount owed, and it may require closer monitoring or specific actions to address the doubts and potential risks associated with the debt. |
| Write down | Financial practice where a company reduces or "writes down" the recorded value of accounts receivable related to specific customers. This reduction in value is usually necessary when a company believes that it is unlikely to collect the full amount owed by a customer. The reasons for such write-downs can include customer insolvency, financial distress, disputes, or other issues that raise doubts about the collectibility of outstanding invoices. By performing a customer write-down, a company acknowledges the reduced value of the accounts receivable related to that customer on its financial statements. This adjustment helps the company to more accurately represent the expected cash flows it anticipates receiving from the customer. It's a prudent financial practice to reflect the economic reality of the company's accounts receivable, ensuring that the financial statements provide a true and fair view of the company's financial position. |
| DSO | DSO stands for "Days of Sales Outstanding"It's a key performance indicator used to evaluate the average number of days it takes a company to collect payment after making a sale. A lower DSO indicates that a company is efficient in collecting payments from customers, while a higher DSO suggests that it takes longer to collect payments, which can impact cash flow. Taking in consideration of these variables:
|
| Best DSO | Idem DSO but with not yet due instead of the outstanding |
| Late DSO | DSO – Best DSO |
| Turnover | Sales (vat included) with posting date in the calculated period |
| Credit exposure (ERPs) | The total amount of credit risk associated with a customer or business partner. It represents the maximum amount of credit that a company is potentially exposed to in the event that a customer defaults on their payment obligations. Managing credit exposure is crucial for risk assessment and financial management. Outstanding |
| Statistical credit limits (PI1) | Not a real credit limit, just to split the limit by GBU Extracted from PI1 using the extractor ZZFCM_LIMIT_BY_GBU |
| Dunning | The process of reminding customers to make overdue payments. It is a part of the Accounts Receivable (AR) module and plays a vital role in the credit management and collections process. The dunning process is used to send reminders, statements, and notifications to customers who have not paid their invoices within the agreed-upon payment terms. The dunning process in SAP helps organizations automate the reminders for outstanding payments, improve cash flow, and maintain healthy accounts receivable. It also enables companies to follow legal requirements and internal policies for debt collection. |
| Dunning Level | SAP allows you to define multiple dunning levels. Each level represents a stage in the Dunning process, and you can set different actions and procedures for each level. |
| Dunning Procedure | It's a predefined set of rules and parameters that govern the Dunning process. It outlines the specific steps, actions, and conditions that are followed when a Dunning Run is executed. The Dunning Procedure allows organizations to tailor the Dunning process to their specific business requirements. Here are key components and aspects of a Dunning Procedure in SAP: Dunning Levels, Time Intervals, Dunning Charges, Dunning Notices, Blocking, Legal Actions, Dunning History. SAP allows organizations to customize Dunning Procedures to meet their specific business needs. |
| Dunning Notice | SAP can automatically generate dunning notices or letters that are sent to customers with overdue payments. The content and format of these notices are customizable. |
4.2 Process Detail
4.2.1. Report/Process Definition
| Domain | Finance |
|---|---|
| Application | BW reports under ITC - Credit Management and ITC - Credit Management - Non Solvay |
| Provider | Several multiproviders from Accounts Receivables scope and MVWISE02, MVWISE03 and MVWISE04 |
Same data DSO/cubes for the working Capital.
| Info | ||
|---|---|---|
| ||
In this section we will approach: |
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 |
For the Accounts Receivable scope:
For the Collection scope:
Workbook Structure Anchor Workbook Structure Workbook Structure
| Workbook Structure | |
| Workbook Structure |
1.Credit Mgt Reporting | Reports available by default in a Consolidation view perspective we cannot change this. |
|---|---|
| 2.FSCM - Cash Collection Reporting (Dispute & Promise to Pay) | Reports specific for the scope for Dispute and Collections. |
| 3.Credit Mgt Without Consolidation Rules | Reports as Accounting view logic (non consolidation). |
| ITC Credit Management - Non Solvay | Reports as Accounting view logic (non consolidation). Whenever we have companies where they left Solvay they have an agreement where they can still use some reports in BW and with these reports were created specific for the users outside of Solvay can access to information. Just one report but the logic in the same for the folder 3. |
| ITC - Credit Management AR Payments | Not used anymore and we don't have any report available. |
Standardization of the master data Anchor Standardization of the master data Standardization of the master data
| Standardization of the master data | |
| Standardization of the master data |
Company codes and customers
- For company code
- Table ZZR_T001_MAP
- Extractor 0COMP_CODE_ATTR
- For partners
- Table KNA1 with new fields
- Extractor 0CUSTOMER_ATTR
- Central table for consolidation methods and rates
- Table ZZF_T001_MGT
Example with a common customer: Transaction XD03 (check on Extra Master data)
GL/Account types and subtypes
- Classification of the GL/Accounts
- Types
- Receivables
- Payables
- Inventories
- Subtypes for Receivables
- 001 : Product and Services
- 002 : Advance payments
- 003 : Doubtful
- 004 : Write down
- 005 : Accruals & Revaluation
- Types
- Extractor ZZF_BW_GL_ACCOUNTS_SUBTYPES
- Table shared with BFC to get the headings of the GL/Accounts :
- ZZF_BFC_SETACCT
- Filter on familly « WC » and « CX »
- ZZF_BFC_SETACCT
- Then we retrieve the types and subtypes from sets (GS03)
- Remark : A set may contain other sets (recursive)
Table ZZF_BFC_SETACCT
In the set :
In the header of the set :
- REC = Receivables
- 005 = Accruals and Revaluation
These data are managed by BFC team.
For master data purpose we can contact Charlotte Rollier.
Assignment of the GBU
- Standardization of the structure of the group
- Before the IECRA for WP1
- AR from SD
- From material sales division + distribution channel => IECRA
- AR from FI
- Profit center from counterpart => IECRA
- Exceptions
- Business area : table ZZR_REPO_DIV_EXC
- Other : table ZWFAT205 at the item level
Credit model (Full factoring)
| Info |
|---|
|
Credit Management Anchor Credit Management Credit Management
| Credit Management | |
| Credit Management |
| Info | ||
|---|---|---|
| ||
|
Blocking status for Credit management
How it works?
- We go through the logs to construct the history of the blocking status;
- We start from the current situation and go back to the history to retrieve the initial status of the blocking code;
- An order is considered as closed when all the items have been delivered;
- The extractor will construct the time segments of all the status to be able to check the situation at any time.
- Some exceptions are taken into account to clean the data:
- Sometimes, we have inconsistencies in the logs of the orders, for example the status of the order are not closed even if the overall status is completed. Then the extractor will automatically consider all the status as closed if the order is completed.
- We extract the status for Credit, but also status for OTC processes, the blocking familly will be used to focus on the part that we want to see:
- This part has not been yet validated.
- Extractor : ZZV_KPI_CREDITBL2.
- The program ZZV_KPI_CREDITBLOCK_ORDERS2 will prepare the data in the table ZZV_KPI_CREDBL_2
- Data loading:
- Each Sunday at 8:00pm with selection : orders created or modifiedlast 8 days.
- The orders created or modified during the period.
GBU delegation matrix
- greement between the CM team and GBUs based on the credit limit amount, defining if an approbation is required or not:
- 3 kinds of delegation:
Colletion Anchor Colletion Colletion
| Colletion | |
| Colletion |
| Info | ||
|---|---|---|
| ||
|
- Model 1 - Cash Collection Piloting Report (FI Open Items)
- Will permit to collection team to see the current situation of the open items, open items with disputes and promises to pay
- Model 2 - Scenario Collection Piloting Report
- Will give an overview of the distribution between the FSCM scenario (to work with priority)
- Model 3 - Dunning Level Report
- Will give the dunning information at master data level
- Model 4 - Statistics Report for Dispute and Promise to Pay (P2P)
- Will give the statistics about the disputes and promises to pay
- Broadcast (Specific + Bursting) – each tuesday morning
- Will send information about the overdues to sales and collection team
Broadcasting management:
Documentation :
- How to solve problems :
| Warning |
|---|
We need to clarify this topic to determine if it is maintained or not. Pierre recommended to contact Claudrik Darnet or Nuno Mendes |
AR Payments Anchor AR Payments AR Payments
| AR Payments | |
| AR Payments |
| Info | ||
|---|---|---|
| ||
Percentage of payments received which are allocated automatically by SAP to invoices at end of period
Total of manual payments posted on customer accounts and fully matched with invoice(s) by A/R with no intervention/clarification from other parties.
Average number of days/ hours between the payment file integration in SAP and the payment allocation on customer accounts.
Errors in the assignment of the payment.
Total number of payments clearings / postings reversed due to wrong instruction or error.
All payments posted on customer accounts, but which cannot be matched with any invoice
All payments remaining in the bank sub accounts but which cannot be posted on a customer account due to missing information on payer. |
- From the bank statements
Extractor : ZZFCM_AR_PAYMENTS
- FI AR (WARP)
- For the unmatched, misdirects and corrections
- FI GL (WARP)
- For the unallocated
ITC - Weighted Paymt terms & delays Anchor ITC - Weighted Paymt terms & delays ITC - Weighted Paymt terms & delays
| ITC - Weighted Paymt terms & delays | |
| ITC - Weighted Paymt terms & delays |
| Info | ||
|---|---|---|
| ||
Workbook: BW_WBK_ITC_0028 This query is defined in Conso. view as all the other Credit Mgt reports, meaning in WP1/PF1/PI1 area and after Intercos eliminations It includes factoring entries that can be seen both in Legal/Affiliate (origin) Company points of view. |
1) Cash in follow up
- Cash in M, M-1..., M-5: Customer entries that have been cleared in current month, current month-1...
NB: Cash in definition is the same as the one used in other WC and Credit Mgt reports;
- Weighted Paymt term M In days, M-1...M-5: [ Cleared (Cash in) date - Baseline (Invoice) date * Amount in Local/Target curr. ] / Amount in Local/Target curr.; it's calculated at document level.
- Weighted Delay M In days, M-1...M-5: [ Cleared (Cash in) date - Net due date * Amount in Local/Target curr. ] / Amount in Local/Target curr.; it's calculated at document level.
2) Open items follow up
- Outstanding: Customer open items at current date.
NB: Outstanding definition is the same as the one used in other WC and Credit Mgt reports:
- Weighted Agreed Paymt term In days: [ Net due date - Baseline (Invoice) date * Amount in Local/Target curr. ] / Amount in Local/Target curr.; it's calculated at document level.
- Overdues: Customer open items at current date with Net due date < current date.
- Weighted Overd. Delay In days...: [ Net due date - Current date * Amount in Local/Target curr. ] / Amount in Local/Target curr.; it's calculated at document level.
5.0 Non-functional Descriptions
5.1 Usability
as per standard.
5.2 Regulatory Compliance
as per standard.
5.3 Security
as per standard.
5.4 Performance
as per standard.
5.5 Reliability
as per standard.
5.6 Scalability
as per standard.
5.7 Compatibility
as per standard.
5.8 Availability
as per standard.
5.9 Refresh of the Data
The loads for the ITC application are:
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)
CM master data: once a week (Saturday).
2.0 Business Process
Capture the business process that the application supports . This can be describe through a process diagram or a business capability model
3.0 Application Feature Overview
Information about the existent Workbooks and the respective BW queries.
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.