cancel
Showing results for 
Search instead for 
Did you mean: 

PR release procedure no longer working-error MEPO 822

Former Member
0 Kudos

I've raised a message previously regarding PR release problem. Now i've found something that need expert helps to clarify on this.

Situation :

One of my client(ABC) implemented release procedure for PR which is not assign to value limit. It is by document type. They had 2 document types; NB and RNB.

NB = NOT subject to release

RNB = SUBJECT to release.

So when they :

create a PR with document type RNB - it will goes for approval.

create a PR with document type NB - it will not go to approval.

It was working fine until after they created a new document type which copied from NB, called ZTP.

ZTP = NOT subject to release.

They did not touch anything on PR release configuration. However, the release has no longer working. Means, when they create PR with document type RNB, it will NOT go for approval as it suppose to. I've check in configuration, all are fine.

Findings:

I've created a PR, and go to ME45N to release it but system prompt me an error message

"Purchase requisition 10000066 cannot be released". I check on the message data, the error coming from MEPO, message number 822.

So i check in OSS and found a note which is similar to this case.

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

Link : https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=939371#Text

But my question is,is it also applied to ME51N and without external application as per my client's case?

Please anyone help.

Thanks.

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi guys!

Wants to share something. I had a problem to release my PR. When i want to release PR via ME54N, system give me error message "Purchase requisition 10000066 cannot be released". When i checked message data, it is coming from MEPO Messafe 822. So i asked SAP, they said this one is caused by different issue. Here's the reply from SAP.

Here's the reply from SAP :

Purchase requisition 10000066 cannot be released

Message no. MEPO822

Now click the other requisition button and let say

choose Purchase requisition 10000068,

Execute ME54N again:

Purchase requisition 10000068 cannot be released

Message no. MEPO822

Comment/explanation:

The log incidence seems not having problem with release

strategy as it was ok but it was the last PR was called

everytime ME54N was called. This same as it works in enjoy

transaction ME21N/ME22N or ME51N/ME52N.

For example, When using ME21n or ME22n to create or change PO,

after saving the PO. There are 2 ways to exit the transaction,

1, enter another T-code or use /n to exit directly.

2, use 'F3' or the 'green tick' to exit ME21n (or ME22n)

Then you can access ME23n to see the difference.

For the 1st way, ME23n won't display the last PO created in ME21n

For the 2nd way, ME23n will display the last PO just created!!!

Please see attached consulting note 595627 that explains a new

functionality as of release 470:

Due to performance problem, a decision had to be taken about the way to

use transactions. If you leave transaction ME21N/ME22N via the

exit button (F3), the expected PO will be displayed next time you use

these transactions. But if you quit abruptly (/nXXX) the PO number

won't be saved for the next transaction ME2?N.

As SAP note is the official document to explain system behavior,

this document is provided by SAP developement to explain this system

behavior to customers.

In your case, you had used ME54N and this was same as you use ME53N.

The last PO always display. You may try to view Purchase requisition

with release strategy, for example Release group R1, Rel. strategy

R1, then after this execute transaction ME54N again, the message

MEPO822 will not be there anymore.

Hope this will help you guys if you're having the same problem in future.

Thanks,

Crystal.

Former Member
0 Kudos

Hi Guys!

Ok i will share the solution with you and perhaps it will helps you as well in future

My PR release strategy is not working even there's nothing wrong with the configuration. When i discuss with SAP, here is the reason why it was not working.

My PR release strategy does not getting determine for any PR which created with RNB because of a project called ZETMEXIT. I can check this using tcode CMOD. This project is active.

Under this project, there are few user exits which one of them is EXIT_SAPLEBND_004. To see this, click on Components button.

When I check this user exit, it contains no functional code but there is one include program name called ZXM06U31. So i double click on ZXM06U31.

No code at all.

So now what i can do is, either deactivate this user exit and my PR release strategy will be working fine or if still need this user exit to be active, then enhance this user exit so that it will cater the release procedure for PR.

Happy to share with you guys!

Thanks,

Crystal.

Edited by: crystal142 on Jun 15, 2009 5:45 AM

Former Member
0 Kudos

spoke to SAP and got the solution.

Thanks everyone!

dipak_kumar3
Active Contributor
0 Kudos

Hi,

Please share the solution, if it has helped you.

Thanks

Dipak

Former Member
0 Kudos

I've checked in me53n under status tab, status is active,not block and processing status is not edited. I don't think there's anything wrong with the release configuration or setting. It's just that its processing because when i go to ME54N, system prompt me error from MEPO message 822, pr cannot be released. when i check in OSS notes, it says that :

*************************************************************************************************************************

Summary

Symptom

It is possible to have purchase requisitions, created from external applications, where items have wrong BANPR values(Requisition Processing State). Such requisitions cannot be released using ME54N and you get the error MEPO 822.

Other terms

MEPO 822, BANPR, Version management, overall release, LOEKZ, Requisition Processing State.

Reason and Prerequisites

It happens because of program error. In such case, the values of BANPR were not handled correctly.

Solution

Before implementing the correction in this note, please enhance the Function Module MEDI_REQ_RELEASE in the following way:

1. TCode SE37.

2. Enter MEDI_REQ_RELEASE. Choose 'Change'.

3. Select Import tab. Add the entry -

Parameter Name - IM_OV_REJECTED

Type spec. - TYPE

Associated Type - MMPUR_BOOL

Default Value - MMPUR_NO

Optional - <checked>

Short Text - Insgesamt Abgelehnt

4. Activate it.

Now please implement this note.

************************************************************************************************************************

But my question is,

is it also applied to ME51N and without external application as per my client's case?

Thanks.

Crystal.

Former Member
0 Kudos

Hi Crystal ,

I think this need to be checked with SAP .

Raise a message to SAP to get it clarified.

I think you were creating PR manually .

Regards

Ramesh Ch

Former Member
0 Kudos

Hi ,

Creation of new document type will not have any impact on the newly created Purchase Requsitions.

1.At check check the release strategies for any errors in customising.

2. Goto Transaction ME53n .Just check the status in Item details Status Tab .

As per the note given it may have wrong value .

Regards

Ramesh Ch