Release Code In Release Strategy

Dear Experts,
We have configured the release strategy for PR on Devlopment Client.
1. I have created necessary Characteristics and Classes  on devlopmnt client and configured the startegy and it has been applied succesfully on Dev client.
Now i want to transport the same to the PRD client , should i require the characteristics and Class again in the PRD client, as else can be transported to the PRD client.
2. Also we have user XYZ who is Purchase manager and we have release code R1 in strategy.
How can i map R1 to XYZ, what is the T Code for the same and authorize him to use ME29N for release of PR.
Best Regards,
sap User

Just follow steps:
PFCG
Create a role or change existing Purchasing role
Maintain the authorization profile:
Manually add authorization object MM_E (MM: Purchasing) if doesn't exist, otherwise just change the existing one.
Add sub-object M_EINK_FRG (Release Code and Group) to above mentioned object MM_E
Add Release Code R1, you may also need release group XXX
Generate and Save
Then SU01 assign the role to User Purchase_Mgr.
Hope this helps.
Rgs
JM

Similar Messages

  • Issue in Release strategy for PO while adding intermediate rel code/Strateg

    Hi Experts,
    we have Existing release code 10,20,30,40,50 & 60. Now, we tried to add an intermediate Release Code(say 25)  & release strategy(say R3) in existing release set up for PO.
    And NO pre-requisite is defined ; final release by the last rel code.
    However, the system shows release possible by 30 & 40 for last release strategy also. It`s showing the alternate release as release possible.
    Pls throw some light on resolving the issue....
    Regards,
    Ganesh S....

    Thanks Ajit.
    I mean the release should get afftected only after release 60. (i.e. final approver) That`s the way it`s been working.
    Now, while I tried adding 1 more rel code in between ; it`s afftecting the release with (20+40) instead of the intended 60.
    BR,
    Ganesh

  • Problem in purchase requisition release strategy code

    Hi
    We are facing a problem in purchase requisition, a new release strategy was created and change request transported but when PR is displayed in release strategy chart a same user is showed in different release strategy code.
    Note: new strategy was copied from other.
    Thanks in advance.

    hi,
    As you said tht you have copied the release stategy n created the new one...
    If you do so, you would have copied the class also...to which the release group is attached...
    If this is the case, then system doesn't recognise the new one, and inorder to solve it you have to define the new characteristic and class...then assign this class to the release group and make your release strategy again...
    Once you do this check the release strategy at OMGSCK...and then try at PR...
    You do all settings at :
    SPRO >> IMG>> MM >> Purchasing >> PR >> define release strategy >> W/o classification >> here edit characteristics/class and all other link are provided...
    Regards
    Priyanka.P

  • Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

    Hi Friends,
    I have a issue to fix. The issue is releated to PR.
    There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
    I have to retrigger the release strategy for all the affected PR's.
    The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
    Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
    Regards,
    Manjunath K

    Hi,
    Refer the discussion to triggers release again on release code addition/change in release strategy.
    release code is changed on PR release strategy - old PR can´t be approved
    Regards,
    Biju K

  • Class and release group and code in release strategy??

    hi experts ,
    Can some body explain me..
    I have created Characteristics and Class for for release strategy.
    But while creating release group , i should assign my class with release group , after doing this when i save , its giving error as check the release classes????
    I m using the same class what i have created for my company..
    So how to over come this issue
    Thanks

    Release Prerequisites
    Definition
    The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).
    The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.
    Release Indicator
    Definition
    When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.
    When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).
    What does the release indicator determine?
    Requisitions...
    External purchasing documents....
    Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
    Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
    Whether an RFQ or a PO may be created with reference to the item
    Whether the document may be changed by Purchasing after the start of the release procedure
    Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
    Whether the purchasing document is released for transmission
    Alternative Release
    Definition
    Within the release sequence, you can define alternatives. This means that several employees can effect release (signify approval) at a certain point in the sequence. If just one of these employees has effected release, the next release status is reached. The other employees thus need take no action.
    Five release codes are defined for purchase requisitions in an ascending hierarchy. The requisition item can be converted into either an RFQ or a PO if release has been effected either with the release codes 01, 02, 03 and 04 or - alternatively - with release code 05.
    The box with the information on the release strategy also offers you the possible alternatives for selection (see Displaying Release Information).
    An alternative release cannot be a prerequisite for the next release code. In the above example, the releases with codes 01, 02, 03 and 04 could not be prerequisites for release with 05.
    Release w. Classification (PReqs./Ext. Pur. Docs.)
    Use
    The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle.
    The person responsible processes the requisition or other purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
    This release procedure can be used to approve requisitions and the external purchasing documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
    Purchase requisitions are released either at item level or in total. There is no provision for item-wise release (i.e. partial approval) in the case of the external purchasing documents. The latter can only be released in their entirety.
    If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated.
    Prerequisites
    The release procedure with classification must have been set up in Customizing for Purchasing. In addition, a class with characteristics must have been created for each document (requisition, purchase order, etc.).
    If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
    How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release Procedure for the relevant documents and in Set Up Release Procedure with Classification for purchase requisitions. You will find detailed information on classification in the R/3 Library in the documentation CA Characteristics and CA The Classification System.
    This procedure offers a wide range of possible combinations of release criteria. Should you nevertheless have other requirements, use the enhancement provided by SAP.
    Operation of Release Procedure w. Classification
    The characteristic values from a requisition or external purchasing document are passed on to the classification system.
    The system checks whether the values correspond with release conditions. If so, it assigns a release strategy.
    The persons responsible for the release codes process the document in the sequence defined in the release strategy.

  • 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

  • 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 codes more than 8 in a release strategy

    Hello,
    Is it possible to have more than 8 release codes in a strategy? I have read this is possible via a user-exit.
    However would like to get some direction on how this can be acheived.
    Thanks for your help in advance.
    saurabh

    http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM
    regards

  • PO Release Strategy for 3 company codes

    Hi
    I am working on PO release procedure for 3 company codes in a client.I have created a one charecteristics called Order Type & assigned to class -POVALUE_NEW .I am using the same charecteristics & class in 3 company codes. I have created a different Rel Group & release Codes & assign as shown below 
    Group                       Class
    AA     2     POVALUE_NEW
    AB     2     POVALUE_NEW
    F1     2     POVALUE_NEW
    F2     2     POVALUE_NEW
    V1     2     POVALUE_NEW
    V2     2     POVALUE_NEW
    Group     Rel Code
    AA     L1
    AA     L2
    AB     L1
    AB     L2
    F1     F1
    F2     F2
    V1     A1
    V1     A2
    V2     A1
    V2     A2
    Created a Rel strategy  as below
    Group       Strategy
    AA     P1------Vendor PO
    AB     P2-------STO PO
    F1     F1------Vendor PO
    F2     F2-------STO PO
    V1     V1------Vendor PO
    V2     V2-------STO PO
    I have maintained all the Doc type in value coloum of the cherecteristics .For vendor PO combination of Group & strategy , I have selected the respective Doc types in clasification .*When I raise the PO I am not getting the Release Strategy Tab in PO header* & when I remove the value in clasification any strategy , I will get the Rel Strategy Tab but this will appear in all  company code POs .I want to give different lease codes for each company codes  I am unable to find a solution to this issue . I am looking for a valuable suggesion from you all .
    Thanks
    Venkat

    Hi,
    1.in addition to existing Characteristic, create one more characteristic for Co. Code. Table CEKKO Field: BUKRS
    2. Assign this new char. to your PO Release Class
    3. Define your Release Codes for each Co. Code.
    4. Define Strategies with characteristic values Co. code and Doc. Type.with co. code relevantRelease codes.
    Ex: Co. Code1   Rel Grp-1 G1; Codes: A1, A2, A3
          Co. Code2   Rel Grp-2 G2; Codes: B1, B2, B3
          Co. Code3   Rel Grp-3 G3; Codes: C1, C2, C3
    Strategy-1:
                  G1   S1     A1 A2 A3;   values: CCd-1, Doc. type1
    Strategy-2:
                  G1   S2     A1 A2    ;   values: CCd-1, Doc. type2
    Strategy-3:
                  G1   S3     B1 B2 B3;   values: CCd-2, Doc. type1/Doc Type2
    Strategy-4:
                  G1   S4     B1 B2 ;   values: CCd-2, Doc. type2/Doc Type3
    Like this you can make as many strategies to meet your requirement.

  • Release Strategy @ Company Code Level

    Hi Guys:
    We have a two plants under one compant code, when we issue PO to the vendor it consists quantities that are required for both plants ( Central purchasing org).
    Release strategy for PO is at header level , I.e Total PO Value can we release strategy @ company code Level?
    with Characteristics as Company Code ,PO Document Type and PO Value?
    Thanks
    Sweth

    Hi
    For example if the release strategy set at c.code level all the documents created for several plants belonging to the c.code will affect the release strategy,so that is not the purpose of release strategy,
    The main purpose of release strategy is certain documents created for particular plant or particular purchasing group or more than the value need to be blocked based on your business,so you cant able to set the release at c.code level because thre is no logic.
    The characteristics for release strategy for external purchasing documents are
    Plant                - WERKS
    Pur.group        - EKGRP
    Pur.org            -EKORG
    Acc.assignment category-KNTTP
    Document value-GNETW
    Document type-BSART
    The table is CEKKO
    Thanks

  • Incorrect Release code called which is not defined in a Release Strategy!

    Dear Gurus,
    I am facing a problem in Release strategy for a specific Purchase Requisition document type. My Release Strategy has two Release Codes for the Approval of a PR. When i create that document type of Purchase Requsition, Same Release Strategy is called, system picks the Two release codes from my Strategy but also pick another Release code which is not defined in my Release Strategy.
    Kindly help me and let me know.
    Thanks in Advance.
    Johi Kapoor

    Hi,
    In Release Simulation (segment of Release Statergy), just  click and you will have small pup up screen and there just double click the release codes all you have and you can see all unwanted release codes will be dissapeared and you have only now needed release codes what you configured for the release statergy. Now similuate  release & set/reset release .
    Regards,
    Biju K

  • How to have more than 8 release code for a release strategy

    Hi,
    In standard only 8 level of release is possible for a release strategy.  Our client requires more than 8 levels i.e., more than 8 release codes for a release strategy.  How can we achieve this?
    Pls provide your views/ideas.
    Reards,

    Hello,
    In case you require more than 8 levels in release strategy , write to SAP, maybe they could give a fitting reply.
    By the way , 8 levels of release should be more than enough . Try to incorporate the client business process
    within this.
    Regards
    Anis

  • Two release code in one release strategy

    Dear all,
    Good Day!
    how can i create two release code in one release strategy on Purchase Order
    Release code is 07 - P & L Manager and 18 - President
    07 will release up to 500,000.00
    07 and 18 will release 500,000.00 and  up
    thanks in advence,
    Ermin D. Concepcion

    Hi Ermen,
                    I am not getting the problem, as Mr Barik has already suggested you the correct solution, if you want the path then the path is
    IMG>Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders-->Define Release Procedure for Purchase Orders.
    Here you must have already designed the Release codes, Release Indicator and release groups for your strategy, you have to define the "Release Strategies".
    Select the group and the strategy and put in the Release codes. and proceed.
    Here in the classification TAB please give the values, if this release strategy is to be triggered for less then 500000 NETW field.
    and same way define another Release strategy with The NETW value greater then or Equal to 50000.01
    I guess you were asking the same thing.
    Regards,
    Yawar Khan

  • CCreate Release Strategy using department name in "Release Code", not User ID SAP.

    hi experts...
    i wanna create new release strategy, but in part "choose activities => Workflow => assignment of role to release code"
    in field Agent ID usually we fill SAP user ID, but i wanna using department name.
    is there anyone can help me
    thanks,

    Hi Raju,
    Are you setting release for purchase requisition or purchase order ? If you are setting the release strategy for purchase requisition you need to enter table name as CEBAN  and for purchase order  give  table name as CEKKO.
    Enter tcode SE11 and give database table name as CEKKO and choose the appropriate field name for the desired component from here. Do the same with table name CEBAN for pur req.
    Hope this was helpful.
    Cheers,
    XsNitin

  • My client wants more than 8 codes for release strategy is it possible

    Hello
    I know that standard sap does not allow to have more than 8 codes to be there in release strategy. Is there any other way to have more than 8 codes
    regards
    mohammed

    HI Mohammed,
    yes!! It is possible. std SAP provides and recommends 8 codes.
    But you can have n number of codes
    Rgds
    Girish Kavital

Maybe you are looking for