CN41 commitment exists even after PR/PO deletion

[Former Member]

Hi Guys

We have scenario as follow

1- Create a PR and coverted to PO with A as account assignment (WBS is assigned in the asset)

2- Above created PR and the PO lines are deleted as the next level

3- New PR has been created with the same WBS and the PO in the point 1 is used to convert this PR as well. MIGO and MIRO is done for this PO and the cycle got completed

4- Again a New PR is created with the same WBS and deleted at PR level itself

Now when we run CN41 the actual value is proper(this has been taken from MIGO and from MIRO for unplanned delivery costs)

But when we come to the commitement, this still has value but which should not have any value

The reason being only one of the PR and PO line is open and for which MIGO and MIRO has been done

2 other PR lines are deleted and the PO first line related to the first PR has also been deleted

Based on the forum and other docs, i have ran various program like RKANBU01, RKACOR04, RKACOR10 etc...and including CJEN transaction. But CN41 still has value in the commitment column, which ideally in our case it should not have any value

Thanks in advance guys

Bala

[Former Member]

Dears...

Note that PO Commitment gets closed in case of unplanned delivery costs posted by MIRO only after flagging the "Final Invoice" indicator at the item level of PO and PR commitment gets closed by flagging the "Closed" indicator at the item level of PR.

Re-run the commitment line items report to check if the commitment is nullified....

Hope this helps....

Regards

Kaashif M

[Former Member]

Did you check the CJI5 report and see whether the commitment is being shown there for the object in question?

You can also check the table COOI to see whether the commitment is being shown there. Ideally, the programs that you ran should have corrected your commitment values. I would suggest you to check the process you are following once again and see if you are doing it correctly.

If nothing helps please raise this with SAP.

[Former Member]

hi

first deactivate the availabilty control - CJBW

regenerate the info database CJEN

activate the availability control. - CJBV