on 05-04-2011 9:34 AM
Hello,
I understand that there are three credit sensitive fields:
Terms of payment
Fixed value dates
Additional value days
We have created a customized field in the Additional Data B in the sales order header. User made a change in this field and it triggered the automatic credit check and the order is put on credit hold.
In our OVA8, the 'Critical fields' is not checked.
Strange thing is when we tested in the test/QA environment, the change in the customized field did not trigger the credit check. It happened only in production.
To me, only fields like ordered qty, pricing condition should trigger the check because the net value of the order is changed and the order should be subject to a credit revision.
Any idea? Would appreciate your input. Thanks in advance.
Dear Friend
I think the document in which user has made changes was already released for credit using VKM3/VKM1.
As per standard system if the you make any changes in the document after the date of released date then system triggers credit check again.
For Ex. If you release document today 04.05.2011 then you can make any changes in the document till todays date EXCEPT increase of order value than released value(if order value increases than released value then system triggers credit check again even on same day).
But if you release on 04.05.2011 and make any small change in document on 05.05.2011(If you are not maintaining Number of Days in OVA8) then system will trigger credit check again.
This is the reason when you tested in quality system didnt blocked the document cause you were trying to change on same day.
Hope this explains your issue.
Regards
Mayank
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Mayank.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
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.