Credit check re-triggered after an Order is released

[Former Member]

Hi Experts

We have a Sales Order which is in "Released" and "Not blocked" Status. The issue is when we add or change a field at Item level --> Additional Data A --> "Customer Condition Group" and save the Order, system re-triggers the Credit check and puts the Order on Credit block.

Business Requirement: Adding the code should not cause the credit check to trigger but changing other fields such as: Payment terms, Incoterms, Due date, Price and Quantity, should trigger the Credit check.

Do we have any standard solution or configuration in OVA8 settings to fix this issue? OR we have to use User exit to fulfill the requirement? Pls suggest.

Regards

Subrat

[VeselinaPeykova]

There are different ways to achieve that, but it depends also on your current settings and process flow.

Could you please share a screensot of your OVA8 settings and check_cm result for the blocked order?

In case you use a custom routine for credit check, please specify what logic is implemented in it.

[Lakshmipathi]

Share your OVA8 configuration.  In normal circumstances, if there is a change in critical fields like Payment Terms, Additional Value Days etc., system would go for credit block once again.

G. Lakshmipathi

[Former Member]

Hi Lakshmi

Pls find the OVA8 Setting and the VA02 Item field screenshot.

Regards

Subrat

[VeselinaPeykova]

Hello,

my idea was to create a sales order, release it from credit, change customer group1 value, save.

Then to use this blocked order number in program check_cm and provide the result, so that you can find out what is the reason that the order gets blocked.

• At the moment I am just guessing about the possible reason, but looking at your OVA8 settings - you might consider entering some values in released documents are still unchecked (at least for number of days).

For the exact number of days or especially regarding percentage value, please discuss with the head of accounting and with the business consultants what the company policy states.

Try first in a test system with entering some value for number of days - e.g. 5, create a new order, release it, save, change customer group and check the result. If this does not solve the problem, check whether you have pricing conditions applied as a result of setting this value for customer group 1 that increase the credit price.

• Also in addition to the days setting you could add a routine similar to 1 (LVKMP001) in OVA8 to bypass credit checks in certain cases - routine 1 compares the old and new net value, and if we do not increase the net value, the order is not blocked.

Message was edited by: Veselina Peykova

[Former Member]

Hi Veselina

Thanks for your reply. Checked CHECK_CM...it doesn't really tells much about the root cause. I have put 999 days in configuration and system is doing any credit check further. But it applies to critical fields like payment terms & incoterms also. So if some one changes payment terms, incoterms system should trigger credit check and block the order.

Regards

Subrat

[VeselinaPeykova]

Check_cm is a very useful program once you get used to interpreting the information there.

• Number of days is used to skip order recheck for a couple of days - if it takes some time to process the order from creation to billing, it can be very useful - you have an order created on Monday and release it from credit on the same day, but delay the further processing until Wednesday for some reason. You add some additional details to the order and you do not want to get it rechecked and blocked again for credit, so you set 3 days in OVA8. 999 days is not a very good idea, becuse it can be easily abused and will cause problems with the auditors.

• The second case is when you are ok to recheck the order, but want to bypass some of credit checks in certain situations. Example: In the case a change in the order does not result in higher net value we do not want to block it for credit, but if somebody changes the payment term for a released order, we want to block it. In this case you copy routine 1 in VOFM to 901 and adjust it according to your requirements. Then you assign the routine in OVA8. For example I have commented out the line MOVE CHARX to BYPASS-CRITICAL_FIELDS in the block where it is checked if XVBAK-NETWR LE YVBAK-NETWR.

One calrification - the check will go through the custom routine only if it does not fall into the tolerances defined in days or percentage for released orders are still unchecked.

Message was edited by: Veselina Peykova

[Former Member]

Thanks Veselina for your explanation !

When the field in Order --> Item--> Additional data --> Condition group 1 is assigned a value and the Order is saved, system triggers a credit check and the Order is blocked. As per my understanding this field should not trigger Credit check. Can you share your thoughts on same.

[jignesh_mehta3]

Hello Subrat,

Is any Pricing condition determined based on Condition Group 1?

If yes then the Sales Order will go for Credit Check again as Critical data ha been changed.

Thanks,

Jignesh Mehta

[VeselinaPeykova]

You need to start sharing the results from program check_cm and the change log for the order .

Did you try the option with the VOFM routine?

Did you check whether the credit price has changed as a result of you entering the customer group?

I gave you a couple of general suggestions that you can use to improve your process, but in order to figure out what exactly is the root cause of your problem, we need to see some data first.

[phanikumar_v3]

I have put 999 days in configuration and system is doing any credit check further. But it applies to critical fields like payment terms & incoterms also. So if some one changes payment terms, incoterms system should trigger credit check and block the order..

It certainly tells us that we might be checking the wrong OVA8 combination here(credit control area,Risk category,Credit group)-Pl confirm. Also your screen shot of OVA8 does not confirms activation of critical fields.

I think normally condition group at item level will never changes the net value

(even If used as a condition Until doing a manual update of pricing or condition group is used in any calculation formulae-

-Is it applicable in your case?? )

Here the question comes is- once an order released-when the user is changing the condition group(On the same day/next days)

If it is on the same day-normally it will not go again-until net value change..

if on Next days-definitely your configs will take for block again(released documents are still unchecked section is blank)

"""""Business Requirement: Adding the code should not cause the credit check to trigger but changing other fields such as: Payment terms, Incoterms, Due date, Price and Quantity, should trigger the Credit check""""""""

Your screen shot does not support this as critical fields are not active here.

Hope this helps.

Phanikumar

[Former Member]

The field condition group is not used in Pricing condition records determination. Even if you type some texts and save the order system triggered credit check & blocked the order. If we don't do any change and go inside VA02, click on Item tab here & there, and then try to save the Orders, system carry out the check again and blocks the order due to credit hold. Can you explain why this is happening?

The Released orders are not changed on same day. These are standing orders having more than 50 line items which are delivered partially time to time. I found some SAP Notes suggesting this as the standard behavior for Partially delivered SO.

The problem with the OVA8 configuration "Released orders are still unchecked" is that for ex: if no. of days is set as 5 days, then system doesn't carryout further credit check for next 5 days, but at same time it doesn't trigger check even if we change fields like payment terms, incoterms, delivery date, price etc. which is the also the requirement of business.

If we set Critical fields check and set the Status to block, in standard SAP it only works for the 3 fields: Payment terms, additional value days & fixed date.

Here the requirement is to add other critical fields like Incoterms, Pricing, Delivery date etc. Pls suggest how can we achieve this in standard OVA8 configuration.

[VeselinaPeykova]

This is exactly where the custom VOFM routine can help you.

After you activate the credit check for critical fields, do not specify any grace days for released orders are still unchecked. Copy the routine to a new one and comment out the critical fields bypassing. Then assign it in OVA8.

In this case the check will go every time through this routine and in case the net value is not increased (nobody adds additional items) , it will not block the order, except if you change payment terms or any other critical data.

If you need additional restrictions on when the credit check should be bypassed, you can also specify them in the new routine (as long as you can get the data from the available structures). You need developer authorizations and access key as for all other VOFM routines, but it a very trivial task for any ABAP-er.

When you have no routine assigned and no grace days, during change/save of the order, the system goes through all checks specified in OVA8 as it does in create mode, so the order gets blocked again.

This is a common issue in some business processes (e.g. DSD), so SAP provides the VOFM routine in OVA8 as a mechanism to solve it.

[phanikumar_v3]

Normally we cannot enter any text in this field "Customer condition group" other than defined values--If required please mask these fields with a variant or screen exits--so your issue of re triggering to credit  block will be solved here.

Still further restrictions needed-we need to use the exits LVKMPFZZ,Z1,Z2,Z3 with Routine as suggested by our member Peykova--Accordingly..

Note: Instead of going for exit-why dont we restrict-- at sales order level-change of fields like Payment terms,INCO terms,Delivery date,price etc..with a variant--Offcourse business decision is very critical here.

Phanikumar

[VeselinaPeykova]

You do not need the user exits you mention to fulfill the customer requirements.

Using a routine in OVA8 does not mean that you need to activate additional user exits there.

It is not a very good idea to restrict completely all the fields you specify with a variant - sometimes the users can have a valid reason to change the incoterms or payment terms before a delivery is created.

Here is one possible scenario - a customer orders a big quantity of products and this is way over his limit. It poses a risk to deliver the products with his normal payment terms (1 week after the delivery), so the the customer agrees that the complete payment will be done at the time of delivery. In some cases it might be acceptable to restrict payment terms changes in the sales documents by field modification, but for your process I can see no advantages compared to using credit management critical fields check.

Requested delivery date - you need to give the possibility for the user to override it during order entry (you agree with the customer that he will get his products not in 2 days, but next week).

Incoterms - well... this depends on your business practice, but sometimes you can agree for different incoterms than the customer defaults for a specific order - this is why you have the option to change it in the document.