RELEASE PROCEDURE/ TCODE ME28

[#1]

Hi,

We have upgraded our system from R/3 4.6 c to ECC 6.0 and the UPGRADE is PURELY TECHNICAL i.e new functionalities are not offered and R/3 4.6 c existing functionalities are maintained in ECC 6.0 as it is.

After upgrade ME28 is not displaying suitable purchaisng documents to be released by a user when he is using his release code and release group , though in Release strategy tab of PO it is showing that this document is to be released by the user as other two had alreadyapproved it.

Release strategy is working as for other release code it is coming ( checked in release simulation also) but not for this user who has to approve finally the PO as everytime he is using the code ME28 ' no suitable purchasing documents found' message is coming.

Rewarded if answered .

Regards

Ankur

[Oscar_DC · Accepted solution]

I know the post is old, but I had a very similar problem.

In my case the issue was not authorizations. I looked for errors in my selection screen but I couldn't find any. In my Sandbox environment it worked ok, but when I recreated the configuration DEV it just didn't work ...

I created a ticket with SAP and they basically said not to use ME28 anymore - it is not currently being supported by SAP .

Please read the following note - I ended up just showing my users how to run ME29N using the document overview button, because I couldn't make ME28 work.

https://launchpad.support.sap.com/#/notes/1803189

Thanks!

[Former Member]

have u checked that after the po is released by two release code are u able to do the good reciept

and r u making use of workflow

[Former Member]

Hi Ankur,

Since you mentioned that release strategy is working fine, try to trigger the release strategy for this PO once again. You can do either way:-

a. Go to change mode of PO, make a change in the the quantity, hit ENTER key, change back to the original quantity, THEN only Save the document. Try ME28 again.

b. Otherwise, you can try to re-create the PO by adopting the details again from the PR, but first flag the current PO for deletion first. See if this will help to solve the problem.

I have encountered this problem before, and the first method works.

Rgds.

[Former Member]

please ckeck the the classification in release strategy

[Former Member]

PLEASE CAN ANYBODY HELP ME OUT FOR THIS

[Former Member]

once the po is relased by the 2 codes then r u able to do the good reciept or still the po remains as blocked

[Former Member]

Hi Rahul ,

User want to cancel the releaseof PO but not able to get the list by using tcode ME28 though PO's are there in the system.

ANKUR

[Former Member]

use tcode me2m or me2L to get the list of po

but we are drifting away from your issue

Edited by: Rahul Tyagi on Feb 21, 2008 12:25 PM

[Former Member]

no we are not using the workflow and for some they are able to do the gr

[Former Member]

the po for which you area able to do gr sholud be under the same strtegy and release code ........if yes then i belive problem is with the release indicator assigned to the relase code

there are 2 things in strategy 1 you will not be able to do the gr for po until it is not released and if your are able to do the gr which is released by only 2 codes it means system is geeting the critera to release the po w/o code 3

what i mean to say that u have configured the strategy in such a way that if a po is released by code 1 then code 2 then it the po status changes from block to release hence system is not asking for the release code 3

[Former Member]

if u do not agree with my point of view or any doubt then let me know

[Former Member]

exactly this was the thing that initially came into my mind...I was also thinking like that but then to cross check I simulated the release in release simulation and found it to be working..i e when the third person releases then only po is released and ready for print out., otherwise for two persons when they are releasing it is showing blocked.......

one thing in this organisation....they take the delivery and then create the po which is against the standard SAP practice...what I am trying to say they keep the delivery date for example 15/02/2008 but document date of po is say for ex 20/02/2008.In all the POs it is like that only for which they are complaining

that they are not able to see in ME28

[Former Member]

Rahul

Is it possible that authorisation after upgrade has changed as because for HR module the problem was there ?

Please suggest.

Ankur