Ansicht
Dokumentation

SIMG_CFMENUOLSDOVA8 - Define Automatic Credit Control

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Define your own credit checks.

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 category (classification characteristic for customers with regard to the credit risk. The credit risk category controls all credit checks)

• 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 whether a credit check in SAP Credit Management is in scope

You can define check rules for the credit check in SAP Credit Management in the Define Checking Rules Customizing activity.

• specify system response to check

• allocate credit control areas

• allocate risk category

• assign description to the credit check

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 up credit management so that credit checks are only carried out for certain, comparatively rare orders, then you can enter an age rate of 0. You should also activate RFC in FI Customizing for credit management (preparatory configurations). This ensures that the A/R summary is always determined if a credit check is to be carried out. Because credit checks are carried out relatively rarely in this case, system performance will not be significantly influenced.

Note:
Fields allowed days and allowed hours are only available for entry if you have entered an X in field Read A/R summary in FI Customizing. The path is:Accounts Receivable and Accounts > Credit Management > Credit Control Account > Make basic settings for credit management.

1. Enter a combination of credit control area, risk category and credit group as well as a description for the credit check you want to define.
2. On the detail screen of credit control, specify the scope of the check and the system response.
3. If necessary, enter the general data for the credit check.

Addresses (Business Address Services)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 7110 Date: 20240523 Time: 201623     sap01-206 ( 140 ms )