Credit status not approved

[former_member431487]

Hi,

The credit status (VBUK-CMGST) for both sales order and delivery is B. I tried to release them in VKM* transactions but I am getting message that No work list is selected.

How to release the credit block for order and delivery?

Thanks.

[former_member431487]

Update - The overall status (VBUK-GBSTK) for sales order is C and Credit status (VBUK-CMGST) is B. So when I am trying to release the order in VKM* I am not able to do because system only considers orders with over all status GBSTK as A or B.

For the delivery document, overall status GBSTK is B and Credit status CMGST is also B. But I am not able to execute delivery in VKM5 because I think if order is on credit block then delivery cannot be released.

Can you suggest how to release sales order from credit block if overall status is C but CMGST is B.

[VeselinaPeykova · Accepted solution]

The first thing that I would do is view the order in CHECK_CM - statuses, credit control area,

If you and your user cannot see the sales order even in VKM3, I would run authorization trace.

If still no luck - debug.

[VeselinaPeykova]

"The overall status (VBUK-GBSTK) for sales order is C and Credit status (VBUK-CMGST) is B. So when I am trying to release the order in VKM* I am not able to do because system only considers orders with over all status GBSTK as A or B."

Actually, you can release such orders. I do not understand what is the roadblock with VKM*. Yes, by default the selection in VKM4 is as you describe, but you can change it if you want to.

For outbound deliveries you can use again VKM4, you just change the selection, because "overall status GBSTK is B and Credit status CMGST is also B".

It works just fine if you have enough authorizations.

[former_member431487]

veselina.peykova - Thanks for your comment. I already tried exactly same way in VKM4 as you have shown in your screenshot but I am getting message that nothing is selected. It didn't occur to me that it could be authorization issue.

[former_member431487]

veselina.peykova - I asked user to try same parameters in VKM4 and they are also not getting the output to release credit block. Can you please suggest anything else?

[Lakshmipathi]

When you post a query and give further updates, please add the content under "Comments" and not under "Answer" as you were not answering to a query but only providing additional informations as asked by the members. Also, when you add the text under Comments, it will be intimated to the person to whom you are responding whereas, if you add the text under Answer, the member will not be intimated. By the way, your above answer has been converted as comment by me.

[Lakshmipathi]

Did you go through the very first point mentioned in the OSS note I referred? It says

and your original post also starts with the same text. So I presumed and suggested

[former_member431487]

Yes I did not mention in my case GBSTK is C instead of Blank, I have updated the question with additional details.

[Lakshmipathi]

It is a standard behaviour. Have a look at OSS note 2764257

[former_member431487]

lakshmipathi.ganesan - Thanks for your reply. I checked that Note, it refers to issue when VBUK-GBSTK is blank but in my case it is C as delivery is already created and after that the credit status in order was changed from A to B. Can you suggest how I can release the order from credit block if overall status is C?

[sanilbhandari]

Hello karan.singh14

Please check the status of the documents in VBUK field GBSTK. If the status is C, than they will not appear in VKM*

Please check if there is any reason for rejection in these documents, that they have the status as C.

Regards

Sanil

[former_member431487]

sanil.bhandari - Thanks for your reply. You are correct, order GBSTK status is C but that is not because of any rejection. Actually delivery is already created for this sales order and after that credit status was changed to B.

So now for the order overall status is C and credit status is B. So how can I release the credit block as I can't execute it in VKM* transactions.