cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Payment Guarantee Procedure is invalidating OVA8 config - Released document are still unchecked

Former Member
0 Likes
744

Hello Experts,

Summary: Payment Guarantee Procedure is invalidating Risk class (OVA8) configuration “Released document are still unchecked”

Configurations:

OVA8 Risk Class – Released documents are still unchecked for 10 days – Basically we don’t want to trigger a credit check for 10 days once the document is released and there is no change in net value of the order. Once 10 days are passed, the credit checks can/should block the order

Now, at the order header, we have Payment Guarantee procedure defined for Credit Card orders

Issue: If we don’t have the Payment Guarantee procedure at order, the OVA8 configurations works just well. It doesn’t invoke credit check for the order for 10 days if net value remains unchecked.

However, as per my research, when Payment Guarantee procedure is present it does not matter what is configured in number of days. The order keeps going on hold even after it is released and no economic edits are made to the order.

One solution I could think of is to write No credit check routine as per requirement. However, could you experts suggest if this can be achieved in standard without no credit check routine? I found quite a few notes on this however all of them are very old. We are on 1511 S4 hana version and none of them are applicable there.

Regards,
Sanket

Accepted Solutions (1)

Accepted Solutions (1)

Lakshmipathi
SAP Champion
SAP Champion
0 Likes

Have a look at OSS note 1454134

Former Member
0 Likes

Thank you lakshmipathi.ganesan for your response. We tried with the note and following resolution suggested. However it all together stops credit check for orders which are guaranteed by cards. Our requirement is to have credit management active and also execute ova8 checks even when the order is guaranteed by cards.

Resolution

Please consider SAP note 170183.

Implement one of the following solutions:

1.Remove SAP note 792943 from your system.

2.Manually insert the code from SAP note 700786 back into your system

Regards,
Sanket

Answers (1)

Answers (1)

Lakshmipathi
SAP Champion
SAP Champion
0 Likes

If you say that even after inserting the code manually as recommended in OSS note 700786, your problem is not solved, then, you need to raise an OSS message with SAP