Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
SD-CAS-BD (Application Component) Basic Data⤷
VIV (Package) Introductory guide R/3 procedures
IMG Activity
| ID | SIMG_CFMENUOLSDOVA8 | Define Automatic Credit Control |
| Transaction Code | S_ALR_87006111 | IMG Activity: SIMG_CFMENUOLSDOVA8 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLSDOVA8 | Define automatic credit control |
| Customizing Activity | SIMG_CFMENUOLSDOVA8 | Define automatic credit control |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLSDOVA8 |
The automatic credit check can target certain aspects during a check and run at different times during order processing. In this activity, you can define your own credit checks to correspond to your requirements in the area of Credit Management.
You can determine an automatic credit check for any combination of the following:
- Credit control area
- Risk class (classifying attribute for your customers from the viewpoint of credit risk which is maintained in FI Customizing)
- Credit group
Example
You can define a credit check for a certain credit control area and for all sales orders in which the customer has risk class 2 (RK2).
It is possible to define a system response for each credit check (for example, warning message). In the case of a warning message, a block can be set in the credit status of a document.
When you define automatic credit checks, you can also freely define requirements which cause a document or the forwarding of the material requirements to MRP to be blocked. This is described in the IMG section "Make default settings for Credit Management".
If you define your own credit checks, proceed as follows:
- specify type of check
- specify scope of check
- specify system response to check
- allocate credit control areas
- define and allocate risk classes if necessary
- allocate credit group
- assign description to the credit check
Types of credit check in integration with SAP Credit Management
If you have activated integration with SAP Credit Management in Financial Supply Chain Management (FSCM), you can perform the following credit checks in this activity:
- Credit check on basis of maximum document values
The order or delivery value must not exceed a value defined in the credit check. The value is saved in the currency of the credit control area. This check is very useful for new customers for whom no credit limit has yet been defined. This check can be controlled by a risk class that is reserved for new customers.
- Credit check for changes to critical fields
The credit check is triggered by changes to credit-relevant document fields compared to the default values from the customer master record (payment conditions, value date days, fixed value date).
- SAP Credit Management
If you select this field, you can perform your own credit checks in an implementation of BAdI Connecting to SAP Credit Management (BADI_SD_CM)
Types of credit check when SAP Credit Management is not activated
If you just have SD/FI credit management, that is, do not have Integration with SAP Credit Management (FSCM) activated, you can execute the following types of credit checks:
- Static credit limit check
Credit allocation depends on the total value of open orders, deliveries, billing documents and open items.
- Dynamic credit limit check
The dynamic check includes both a static part which checks all open items, deliveries and billing documents and a dynamic part which checks all outstanding order values, that is, all orders not yet delivered or partially delivered. The value resulting from the checks is accumulated up to the shipping date in the information structure "S066" in freely definable time units or periods (day, week, month). This information structure is entered in Logistics Controlling and described in the section "Carry out default settings for credit management" under Basic functions.
To define the credit check, you specify a certain number of relevant periods from which a date in the future can be calculated (for example, 10 days or 2 months depending on the selected period). This ensures that sales orders which lie further in the future are not used to determine the credit exposure.
The total of the static and dynamic part of the check must not exceed the granted credit limit.
- Credit check on the basis of the maximum document value
The sales order value or the value of goods to be delivered must not exceed a certain value defined for the credit check. The value is stored in the currency of the credit control area. In particular, this check is useful if the credit limit of new customers has not yet been specified. This check can be accessed explicitly by a risk class reserved for new customers.
- Credit check when changing critical fields
The credit check is started when changes are made to credit-relevant document fields so that they differ from the default values proposed from the customer master record (terms of payment, value days and fixed value date).
- Credit check at the time of the next internal check
The credit check is started automatically on a certain date. All sales orders entered up to this time are regarded as not critical.
- Credit check on the basis of overdue open items
The ratio between open items, which are overdue by more than a certain number of days, and the customer balance must not exceed a certain percentage.
- Credit check on the basis of the oldest open items
The oldest open item may only be a certain number of days overdue.
- Credit check against maximum allowed dunning levels
The dunning level of the customer may only assume a certain maximum value.
- Customer-specific credit checks
If you require further checks to those defined in the standard system, you can define them in the corresponding user exits (LVKMPTZZ and LVKMPFZ1).
Requirements
In the No Check field, you can enter the number of a requirement with which you can control when credit checks are not carried out. You can deactivate some or all checks. This allows fine tuning on an individual basis for defining credit-relevant transactions and when credit checks do not need to be carried out.
For example, you could deactivate the credit check for the following sets of circumstances:
- As long as a document contains no items, no check will be carried out.
- No check will be carried out during order creation, but rather 14 days before delivery using a background program.
- A check should be made to see whether the payment guarantee form has changed (letter of credit, payment card). If the payment guarantee form has not changed and if the old net value does not exceed the new net value, then no credit check is carried out.
You can also reset the credit document status. The following example demonstrates when this is necessary:
You are working with risk management and have specified payment card as the payment guarantee form in the payment guarantee procedure. You create a sales order but do not enter a payment card and the credit check is carried out. You then change the sales order and enter a credit card. Since the credit card is a secure means of payment usually for an unlimited amount, you do not want to carry out another check. You can now use a requirement to have the system bypass all checks and reset the status.
Requirements are stored as routines. For further information on routines, see the IMG of SD under Routines. The two following example routines are supplied in the standard system. You can display and edit them using transaction VOFM:
- 1 Order
- 2 Delivery
You can copy and change these routines according to your own requirements. The routines contain different example scenarios in which credit checks would not be carried out.
Caution:
Make sure that the coding in your routines is consistent with the coding in risk management and the import and export parameters for the example routines supplied with the standard system.
Check financial accounting/old A/R summary
In distributed systems (central financial accounting, decentral sales and distribution), the FI data from the central system is needed for the credit check (see also: Release note Credit management in distributed systems). At the payer level or credit account level, for example, the following data would be needed for a check: Total of open items, detail information on open items (i.e. oldest open item), maximum dunning level, etc. Using the A/R summary, the FI data in the central system can be collected and then transmitted to the decentral SD system using the distribution function. The data is then evaluated in the SD system. The A/R summary represents compressed FI information for the credit check.
In check financial accounting/ old A/R summary, you can specify the allowed change rate for the A/R summary using allowed days and allowed hours. This is where you define how old the A/R summary can be for a check to be carried out. If the age rate for the A/R summary is exceeded during a credit check, the document is blocked.
Tip:
If you have set&
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUOLSDOVA8 | 0 | HLA0006563 | Credit Management |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_T691F | V - View | OVA8 | 0000000001 | Automatic credit check |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
