Skip to Content

PO release code change in the release strategy

Hi,

I hope somebody can enligthen me with this issue of mine.

One of our previous PO releasers resigned so we have replaced him with another one in our PO release strategy setup. What we did is create a new release code (the old release code was not deleted). We then assigned this new release code as replacement to the code of the person who resigned. The result seems fine, we are able to release new PO using the new releaser code.

The problem is if we open an old PO released by the previous releaser, SAP displays that the PO was released by the new releaser. Can anyone explain if this is the standard behaviour of SAP given what we have setup? I don't think it is right to see old PO under the new releaser when they were actually released by a different person.

Thanks in advance for your help.

Aloy

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Nov 13, 2009 at 04:42 AM

    Dear,

    The problem is if we open an old PO released by the previous releaser,

    SAP displays that the PO was released by the new releaser.

    This is the standard Behaviour of SAP. Reason behind this is, when ever you are opening previous PO which was released by the previous releaser, system will check the release startegy and release codes...

    Now you have deleted your previous releaser code and entered new release Code ID, so system will check in the tables and find the current releaser ID and displays it.

    I don't think it is right to see old PO under the new releaser when they were actually released by a different person

    This is standard SAP behaviour.

    Hope this makes your doubt more clear.

    Regards

    Utsav

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 13, 2009 at 04:45 AM

    Hi,

    Release codes and strategies do not have validity date information and hence teh behaviour.

    Normally, the new person is given the authorization of the existing code instead of creating a new one and changing the strategy.

    depending upon complaince issues, new release strategies may also be created in such scenarios.

    Hoep this helps.

    Regards

    Sai

    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.