on 04-05-2012 4:12 AM
Dear Experts We have dynamic credit limit check and using only one credit control area and only one risk category, It is working fine since long time and blocking to create delivery when ever they cross credit limit…
But recently, only two customers could create s.order,delivery and billing successfully even when they have crossed their credit limit.
Could you please tell where to check exactly in the system to identify and solve this issue.
Thank you very much in anticipation.
Regards
Rajesh
Hi Rajesh,
Credit update happens with the update group working in tandem with information structures S066 and S077.Sometimes when there will be problem with update group and credit update may not happen properly and may result in improper credit checks in sales documents.
First check the credit analysis of the orders for which you think system has bypassed credit check using the Program CHECK_CM in the transaction code SE38 /SA38 by inputing the sales order number. Here you can check whether system eveluated credit check for the order if not for what reason.
Hope you will get some clue here.
Secondly for correcting improper credit checks in sales documents because of update errors, you have to run the program RVKRED77 for the payer and credit control area combination
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rajesh,
you have the 2 payer numbers (only two customers could create s.order,delivery and billing successfully even when they have crossed their credit limit) based on which you can trace the invoices created recently by searching in VBRK table by inputting the payer numbers and to and from dates and there by trace prceeding orders.
I further suggest you the following.
1. Run the program Z_CREDIT_VALUE_COMPARE for payer and credit control area combination and compare simulated new credit values with database credit values. This will give you an idea of the difference between actual and the current database credit values.
2. Further as you have issue with 2 payer customers run RVKRED77 for 2 customers during week end and check if credit is getting evaluated correctly in the orders created during the next week.
Hi
We could narrow down the sales order which could exceed the credit limit with out getting blocked.
But while running the program CHECK_CM by giving the concern sales order number , not able to get any clue as no error over there.
Could any please suggest on how to proceed further in finding the root cause of this issue.
Regards
Rajesh
Rajesh,
Check_CM report of the sales order will give you the complete analysis of how system passed the credit and on what basis system evaluated credit check etc. this will give you some idea of how credit check is being performed for the order.
As suggested earlier run the program RVKRED77 for the 2 payers and moniter the credit check performed for the corresponding customers for next few days
Hi Rajesh,
As per my knowledge, we can not get the credit related values for an old order which system had considered at the point when it was created. Check_CM can give you the way how system evaluated the credit.
But as I had suggested by executing the program Z_CREDIT_VALUE_COMPARE, system can compare the current credit values of the database with the simulated values there by you can get an idea if the actual values and the values of data base. Executing RVKRED77 will reorganize the credit and can probably fix the issue.
Hi Rajesh,
System evaluates dynamic credit check based on the below formula.
customer's credit limit- (All open orders value whose delivery date is within time horizon + open deliveries + open bills + Accounts receivables).
If this value is greater than or equal to the current document value system passes the document for credit. The time horizon is the beauty of dynamic credit check. For example I have created an order today (i.e. 11/04/2012 ) and If the delivery date is 20/06/2012 and time horizon is 1 month; then system while performing dynamic credit check will initially check if the delivery date of the order is within time horizon i.e. one month. If yes then system will evaluate dynamic credit check based on the above formula if no (as in current case) then system will not perform credit check at all and pass the document for dynamic credit check. If we take month as the period it will take into consideration the end of month, if we take week then system will consider end of the week this is how standard SAP behaves.
If you keep the number of months/days as blank, or you have horizon 0, the horizon end data is the end of the actual month or week.
Horizon 0 does NOT mean that you work without horizon! to have such thing you have to enter horizon '999' . Then system will consider all open orders while evaluating the credit check and will not be considering horizon. Then it will be as good as static credit check.
Dear Rajesh,
Check whether RISK CATEGORY is maintained for the customer in FD32.
(hoping these 2 customers are using the same sale document type as used by other customer codes)
Check and revert back.
Thanks & Regards,
Hegal K Charles
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Rajesh,
Whats the Item Category which is coming for the new customers in sales order?
check in VOV7 , whether the item category is active for credit.Also check whether the pricing procedure which comes in sales order have a subtotal A assigned as mentioned by sesharao mattupalli
Check and revert back.
Thanks & Regards,
Hegal K Charles
Hi Rajesh,
Please check weather you have maintained credit master (FD32) for those two customers, and check pricing procedure for those two customers in sales order and check weather subtotal A has maintained for those two customers,
Thanks
seshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.