cancel
Showing results for 
Search instead for 
Did you mean: 

Po release

Former Member
0 Kudos

HI,

My client have an issue;

If a Po value is less than 1000 it will approve by a approver A and B. there is no workflow scenario. Normally they will go to ME28 transaction code and they will approve.

Even if one guy approve the Po will rellease.

Now the user asking that the PO will not be able to see in mmE28 for approver B. So the now Approver A approved.

Where to check whehter the PO is available in ME28 for the approver B before release

pls advice

Accepted Solutions (1)

Accepted Solutions (1)

JL23
Active Contributor
0 Kudos

go into the PO itself and open the release strategy tab at header level, here you should see which strategy code is still to be executed.

Answers (3)

Answers (3)

BijayKumarBarik
Active Contributor
0 Kudos

Hi,

In t.code: ME28 ,you can view the list of POs which are pending for release and can view the necessary release code for a PO in t.code:ME23N.

But in your case two users / approver A and B( may be both R working back to back or one person should be always available to release PO at any point of time), need to relaese the PO of value is less than 1000.So better ask Basis Consultant to give authorisation to two users / approver A and B for the release code of value less than 1000.

Regards,

Biju K

former_member197616
Active Contributor
0 Kudos

Hi,

In the same ME28 you can list the POs which are ready for release for that release code.If you are working with 4.7 onwards you can release the PO in the ME22N screen itself.At the same time you can check the release in the ME23N screeen of the release tab.

Regards,

Former Member
0 Kudos

In SPRO>MM>Purchasing>Purchase Order>Release Procedure for POs,

when you get into your release strategy using A and B codes,

use a Release Prerequisite (there is a button on that screen with classification and simulation buttons)

...A B

A

B X

Make above shown tick. Now B can release only after A has released.

NOTE: this restriction will only work if different user ids are assigned to A and B in workflow part under release strategy setting.