MEPO822 Error when unreleasing through ME54N

[former_member685544]

I am trying to unrelease a PR through ME54N but I am getting this error MEPO822.

This PR cannot be released. This PR was created through external application.

This was a good link I came across:

http://scn.sap.com/thread/1370272

EXIT_SAPLEBND_004 is not maintained.

Note 939371 - Overall release PR using ME54N gives error MEPO 822 is already maintained

still this error exists.

What should I do more to get rid of this error?

[Former Member · Accepted solution]

Hi,

Do you have authorization to this transaction ME54N? Did you check your SU53?

/Manoj

[former_member685544 · Accepted solution]

Definitely I have access to transaction ME54N and when I unrelease through this transaction I am getting this error and yes SU53 is also coming up with all authorized. No issues in SU53.

I found another thread with JURGEN answer as correct, but I dont understand how to implement this answer or get it checked. I have checked my release strategy, its working correctly.

http://scn.sap.com/thread/2117611

"the where-used list for message MEPO822

gives me following objects:

L2014I02                         CLASS lcl_bapi_header IMPLEMENTATION

L2105I02                         CLASS lcl_bapi_header IMPLEMENTATION

going into the detail, this message is triggered in the METHOD check_authority.

Is everything green when you execute the check transaction for release strategies?: QMGQCK"

[JL23 · Accepted solution]

first you should execute transaction OMGQCK

if all traffic lights are green, then your release strategy is okay and should not make any problems.

This in general the last task when you setup strategies. with red traffic lights you certainly have a problem and your strategy does not work as expected.

Now to MEPO822:

SE91 is the transaction to define/display messages like MEPO822

there is a button for Where-used

if you click this, then SAP shows you in whic programs the error is triggered.

I had found only the 2 objects mentioned. 

A friendly ABAPer can help you reading the source code, if you cant read it yourself.

I found out that the error message is triggered in a section that deals with authority.

These objects have BAPI in the name, which means that is an enhancement, either from SAP or defined by your own company to make additional checks

So there is probably something activated in your system that causes your trouble.

we do not know your release, but MEPO822 appeared often after activating version management.

see for example OSS Note 887716 - ME54N: Purchase
requisition cannot be released

maybe this note can already help, maybe others, there are more notes if you search with MEPO822 as keyword

[former_member685544 · Accepted solution]

Jurgen,

Thanks again for the pointers, I checked all the above settings mentioned by you. They were already maintained correctly.

There is no version management involved as well. Then I did further research on SAP NOTES and found this note helpful:

Note 620175 - ME54N: Overall release not possible (MEPO822)

Solution

Implement the attached source code corrections.
If you have already created purchase requisitions prior to the corrections, as described above, try to release these using Transaction ME54.
If this is not possible, please contact SAP Support.

Through this line, I guessed what goes of trying ME54 before implementing this NOTE, so I tried

unreleasing my PR through ME54 and it worked, my PR is released now, so no need to implement this NOTE.