Release stratregy for PREQ

Hi,
   I have configured release strategy for PREQ with classification. this procedure enables to release PREQ both item by item and in their entirely.
my procedure is working fine.
In PREQ Screen, the Release Strategy TAB is appearing at item level after contact person TAB.
Is it ok?
somebody told me in PREQ, it should appear at header after text TAB.
Pl confirm
Thanks

Hi Ritalee,
One doubt, is your configuration is by header means Over all release or by item level?
If you want by header level, you have to select the Overall Rel box in SPRO-MM-PR-Define Doc types.
You will have a Rel Strategy tab at the header level.
If you practice by item level, this is not a problem for you.
Hope this clear any doubt.
Regards,
Maia

Similar Messages

  • Release strategy for PREQs created from PM work order

    Hi All,
    I have an issue with determining  release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
    We have activated release strategy for Purchase requisition based on the following characteristics:
    CEBAN_PLANT
    CEBAN_COST_CENTER_GROUP
    CEBAN_MANUAL
    Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding  cost center goups.
    In the user exit we have consider to cases:
    The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
    The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
    The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
    We have defined  for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
    Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
    Best Regards,
    Desislava

    Hi,
    For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
    Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
    Regards,
    Raj

  • Release Strategy  for Preq

    Hi SAPgurus...
    I have release strategy implemented in my system with 7 level approvals for the Pur. Req . Now i need to Change the release strategy to 4 levels approval based on one of the Characterstics that is the Preq Net Price. Which cud be the best process to ahcieve it , since if i am going to keep the old one and create a new one then wheneve similar characterstics appear the system cant recognize which strategy to apply.......
    Please can any one advice me how can i approach ...
    Regards
    Balaji

    Hi Lakshman, Srini & Venki
    From ur statements i understand to modify the existing ones , okie as u said i will delete the extra release codes and modify it . Now fine..
    What happens when i moved to prodcution these changes then, say if i have Preq
    with older version of release strategy how it impacts.....How i can handle  this in
    effective manner...To my knowledge i think whenever if i go for a change in preq the new release strategy will be affected....( In this case its fine) what abt the ones which doesnt need a change and has to be released....
    Thanks for the time ...
    Regards
    Balaji

  • Function Module to fetch Release Code for PReqs

    Hi,
    Is there any function module to get the current release code applicale by passing the requisition number?
    Example : If we have 4 levels of approval, say A1,A2,A3 and A4, and I want to know with what release code shall I release the requisition.
    If release has benn effected for the requisition with codes A1 and A2 and if I query with the function module what is the current release code applicable, then it should give A3 or atleast a result that A2 has been the last release code effected.
    Also where is the release related info stored ? I mean which tables...
    Not the release strategy related info but the release effected info.
    Dont worry about points...

    Hi
    Pur requisition Release Codes are stored in <b>T161E</b> table
    Release code is linked with Release strategy in <b>T161F</b> table
    Link the code with Release strategy field in <b>EBAN</b> table
    Also check the fun modules
    MM_CHECK_RELEASE_CODE_EQUAL_KI
    MM_CHECK_RELEASE_CODE_NOT_KI
    ME_RELEASE_REQUISITION
    BAPI_REQUISITION_RELEASE
    Reward points if useful
    Regards
    Anji
    Message was edited by:
            Anji Reddy Vangala

  • Challenge for release strategy in Preq

    hi all.
    our maintenance department requested a very specific release strategy for purchase requisitions with account assignment F (workorder).
    their release is based on several factors:
    1) amount: 0>2000 it must be released by the main work center which of course, depends on what is on the workorder and can be one of 3 (WC1, or WC2, or WC3)
    2) amount 2001>6250 it must be released by the following:
    WC1and/or Maintenance manager
    or
    WC2 and/or maintenace manager
    or
    WC3 and/or maintenance manager.
    the and/or mean that if WC1/2/3 releases, the maintenance manager will still need to release but if the maintenance manager releases first the Preq is released and there is no further need to release by WCn.
    anything >6250 must be released by the maintenance manager.
    our release strategy is with classification and we will use a user exit to determine which WC is being used and needs to release but i have a problem with point 2: how can i set the strategy in such a way that it can perform the release and/or?
    can someone help?

    Hi Alisa,
                 Your Requirement is very Complex,
    first thing if you want to have the Release strategy for the Account Assignment, you need to have that Characteristics in the class, and make sure that same rule is followed by all the Other PR, directly created.
    Second thing if you say that any thing less then 2000 should be released by the Main Work Center responsible person, which you have maintained by the user Exit, there must b a cross check that the person belonging to one work center should not be allowed to release the PR being generated in other Main Work Center.
    for that you need to have different Release codes assigned to the user in the roles.
    for any thing >2000and <6250, you need the WC1 and Maintenance Manager should release, but only Maintenance manager releases then also the PR should be released,
    Question: in above case what is the need of the WC1 or WC2 or WC3, let it be released by Manager only
    Please revert back.
    Regards,
    Yawar Khan

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

  • Why release strategies for PO at header level only

    We have release strategy for Purchase Requisitions and Purchasing documents like PO, Contract and SA.
    In case of PREQ we have a choose for either item level release or header level release, whereas in case of PO, Contract and SA only header level release is possible.
    My question is why SAP has provided only the header level Release Strategy for PO, Contract and SA? I wan to know the reason and logic behind this.

    Hi,
    For PR's, there is no header level data. Becuause vendor number is optional since it is internal document from the user dep. to pur org. That's why, vendor number fields is at item level in the source of supply screen. But this is optional field.
    That's why, you can release PR line items one by one or all at a time.
    If you are releasing all line items at a time, need header level release.
    If you release line item by line item, need item level release.
    But in the case PO/Contract/SA, these are final reference documents and sending to the vendor as external documents.
    That's vendor number is at header level field and line item in the PO are related to the single vendor.
    That's why u cann't release line item by item, i.e., item level release.
    You can relase all the  items in the PO or u can reject entire PO, not a single line item.
    That's why, only header level release is possible for the PO/Contract/SA.
    Regards
    KRK

  • Problem in creating Release group for Release Procedure for PR

    Hi Experts,
    I could not able to create Release Group ( 01 & 02 ) for Release Procedure and assigning it with a Class
    ( Z_CLASS_PR ) in Set up Procedure with Classification.
    The following error is getting displayed.
    Please check release classes (see long text)..
    How to over come this problem.
    Thanks in advance.
    Regards,
    Nani

    Release group:
    You are only allowed to use one class for each release object (1=PReq, 2=Purchase order). When you use the overall release (as of Release 4.0A), you are only allowed to use one class for the overall release or individual release. If you use the overall release for purchase requisitions, you must mark this for the document type (transaction OMEB, flag for V_T161-GSFRG) and the release group (transaction OMGQ, flag for V_T16FG-FRGFG). In the overall release, the system only takes into account characteristics that are identical for all items. If, for example, item 10 of a purchase requisition contains material group 001 and item 20 contains material group 002, the material group is set to BLANK for the strategy determination.

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

  • 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 for SA/Contract/PO

    Hi friends,
    Should we have different release groups and release codes in contracting/ SA/ PO.
    Because...
    I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
    But i want to maintan only 2 characteristics in release strategy for contract  [plant, total net order value]
    because the same is reflecting in contract config also.
    Is it possible..please help me frnds.
    Prabhu

    Hi Prabhu,
    Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
    Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
    Regards

  • Release Build for Dev vs. Production environment

    I'm working on a very small project that performs an LDAP
    search using a CFC on our Dev box. The folder structure between
    Development and Production are the same so when I create a release
    build and copy it from the dev environment to the production server
    I get a "send" error on the client. The compiled release build is
    copied to the same folder structure location as it was on the dev
    box, but I believe the application is still trying to point to the
    dev box ip address vs. the production server address. How do I
    handle exporting a release build for a different server than the
    one I'm developing on?

    How is your classpath build up?
    if it's like this:
    SET CLASSPATH=c:\prod;c:\dev
    try
    SET CLASSPATH=c:\prod
    CLASSPATH=%CLASSPATH%;c:\dev
    if that doesn't work try setting your classpath to nothing:
    SET CLASSPATH=%CLASSPATH%
    Please tell me if this helped, I've had a lot of problems with my PATH and CLASSPATH to, and I ain't sure I gave the solution. So please reply to let me know this is the answer or not.

  • Release Strategy for Contract is not getting picked whereas it is ok for PO

    Dear Experts,
    I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    Kindly resolve the issue.
    Satish

    S0004830404 wrote:
    Dear Experts,
    >
    > I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    > I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    >
    > Kindly resolve the issue.
    >
    > Satish
    hi,
    use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
    Thanking you

  • Release strategy for Schedule lines in SD

    Hello All
    Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
    I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
    Thanks in advance.

    Hello,
    I think you are in the wrong forum. Please choose the right forum category and post it there.
    Matthias

Maybe you are looking for