Order back on credit when within Number of days

[Former Member]

Hoping that someone can explain this scenario:

Order is entered and released on 7/28/2011. Went on hold for Oldest of Open Item which configuration indicates should be done if 20 days.

The Release Document Still Unchecked in Automatic Control indicates Number of Days as 30.

On August 19, a change is made to the order and it goes back on hold for Oldest of Open items.

Why would this happen if the Number of Days was not met?

Further, the accouting manager says that the order didn't show up on the VKM1 transaction until today (which may be related to the 30 days?) Why had it not shown up sooner, like when the status actually changed?

Thanks in advance,

[Shiva_Ram · Accepted solution]

On August 19, a change is made to the order

What was the change made to the order. In OVA8, can you check any value maintained in the field Deviation in % under released documents are still unchecked? Also check the fields User 1, 2, or 3 is checked or not. If checked, then there is an user exit that might cause this behavior.

Regards,

[Former Member · Accepted solution]

Thank you Shiva,

A line was added on that day, but the amount of the order was not changed by 100% deviation and it also did not exceed the credit limit. The reason for credit block was 'Oldest of Open Item'.

We do not user User1, User2 or User3 user exits.

[former_member209761 · Accepted solution]

Dear Anabela,

What i suggest is, you look in FBL5N whether there is any uncleared accounting document for billing (for the customer)

Also you may check in fd32, environment-->oldest item and see whether there is any value shown there with the due date.

Check and revert back,

Thanks & Regards,

Hegal K Charles

[Former Member · Accepted solution]

Hegal,

As of this morning, there were uncleared documents in FBL5N, but are now cleared. This morning showed a document with 6/1/2011 and with 71 days arrears. It is no longer showing.

Keep in mind that the order originally went on block on 7/28 because of Overdue items which was because of the 6/1/2011 document. The changes to the order were on 8/19 so it is not 30 days.

In FD33, Environment doesn't have have a menu option Oldest Item.

Thanks for your response,

Bela

[former_member209761 · Accepted solution]

Dear Bela,

Sorry.

That oldest item is in EXTRAS in the FD32 menu

Now, coming back to your issue, you told that there was an overdue document till today morning with 71 days.

Now the order which is changed in 8/19 will also have this overdue document right?

today is 8/27 and the overdue was 71

8/19 is 8 days less than 8/27 which means that document will be overdue by 71-8 = 63

So when u change the order, system will obviously block due to oldest open item.

Whats the date of creation of this sales order which is under dispute?

Thanks & Regards,

Hegal K Charles

[Former Member · Accepted solution]

The order was created on 7/27 and today is 8/26 where I am.

The order went on credit block when it was created because of Oldest Item. It was RELEASED on 7/28.

It was modified on 8/8 with no credit status change.

It was modified on 8/11 with no credit status change.

It was modified on 8/19 and went back on credit block.

The credit status was changed only on 8/19 to credit NOT ok.

In FD32 (this afternoon - would have been different this am),

Net due date 8/25/2011

Net arrears 1

Summary again:

Deviation in % = 100%

Number of days = 30

Oldest of Open items: 20 days

Reason for credit block on 7/27 and 8/19: Oldest of Open items

Thanks again,

[Shiva_Ram · Accepted solution]

As today only the oldest open item was cleared in FBL5N, the system behaved correctly putting on block on 07/27 and 08/19. You may ask why on 08/19 and not on 08/08 or 08/11. For this you need to check the history of the open item that was cleared today.

You can run program RVKRED88 in SA38, just to see how the system reacts for the credit account (customer account) and document number.

Regards,

[former_member209761 · Accepted solution]

Dear Bela,

It was modified on 8/11 with no credit status change.

It was modified on 8/19 and went back on credit block.

Between 8/11 and 8/19 , check how many billing documents where there for the customer.

Find the due date from the billing header and cleared date from FBL5N.

Between 8/11 and 8/19, there might have been documents which got due.

That is the only possibility for system triggering message for credit check due to oldest open item.

Thanks & Regards,

Hegal K Charles

Edited by: Hegal . K . Charles on Aug 28, 2011 11:17 AM

[Former Member · Accepted solution]

I understand all that is said. The question remains that the Number of Days says 30 so why would it go back on within the 30 days? The oldest item was overdue throughout the whole process.

Perhaps, this is one that may be unsolved for a while.

Thank you.

[kalyan_mokirala]

Hi Bela,

CHECK_CM is a standard report provided by SAP which gives you the correct analysis of the reason why the document is kept on hold for credit.

If you have authorization to SA38 transaction you will be able to execute this.

Enter the transaction code SA38

You will be faced with ABAP program execution screen

Enter the program CHECK_CM and execute the transaction.

You will be faced with analysis of SD document with regard to credit management screen

In the document number field enter the sales document number (Order number) and in the settings box check both the check boxes available and execute the transaction.

You will be now faced with complete explanation of the credit check done for the order

Based on this analysis we can conclude the reason of credit check and have the issue analyzed further.

we can use the same report even for getting the analysis of credit check done for delivery also if we have credit check at delivery or goods issue level. Unfortunately SAP does not provide any transaction code for this report.

Hope this explains

Edited by: mokirala tilak on Aug 29, 2011 3:43 PM

[Former Member]

Thank you. I had executed this transaction and was not able to get the information I was looking for. It is useful, but it doesn't explain whyit went BACK on hold within the 30 days of release. That is the only thing missing.

I appreciate your contributions.

Bela