Hi All, I have a question pertaining to PR & PO commitments cost reporting via Cji5.

[JayGR]

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

[Ken_Melching]

What step by step procedure are you following to make the changes, are you using ME52N then using ME22N to make the same changes or are you using the PR to make the changes in the PO? A simpler proicedure would be to just make the changes in the PO directly and not bother with the PR.

[JayGR]

@Ken_Melchingthats correct, me51n/52n for preq and me21n/22n for Po.

I use me52n first to amend the PReq and once the Preq is approved the changes are made in the PO via me22n. Please note it's a service PO with two-line items. The changes cannot be made directly in the PO due to the approval process in place.

With ref to the above image, the transaction value against Service Preq needs to be 0 as the service PO value is equivalent to the amended pr. I tried running the program RKANBU01 but no luck with the correction and issue with cji5 report still persists. 

[JayGR]

Any Config settings to be looked into?

[Ken_Melching]

I added the MM Purchasing Tag. I believe your issues is related to the fact that you have manually changed both Purchasing documents and the PR changes have not been processed.