1. ransaction OB38 Check which credit control area is assigned to the company code.

2. Transaction OVFL Check which credit control area is assigned to the sales area.
3. Transaction XD02 or VD02 Check which credit control area is assigned to the 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.
6. Settings for the credit checks :
 Transaction OVAK which settings do exist for the sales document type used?
 Transaction OVAD Which settings do exist for the delivery type used?
 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.
 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").
 Transaction FD32 Credit master data for the payer of the relevant document.
 Settings for updating the credit values Update of the credit values is required for
the limit check (static or dynamic credit limit check).
 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.
 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.
 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':
 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.
 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.
7. Here is the total check list for Credit Management.
8. 1. Transaction OB38
9. Check which credit control area is assigned to the company code.
10. Company code:
11. Credit control area:
12. 2. Transaction OVFL
13. Check which credit control area is assigned to the sales area.
14. Sales area:
15. Credit control area:
16. 3. Transaction XD02 or VD02
17. Check which credit control area is assigned to the payer.
18. Payer:
19. Credit control area:
20. 4. Transaction SE37
21. Is user exit EXIT_SAPFV45K_001 being used?
22. 5. Transaction OBZK
23. For the settings under items 2 - 4, field "All company codes" must be
24. marked in Transaction OB45, or the credit control area must be entered
25. under the relevant company code in table T001CM of the credit control
26. areas allowed.
27. Company code:
28. 6. Settings for the credit checks
29. 7. Transaction OVAK
30. Which settings do exist for the sales document type used?
31. Sales document:
32. Check credit:
33. Credit group:
34. 8. Transaction OVAD
35. Which settings do exist for the delivery type used?
36. Delivery type:
37. Credit group for delivery:
38. Credit group for goods issue:
39. 9. Transaction OB01
40. Credit management/Change risk category
41. Definition of the risk category for each credit control area. You can
42. use Transaction FD32 to assign this risk category to a credit account.
43. 10. Transaction OVA8
44. Here, the individual credit checks for key fields
45. - credit control area
46. - risk category
47. - credit group
48. are set. Take these key fields from the above settings and go
49. to the detail screen. In particular, check whether fields
50. "Reaction" and "Status/block" are set correctly. To carry out
51. follow-up actions in case of a credit block, the credit check
52. status must be set (field "Status/block").
53. 11. Transaction FD32
54. Credit master data for the payer of the relevant document.
55. Credit account:
56. Credit limit:
57. Risk category:
58. Currency:
59. 12. Settings for updating the credit values
60. Update of the credit values is required for the limit check (static or
61. dynamic credit limit check).
62. 13. You want the item to be relevant for billing. If an item is not
63. relevant for billing or for pro forma billing, no update occurs.
64. 14. Transaction OVA7
65. Update of the credit value is active for the corresponding item type
66. if the check box is marked. This field corresponds to field "Active
67. receivable" in Transaction VOV7.
68. Item type:
69. Active receivable:
70. 15. Transaction V/08, Pricing
71. In the pricing procedure used for pricing, subtotal "A" must be
72. entered in a line for determining the credit value (mark the pricing
73. procedure and doubleclick on "Control"). Usually, the net value plus
74. taxes is used. This way the system is determined to use this subtotal
75. for credit pricing. The credit price is stored in field VBAP-CMPRE and
76. used for update and credit check.
77. You can find the used pricing procedure of the order under "Item ->
78. Condition -> Analysis".
79. Pricing procedure:
80. Line with subtotal = 'A':
81. 16. Transaction OB45
82. Which update group (field "Update") do you use in the relevant credit
83. control area? The default setting is "12". If you use another update
84. group, check whether this is fine with you. If you open an OSS
85. message, please tell us the alternative update group.
86. Credit control area:
87. Update:
88. 17. Transaction OMO1
89. Which kind of update did you choose for structure S066? In any case,
90. "Synchronous update (1)" has to be chosen as the kind of upda