on 05-16-2016 8:12 PM
Hi MM experts,
We are facing a situation on production that I hope someone here has faced before and may could share solution with us:
Sometimes when a user runs MRBR to release invoices, the Payment Term is been changed from the value set in master data to a new aleatory number.
This is the change log after MRBR:
The change from 30 to 38 happened after MRBR
We need to figure out what is triggering this.
30 days is the correct payment term in master data.
38 days is wrong, the system don't even have this condition set in MD.
So after identify the error, the user needs to adjust it manually again.
Does anyone have faced a similar situation? or have any idea what we need to check to find this root cause?
Thanks and regards,
Rennes M
It is not the nature of transaction MRBR to change such fields, the purpose of MRBR is to release invoices from a block.
I would suggest to use transaction ANST (or ANST_SEARCH_TOOL) to investigate if there is custom coding which causes such effects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
104 | |
12 | |
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.