on 08-22-2018 1:10 PM
Hello
I am facing a scenario where PO is created on 20.05.2010 without release strategy set.That time release strategy was not set and it is set in July 2018.
Recently user complained that one of the user checked print preview of that old PO and release is trigerred in PO.He did not save PO or done anything to trigger release.
I have checked changed document but there is really no change log updated with any changes that leads to PO release strategy.
Can you please help me out in this case as why PO is set to release strategy though there is no change log about any change.
SAP always writes changes log for purchase order whenever some changes are happened from standard transaction code. Only possible way where changes logs are not written that is any custom program. If a custom program make change anything in purchase order (by doing a hard table EKKO/EKPO update), then changes logs are not written.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please check the release indicator table (T16FB) setting along with release id and the changeable parameter (whether it is 5 or 6).
regards,
Bala
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You have specified that your user "checked the PO and done the print-preview", because of that, PO release got re-triggered. You can simulate the same in your test system (QA) by creating a new PO and confirm whether above is true. Otherwise it is very difficult to identify reason.
As Dibyendu suggested, check with any custom code/BADI is written on these objects. Release Indicator - changable parameter 6 is the appropriate (which is usually used for the last level of approval stage).
regards,
Bala
User | Count |
---|---|
105 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
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.