SAP FSCM Credit Management Config Steps

SAP Note
18613 - Checklist for Credit Management

Version 16 Validity: 01.12.2005 - active
Language English
Header Data
Released On 01.12.2005 16:53:23
Release Status Released for Customer
Component
SD-BF-CM Credit Management
Priority
Recommendations / Additional Info
Category
Help for error analysis
Symptom
Credit management does not work correctly or not at all. This is a general customizing check that is
urgently recommended in case of problems with credit management.
Other Terms
CHECKLISTSD, customizing, credit
Reason and Prerequisites

Solution
Check the settings in the following transactions:
You can print this note and use it as a form for entering all current settings. In addition or as an
alternative, you can use Report CHECK_CM as of Release 4.6B (see Note 381685).
Settings for determining the credit control area of a document
The settings of items 1 - 4 are taken into account according to their priority. The credit
control area found is stored in field VBAK-K K B E R .
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
4. Transaction SE37
Is user exit EXIT_SAPFV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table T001CM
of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. You can
use Transaction FD32 to assign this risk category to a credit account.
10. Transaction OVA8

Here, the individual credit checks for key fields
credit control area
risk category
credit group
are set. Take these key fields from the above settings and go to the detail screen. In
particular, check whether fields "Reaction" and "Status/block" are set correctly. To carry
out follow-up actions in case of a credit block, the credit check status must be set (field
"Status/block").
11. Transaction FD32

Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values
Update of the credit values is required for the limit check (static or dynamic credit limit
check).
13. You want the item to be relevant for billing. If an item is not
relevant for billing or for pro forma billing, no update occurs.
14. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked.
This field corresponds to field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
15. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control"). Usually,
the net value plus taxes is used. This way the system is determined to use this subtotal for
credit pricing. The credit price is stored in field VBAP-CMPRE and used for update and credit
check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
16. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The default
setting is "12". If you use another update group, check whether this is fine with you. If you
open an OSS message, please tell us the alternative update group.
Update:
17. Transaction OMO1
Which kind of update did you choose for structure S066? In any case, "Synchronous update (1)"
has to be chosen as the kind of update. All other settings will lead to errors.
Other Attributes
Transaction codes
FD32
HIER
OB01
OB38
OB45
OBZK
OMO1
OVA7
OVA8
OVAD
OVAK
OVFL
SE37
TRANSAKTIONEN
V/08
VD02
VOV7
XD02
Validity
This document is not restricted to a software component or software component version
References
This document refers to:
SAP Notes
1714480 Credit values for product selection
1626376 CSFG: Error in credit update
1590471 CSFG: Credit value not updated correctly
425523 Collection of consulting notes: Credit update
425483 Consulting note collection: Credit checks
396338 Problems in credit management - analysis help
381685 Analysis of the credit-relevant data of a document
377165 Update open credit values for credit management
65865 D16 Credit Management Customizing for Val. Contract
This document is referenced by:

SAP Notes (9)
1626376 CSFG: Error in credit update
1590471 CSFG: Credit value not updated correctly
1714480 Credit values for product selection
65865 D16 Credit Management Customizing for Val. Contract
425483 Consulting note collection: Credit checks
425523 Collection of consulting notes: Credit update
381685 Analysis of the credit-relevant data of a document
396338 Problems in credit management - analysis help
377165 Update open credit values for credit management

SAP FSCM Credit Management Config Steps

Uploaded by

Copyright:

Available Formats

SAP FSCM Credit Management Config Steps

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP FSCM Credit Management Config Steps

Uploaded by

Copyright:

Available Formats

SAP Note

18613 - Checklist for Credit Management

Reason and Prerequisites

10. Transaction OVA8

credit control area

11. Transaction FD32

This document is referenced by:

You might also like