Can "Approver" creates PO without the need to release?

[Former Member]

Dear Experts,

I've setup 2 Release Strategies for 2 level of users (approver) - one to release PO below $5K and the other one is to release PO equal to $5K and above.

Can I setup in such a way that one user(approver) to be able to create his/her PO without the need to release since he/she is the highest ranked of Approver?

regards,

Abraham

[BijayKumarBarik · Accepted solution]

Hi,

As you said, it should not be like that. If you are practicing you can design as your wish but when you are running your or company business in SAP, then you have to follow certain process and procedure.

OK, you can design PO release for PO value below or equal to $5K and the other one of PO value more then/ above $5K.

Do not design release process of PO as you explained. PO releaser always a PO releaser only and he should not create any PO. Also PO creator always used to create PO and PO creator should not release PO, but if authorization given he can change PO.

You can easily restrict and control PO release process by having well designed user authorization matrix and release matrix. As per release u201CVALUESu201D, release matrix designed and based on authorization, control can be established for transaction codes for users.

Lets example: User 1 will create PO, user 2 will release PO of PO value below or equal to $5K and user 3 release PO of PO value more then/ above $5K.Now you can allow (authorized to) user to do following transaction.

Transaction Code----

---

> User

ME21N----

---

> user 1

ME23N -

---

>(All users ie..user1.user2 & user3)

ME29N or ME28 with release code( <=5000USD)----

---

> user2

ME29N or ME28 with release code(>5000USD)----

---

> user3

NOTE:

For more details contact basis team and control all these users by authorization object.

Regards,

Biju K

[Former Member]

thanks.

[JL23]

It is possible to create such kind of release strategy, but it is certainly not good practise.

you would either need to add the Creator of a PO as a characteristic for your classification used in PO approval, or you make use of the user exit and decide there whether the PO becomes subject to approval or not if the creator is XXXX.

[Former Member]

Hi,

You can have a work around. Create new document type for the approver and restrict authorization for that document for that user only so that others cannot create PO using that document type. Do not use this document type in your release strategy.

Kiran

[Former Member]

Thanks Guys for your valuable replies.

I've tested with Kiran's idea of work around by using different document type for PO and restrict that for that user only, and it works.

regards,

Abraham

[Former Member]

This is not possible. You can only restrict by value or document type etc but not by user.

[kailas_ugale]

Hi,

Po approval and Po creation are two different things.

When Po is created by Approval by his ID in ME21N ,Po release tab will come in Header .Then he has to release by ME29N.

without release he cannot create PO,need to release it

Regards

Kailas Ugale

[ajitkumar]

i don't think it is possible in the standard system. if the creator is the approver, he / she has to login to the approval transaction and approve the document.