ME52 & ME52N - Release Strategy

Hi Experts,
My requirement is to hide release strategy tab for some particular POs depending on the total PO quantity. Through configuration we can remove for all POs, but requirement is to remove release strategy only for some POs in ME52 and ME52N. Are there any user-exits or BADI to do this.
Please help me in this asap.
Thanks in Advance.
Siva Sankar.

Hi,
You need to use Transaction Variant SHD0 to achieve what you need.
Check the details in this link
http://help.sap.com/saphelp_47x200/helpdata/en/67/232037ebf1cc09e10000009b38f889/frameset.htm
Regards
Kiran Sure

Similar Messages

  • Cusotm data tab In ME52n, copy release strategy tab details in custom tab

    I have created a custom data tab in Me52n using exit mereq001, and I need to get purchase requisition number, releasegroup, release code and release strategy values in the custom data tab screen in order to fulfill my requirement.
    I am using the screen exit and trying to code in the include (PBO), But in the include I am not able to get the required data as afore said.
    Can you please tell me the procedure for getting the global structure that I can use in the include to get these values?
    *Please give me the solution ASAP.

    HI,
    Use the fm  EXIT_SAPLMEREQ_001 and get the data ..............
    data : wa type mereq_item .
    call method im_req_item->get_data
      receiving
        re_data = wa
    the structure wa will contain the data .....
    Thanks,
    Shailaja Ainala.

  • ME51 / ME52 user exit for release strategy

    Hi Experts.
    I have to set in user exits release strategy during creating or changing Purchase Requisition. Please give me proper name of user exits which can helps me (not all list for ME51 or ME52)
    Thanks in advance

    Hi ,
    These may help
    M06B0001            Role determination for purchase requisition release
    M06B0002            Changes to comm. structure for purchase requisition release
    M06B0005            Changes to comm. structure for overall release of requisn.
    M06E0004            Changes to communication structure for release purch. doc.
    M06E0005            Role determination for release of purchasing documents
    MM06E008            Monitoring of contr. target value in case of release orders
    Regards
    Saket Sharma

  • New release strategy / Old PReqs

    Hi,
    New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
    But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
    Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
    Many thanks in advance for your clues.
    Regards,
    Grzegorz

    Hi,
    Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you.

  • Preq release strategy

    My Preq release indicator has it's changeability indicator set to 4.  So if the value increases (qty or price) after release this works fine and PR is resent for approval 
    However if I change the material after it's been released (ME52N) but the value does not change the release strategy's not triggerred again.  Is there no means of making the release strategy field dependant, or should I set the material field to display only in the field selection after release.  My concern is a Preq could be created for say u20AC100, the PO changed and material A replaced by material B for the same value (or less) and the release strategy not triggered.
    Thanks in advance.

    I think the only way is to set the field selection of the release ID to display fields.
    This will restrict the users from changing the field value once the Release ID say "4" is set.

  • Overall Purchase requisition Release strategy : Changed after Rejected

    Hi All,
        I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
      Problem I have is when PR is rejected .
    When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
    But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point. 
    ME52 changes for PR is not trigerring any event which can trigger the WF.
    Is there any way we can trigger Workflow in this scenerio.
    Please suggest.

    Hi Subhashini,
    This all depend on release strategy. release should reset completely on tha change.
    For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
    When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
    If no other release strategy is determined by the reduction of the
    amount or value, the system will keep already existing releases.
    changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
    Sanjeev

  • MM Release Strategy with Cost Centre

    My characteristics for the release strategy is Accnt Assigmnt (KNTTP), Cost Centre (KOSTL) and Amount (GSWRT). I link all to the ceban straucture, and for the cost centre, I entered in the value tab the cost centres that I am using, and I entered the cost centres in the release strategy. Everything seem OK for the release strategy, but the release strategy is only selecting the strategy according to the values and not considering the cost centre, what can I do let it consider the cost centre and the value. I have been struggleing with this problem more than a week now. I tried everything that I can think of. Can someone assit me in this matter. I am on ECC 6.
    Thank you.

    Refer OSS Note :: 52225
    Solution ::
    Summary
    Symptom
    Purchase requisition release strategy with classification does not work as expected when the characteristic for cost center KOSTL is included.
    Message  ME297 is displayed.
    Additional key words
    CEBAN-KOSTL, KOSTL, Cost center, Release strategy, OMGQ, ME297
    ME51, ME52, ME53
    Cause and prerequisites
    Numeric values used for the cost center characteristic in the purchase requisition release strategy with classification is not recognized. CEBAN-KOSTL is a CHAR field of length 10.
    Solution
    Enter leading zeros for the cost center value in the release strategy. eg. If the cost center value is 123456, while entering this value for the cost center in the release strategy, enter it as 0000123456.
    Cheers !!!!!!
    Biswajit

  • Release strategy:ME53N : Older PR documents shows, modified PR rel.strategy

    Hi Friends
    We have updated the sequence of release codes for certain PR release strategies. But when we moved the changes production, i observe that all the older PR documents (Which were released last year and completed) also shows the updated release strategy in transaction ME52N/ME53N.
    Can someone pls some explain? Is this normal?
    SAP doesnt store the release strategy and its sequence of release codes, which were determined at the time of document creation?
    Thanks for your help...Raj

    Hi,
    There is no change in the older documents.
    The documents are older by few years.
    I have checked few documents randomly, the tcode ME53N shows only the updated release strategy.
    I did some investigation today on this.
    i think system will not keep the release strategy pertaining to document creation.
    It will just store Release Group and Release strategy in the Purchase Requisition tables (like EBAN).
    And when ever we try to display the document it will go and read the release strategy sequence from relevant tables.
    Hope someone helps to validate if my investigation is correct.
    Good day..

  • 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.

  • PO Release strategy

    Hi,
    I have a unique requirement in PO release strategy. The requirement is if the PO doesn't have any contract it should be subjected to 2 step release process. If there is a contract then it should be subjected to 1 step release process.
    Now i have created 2 release strategies one with 2 step release and the other one with 1 step release with the same charecteristic values. The only exception is i have used the 'USER DEFINED CHARECTERISTICS' - USRC1 with the value of X in one step release strategy and the value of BLANK in 2 step release strategy.
    After doing all these settings Release strategy is not trigerring at all. Firstly it has to trigger the release then using the exit we can change the release strategies depending upon the conditions.
    Any suggestions are highly appreciated to fix this issue.
    Regards
    Sudhakar

    Hello,
    After you have done config for the release strategy please execute " Check Release Strategies". This will also help you in giving first round of check/errors in your config.
    regards
    anand

  • 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

  • Contract & PO Release Strategy

    Hi All,
    We are in the process of designing the release strategy for contract and PO. I  would like to know whether we can have the different release conditions for contract and different release conditions for PO. For example.
    The release conditions for Contract required are
    1)Porg
    2)Pgroup
    3) Value
    Also, for quantity contract how can we make the release strategy trigger based on value.
    The release conditions for PO required are
    1)Porg
    2)Pgroup
    3)Material Group
    4)Value
    The release strategy is not getting determined if we create po with two line items which belongs to two different material group. Is there any way out to solve this issue?
    Request your help.
    Regards,
    Kannan

    Hi Kannan
    Yes your requirement is possible...
    While creating Charectristics in CT04 for External Purchase Documents...Create one more Value  for your Document Category...ie) Table as :CEKKO   and Field  as BSTYP   and choose the Purchase Doc. Category  values K  and F.
    Then create Charecteris for  CEKKO - EKORG,  CEKKO - EKGRP   and   CEKKO - GNETW, CEKKO- MATKL...  and assign these all 4 Chareteristices in your release class.
    And Configure your release statergy according to your requirement...
    Reward if useful
    Regards
    S.Baskaran

Maybe you are looking for