Skip to Content
author's profile photo Former Member
Former Member

Release Procedure for PO

Hi Experts,

I have two users for releasing PO.

When I release a PO using tcode me29n for user1 and saving the scenario.

Once I come back again into tcode me29n ( using F3 ) with same user, I able to change i.e. , I can cancel the PO.

I want, if PO is released from user1, he cannot able to change or cancel the PO.

Please explain me the process to over this problem.

Regards,

Nani.

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 29, 2009 at 01:26 PM

    Hi,

    As USER1 is having authorization to release the PO, he will always be able to change or cancel the PO.

    Rgds,

    Manish

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 29, 2009 at 01:53 PM

    Manish's correct..moreover, You should not do that even if you were capable to do so for good reasons.. You could always use the change log to monitor changes as such to advise users not to do so and since you are authorizing them for an appropriate action.. it is usually up to them.. you culd always ask the mto put a note in the header text..before cancelling it.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 29, 2009 at 05:31 PM

    Only complementing Pavan's answer - after changing the Release Indicator, Changeability parameter = 1, you will need to assign the release indicator to yours Release Strategies on button Release Statuses. Then, once approved the PO won't be modified ( any field ).

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 11, 2009 at 12:51 PM

    Hi,

    1. In IMG You need to define different release codes for user1, user2, user3

    2. In IMG you need to define Release Prerequisites in Release Strategy i.e. If user1 doesn't release user2 cannot release & user2 doesn't release user3 cannot release

    3. In IMG Set the release indicator to 1

    4. In Authorization to be done by basis you need to assign respective release codes in object M_EINK_FRG.

    With the above points are followed, user2 cannot release until user1 releases & once released he cannot make changes.

    Hope it clears your doubt & problem.

    Naidu.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 25, 2009 at 04:41 AM

    sloved

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.