on 2024 Feb 13 5:39 AM
I use me51n to create Preq & post release, raise a PO via me21n.
Currently, when a change is made in Preq using me52n, after its subsequent release, the changes are made in the same PO using change Po me22n transaction rather than creating a new PO for the changes in the PReq. This has been impacting the commitment costs against the Preq which ideally should be 0 given that the PO has been amended to accommodate the changes but the system is not syncing between the two and ends up showing some commitment cost values.
I would run the RKANBU01 prog to correct this issue for existing projects but going forward is there a way to ensure all the changes made in a Pr can be captured against same PO rather than creating new and having no issues on the reporting aspect of it ?
regards
Jr
Request clarification before answering.
Any Config settings to be looked into?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
116 | |
7 | |
6 | |
3 | |
3 | |
3 | |
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.