on 08-24-2018 2:06 PM
When we create an SD order and the value exceeds the stored credit limit, we release the order anyway (via VKM3). So that's fine and no problem. However if anybody needs to do any change in the order (e. g. text or delivery date ....) afterwards, the order runs again into the credit limit check (and is blocked).The disaster is, that after the re-release the delivery date is determined new.
I'm wondering why the system does an new credit check if only minor fields are changed (like text or delivery date ...). I understand that a new credit check is necessary if the value or the payer has been changed, but not for other changes. Also why is it necessary to determine a new delivery date?
1.if change net value,payment terms then only system should block the credit again, not for the HEADER TEXT,PO date.
2.If system again go for a credit check,need not to delete schedule lines.
Do you have an idea what could be done to improve this process? Unfortunately this occurs very often.
Hi,
check if any critical fields(NO IMPACT) is marked or any User1,2,3 fields are marked in OVA8
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
check oss note 718260 you´´ find a nice explanation on when released documents are credit checked again.
Regards
JM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.