cancel
Showing results for 
Search instead for 
Did you mean: 

Credit block @ Delivery Level

Former Member
0 Kudos

Hi all,

I have the following scenario where expert advice is really appreciated.

Our credit management module will check credit conditions of the customer at Sales order and Delivery level.

Scenario

Customer credit conditions are not breached.

Initially, Sales order and Delivery created without any credit block becuase the credit conditions are not breached. Delivery has been picked awaiting for PGI. Physical goods already left the warehouse. We need to make some changes at the Delivery level in SAP before the PGI. However, the customer is now breaching the credit conditions as such when we tried saving the Delivery when the change is made it will be blocked because of credit issue.

Is there a way for preventing the delivery from subjecting to credit check IF the picking is already completed?

Your prompt reply is appreciated.

Regards,

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

hi

for prventing delivery after picking do the below

1.You need to deactivate the credit group "03" in the t code OVAD fo rthe delivery document type in the GI credit group field

2.You should not maintain the credit check combination Credit control area//Risk category //Credit group ("03")

As [per my undersatnding in your case the value is more than the credit limit given

if you provide me the correct error with message no iy may help to resolve the issue

Regards

Damu

Former Member
0 Kudos

Hi Damu,

We currently do not use credit group 03. The message we received from SAP is 'Goods issue from delivery 80690992 not possible due to credit block'. It sounds strange that PGI is not possible due to credit block eventhough we do not use credit group 03. However, I think the message provided by SAP is inaccurate because I can confirm that the credit block is triggered at Delivery level when some fields are changed in delivery document.

Thanks.

Francis

former_member131745
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

The functionality to stop the PGI at delivery with an error message as oppsed to a warning was brought about by OSS note 441009. I'm not sure if it is a good idea to remove this code or if it would resolve your issue. Does it resolve your issue?

Also, why cant you simply release the delivery in VKM4 again and then PGI on the same day?

I hope this helps.

Gerard

Former Member
0 Kudos

Hi

If my below understanding is correct, you can follow below solution given

Sale order - > Credit check happened, within credit limit, NO BLOCK

Delivery created --> NO Block

Delivery to PGI --> while doing changes VL02n, Credit check happens, credit limit exceeds (or any other condition) -> setting a Credit block.

If my above understanding is correct, you can go to OVA8 (credit control settings). In the 'number of days' field --> please maintain some days ( depending on your Delivery creation to PGI duration e.g. if it is 2 days) maintain 2 days.

System will not set a block for so many number of days.

please try above option & revert

thank you

Former Member
0 Kudos

Hi Anirudh.vb ,

We already set that to 10 days. However we made the changes within the 10 days period of the delivery creation but the delivery is still being blocked by due to credit reason.

Thanks.

Former Member
0 Kudos

Hello

You can create a simple routine & maintain in OVA8 -> no credit check field.

You need to maintain a necessary logic e.g. No check, if the new net value does not exceed the old net value in VL02n etc.

Please check if Item Check is unticked.

thank you

Former Member
0 Kudos

Hi Anirudh.vb ,

Thank you for the input. The item check is uncheck and we do not currently use any routine for this. It is a great idea to be explored further.

Any further advice is appreciated.

Thank you.

Francis

Former Member
0 Kudos

Hi,

What are the changes you made to the delivery document and date on which you changed?

Thanks,

VNR

Former Member
0 Kudos

Hi VNR,

We add a new partner (Forwarding agent) @ the header level and also created a handling units.

Thanks.