Release strategy: User should release only with his highest release code

Hello,
Because of personel absences we want to configure the release strategy so that:
User A or user B releases in the normal case the first level of a PO (with release code 01).
User C (Manager) releases after release code 01 with release code 02.
User A is deputy of user C. In this case user B will release with code 01 and user A will release with code 02.
Because user A can use depending of the case release code 01 or 02 (C deputy) it must be avoided that user B sets release code 01 and 02 for the same purchase order.
Do you know about a solution for this issue
Br
Manuel

Dear W1N,
But the systems knows that A released with code 01 and when A tries to release  with code 02 the system knows that the same person of release code 01 is trying with release code 02.
<b>The aim is to avoid the second release from the same person and not to automate the release strategy.</b>
In such a case A has to cancel the release for code 01 (ME28) and wait until B is reachable to do the release of code 01.
When C is absent A knows that his task is to release code 02.
Is this check really not possible?
Best regards
Manuel

Similar Messages

  • PO Release strategy User Exit  if value is Reduced

    Hi,
    I need to write a user exit to trigger the release strategy in Purchase order even if the value is "Reduced".
    As you may be knowing releases will only be triggered if the value is increased according to standard SAP functionality.
    So to trigger the release stratgey even if the value of PO is reduced some one suggested me user exit "M06E0004" Program :ZXM06U22.I guess we need to define a new characteristic called "URSC1".But cannot make out how really i can achieve this.
    Can any one please guide,if you have worked on it earlier.
    Thanks.

    Gentlemen,
    Any Ideas....!!!

  • In release strategy unrelease should happen from higher level

    Dear Users,
    In our release strategy we want to make changes like whenever user want to unrelease it should happen from higher hierarchy to bottom level as vice versa of release process. If there is any solution for this process please provide your suggestions.
    Thanks,
    Manoj

    Hi,
    For restriction from higher hierarchy to bottom level, refer similar blog
    Release Strategy: Restrict lower users to revoke PO after the complete release by superior
    Regards,
    Biju K

  • PO release strategy user exit

    Hi Experts,
    This is regarding the PO Release strategy.
    I have implemented user exit u2018EXIT_SAPLEBND_002u2019 for filling User defined field i_cekko-usrc1 based on PO line item net values for PO release strategy.
    Our function consultant defined characteristic on this field and created at the release strategy.
    My code in the user exit:
    i_cekko-usrc1 = 'X'.
    e_cekko = i_cekko.
    It is triggering the user exit and setting the  USRC1 to u2018Xu2019. But it is not triggering the release strategy.
    Do I need fill any additional fields?
    Thank you for your help in advance.
    Regards,
    Soujanya

    Gentlemen,
    Any Ideas....!!!

  • Why CUA (Release 7.00) is Not Working with Old Clients(Release 4.6C, 4.5B)?

    Hi all,
    We have CUA (release 7.00) that is not working with older release clients. I implemented 2 release 7.00 clients to CUA; they both work fine. However, when I implement some older release clients (like, 4.5B, 4.6C, 6.20 and 6.40) to CUA,  I can only create ID and pull out to client, but roles do not go through.
    It is kind of argent.
    Do anyone know how to fix it????
    Thank you for reading this.

    > It is kind of argent.
    I think you meant "ardent"...
    THe word u r g e n t is blocked by our content filters, because a while back everything was like that and these forums are actually discussion forums...
    Anyway, sounds like faulty config or perhaps a problem with logical system assignment.
    Have you checked that? Also check in SCUL?
    That you can create users but not assign roles might also be that in the lower release systems they are checking activity 22 (assighn) AND 02 (change) to assign the role. Doesn't make sense, really....
    Check the drop down menu in table PRGN_CUST for the option to change this, and compare whether the settings are different.
    Cheers,
    Julius
    Edited by: Julius Bussche on Jul 30, 2009 11:34 PM

  • How to give access to user when he login with his credentials to create his own virtual machine

    Dear Experts ,
    In scvmm ..how we can allow an user to create his own VM with out providing him administrator rights...
    I am able to create machines with user accounts when I give Administrator rights only..and if i remove Administrator rights..i am gettting a message for user-"you cannot access the private cloud", where as If i give administrator rights to that
    same user , I can able to access private cloud and template for the user.
    Please suggest me and help with any useful link.
    Regards
    N.V.Srinivas ,
    [email protected]

    Self-Service user delegation
    SCVMM 2008 - 2008 R2:
    http://technet.microsoft.com/en-us/library/dd548291.aspx
    SCVMM 2012 - 2012 R2:
    http://technet.microsoft.com/en-us/library/gg696971.aspx
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

  • Current day and prior day prompts..BUt user should select only one prompt

    there is table in my universe ..mi.dim_date...... the columns/objects are ....ID_date ,Date,Datetime,month,quarter,yeID_date column type is
    Number,Date column type is Date.
    here i want to apply a prompts on Date column, and that prompt,when user select specific date,the prompt should display yesterday data and todays data.
    example..user selects 20140915......prompt should display 20140915 data and 20141409 data..
    i have written a prompt like as follows ..... select mi.dim_date.date where mi.dim_date.date between @prompt('select date','D',mi.dim_date.date,mono,free,not_persistent,user:-1) AND @prompt('select date','D',mi.dim_date.date',mono,free,not_persistent,user:-1)-1
    but i am getting errors like 7 th parametr is wrong...cannot convert data type,...invalid expression type...database staements could not be prepared.

    Hi vbattu,
    According to your description, you want to select some records in the report when export it to Excel. To achieve the goal, we can add a parameter to filter certain rows by following steps:
    Add an additional Multi-value parameter to the report.
    Set the Available Values and Default Values are all got from a field which can be used to select the records in the current dataset.
    Add a Filter based on the new parameter in the tablix to filter the rows.
    The parameter does not affect the data when we view the report. While we can use the parameter to select certain rows when we want to export the report to Excel.
    If you have any more questions, please feel free to ask.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Chek budget in PO with release strategy

    Hi
    When i created a PO with a release strategy and the comand need it, the budget are not checking at the save, only when i release the PO.
    Is it possible to check the budget (on a PM order or on WBS element) at the PO save.
    Thank's
    serge

    Normally checks like those happen once the PO is released ( example  - output is not allowed etc)...
    You may need to add something in the PO release strategy user exit to do the check before release (after save), Look into the below to see if this works.
    Name of the Enhancement: - M06E0004
    Name of the function module: - EXIT_SAPLEBND_002
    Hope this helps

  • Release strategy and code authorizations

    Hi,
    We need to create a new release strategy for PO.  After setting strategy, we are assigning existing release codes A1 and A2 to strategy.  The same release code is also used in existing release strategy.
    Now, will this create any authorization issue if we assign same release codes to different strategies, and different users in user roles.
    Thanks
    Alex

    Hi,
    I am confused with your requirement. When you have a business requirement to control the release, may be a new department created or new character value requires for adding to release process.
    Option-1:--- >When you decided to create new release strategy, you should have gone for creating new release codes & design your release process with new release strategy with new release codes. Do not use same release codes, use different release codes for new release strategy which will be easy to control for authorization based on respective users.
    Option-2:--- > When you added a new release characteristic to release class based on requirement, then check assignment of release group to release class ( just make change & TR need to be transported),release strategy design which trigger on how release is to be affected & which manner with a logic. Also check the new value you are entering with your release class, release group & release strategy in Cl20N/CL24N t.codes. Also check during creation of new release characteristic, you have values with correct field name.
    Regards,
    Biju K

  • Release Strategy with Workflow for PR & PO

    Hi Experts,
    I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
    So User should get the information about the releases for PR & PO.
    But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
    Points will be awarded .
    thanks & rgds
    Swamy

    Hi Swamy,
    The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
    How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
    Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
    How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
    How to configure?
    Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
    For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
    For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
    Maintain the details u already have in hand:
    For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO.  After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
    Hope this will give you an idea how the workflow works and how to configure it.
    Rgds.

  • Release Strategy should be effected even if the PO Price is lowered?

    Hi users,
    Another doubt of mine is based on the release strategy (the Purchase order goes for rerelease) only in case of the increase in the PO Order Price (that is if the price is manually increased in a PO or if it indirectly increased by the increase in quantity)
    Requiremnent: the current requirement is the po should go for a rerelease even if there is a decrease in the po price. alternately any change in the PO effecting a rerelease would also be acceptable.
    anticipating an rearly answer.
    thanks and regards
    vinay

    This is standard SAP. Release strategy will be reset only on increase in value.  You have to make the release strategy think that the value has increased (even if it has decreased).
    Please see (the second part of) my comment in
    Re: release strategy is not reset in PO?
    Reproduced here for your ease:
    You can use the release user exit. If the PO is in change mode and Save option is selected, then increase the value in the user exit (This does not increase the PO value actually, just fools the release strategy into thinking that the value has increased).
    Hope this resolves.
    Lakshman

  • Workflow with Release Strategy for PR & PO

    Hi Experts,
    I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
    So User should get the information about the releases for PR & PO.
    But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
    Points will be awarded .
    thanks & rgds
    Swamy

    Swamy,
    There are several posts available for this requirement, I would suggest you to search this forum and you would hit many threads which address this in more details and handy explaination
    check this link for PR
    http://help.sap.com/saphelp_47x200/helpdata/en/04/92768046f311d189470000e829fbbd/content.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/04/9276e846f311d189470000e829fbbd/content.htm
    For PO:
    /thread/743773 [original link is broken]
    Standard workflow template for PR and PO are:
    WS20000075
    WS20000077
    These can be viewed using PFTC/SWDD etc.
    Cheers
    Jai

  • Release strategy with classfication & w/o classfication problem

    Hello guys
    I am facing problem in setting up the release strategy .  ECC 6,0 came up default without classification. we need with classification.  i set up w/o classification, then delete it and then did with classification.. it works fine for me in the Sand Box ,  but in dev server it didn't work for me. It is working only w/o classification , When i am trying to set up with classification , it didn't work for me , i am getting the error message in the check release strategy as follows . How i can find which release group need to create ?
    Any help will be highly appreciated
    Thanks
    N
    Release code  for release group  is inconsistent
    Message no. ME_RELCHK057
    Diagnosis
    The release code  is not allowed because the associated release group  no longer exists.
    Procedure
    1. Recreate release group .
    Note
    The release codes and release strategies for a release group are only displayed if the release group still exists. Therefore you must create release group  in order to delete the release codes and release strategies.
    2. If necessary, delete the release strategies and the release codes for release group .
    3. Then delete release group .

    Hi,
    If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated. The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
    To set up a release procedure with classification, you please delete all entries in the Release codes and Release Groups for Purchasing Requisitions and start a fresh creation of new Release Codes and Release Groups.
    Hope you have followed the following procedure:
    1. Create characteristics and classes
    Note
    If you wish to link your release procedure to workflow, you must perform steps 2 and 3. You make these settings in Customizing for Business Workflow (Basis -> Business Management).
    Otherwise, continue with step 4.
    2. Define organizational plan
    3. Assign standard tasks and activate event-receiver linkage.
    4. Set up release procedure with classification
    a) Create release group
    b) Create release code
    c) Create release indicator
    d) Create release strategy
    Note
    You need only carry out the following step if you wish to link your release procedure to workflow.
    e) Assign release code to a release point
    5. Check release strategies
    Hope, this time you will be able to perform the PR Release with Clasiification.
    Regards,
    Narayana.

  • Why PO is automatically assigned with release strategy?

    I created a PO with PO document type NB and NB is not assigned with any release strategy.
    But the PO with NB type is automatically assigned with release stragety when I save it as a completed PO.  Why?
    And only when the PO is in held status, there is no release strategy assigned to NB PO.
    Is the normal ERP behavior?
    I only assigned a release strategy to PO document type DB, which means dummy document type.

    Please check the release strategy of PO, whether document type NB is assigned to it. May be you are checking the wrong release strategy. Look up the release strategy under CLASSIFICATION button, may be if multiple release strategies are used, your document type is assigned to some other strategy.
    Easier way to check which strategy is getting applied, is in PO release strategy look up rel. strat No. which will come under release group, look up in spro with this release strategy no. in spro which will shorten your search.
    Edited by: Afshad Irani on Jun 3, 2010 1:58 PM

  • PR overall release strategy with acc. assignment category characteristics

    Hi,
    Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
    see below more details :
    I have created the following PR release strategy with classification.
    PR type concerned " NB": overall release
    Rlease group concerned : overall release
    In this release group i have 1 class
    in this class i have 2 characteristics : PR type and Account assignement category.
    Release strategy 1 :
    PR type = NB
    Acc. assignment cat = P, W
    Release strategy 2:
    PR type = NB
    Acc. assignment cat = K, V
    TEST 1 : PR type NB, 1 item with P category
    OK the release strategy 1 is generated
    TEST 2 : PR type NB, 1 item with W category
    OK the release strategy 1 is generated
    TEST 3 : PR type NB, 2 items with P category
    OK the release strategy 1 is generated
    TEST 4 : PR type NB, 2 items with P and W category
    TEST KO, no release strategy is generated
    => what should i do to solve this issue ?
    Thank you in advance for your quick answers,
    Isabelle

    What is the specific requirement for Overall release strategy?
    Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
    Every line item generates a PO, so logically should be set to a release strategy.
    Bottomline is use release strategy at line item level Unless a specific reason exists.
    Regards,
    Sameer

Maybe you are looking for