Making RFQ mandatory for creation of purchase order

Hi,
I need to set up the following:
1. For specific purchase order document types, RFQ should be mandatory i.e. it should not be possible to create purchase order before RFQ is created.
2. Purchase orders can be created only if RFQ is approved.  How can i set up the release strategy in RFQ?
Thanks in anticipation of your reply.

Hello Sameet,
1. You can use default parameter EVO to make the RFQ manadatory for purchase order. In the parameter you need to flag mark "reference to reference document " indiactor on Fast processing tab and assign this parameter to the user profile.
2. For setting up RFQ approval process, please follow the steps:
You must perform the following steps:
1.  Create characteristics and classes
        For more on this topic, see Edit Characteristics and Edit Classes.
Note
If you wish to link your release procedure to workflow, you must perform steps 2 and 3. You make these settings in Customizing for Business Workflow (Basis -> Business Management).
Otherwise, continue with step 4.
2.  Define organizational plan
        For more on this topic, see Edit Organizational Plan.
3.  Assign standard tasks and activate event-receiver linkage.
        For more on this topic, see Perform Task- Specific Customizing.
4.  Set up release procedure for RFQs
    a)  Create release group
    b)  Create release code
    c)  Create release indicator
    d)  Create release strategy
Hope this helps
Regards
Arif Mansuri

Similar Messages

  • Reg bapi for creation of purchase order

    hai to all,
    i have to upload purchase orders from  legacy file to R/3 system
    certain order having more than 50 line items
    so please any one send me <b>stardard bapi program or bdc program for me21n</b> transaction which will suitable for my senario.
    please send asap
    regards
    vijay

    hai
    i am trying to create po using bapi
    the following code explains
    constants : c_x value 'X'.
      data: del_date type sy-datum.
      data: pohead  type bapimepoheader.
      data: poheadx type bapimepoheaderx.
      data: exp_head type bapimepoheader.
      data: t_return_out  type table of bapiret2 with header line,
            wa_return_out  TYPE bapiret2.
      data: poitem  type table of bapimepoitem with header line.
      data: poitemx type table of bapimepoitemx with header line.
      data: posched  type table of bapimeposchedule with header line.
      data: poschedx type table of bapimeposchedulx with header line.
      data: ex_po_number type bapimepoheader-po_number.
    Header Level Data
      pohead-comp_code = '1011'.
      pohead-doc_type   = 'NB'     .
      pohead-creat_date = sy-datum   .
      pohead-vendor = 'A1138'.
      pohead-purch_org = 'DOMS'.
      pohead-pur_group = 'MFR'.
      pohead-langu      = sy-langu   .
      pohead-doc_date   = sy-datum.
      poheadx-comp_code  = c_x.
      poheadx-doc_type   = c_x.
      poheadx-creat_date = c_x.
      poheadx-vendor     = c_x.
      poheadx-langu      = c_x.
      poheadx-purch_org  = c_x.
      poheadx-pur_group  = c_x.
      poheadx-doc_date   = c_x.
    Item Level Data
      poitem-po_item  = 1.
      poitem-material = '000000000100001079'.
      poitem-plant    = 'HO01'.
    poitem-stge_loc = ''.
      poitem-quantity = 1.
      append poitem.
      poitemx-po_item    = 1.
      poitemx-po_itemx   = c_x.
      poitemx-material   = c_x.
      poitemx-plant      = c_x .
      poitemx-stge_loc   = c_x .
      poitemx-quantity   = c_x .
      poitemx-tax_code   = c_x .
      poitemx-item_cat   = c_x .
      poitemx-acctasscat = c_x .
      append poitemx.
    Schedule Line Level Data
    posched-po_item        = 1.
    posched-sched_line     = 1.
    posched-del_datcat_ext = 'D'.
    del_date = sy-datum + 1.
    write del_date to posched-delivery_date.
    posched-deliv_time     = '000001'.
    posched-quantity       = 1.
    append posched.
    poschedx-po_item        = 1.
    poschedx-sched_line     = 1.
    poschedx-po_itemx       = c_x.
    poschedx-sched_linex    = c_x.
    poschedx-del_datcat_ext = c_x.
    poschedx-delivery_date  = c_x.
    poschedx-quantity       = c_x.
    append poschedx.
      call function 'BAPI_PO_CREATE1'
           EXPORTING
                poheader         = pohead
                poheaderx        = poheadx
                testrun          = ' '
           IMPORTING
                exppurchaseorder = ex_po_number
                expheader        = exp_head
           TABLES
                return           = t_return_out
                poitem           = poitem
                poitemx          = poitemx.
               poschedule       = posched
               poschedulex      = poschedx.
    call function 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
               wait = 'X'.
    if not ex_po_number is initial.
       call function 'DEQUEUE_ALL'.
    else.
       call function 'DEQUEUE_ALL'.
       message i036.
    endif.
    **endform. " create_po
    IF ex_po_number IS NOT INITIAL.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
          PERFORM show_result.
    ELSE.
          CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
          PERFORM show_result.
        ENDIF.
    *&      Form  show_result
          text
    -->  p1        text
    <--  p2        text
    FORM show_result .
      LOOP AT t_return_out INTO wa_return_out.
        write : ex_po_number.
        WRITE : / wa_return_out-type,
                / wa_return_out-id,
                / wa_return_out-number,
                / wa_return_out-message,
                / wa_return_out-log_no,
                / wa_return_out-log_msg_no,
                / wa_return_out-message_v1,
                / wa_return_out-message_v2,
                / wa_return_out-message_v3,
                / wa_return_out-message_v4,
                / wa_return_out-parameter,
                / wa_return_out-row,
                / wa_return_out-field,
                / wa_return_out-system.
      ENDLOOP.
    <b>iam geting the error such that</b>
    E                                                                            
    BAPI                                                                         
    001                                                                          
    No instance of object type PurchaseOrder has been created. External reference:
    000000                                                                       
    PurchaseOrder                                                                
    POHEADER                                                                     
            1                                                                 
    E                                                                         
    ME                                                                        
    062                                                                       
    Account assignment mandatory for material 100001079 (enter acc. ***. cat.)
    000000                                                                    
    100001079                                                                 
    POITEM                                                                    
    <b>how to correct this error</b>
    regards
    vijay

  • Field "Batch" mandatory for components in Purchase Order

    Hi,
    If a PO with item category 'L' subcontracting is created, the system explodes the material BOM for the material being purchasesd. In the subcreen for components in the purchase order (as determined by BOM explosion), there is an option to assign batches for each component. I want to make the batch field mandatory so that when the PO is created, the user has to input batches. How can this be accomplished? Help is appreciated, thanks.
    Regards

    1. All components are batch managed.
    2. All materials are stored in batches.
    3. The reason for this requirement is that if batch numbers for components are not specified in PO, when GR is done for finished good received from subcontractor, subcontractor stock is not consumed.
    E.g. 100 KG of component is posted to subcontractor stock (mvt. 541)
    PR -> PO created. No component batches entered in PO. GR posted for finished good. Stock balance updated for finished good but MMBE still shows 100 KG of component stock with subcontractor. If batch numbers are entered for components in PO, then stock at subcontractor end is consumed.
    If someone can tell me how to fix this without entering batch numbers for components in PO I wil be just as happy.
    Regards

  • Do you have any idea what is the BADI for creation of Purchase Order?

    Hi Gurus, I would like to ask regarding the BADI for the P.O creation in SRM. I have a requirement that if the Account Assignment Type is "asset" it should tick the checkbox (goods receipt/confirmation of performance of service) in the related documents tab of item.  Thanks a lot. I hope you can help me gurus.

    Thanks for the help.

  • Creation Of purchase order

    I want to create purchase orders using LSMW. But i am unaware of standard object or BAPI to do the same. I got it in the list present in LSMW but i am unable to use them..getting errors.So can anybody tell me process for creation of purchase order using LSMW?

    Check this thread.
    LSMW For T-code ME21N
    Regards,
    Maha

  • Automatic creation of purchase orders at goods receipts

    Dear guru ,
    I want to create purchase order when i execute GR Returns (mvt 161).
    Where I define the purchase order document type that I want to automatic create ?
    Thanks.

    Dear,
    Before configuration of setting for creation of Purchase Order automatically, consultant needs to under stand the business requirement and he should be aware of the difference between the different components of Material Management. Such as difference between creation of purchase order automatically in Purchasing and creation of purchase order automatically in Inventory Management. In SAP we can take this activity in both the sub components (Purchasing as well as in Inventory Management).
    By this time, I hope that you have understood that there are different settings for each of these components and we have to configure two different set of information to meet each requirement separately. Hence let me define this activity as follows:
    Create Purchase Order Automatically in Purchasing
    For creation of purchase Order automatically from Purchase Requisitions we need to do the following additional settings in addition to our standard ones.
    Activate u2018auto PO' indicator for material master
    Activate u2018auto PO' indicator for vendor master
    Create Purchase Requisitions using T Code ME51 or ME51N
    Use T. Code ME59 or ME59N for auto conversion of PR into purchase order
    Create Purchase Order Automatically in Inventory Management
    For creation of purchase Order automatically in Inventory Management we need to do the following settings which are independent of the setting what we do in Purchasing for creation of automatic PO from PR.
    Define one of the purchase organizations as Standard Purchase Organization
    Assign your plant to Standard Purchase Organization
    Maintain purchasing information record with price
    Maintain the indicator for movement types 101 & 161
    Define Default Values (MB01) for Document Type
    Now you can enter a goods receipt without entering the purchase order number, a purchase order will be created automatically when you post the goods receipt. All such goods receipt will be valuated at the price maintained in the purchasing information record.
    First you can try this with T. Code MB01 if it is working then try with T. Code MIGO, if you face any error or functionality is not working check with your basis consultant some authorization or some patches may be missing. Ask him to apply all relevant patches.
    Try using automatic PO for 161 movement for transaction MB01. For MIGO Goods return, its not allowed to create automatic PO due to system settings. This info as I know.
    Regards,
    Syed Hussain.

  • Automaticf creation of purchase order through pr

    Dear Consultants,
    system is not creating automatic  purchase order. in me59n i am getting the following error
    Requisition could not be converted
    i have done the following setting for automatic creation of purchase order
    1. in materil master record i have checked auto po.
    2. in vendor master record i have checked automatic purchase order
    3. i have created purchase info record with the combination of material vendor purchase organization.
    4. in source list i have fixed the vendor in me01
    5. in source determination under define regular vendor i have checked the box against the required plant.
    kindly let me know what all other configurations are required for creating automatic purchase order through purchase requisition
    Regards/ Siri

    Hi
    Is this purchase requisition created during MRP run??
    If yes then have you marked the sourcelist record for this vendor as MRP relevant??
    If the purchase requisition is generated manually then whether the source of supply was assigned in the PR??
    In ME59N, the PR would be converted to PO if the PR has the assigned source of supply.
    Regards
    Prasad

  • BOM Selection Mandatory while creation of Production Order

    Hello Friends,
    I would like to know that is there any option other than production version which makes it mandatory to have valid BOM must for creation of Production order / coversion of planned order to Production order.
    I have tried with Production version option but it doesnt throw any error in case BOM with inactive status has been selected in it & also Production order gets created & released.
    Before going for user exit / enhancement option, I just wanted to ensure that it is not possible with standard SAP.
    Kindly share your views on the same.
    Your urgent replies will be highly appreciated.
    Regards,
    Tejas

    Hello Tejas,
    I think this is standard SAP Behaviour.
    Try with following exits:
    PPCO0018
    PPCO0012
    Also check out the following link:
    [How To Make BOM Mandatory while creating Production Order;
    Regards,
    Vinod

  • Creation of Purchase order - set net price in display mode

    Hello,
    During the creation of purchase order from contract or DA (ME21N-ME59N),  I want to set the net price in display mode (under any conditions) .
    Is there a parameter setting or a point of modification to make ithis?
    Thanks for your contribution.
    JLC

    Check for existing screen layout name from below settings -
    Goto SPRO -> IMG Settings -> Materials Management -> Purchasing -> Purchase Order -> Define Document Types
    Check for Field selection key against the PO Type.
    Then goto below setting -
    SPRO -> IMG Settings -> Materials Management -> Purchasing -> Purchase Order -> Define screen layout at document level
    Select the screen layout / Field selection key in this setting and modify the field selection group Quantity and price. Make Price and price unit as display only as per your requirement.

  • Authority check on Creation of Purchase order usin badi BBP_ITEM_CHECK_BADI

    hi all,
    i have to apply authority checks on creation of Purchase order and shopping cart in SRM using badi BBP_ITEM_CHECK_BADI.
    i have applied checks on creation of shopping cart   using this badi which have some filters but how to apply on purchasing order using BBP_ITEM_CHECK_BADI.

    hi,
      You can use the BBP_DOC_CHECK_BADI.
    BR,
    Disha.
    Pls rewar points for useful answers.

  • Creation of  purchase order automatically  by taking  purchase requesition

    Hello Gurus
    Is it possible to create purchase order  automatically  by taking purchase  requesition  no from  sales order?
    i checked in all the  forms  couldn't find  any answer .
    thank you  in advance
    regards
    venkat

    Hi Venkat,
    When you save a sales order that contains one or more third-party items, the system automatically creates a purchase requisition in Purchasing. Each third-party item in a sales order automatically generates a corresponding purchase requisition item. During creation of the requisition, the system automatically determines a vendor for each requisition item. If a sales order item has more than one schedule line, the system creates a purchase requisition item for each schedule line.
    Purchase orders are created from purchase requisitions in the usual way. But If you want the Purchase orders to be created automatically, then you should automate the creation of purchase order by creating a job or using workflow. Other wise to create a PO from PR use ME57. A third-party order is usually created referencing a third-party item in a purchase requisition. You can create purchase orders in this way individually or collectively. For Configuring Automatic PO kINDLY PLEASE LOOK into this.
    "http://help.sap.com/saphelp_47x200/helpdata/en/94/da2e3b2bdab96be10000000a114084/frameset.htm"
    Kindly please let me know If you need any more information on this.
    Regards,
    Ram Pedarla

  • How to create a Inbound delivery type for a special  purchase order type

    Hi,
    I try to create a special Inbound delivery type for a special purchase order type (a transfer purchase order).
    In SD module, I can créate a special outbound delivery and precise the sale order type, but I don't manage to do it for a Inbound delivery type.
    Do you know if i can do it without specifiq?
    Regards,
    Roselyne

    Hi Roselyne,
    What you experienced is standard system behavior. Inbound delivery type is uniquely assigned to confirmation control key. You can only specify confirmation control key on item level in PO. The assignment of Delivery type can be seen in the following table:
    T163D
    IBTYP EBTYP LFART  RETDLV
    1        AB                      X
    2        LA        EL           X
    3        GW       EG
    The field T163D-IBTYP is checked in different programms. For example in programm RM06ENAB (TA: ME92F). If you insist to customize the determination of delivery type by PO type, I strongly suggest you discuss with the Application consultants before making the modifications to ensure it won't impact other areas.

  • Auto creation of purchase orders in background

    Hi,
    Can anyone help me with auto creation of purchase orders in background while saving production order as in standard sap only purchase requisition is getting created.

    Hi,
    Yes according to standar SAP only requisitions get created while saving production order ..........if you want to have Purchase order also to be created you can approch this way...
    1.     use exit PPCO0001
    2.     fm EXIT_SAPLCOBT_001
    create a background job id in SM36 .....call the methof for external event triggering
    CALL METHOD cl_batch_event=>raise
        EXPORTING
          i_eventid                      = 'ZME59'
          I_EVENTPARM                     = V_MANDT
        EXCEPTIONS
          excpt_raise_failed             = 1
          excpt_server_accepts_no_events = 2
          excpt_raise_forbidden          = 3
          excpt_unknown_event            = 4
          excpt_no_authority             = 5
          OTHERS                         = 6.
    Thanks,
    Shailaja Ainala.

  • MULTI LEVEL REPORT FOR STOCK TRANSPORT PURCHASE ORDER

    Hi,
    I will have lot of stock transport purchase orders,like md4c transaction where we get multilevel report for sale order/production order,is there any report for stock transport purchase orders.its urgent kindly help

    goto purchase order history tab
    you can see all the details of PO-deluvery-GI, GR, imvoice. Click on delivery, you can see the billing document throughdocument flow button.
    This function is not availilable for production order, hence we have MD4c.

  • How to setup a release strategy for store generated purchase order

    Hi there,
    Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
    Greatly thank for your help.
    Kind Regards,
    2tea

    Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
    PO RELEASE STRATEGY
    The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data Table name CEKKO Field name GNETW and press enter
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group Rel. Object Class Description
    02 REL_PUR Rel. Strategy for PO
    Release codes - New entries
    Grp Code
    02 01
    Release indicators
    Release indicators Release Description
    0 Blocked
    1 X Release
    Release Strategy
    Release group 02
    Rel.strategy 01
    Release codes 01
    Release status 01
    Classification Choose your check values
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order.
    Regards,
    Ashok

Maybe you are looking for