on 07-11-2012 8:04 AM
Hello,
We have POs (doc.type NB) for which different release strategies have been set up.
Due to some business reason, buyer is cancelling the POs after the release is initiated.
(The flags set are delivery completed indicator, final invoice & deletion flag for PO item)
But, these deleted POs are still showing in the ME28 list for release.
This is causing quite a lot of confusion because the persons in the approving hierarchy are not aware of this deletion and are thinking they have to be released.
And the buyer has to inform them to ignore such POs. (Quite often, the approving persons happen to be senior management people)
The worst part is that system allows the concerned approvers to release the deleted POs with their release code.
Is this standard SAP behaviour?
Can something be done to prevent the deleted POs from showing in ME28 list?
On the other hand, is deleting a PO item after release has started, an acceptable business practice?
Should the buyer be advised not to do so? What is the correct business practice?
Regards
Prabhu
hi ,
Release strategy is at header level in PO and you are marking deletion at item level , don't you think it is still logical to have PO in release if one or 2 line items are marked for deletion. It is not possible for sap to consider PO deleted at header even if all line items are deleted. so yes this is standard functionality.
To avoid above scenario , we generally keep Gross PO amount as characteristic in release strategy and we consider release for amount greater then zero. So in case all items are delete , gross value of PO becomes zero and hence system does not determine a release strategy for it.
Alternatively ,I have seen deletion flag in header table EKKO and it can be updated in MASS processing. I don't think you can set deletion at PO header via ME21N , you could explore it and check if that serves your purpose
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Workaround found & problem resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The workaround is little funny but it works..
First undelete the PO item, reduce the PO item amount to a very low value, say Rs.100 for eg., and save. By doing so, the old release is cancelled and a new one is assigned to the PO. Then, reinstate the PO item's original amount and save. Then, mark the items for deletion. This will put the correct Release strategy for the PO, that is inline with the total PO amount.
Cheers.
Prabhu
Hello Guys,
We had the same problem this week. We found the users had also set the "Delivery complete Indicator" and/or "final Invoice" flag as well as deleting the PO line. So we undeleted the PO line, removed the flags and redeleted the PO line. The EKPO-STAPO flag was then set and the PO no longer appeared in ME28.
Ben
Hi Ben,
You are right.
What you explained was the 2nd alternative that I stumbled upon - resetting the delivery completed and final invoice indicators for the PO item - and this option works too.
I feel this option is a better one than playing with the PO amount.
But, will unmarking these indicators have any adverse impact on archiving of POs later on?
Regards
Prabhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
103 | |
12 | |
11 | |
6 | |
5 | |
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.