Release startegy--Purchase group

Hi,
I have included new created purchase groups into Characteristic value ,
but this purchase groups are not having release strategy into PO,
What other setting requires?
Devendra

Hi,
As you have already included newly created purchase groups into Release Characteristic value, just cross check you have VALUE of "newly created purchase groups " in the release statergy.if not VALUE need to add in to the Release Strategy.
As  TR transported from customising client to testing client and you can directly  add  newly created purchase groups into Release Characteristic but the VALUE of "newly created purchase groups " can not be added directly in testing client for Release Strategy . Now add newly created purchasing groups in CL24N/CL20N for your Release Strategy with Release Group with Release Class.
Regards,
Biju K

Similar Messages

  • Purchase order release startegy

    Dear Experts,
    We have got release startegy for five release codes i.e L1,L2,L3,L4 and L5 for purchase orders
    Release startegy is based on Pur order category,doctype, Net order value and Pur group.
    For L1-L5 authorisation(all authorisations) is given for General managers.
    Currently when emergency is there general Manager has to release L1 to L5 all release codes.
    Requirement is that instead of releasing all can it be possible to release only L5 so that all can be released.( This authorisation is for only for L5)
    Once the authorisation is there for all any customisation possible for releasing code L5 so that remaining all release codes can be released.
    Please suggest.
    Regards,
    Dayanand

    Hi Mr.Shawn,
    I have removed ticks for L1,L2,L3,L4 in Release prerequisites then release startegy L1 L2 L3 L4 kept as Released.
    Then Even if release one all releasing.
    But Requirement is that when only L5 is released only All shall be removed, other wise remaining Releases shall be based on the old procedure only. L1 to L4 shall be L1 is released then only L2 can be released principle. But in case of L5 releases all shall be released.
    Is it possible, what needs to be done ,please suggest.
    Regards,
    Dayanand

  • Escape Release strategy based on purchasing group

    Dear Experts,
    In our system,  PO release strategy is set up,
    But, some of the POs are not subjected to release strategy because they belong to a perticular Purhasing Group (P01).
    Where this set up is done?
    Regards,
    Shashidhar

    Hi Shashidhar,
    In your system it seems there is a characteristic created for Purchasing Group, if you want it activated for a particular Purch Group, then please do the following
    Determine the strategy that you want to be called ( You can see any existing PO to find it out), once done, you need to identify the characteristics and class
    SPRO-MM-Purchasing-Purchase order-release strategy, define release strategy, select your strategy and go to details and click on classification, in case you get an error and not able to, click on release pre requisites, come back and then try again, in classification you will get to see the various characteristics maintained and also the class name at the top.
    Once you have done that, please go back to the node Edit Class, please put the class that you obtained earlier and get the characteristics for Purchasing Group.
    Then go to the node Edit Characteristic, put your characteristic name say PO_RELEASE_EKGRP, Click on the tab values, and add your Purchasing group here and save it.
    Then go to transaction CL24N, provide the class, and select the release strategy you are interested in, and select change, and detail, there for the characteristic for Purchasing group, you can add the previously added Group, and you are good to go.
    Please let me know if this helps.
    Regards
    Shailesh

  • PR Release Strategies on purchasing group basis

    Dear All,
    I want to define PR Release Strategies on purchasing group basis. please suggest process.
    Regards,
    Mukesh Chejara
    SAP

    you can use Table name CEBAN and Field name EKGRP define in the characteristics and then maintain the master data in CL20N.
    Regards,
    qsm sap

  • Workflow for PR release for multiple purchasing groups

    Hi Guru,
    We have multiple purchasing groups and want to send emails to the responsible person for PR release for their own purchasing groups.  In the standard SAP pr release work flow configure, there is no place to specify purchasing groups.  Do you have any recommendation?  If we need ABAP development, do you know the user exit that we need to modify?
    Thanks a lot!

    Hi
    Define the release codes for each person heading a department (purchasing group) and assign the work flow for concerned person. When ever you create PR, depending on purchasing group work flow will be triggered. Assign the release code and release group authorization to particular person's profile in PFCG. Then he can be able to release PR.
    Thanks

  • To maintain the purchasing group to all release strategies

    I want to maintain the purchasing group to all release strategies using cl24n transaction.
    plz help me out.
    I am trying to do that using 'BAPI_OBJCL_CHANGE' and passing the values as:
    OBJECTKEY:   A0T1
    OBJECTTABL: ******
    CLASSNUM: available
    CLASSTYP: 032
    Plz tell me the what table name need to pass in OBJECTTABL field.

    There are few tables with T16F* , please try with suitable one...

  • Inclusion of Purchase group in service entrey sheet release strategy

    Hi
    We are trying to include the purchase group in service entry sheet release strategy but system is not considering it.
    Pl. let us know which table you have considered for purchase group character. We had considered EKKO table and Field EKGRP.
    Regards
    Kandre

    Thanks Solved. The same field is done in development server, but after the request is moved to 201 and we manually changed to EKKO and EKGRP, that why the release strategy is not picking.
    Thanks for fast response.
    B.Kandre

  • Purchase Requisition with wrong purchasing group - release strategy

    Hello
    There is a lot questions about release strategies but I cannot find answer.
    I have release strategy based on:
    - Plant
    - Purchasing Group
    If I create Purchase Requisition with right purchasing group release strategy is assigned to PR item.
    When use wrong purchasing group - release strategy is not assigned.
    How to easy set control – if user use wrong purchasing group system automatically set one strategy which not allow to create purchase order.
    There is too many plants (150) and purchasing groups (60) to create all combinations in strategy. So I cannot do that.
    Maybe there is some useful user-exit?
    I use SAP ECC 6.0
    My problem occurred because SAP allow to create PO with reference to PR which have no assigned strategy.
    Thanks in advance for help
    Arek

    Yes it is solution
    But as I wrote before – there is too many incorrect combination.
    Example
    PG A1, A2, A3, A4…. A50
    Pl 2200, PG A1 – OK
    Pl 2200, PG A2 – OK
    Pl 2200, PG A3..50 NOK
    For this example I have to set 48 combinations (strategy with S).
    I noticed that I would have to set about 200 strategies. Client don’t want accept it.
    You wrote – “set up one unique strategy”. How? As I know I need 200 strategies (or there is something I don’t know
    Kind regards
    Arek

  • Release Strategy in PR not triggered for different Purchase Groups.

    Dear Experts,
    For Purchase Requistion - Header Level Release Strategy has been defined with Purchase Group as one of the Characteristics(Characteristic Values are V1, V2, V3).
    When PR is created for 30Line items with V1, V2 or V3 as Purchase groups independently- Release Strategy is triggered.
    But when  a combination of all 3 Purchase groups is used in the same PR for 30 Line items together. No Release Strategy is Triggered. All these 3 Purchase groups have been assigned for all strategies.
    Thanks & Regards
    Chandan H N

    You are using characteristic P. Group for different RS. That means that if only one value exists, the system will be able to understand which RS to implement. If you are using more than one values for this characteristic, the system simply does not know which RS to choose and takes nothing.
    More simply you are using a header data (p. Goup) for RS and you are using it in line items. This is wrong. You have to make PR's only for the respective P. Group

  • Purchasing Group in PR to be made editable after PR release

    Hi experts,
    We  raised PR with some Purchasing Group.  Afterwards, PR is released . Now it has been found that Purchasing grp put in PR was wrong.  We want to edit that.
    In other words, we want that purchasing grp field to be made editable even after PR release.
    Please guide.
    Regards,
    ( Rajneesh Gulati )

    Dear Pankaj,
    Thanks for your prompt reply.
    I followed your below mentioned instruction :
    Now go to SPRO > MM > Purchasing > Purchase Requisition > Release Procedure > Procedure with Classification > Set Up Procedure with Classification > Release indicator > Here for indicator "2" check the field selection key for e.g. "XXX"
    Now go to SPRO > MM > Purchasing > Purchase Requisition > Define Screen Layout at Document Level > Here for field selection key for e.g. "XXX", under Selection group "Basic data, item", mark "Purchase Group" as optional
    In our case purchase group is already optional.   Please suggest further course of action.
    ( Rajneesh Gulati )

  • New purchasing group release strategy classification

    Hi all,
    I am creating a new purchasing group and need to do the release strategy classification. Please would you outline the process involved including the transaction codes?
    Thanks in advance.
    JJ

    Hi,
    Please go through this link, it has all the required information,
    http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM
    In case you encounter any issues, please let me know all details, would he happy to help.
    Regards
    Shailesh

  • PR Release startegy

    PR release startegy  should be flexible so that if we add any of the parameters, the program should follow the rules. The parameters that can be changed are:
    1. Document Types
    2. Project Types (We will need a custom table)
    3. Plants Groups
    4. Threshold Amounts
    The routing of the Purchase requisition approval is primarily based on the amount on the requisition, the Plant, and the department the requisitioner belongs to.
    In standard sap we have static parameters for release staregy, but here requiremnet is dynamic, when ever you chnage any of the parameters the syatem should adapt those chnages and the existing rules must apply for new one.

    Why would you change Doc. Type?
    If your requirements are not firmed than you should not raise requisition.
    No matter how dynamic your business is, requisition raised for a particular requirement should not vanish or change in a day or so.
    Practically speaking, it seems your supply chain is not process driven.
    For such scenarios you should allow to create POs directly once the requirements are firmed and aprovals covered for POs only.
    Regards,
    Dakshesh

  • Release startegy for service PO

    Hi,
    Can you people help me out with release startegy for Service PO and service entry sheet?
    Regards,
    Satyendra

    Hi,
    Please refer below mention format.
    SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
    Three steps involved in release process of purchase order.
    1) Edit Characteristic: -
    Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP
    2) Edit Class: -
    After creation of characteristic, create class for release purchase order. In which you can take reference of
    Class Type: - 032,
    Status: - Release,
    Class group: - Release strategy class,
    And put reference of your characteristic, which are created by you in first step.
    E.g: - Class u2013 REL_PO
    3)Define Release Procedure of purchase order: -
    In this step four processes involved.
    1) Release Groups
    2) Release Codes
    3) Release indicator
    4) Release Strategies
    1) Release Group: - In which you can define release strategy group
    For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    2) Release code: - In which you can define release code. Enter value as
    Release group: - 01,release code: -01 u2013 Purchase Head,
    Release group: -01, release code: - 02 u2013 Auditor.
    3) Release indicator: - In this step you have to define release indicator.
    Like X u2013 Blocked, I u2013 Under process, S u2013 Release.
    4) Release Strategy: - This is the final step for release strategy.
    Assign release code 01, 02.
    Click on release prerequisites, select 02 u2013 check box and click on continue.
    Click on release status button, enter release indicator X, I, S and click continue
    Click on classification button, Enter values of purchasing group for which you want to created release strategy.
    Note: - Create characteristics for service order document type in CT04.
    Regards,
    Mahesh Wagh

  • Can't use Overall Release for Purchase Requisitions

    I have two groups, AA and ZZ.  Each group has it's own Class.
    Group AA uses Cost Center Class (CN)  (uses Characteristics Cost Center and Line Amount)
    Group ZZ uses Order Class (OC) (uses Characteristic Order)
    I have built one and only one Release Strategy for each of these Groups.  These Strategies both work successfully when I select the other group to be the group for Overall Release.  That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully.  However, if I modify the req the strategy for ZZ, does not get applied.
    The opposite is true.  When AA is set to be for Overall release, then ZZ works.  However, if I modify the req, then AA's release strategy does not get applied.
    Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release.  However, neither strategy works if its group is set to be the one for Overall Release.
    What am I missing?  I only have two classes, two groups, and two release strategies.

    SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
    Release procedure is of two types
    Release Procedure without classification
                 This procedure is applicable only for Purchase Requisitions.
                 Here PR is released Item by Item only.
    Release Procedure with classification
                This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract  and scheduling agreements.
                Item by Item and Header level releases can be configured
                For PR - both item by item and Header level release can be configured
                For external purchasing documents - Release is possible only at Header level.
    Step 1:
    Create Characteristics
    In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
                1) Total value of PR more than Rs 50,000
                   create  characteristic as "Release_PR_total_value" in transaction code CT04.
                  Tab -  Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency  eg. INR or USD"
                  Tab -values key in > 50000 INR
                  Tab -  Additional Data-  Table Name "CEBAN" and Field Name "GSWRT"
                  Tab - Restrictions - class type - 032 - Release strategy
                2) Plant
                     Create characteristic "Release_PR_plant" in transaction code CT04.
                     Tab - Basic data - Data type - CHAR; Number of chars - 4
                     Tab - Values - Key in all the plants for which you are required to configure release proc.  eg. 1000,2000,3000
                     Tab - Additional data - Table name CEBAN and Field Name is WERKS.
                3) Purchaisng Group
                     Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                    Tab - Basic data - Data Type - char, Number of chars eg. 3
                    Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                    Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
    Step 2:
    Define class in transaction code CL02
    Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
    Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
    Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
    Tab - Basic data - Enter description as "PR_Release-Proc",
    status- Released, Same classification - check the push button - Warning Message
    Tab- CHAR Enter above created 3 characteristics
    1.Release_PR_total_value
    2.Release_PR_plant
    3.Release_PR_PurchasingGroup
    step3:   
    Menu path is
    SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
    here define
    1.Release Groups
    Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
    Here assign class "PR_Release_proc" against release code "01"
    check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
    2.Release codes
    Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
    PRs are released by users in transaction code ME54N.
    Eg
    Type of user            - Level -             Release code                    
    PR creator - clerk or Business user -  
    Approver    -  Supervisor                 -   R1
    Approver  -   Project Lead              -   R2
    Approver   -  Asst. Manager             -  R3
    Approver   -  HOD/General Manager  - R4
    Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
    For detailed info please refer
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    3. Release Indicator:
    Release indicators show the release status of a Purchase Requisition.
    For detailed info please refer SAP Help official site
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    4.Release Pre requisites:
    These define the order in which individuals or departments release the PR in sequence.
    3.Release strategies
    Create a new release startegy  eg ."A1" or "U1" , write its description PR release for value >1 lakh
    Now select release codes according to the Chart of Authority set by your client.
    Eg.
    Release startegy " A1 - PR release for value >1 lakh"
    R1 - Supervisor   
    R2- Project Lead    
    R3- Asst. Manager 
    R4- General Manager
    Now click on" Release  Prerequisites "push button and check all the boxes in ascending order.Save the document
    click on "Release statuses" push button, check release statuses then click on "Continue" push button.
    In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
    Classification data for example
    1. Value - > 100000
    2. Plant - 1000,2000,3000 etc
    3. Purchasing groups - 101,102,103 etc
    By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
    In this way you can configure all the required Release startegies.
    Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
    Tcode - ME54N - For Individual Release
    Tcode - ME55 - For Collective Release
    For detailed info please visit SAP HELP website
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Regards,
    Indranil

  • Error In release of Purchase Requisition

    Hi All,
    In Development Client PR release strategy is working fine but when iam testing in testing client PR release startegy is not working.
    I have created class and characteristics before transporting the rel groups but when i checked i am getting error in classification.
    What would be the reason? is there anyway we can trasport class and charecteristics.
    Regards
    Krishna

    Hi,
    In my understanding the correct way to transport characteristics is using transactions BD91, BD92 and BD93.
    BD91
    Characteristic                RELEASE_STRAT_CHAR  
    Logical system               EQ0CLNT100_X
    Change number             400000000XXX
    Valid from                      31.03.2011
    RUN
    BD92
    Class type                    032               
    Class                            RELEASE_STRAT_CLASS
    Logical system             EQ0CLNT100
    Change number            400000000239
    Valid from                     31.03.2011
    RUN
    BD93
    Class                            RELEASE_STRAT_CLASS
    Class type                    032
    Logical system             EQ0CLNT100
    Change number            400000000239
    Valid from                     31.03.2011
    This way you can transport classes and characteristics from each client, don't forget to create the modification number in each client before execute these transactions to transport the classes and characteristics.
    You can check tables KSSK and AUSP to have sure about the transport too ^^
    See ya
    Jony

Maybe you are looking for