cancel
Showing results for 
Search instead for 
Did you mean: 

Static Credit Limit Check for Sales Orders - Net Value vs Credit Value

Former Member
0 Kudos

We are testing order credit check and we have run into a problem with the Static Credit Limit Check. The Static Credit Limit Check is set to use both Order and Delivery Values. SAP uses the values in S066 and S067 to determine what values it uses to check against the credit limit. Standard SAP uses the confirmed quantity times the credit price to get the order values - this is the credit value.

So the problem is, once an order is released it is set up so it does not go back on credit hold, so anything which is not confirmed (but could be) it a potential credit value which is unaccounted for in the credit exposure and the customer can go over the credit limit.

Additionally, we run AFS and have items which are rejected with a J0 rejection code (unconfirmed) which have the potential of being confirmed and shipped and we want to include these items in the value of the order which is being checked against the credit limit (along with the deliveries, invoices and receivables).

Here is a quick example.

Customer has a credit limit of $100 (no deliveries, invoices or receivables - to keep it simple)

Order 1 is placed with a credit value of $50.00 but a potential value of $100 (the other half is J0) - this passes the credit check since $50.00 is less than the limit.

Order 2 is placed for $50.00 and has a credit value of $50. This also gets approved.

At this point, the credit limit used is 100% (based on standard SAP)

Then Order1 backorder is confirmed and the new credit value is now $100. This order now puts the customer over their limit and if the order had been released would not go back on credit hold and therefore the customer is not over their credit limit by 50%.

What I want is for Order1 to be credit checked for the $100 not the $50 so the exposure is correct.

Does anyone have any suggestions as to how we could use the Net Value of the order to perform the static credit check? And any thoughts on how to determine the correct credit exposure (open order value plus items which are J0, plus deliveries, plus invoices, plus receivables)?

I am thinking about a Z table to track the adjusted values on the orders and then use one of the customer checks to do a static credit check with the adjusted value. And for the exposure, use the adjusted value to recalculate the values in F.35 to show a more accurate view of the credit exposure.

Does anyone have an easier way to do this? Any advice is appreciated.

Thanks,

Suzanne

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Some good responses. Honestly, using the reason for rejection for the purpose is not optimal. The delivery block - or perhaps status management would be better.

In the traditional FI/SD credit management, I odn't think you can adjust the values in the info structure without a modifation. In SAP Credit Management - it looks like there are BADIs that can be used to affect the update to teh S066 and other structures.

Former Member
0 Kudos

I tried the item check in OVA8 and that seems to have no impact on what I am trying to do.

Vinu - when you say you can use a user-exit to trigger the credit check again even though it has been released already, where are these user-exits? Are you talking about the reserve checks in OVA8?

Thanks for your help.

Suzanne

Former Member
0 Kudos

Once the back order confirms and the schedule line is updated the system should carry out a second credit check

Please check to make sure that the deviation % and max number of days are not causing the issue.

If the BO Update takes place within the max number of days before the credit check is carried out again then that might be why the check is not taking place.

former_member183879
Active Contributor
0 Kudos

Hi Suzanne,

I dont know if this will help you.

In OVA8, there is a checkbox called "Item Check". If it is checked for you already, uncheck it and then try your scenario. It will take care of the value of the order instead of the value of the item alone.

If it is not working, pls let us know.

Former Member
0 Kudos

Hi Suzzane,

In the scenario that you have provided, in the first order items worth 50$ are rejected. Hence standard SAP will not take this into account as this item is rejected.Two solutions can be provided here:

1) The line item can have a delivery block instead of a reason for rejection.This way the 50$ will get accounted.However, if this is against customer norms as this will appear in the order acknowledgment, this cannot be used.

2) User exit can be used where a credit check can be triggered once the document value changes, even though the document has a released status.

Hope this helps.

Thanks,

Vinu