RFQ Release

Hi,
My Requirement in RFQ Release strategy,
1)Needs to send the RFQ Before Releasing it to Vendor .
2)While creating PO if RFQ is not Released system should not allow to create ..
Pls Help Me,
Thanks,
Mohan

no.2 is automatically achieved, if no.1 is achieved
No.1 can be configured foillowing the existing procedures. If you already have a release strategy for external documents configured, you can use those, else create fresh characteristics, especially document category - since it would be A in your case, and assign them to a class. and follow up with configuration and agent assignment. Let us know if you have issues with these

Similar Messages

  • RFQ release procedure deactivation

    Hi Experts,
    I have configured PO release strategy & its working fine.
    But even its applicable to RFQ. My client dont want release strategy for RFQ.
    How to deactivate RFQ release stategy.
    Please suggest.
    Thanks,
    Jack

    Hi,
    Create NEW Release characteristics as purchasing document category CEKKO-BSTYP and during release strategy design you can keep VALUE as F for Purchase Order and save withy other vital release values.
    This will not effect release procedure for RFQ or automatically deactivate release process fro RFQ and only Applicable for Purchase Order ONLY!
    Regards,
    Biju K

  • 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

  • BAPI for RFQ Release

    Hi,
    Can Anyoone tell me BAPI for RFQ Release?

    Hi,
    There is no such kind of BAPI function / MASS release to process        
    RFQ.                                                                    
    Sorry that we can not provide a more positive answer.                   
    Regards,
    Edit

  • RFQ Release Doesnu2019t Run

    Dear colleagues,
    I have configured release strategy for RFQ with predefined release class for PO. In classification, besides PO characteristics, RFQ has only one active characteristic which is order type as u201CANu201D. RFQ is created through ME41 then Maintained through ME47. After all steps are completed RFQ doesn't release for approval. I checked CL24N, CL20N and OMGSCK and no error message is to be seen.
    I would like to hear your valuable thoughts.
    Best regards,

    Thank you for quick response,
    I forget to mention that I have also simulated RFQ release and no error message has detected.
    In overall release class we have 5 characteristics which are purchasing org, purchasing group, purchase order type, total net order value and collective number. For RFQ release strategy, only purchase order type, so far, is used any other characteristics are maintained as blank (empty) to determine agents.
    For PO release strategy, despite blankness of collective number characteristics, it works without a hitch.

  • RFQ release stratergy

    Hi Gurus,
    I have configured the release stratergy for PO ,RFQ,SES,And contract it is working fine, but when i add the character *Gnetw* (Net order value) RFQ release is not getting triggered.
    i have checked the release strategies all are showing green.
    what could be the reason, please help us in resolving the issue.
    Thanks,
    Naga.

    Hi Naga,
    RFQ release will not work if GNETW is one of your characteristics since there is no price determination in ME47. I had also same issue and open a ticket to SAP and the answer they have given is;
    u201CThe release strategy is determined when you create a RFQ in transaction ME41. In ME41 there is no price, so that CEKKO-GNETW can't be used here. The price is determined in ME47, but in ME47 there is no determination of the release strategy. So you will have to set net value as 0"
    But I asked them to change the logic and they said they forwarded my message to next support level for further processing.
    I will let you know when there is any progress.
    Regards

  • 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

  • How to Reject RFQ (Release Strategy)

    Hi,
    In ME29N , we have facility to Reject / Approve a Purchase order in Release staretgy tab .... but how to reject a RFQ .
    There is no option available in ME45 to Reject a RFQ, only we can release it.
    Need your help
    REGARDS
    SHREY

    hi
    rejection of rfq is not possible
    ru talking of calcelling or reversing the release
    if yes
    then in me45 select therel code then belowt that tick on cancel release
    execute ,select ur po and click on cancel release
    regards
    kunal

  • 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

  • PO Creation without RFQ Release-USER EXIT

    HI Gurus,
    if i am creating PO with ref to Released RFQ
    then system should allow
    if PO created with non released RFQ then system should not allow
    this is requirement
    Standard is we can create PO with Ref to Release/non Releae RFQ
    How to solve this issue? is there any USER EXIT available ?

    Hi
    Have you configured release strategy for the PR ? please check and whether the PR is going for the approval . In standard system if the release strategy is applied , system will not allow you to make PO using an unreleased PR.
    If PR is not going for the approval such PRs can be used to create PO .Check the characterstics and the values for the PR which are subjected to approval process.
    GKK

  • Exit / BADI for RFQ Release (ME45)

    Hi all,
             I need an exit or badi when an RFQ got released.
    Can anybody please help me to find the badi when an RFQ has been released.
    Thanks & Regards.
    Ranganadh.

    Hi,
    Exits for RFQ are following-
    AMPL0001            User subscreen for additional data on AMPL
    ME590001            Grouping of requsitions for PO split in ME59
    MEETA001            Define schedule line type (backlog, immed. req., preview)
    MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
    MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
    MEQUERY1            Enhancement to Document Overview ME21N/ME51N
    MEVME001            WE default quantity calc. and over/ underdelivery tolerance
    MM06E001            User exits for EDI inbound and outbound purchasing documents
    MM06E003            Number range and document number
    MM06E004            Control import data screens in purchase order
    MM06E005            Customer fields in purchasing document
    MM06E007            Change document for requisitions upon conversion into PO
    MM06E008            Monitoring of contr. target value in case of release orders
    MM06E009            Relevant texts for "Texts exist" indicator
    MM06E010            Field selection for vendor address
    MM06E011            Activate PReq Block
    MMAL0001            ALE source list distribution: Outbound processing
    MMAL0002            ALE source list distribution: Inbound processing
    MMAL0003            ALE purcasing info record distribution: Outbound processing
    MMAL0004            ALE purchasing info record distribution: Inbound processing
    MMDA0001            Default delivery addresses
    MMFAB001            User exit for generation of release order
    MRFLB001            Control Items for Contract Release Order
    LMEDR001            Enhancements to print program
    LMELA002            Adopt batch no. from shipping notification when posting a GR
    LMELA010            Inbound shipping notification: Transfer item data from IDOC
    LMEQR001            User exit for source determination
    LMEXF001            Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001            Customer-Specific Source Determination in Retail
    M06B0001            Role determination for purchase requisition release
    M06B0002            Changes to comm. structure for purchase requisition release
    M06B0003            Number range and document number
    M06B0004            Number range and document number
    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
    Regards,
    Sujit

  • RFQ Release Process

    Hi,
    Please tell me when Release strategy triggers for RFQ
    at the time of sending  RFQ to Vendor?
    or
    at the time of comparision of Comparision?
    or
    at the time of updating the inforecord
    Thanks
    Prasad

    Is it correct?
    why i am not getting?
    I maintained the required characteristic also.
    Thanks,
    Prasad

  • Rfq Releasing not working

    Hi,
    I kept release strategy for Rfq and Purchase Order,But Iam able to refer RFQ for creation of Purchase Order without Releasing RFQ through document overview.How can i Resolve it..

    Hi,
    You can try putting check in PO creation by implementing BAdi "ME_PROCESS_PO_CUST" using "PROCESS_ITEM" method.

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

    Dear Sappers,
    I'm configuring RFQ release.I've taken charcteristics as Purchase group and assign the respective values.In Class I've maintained the PO release i.e net order and RFQ i.e. release group.In Release Strategy, I'm created two different release group.One for PO and the other for RFQ.But in Release Strategy,when I'm maintaining my release group with release code, in classificatin RFQ strategy is not picking.
    What is the problem??Any where I skip any steps.
    Thanks & Regards
    PKB

    Individual Release of Purchase Requisitions
    Choose Purchase requisition ® Release ® Individual release.
    Enter the requisition number and your release code.
    Press ENTER .
    The item overview appears. Here you can make changes.
    Choose Goto ® Release info ® Release options to establish which items you can release.
    Select the item to be released and choose Edit ® Release ® Set to release the item. If the item belongs to a Complete Purchase Requisition, releasing the item will simultaneously cause all other items to be released.
    You can cancel (revoke) the release and reinstate the previous release status. To do so, choose Edit ® Release ® Cancel.
    Save the release.
    Collective Release of Purchase Requisitions
    Choose Requisition ® Release ® Collective release.
    The selection screen for collective release appears.
    Enter your release code and any other selection criteria.
    Choose Program ® Execute to display the requisition items or Complete Purchase Requisitions awaiting release.
    Decide whether you wish to release all items or complete requisitions at once or release - and possibly change - individual items.
    u2013 All
    Choose Edit ® Select ® Select all.
    u2013 Individual
    Select the item and choose Goto ® Individual release.
    The item detail screen is displayed.
    At this point, you can make changes.
    You can cancel (revoke) the release and reinstate the previous release status. To do so, choose Edit ® Release ® Cancel.
    Save the release.
    Hope this helps you. Iam new to sap. So pls neglect if Iam wrong.
    ashwin_.

Maybe you are looking for

  • Outlook-crashed

    Dear Concern, I have been using Outlook 2010 since July 2014. Certainly last Saturday my outlook crashed. I had no back up. All my important official mails lost. I am in huge problem. But my HP system is all fine. Please assist in recovering back the

  • How can I fix incorrect connections caused by duplicate file names?

    I have many slides, scanned over the past 10 years, with duplicate file names and filed by date.  I converted my Elements 9 from PC to iMac and many incorrect connections occured.  Is there a way I can correct these connection errors?  This problem i

  • ORA-24777 when trying to call multiple Oracle SPs...

    I had a SP in Oracle that called another SP in a SQL Server DB via DBLink. I was calling the Oracle SP from VB.NET (3.5) and because of transaction commiting I was not able to do this, so I removed the SQL SERVER SP call from inside the Oracle SP. Ho

  • Maverick. Mirroring Screen to TV Airplay Icon Not visible in Menu bar

    Hi, I recently upgraded my OS to Maverick 10.9.1 from Snow leopard. My Laptop is a Macbook 13" Aluminium Late 2008. How do I get the Airplay Icon to appear in the Menu Bar so that I can Mirror whats on my macbook to my Television. This is the only re

  • How do I convert .mkn files I created in Lion

    how do I convert notepad .mkn files I created in Lion to something I can past into Word.