cancel
Showing results for 
Search instead for 
Did you mean: 

Credit Management on Oldest due days and credit limit

Former Member
0 Kudos

Dear All,

Our Customer having requirement for credit management on credit limit and oldest due days ,

I.e. 1) If credit Limit gets exceeds then system should give the warning message during delivery   &

2) If there is Oldest days are set then system should check it & stop to create the delivery

But during testing it is observe  that system neither check at credit limit nor at oldest days ,

I have use the automatic credit management to execute the credit management,

Kindly guide to resolve the above issue,

Regards,

sourabh

Accepted Solutions (1)

Accepted Solutions (1)

former_member187236
Participant
0 Kudos

Hello Pai,

By looking at the settings it looks like wrongly mapped.

You need to correct the setting and before doing that you need to understand the concept and meaning of each and every filed.

You need to follow the below mentioned process.

Here is the total check list for Credit Management.

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:

Credit control area:

3. Transaction XD02 or VD02

Check which credit control area is assigned to the payer.

Payer:

Credit control area:

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:

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.

Credit control area:

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 then this you can go through these links too.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00a9015a-3664-2e10-5bb2-a3ab2b61f...

This links will give you the better clarity on credit management and it will help you in doing proper config.

Regards

Parag

Former Member
0 Kudos

Thanks parag ,

Former Member
0 Kudos

Dear sir,

I have check all the settings and link you have forward as above  as mentioned above , all settings are correct in my system , only make some changes at OVA8 ,

But it is observed that during testing, system is not working as per settings at OVA8 screen

and client requirement is ,system should work on both credit limit and oldest item

Kindly guide to resolove the issue,

Regards,

sourabh

Former Member
0 Kudos

Please do the needful to resolve the above issue,

Regards,

Sourabh

Answers (0)