Release Strategy Doubt

Dear experts,
We have a requirement to display the name of the persons who released the PO or RFQ in the report output.
I could refer to the tables T16FS and T16FW to display the authorized person for that particular release group and release code.
For a particular release group , release code and a plant, there is only one entry in the table T16FW.
But the req states that there will be 2 persons at each level (suppose , there are 3 levels for PO release , 2 persons per each level will be authorized to release the po) .  How will I get the name of the 2 persons for each level and how can I determine who has released the PO among them? Please help.

Hi Nayana,
You can get that details from CDHDR table.
Give object value as Your PO number with leading zeros and transaction as ME29N and execute.
Regarding your query How will I get the name of the 2 persons for each level
I am assuming you know the release groups and codes, you would need to go to SUIM-User-Users by Complex Selection Criteria-Users by Complex Selection Criteria- give authorization object as M_EINK_FRG and click on entry value box above it.
Then provide the release code and group, you would then be able to find out the users who are assigned that role. I have never really explored the tables for finding this information, hope this helps.
Regards
Shailesh

Similar Messages

  • Release strategy for quantity contract

    Hi Gurus,
    In quantity contract ..  target value will not filled by the value(in header details) as it is quantityt contract.
    We may have different line items with different cost..
    my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
    please explain/clarify
    regards
    subbu

    Hi,
    The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined  based upon the total net value of the entire purchasing document.
    Cheers,
    HT

  • 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

  • Transportation of release strategy

    Hi guys,
    We heard that in ECC 6.0, we can transport release strategy for PRs and POs along with characteristics and classes.  I have the following doubts on this
    1) Can we transport the values assigned in the strategies also with this functionality ?
    2) From MM side can we configure the strategies in the normal way i.e. creating characteristics, creating classes, creating release groups, creating release indicators, configuring release strategies (or) we need to follow any other procedure for transporting the strategies
    Any suggestions on this

    Hi
    I dont think this functionality exits of transporting the charcterisitcs & classes.
    In ECC 6.0 also this functionality does not exist as per my knowledge.
    Jurgen Thank you for the SAP note
    Thanks & Regards
    Kishore

  • Release strategy(urgent)

    hi,
       i have doubt regarding PO creation.
      Purchase Order has to be approved after modidfication, but,
          release strategy is not getting updated when i am modifying my PO......so i can't approve it..........
    and i am chaning quantity,delivery date, price and condition type, actually i want to know wht is the problem......... and why this is happening......
    and "on wht factors will the release startegy depend ?????????"

    Hi,
    Please can you clarify the following.
    You are saying that it should be approved ONLY after modifying it.
    But was it caught by the release strategy BEFORE it was modified?
    Or are you saying that when a released PO is modified you want the strategy to be reapplied?
    Steve B

  • P Req Release Strategy

    Hi,
    We have scenario in which there are lot of strategies based on P Req's created for Cost centres, Assets, Orders and P Req created via MRP etc. In each of them depending on the Total Item value, Creation Indicator, Plant and Account Assignment Release Strategies varies. So Characteristics of each of the above were created and assigned to Class.
    The problem occured when one of the Release Group required Material Group in their Strategy. So the Characteristic for Material Group (CEBAN-MATKL) was created and asssigned to the Class. But now this Material group gets reflected in other Strategies and appears as blank and the other Release Strategy which worked well before does not work as the Material Group is Blank. We cannot define the Material Group in each of them because there would be enough Material Group and its rather cumbersome to define for each and eveyone.
    How can i overcome this situation?
    Sonu

    Hi,
    this will happen like this only. There is a sap  Note 47089 - Release procedure for purching docs - Aggregation that explains this for material group if used as one of the charateristics.
    Summary
    *Symptom
    Release procedure for purchasing documents
    No strategy is found if the plant and material group were defined as characteristics and no blank entry was maintained.
    Additional key words
    OMGS, ME21, ME22, ME23
    Cause and prerequisites
    Solution
    The release procedure for purchasing documents is carried out on header level. For this, the following values are aggregated from the items on header level:
    item value
    plant
    material group
    Example WERK:
    The plant is only aggregated on header level if all items contain the same plant. If only one alternative plant exists, ' ' is aggregated on header level.
    A release strategy is then searched for with this value.
    Of course, a corresponding strategy is only found if the value ' ' was maintained for the haracteristic 'Value' as an object value.
    The same functionality applies to the material group as for the plant.
    this will info will resolve your issue.
    if still have doubts let me know.
    Thanks and Regards
    Rajesh

  • Po workflow( release strategy)

    hi,
      we had defined release strategy for po workflow. i assigned the users to release codes in SPRO. what my doubt is .... is there any further configuration is there to go purchase order to agent inbox.
    i am not defining workflow template.
    is it required define workflow template  for po, or is it sufficent release strategy.
    let me give reply asap,
    thanks
    suresh

    Hi,
    You MUST have the workflow template  for PO release strategies.
    There is a SAP standard workflow, which you need to activate for the workitems to go to respective agents.
    Hope it helps.
    Regards,
    Shashank

  • Why we Maintain the data in Trxn  # CL20N  / CL24N for Release Strategy ?

    Dear All Gurus,
    Please resolve my Query , that during maintaining the Release strategy for a P.O , i used to create characteristics for defined values such as plant , currency , doc. type etc, then creating class and assigning these characterstics with this class created.
    Now after this i had create Release Group , Release Code and Release Strategy and assigned the Rel. Code with the Rel . Str and in Classification tab i had manually mentioned all those created Characterstics in CT04 and finally saved this Process.
    Till now i had not at all made any entry in Trxn # cl20n.
    But when i had create a P.O with all  the values as same as defined in characteristsc , the Rel Str got triggered succesfully.
    My Question is that , what is the use of mainiating data in Trxn # CL20N & CL24N ?
    Please clarify my doubt.
    Many Thanx in advance.
    Rgds
    sap11
    Edited by: Rajeev Chaturvedi on Jan 20, 2011 5:08 PM

    it is just another way to maintain the same thing in the same tables. Classification notspecific to release strategies, materials and batches, vendors and customers can be classified too.
    You can do this from withion those objects, or from the central classification menu using the classification transactions.
    People here recommending this for production system after you have transported the strategy from developement to production. Becaues classification is master data and cannot be transported the usual way. And many here do not know how this can be done with ALE

  • Missing Release Strategy Tab in PO

    Dear All,
    I am using EXIT_SAPMM06E_006 exit and added a new field using SAPLXM06 0101 ( ME21N ).
    Here i am able to see my custom field but unfortunately release strategy tab is missing.
    Can anyone help in this please....
    Thanks in Advance..

    Dear Faheem,
    Thank you very much.
    Your suggestion helped me a lot.
    One more doubt i am having.
    Here i want to use only SAPLXM06    0101.
    But i dont want to use other screens in that exit ( Screen numbers 0111, 0201, 0211, 0301, 0311 ).
    Because of these screens i am getting run time error as  "  The system attempted to use dynpro 0301 in program "SAPLXM06".
    *This dynpro does not exist. " while using RFQ or Quotation transactions.
    How can i deactivate or remove these screens from my exit MM06E005.
    please help me in this.
    Edited by: kalyan varma on Jan 5, 2011 6:17 AM

  • Purchasing Release strategy in Shipment Cost

    Hy collegues,
    i need some information about Purchasing Release strategy in shipment cost.
    1° question: Release strategy on Service entry sheet document
    Is it possible set the Release strategy on Service entry sheet document?
    I have just created a release strategy on Service entry sheet but when i transfered the costs with transfert field on Shipment Cost document in VI02 the system didn't feel the Release Strategy on service entry sheet and trasfered the cost in FI/CO.
    2° question: Release strategy on Purchase document
    Because of the point one I try to set a release strategy on Purchase Order (on purchase order type that i create when transfering the shipment costs).
    When i transfered the costs with transfert field on Shipment Cost document in VI02 the system felt the Release Strategy. Infact the purchase order was create without service entry sheet document and good receipt but, in this case, i lost the link from Shipment Cost and the created purchase order.
    This in correct, this is a standard behavior???....if this is correct, how will the user (that release the purchase document) release the document if he don'tknow the Shipment cost linked??
    Thanks for your precious help.
    Piera

    Dear Piera,
    Please refer note 844752.
    This note removes former OSS note 611846. As a result, the automatic
    processing of shipment costs should be used WITHOUT release strategy.
    This will be STANDARD now for releases 46B, 46C, and 470!!
    The release strategy will not be triggered if the KZABN = X,
    this is the standard functionality.
    I hope this note will clarify your doubt.
    Regards,
    Rakesh Ojha

  • UserExit required - Do not Create PO without Release Strategy

    Hi
    My requirement is Do not Create PO without Release Strategy.
    When user try to save PO, it should not allow to save, if it does not have Release Strategy.
    For this scenario, we require which UserExit.
    If UserExit, can you guide me which userexit and the following steps.
    For this scenario, which is the best way to control.
    If you got anyother options other than userexit can also be advised.
    Pls advise me.
    With Regards
    Kamesh

    Hi Shailaja
    Very thanks for your reply.
    Some more doubts,
    I think Release strategy data will be populated in I_EKKO table.
    I can use fields from I_EKKO-FRGSX & FRGKE.
    If these fields are initial (ie) PO without release strategy, I want to exit PO without saving - Creation.
    So here can i put Error message if the fields are initial.
    IF i put Error message then the PO screen will be block ? in that Error message.
    Just want to confirm before testing something with the Exit code.
    Is this the way to proceed.
    Thanks in advance,
    With Regards,
    Kamesh

  • PR Release Strategy tab processor field is not getting displayed

    Hi Experts,
    While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
    SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
    release strategy - Release code  -work flow 1
    That processer name is not displaying
    Thanks
    chandoo

    This is the workflow forum.

  • Release strategy for purchase requisition does not kick in

    Hi Gurus!
    I've been struggling with this issue for some weeks now.
    I have set up the release strategy configuration for purchase requisitions with classifications.
    However, if I create a purchase requisition the release functionality is not taken into account by the system.
    See below some more information regarding my configuration:
    1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
    2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
    3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
    4. I have 5 release codes. Grp: T1, Code: 01....05
    5. I have 2 release indicators:
    "R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
    "X = Blocked",  Changeabil: 4, Value chgs. 100,0
    6. I have 1 release strategy:
    "T1 with Grp T1"
    - one release group, 01 Manager
    - release prerequisites not applicable because of only one release group
    - release status, nothing marked = blocked, 01 marked = released
    - classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
    I intentionally kept the configuration as simple as possible so I can try to get it working first.
    Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
    Could you please assist in getting this working?

    Hi,
    Have you checked in CL30/CL30N if your release strategy is derived successfully?
    See section 3 of Note 365604. A small section of it:
    You can use transaction CL30 search for an object using the data
    of the purchase requisition/purchase order. Here, it is important
    that the object search determines exactly one strategy. If this
    is not the case, this indicates that there are overlapping
    strategies in the system or that the release strategies in
    Customizing do not correspond with those from transaction CL24.
    See the previous point. If the object search returns more than
    one result, the system subsequently determines an incorrect
    release strategy or no release strategy at all.
    If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
    The following assignment statement has to exist within activated SAP
    enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
    for purchase requisitions:
         E_CEBAN = I_CEBAN.
    Regards,
    Purnima.

  • Release strategy for PO and Contract

    Hi,
    I maintain characteritic for PO
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    I maintain characteristic  for contract
    Company code
    Target Value
    Doc Type
    Purchasing group
    My class consist of
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    Company code
    Target value
    Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
    Q2:  What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
    Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
    Thank for your advice

    First of all
    For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
    You have to maintain all the characteristic value then only it will trigered release.
    Check the release indicator as well.
    Hope it will help.

  • PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

    Hello everyone,
    I've run into an interesting problem:
    We have defined several PO release strategies.  Most of these work in the traditional manner, requiring manual approval by a given user.  One release strategy, "99," gets picked up by a batch job and released automatically using BAPI_PO_RELEASE. Either way, the release indicator for all released PO's is set to "R." This all works as intended.
    We have maintained Changeability settings for each release indicator in customizing. "R" is set to "4 - Changeable, new release in case of new strat. or val. change," with a percent value change tolerance of 10%.
    If we make a change to a manually released PO that exceeds the threshold set in customizing, the release procedure starts over as intended.
    If we make a change exceeding the threshold to a PO that was released automatically by BAPI_PO_RELEASE, the release procedure does not start over, and the PO remains unblocked.
    What would cause this discrepancy?  The two records look virtually identical in EKKO, particularly in respect to the fields relevant to release.
    Thank you ahead of time for your help.
    -Jarrod

    Configuration issue/user error.

Maybe you are looking for