MM - PO was created from a PR that didn't have Release Strategy

[aeramirez]

Hi,

We were reviewing our PO process and found that we are able to create PO from a PR that didn't have Release Strategy.

Currently we have defined RelStrategy for most of our scenarios, if an scenario is not defined, we would review it first and disable the option to create a PO from that PR.

Since the PR doesn't have a RelStrategy, it doesn't follow the Release status, so I can't block it from there.

Is there any standard message or way to control this option?

[Prasoon]

Hi,

You may check the below options:

• Find all PR's without release strategy using the processing status 02 in ME5A and trigger the release strategy with any release characteristics change.
• Find the old PR's without release strategy and either block it or delete it and re-create new.

Regards,

[robin_mcrae2]

A few quick ideas come to mind.

Cast a wider net with your release strategy. Although it may be normal to have some documents not subject to release, but if this is not your case, make your release strat as general as possible.

Second - check in SE91 for ME errors with the word release.. you may be surprised to find something useful there. I'm not sure what message 493 can do for you. Set it as a warning a have a looksee. Won't hurt.

If a standard error does not exist… (I don't remember one for a PR without release) add a little check in the PO document (ABAP magic) to fit your specific scenario with a custom error message.

Good luck,

Robin.

[pataselano]

If PR have no release strategy then PR can adopt to PO. This is SAP behavior, no standard message for control this option.

So, you must create enhancement in BAdI ME_PROCESS_PO_CUST method PROCESS_ITEM. In this BAdI, you can get PR number and check to table EBAN. If EBAN-FRGST is initial then you generate error message.

[aeramirez]

I understand that, but will be possible perhaps to maintain an error message that shows an error if the PR doesn't have RelStrategie?

This error wouldn't let the PR to be saved and having a similar effect, right?

[pataselano]

For blocked PR, you can make validation using BAdI ME_PROCESS_REQ_CUST. So, user can't save PR in case no release strategy.

More better if you improve your team work. You can create check list. If any change of PR type, user, etc for PR, don't forget for update your release strategy. It is so late if you are waiting feedback from users because they can't create PR because mistake by your SAP team.