cancel
Showing results for 
Search instead for 
Did you mean: 

Dates affecting credit check

Former Member
0 Kudos

Hello,

I've come across two problems pertaining to credit check

1. In the sales order the scheduled line qty is shown as 0 and when the schedule line qty is confirmed system is showing the message " sales order has exceeded the static credit limit " and once saved order is going back to the credit check.

2. Whenever there is a change in the transportation planning date , loading date etc the sales order is going back into the credit check after its release through VKM3

May i know the reason why this is happening.. would greatly appreciate your replies

regards

joseph

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member

Hi,

As per the standard functionality if you change at header or item level the system will again do the credit check .

To restrict this you can create routine by copying the standard routine "1" (order related) and maintain the required logic with the help of abaper.

To create the new routine Go to VOFM --> Requirements --> credit check.

Once you create the routine assign it at document controlling field in OVA8 for the respective selection and tick at item check.

Hope this will help you to resolve your issue.

REgards,

Krishna O

former_member188076
Active Contributor
0 Kudos

Hi

1. In the sales order the scheduled line qty is shown as 0 and when the schedule line qty is confirmed system is showing the message " sales order has exceeded the static credit limit " and once saved order is going back to the credit check.

Once the Sales Order schedule Line confirmed, the system consider the Value of Confirmed Material as Open Order Value, and in your case you must have taken this Open Order Value for checking the Credit limit, Update Group : 000012. If you do not want top consider Open Order value for Credit Limit Check use Update Group 000015, in enterprise Structure for your CCA.

Whenever there is a change in the transportation planning date , loading date etc the sales order is going back into the credit check after its release through VKM3

After releasing an Order through VKM3, if you make any changes in Sales Order, system will again re-check the Credit Limit and so if it is not within credit limit, the order will again go back to Credit limit block. Check whether the Critical Fields in OVA8 is selected in your case, if so remove the check box selection, and try again.

Regards

Amitesh Anand

Former Member
0 Kudos

Hi amitesh,

thanks for your reply.. I shall check the suggestion you made in #1. Hower i would like to clarify on your second suggestion that there are no critical fields selected in OVA8 and neither quantity or rate is being changed in the sales order and it is only the dates of availability that are getting changed in the SO by a background program. Can you please suggest.

Thanks and regards

Joseph

Edited by: Joseph Kiran Kumar on Jun 14, 2010 11:26 AM

Former Member
0 Kudos

Hi,

I would like to suggest that you also check if you are working with credit horizons, as this affects the range of the credit check and could explain why your sales order is credit checked again and again every time the quantity is confirmed.

I really do not think you should change the upgrade group as this may affect your entire credit management business processes.

If you are working with credit horizon, the system will check all open documents within that horizon; for example 30 days horizon, will take into account all the open sales documents 30 days back and 30 days forward. So if your sales order falls within that bracket (schedule line confirmed) it might exceed the credit limit.

If you do not work with credit horizons, you might want to check sales orders that remain open and "consuming" your credit limit.

Let us know

Kikas

ajitsingh6
Active Contributor
0 Kudos

Dear,

Every time you do changes is S.O. System will run credit check otherwise it will be very easy that you make a S.O. with low value and save without blocking the S.O. and then you will increse the value and save the order without blocking

S.O. wcich is wrong.

Regards

AJIT K SINGH