Release strategy in RFQ

Hello Gurus,
   Is there any way I can implement a release strategy for RFQ?
Thanks,
Jeffrey

Hi Jeffrey,
yes you can set up release strategies to RFQ also in
trasaction SPRO->MM->purchasing->RFQ/Quotation->Release Procedure for RFQs->Define Release Procedure for RFQs.
RFQ's use the same structure as purchase orders for the release strategy classification (CEKKO). Nevertheless, there are some fields in this structure that are only relevant in POs. Field CEKKO-GNETW (Total net
order value) is not relevant to RFQ release strategies. You can enter a value for this characteristic in transaction OMGS, but the system won't consider it.
Since RFQ is just a  Request for Quotation, it does not make sense to set the release strategy of RFQ according to value change.
By using the characteristic CEKKO-BSART you can exclude certain release strategies for certain document types. A release strategy with CEKKO-BSART = NB won't apply to documents with the document type AN (RFQs).
hope this will helps you.
Regards,
Sunitha

Similar Messages

  • Cannot reset release strategy for RFQ

    Dear SAP gurus,
    I set release procedure for RFQ. I set anyway that the changeability is 6, and the tolerance is zero. I expect that after it is released, whenever anyone is changing everything the release strategy will be reset.
    But this is not happening. In my case, the manager already approve the RFQ but the RFQ has not been sent yet. Then someone change the quantity of the RFQ, and the release strategy is not reset. When I check again I realize that changeability 6 means the release will be reset if the value is changed; while in RFQ there is no value mentioned anywhere, it means that the release strategy for RFQ will never be reset.
    Do i miss something? Is there any way to make sure that the release for RFQ is reset if someone change anything in the RFQ?
    Best regards,
    John.

    Why are you having a value based release in RFQ? And more important, why do you need release for RFQ?
    However, if you still want to go ahead with release, then you need to use the user exit for purchasing document release to achieve your objective. Please search for my earlier posts on how to reset release even on decrease of PO value. You can use the same logic for RFQ also.
    Lakshman

  • Release strategy for RFQ

    Hi,
    Please let me know,how to set release strategy for rfq.. i'VE ACTIVATED MY RELEASE STRATEGY FOR po USING TABLE cekko... iF I WANT TO ACTIVATE RELEASE STRATEGY FOR rfq... WHICH TABLE AND FIELD NAME I WANT TO USE... PLS EXPLAIN..

    For RFQ also we can use the same communication structure CEKKO, but for differentiation between release startegy of Contrcats Purchase orders & RFQ's better to use the Charcteristic Document category i.e CEKKO - BSTYP - Purchasing Document Category

  • Release strategy for RFQ's not triggered after change

    Folks,
    Release strategy is active for RFQ's. In case of initial creation, the release strategy is active. After releasal a change is made to the existing RFQ. However, the release strategy is not triggered. Characteristics used are:
    1) document type (AN)
    2) purchasing type (RFQ purchasing document)
    It is obvious that these characteristics will not re-trigger the release strategy. On header level, there is no field in CEKKO available to re-trigger, for example total quantity? Any suggestions for a characteristic that can re-trigger the RS?
    Message was edited by:
            MdZ

    Hi,
    For RFQ Release strategy will be applicable only for Document type.No other characteristics will apply for that.
    As RFQ don't have any specific table where the data is stored related to RFQ.
    So we Use CEKKO which only identifies the document type of RFQ.
    In your case in initial process while creating the RFQ release strategy is active.
    What change you have made to the Released RFQ.
    rgds
    Chidanand

  • Release strategy error in RFQ

    Dear MM gurus
    I have maintained all the steps for release strategy for RFQ, while clicking on release flag in ME42 it is giving following error. please guide
    Purchasing document 6000000015 not subject to
    release strategy
    Thanks in advance
    kailash N. thakkar
    9869171090

    Hai,
          Release strategy gets effected when all the characteristics mentioned for the release strategy are complied otherwise the strategy will not affect the RFQ.You might have given any value not relevant to the characteristic.For eg you might have given alower value than the value mentioned for the characteristic RFQ value.
    Regards,
    Gangadhar

  • Release procedure for RFQ

    Hello All,
    I'm trying to configure release strategy for RFQ, but it's not working.
    I have create characteristics for CEKKO-BSART,CEKKO-BSTYP,CEKKO-EKGRP,CEKKO-WERKS.
    Have assigned objects to classes. Release indicators are assigned properly.
    But in ME41 it is not getting activated. What could be the reason? I think I have made a mistake somewhere.
    Thanks in advance,
    Piyush

    Hi,
    Is it necessary to assign release code & release group to user id?
    Because I have never done it for any release procedure uptill now.
    Please explain the same.
    Thanks in advance,
    Piyush

  • Release strategy problem in RFQ

    Dear cons
       In release strategy of P.O we are using  three characterstics. I.e- net order value, purchase group & plant. Wehave not made any Release strategy setting for RFQ..while we are creating RFQ the system ask to release the RFQ. wHY.wHAT IS THE REMEDY FOR THAT. BECAUSE WE DONOT WANT TO RELEASE THE RFQ. I saw which data I have entered  for P.O release strategy The same data is available In RFQ path.The path is img-material mang- purchasing- P.o- rel. PROCEDURE for P.O- DEFINE REL. PROCEDURE FOR p.o. you can check same data is avaiable in RFQ PATH.
    PL. GIVE ME SOME HINTS.

    Hi,
    Please use document category or document type or both as chanracteristics for the release class.

  • Release Strategy for PO and RFQ

    Hello
    iI have configured following Release Stategy for PO.
    0-1500 INR-Officer
    1500-50000-Manager
    >50000-General Manager.
    The same release startegy has got coped fr RFQ also which is fine.However after I for release in ME45 it is selecting Release Strtagey 0-1500 only.
    Even though I raise RFQ for more quantity I get the same Release Strategy applied.
    I am not sure why this is happening,can anybody explain the reason for the same.
    Regards

    Dear All
    Thanks,issue got resolved.

  • How to avoid po release strategy replicating in RFQ

    Dear Sapiens,
    I am aware  as we are using same class for PO RFQ and Contract the release strategy will repliacte in rest,
    but I dont want PO release strategy to get repliacted in RFQ,because I dont have realease for RFQ
    how to avoid po release strategy replicating in RFQ?
    Regards
    Kantha

    Hi,
    Yes they are same unless you differentiate by using
    1> Purchasing Document Category i.e CEKKO -BSTYP
    A.....     Request for Quotation
    F......Purchase Order
    K......Contract
    L......Scheduling Agreement
    So if you just create a characteristics for CEKKO-BSTYP then maintain its values only for F so it will not be applied to RFQ

  • Release strategy for PO, RFQ & Contract

    Hi,
    We have created release strategy for PO, RFQ & Contract.
    Characterisitc is created for Target Value for Header Area (CEKKO-KTWRT)
    for RFQ & Contract it working fine but for PO not triggering.
    what can be the cause.
    Pls guide.

    Hi,
    Melih is right, for POs you can not use the target value.
    What you might do is to include the document type and CEKKO-GNETW as additional characteristics and then set for contract document types the GNETW blank, and for PO documet type the target value blank. Blank means any value should fit.
    I hope this hint helps!
    Best Regards,
    Arminda Jack

  • RFQ release strategy

    Hi
    I have a problem.
    I use RFQ release strategy but can create PO with reference to not released RFQ.
    I need to create PO's only with reference to released RFQ, same as with reference to
    released contract (I can't create PO with reference to not released contract).
    Thanks
    Meir

    Hi,
    It is of the standard functionality of SAP that you can create PO with reference to unrelease RFQ. Yet, you can't be able to create PO with reference to unrelease PR.  If you would like to meet your business requirement, you will have to activate the user exit.
    Cheers,
    HT

  • RFQ release strategy not triggered

    Hi,
    We have configured as follows,
    Communication structure:-Cekko-Bsart = AN (RFQ doc type)
    Created char with the above comm structure.
    Class with 032 and assigned char as below.
    Release groups,rel codes and two level of release.
    When i simulate release strategy, showing blocked and released.
    But when i create a RFQ and no release is triggered and when i checked in release rfqs(ME45) no suitable purchasing documents.What might be the mistake.
    Regards
    Kris

    Hi,
    Check you release procedure prerequisities & stateus in rel. strategy.
    check below link:
    [Re: PR Release strategy Problem]
    [With and w/o classification;
    [Re: release code deletion]
    SAM

  • Resetting RFQ Release Strategy

    Dear colleagues,
    We are using RFQ release to select appropriate bid among set of biddings. Suppose an RFQ is approved, letu2019s say RFQ number 10, within a set of RFQsu2019. After negotiations with vendorsu2019 new bids are made, letu2019s say RFQ number 20 and 30, which has fewer prices than the approved one. In this case RFQ release should be reset, but it does not.
    I know that SAP considers PO, RFQ, and Contract as purchasing documents and logic of release strategy are same.
    Is there any way to achieve this requirement?
    Regards
    Metin

    Hi,
    You are trying to use release for which it is not supposed to be.
    Release is for only for the approval of an RFQ before it is issued to Vendor.
    In your case if you are having multiple quotes for an item based on the negotiations carried out with vendor, the same should be updated to the existing RFQ created.
    For example you created RFQ-R1 for vendor V1 and RFQ-R2 for Vendor V2.
    When you first receive the quotations you maintain using ME47 for RFQ R1 and R2.
    Now when you negotiate with V1 and get a better price the same should be updated in R1.
    So this way R1 at any point of time will have the latest negotiated price.
    The item changes recorded when doing the changes can be viewed if you require. You may have to create a custom report to view these.
    Similarly the Me49 might need to be customized to suit to your comparison needs.
    Hope this clarifies.
    Regards

  • 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

  • Purchase Order Release Strategy didn't trigger

    Hi Gurus and SAP People!
    Good Day!
    I currently have a problem regarding one purchase order which didn't trigger a release strategy. I checked the classification/conditions/classes and it's all satisfied. I tried replicating the scenario in our Development server and I always end up triggering a release strategy.
    Moreover, as far as i know, the release procedure is not locked as it is one of the most commonly used release group and code. Can anyone have any ideas why that certain PO didn't trigger any release procedure upon saving?
    More details that might help.
    1. PO was initially on hold status then saved. (tried to replicate this as well and yet a release strategy was triggered)
    2. Upon saving, PO triggered an IDoc successfully. (my replication results always stayed "yellow" as it is still waiting to be released/approved before the actual Idoc generation (green)).
    3. Line item details had been changed between the PO being on hold and the actual saving. (but yet it still satisfies the release classifications)
    4. Line items came from PRs, Contracts, RFQs.
    Will greatly appreciate your help.
    Thank you very much!
    Regards,
    JV

    Hi Suzy!
    Thanks for the answer.
    I already checked the classification and searched our documentation repository if there were changes made and did not find any. Development and Production environment customization are the same.
    I forgot to include that after a few days the PO was created, they deleted one line item. That deletion made the PO trigger a release strategy.
    Nevertheless, the question still remains - why the PO didn't trigger any release procedure upon the initial saving.
    Regards,
    JV

Maybe you are looking for