Purchase requistion automaticaly creation

HI
I want to create purchase requisition with 100 line items with different plants,different materials,quantity,price.account assignment,assets,user need not want to all 100 line items enter manually in me51n t.code.is this possible to upload automaticaly.
Regards
Sam
Edited by: sadaraji on Mar 31, 2011 9:52 AM
Edited by: sadaraji on Mar 31, 2011 9:54 AM

Hi dear,
Consult with your ABAPer and check if u can do this with BAPI.But there also u have to created a flat file and then it is to be uploaded.

Similar Messages

  • Set up purchase requistions "Closed" automatically after creation of PO

    We have following requirement
    Purchase requistions should be "Closed" automatically after creation of Purchase order. Purchase orders are created manually.
    Is there any settings or config to achieve this?
    Thanks in advance

    Hello
    The closed indicator (EBAN-EBAKZ) could only be set manually within the transaction ME52N or when converting the purchase requisition into a PO. via transaction ME21 or ME21N.                                     
    In the case you use transaction ME21 or ME21N to create the PO with reference to purchase requisition the 'closed' flag has to be set manually. In ME21 before you adopt the item, in ME21N the indicator to close the PReq in ME21N is in the delivery schedule tab of the item details at the far right end of the window.                            
    In the change requisition transaction ME52N, set the close indicator.   
    In ME57, while creating a PO with reference to a requisition, set the close indicator on the item selection screen (SAPMM06E, 0125). 
    You are able to create multiple PO's from the same requisition;  however, once the total quantity of the PReq has been assigned to PO's, your quantity of the PReq will be 0.                                  
    In other words, when you go to ME21N or ME21 and you create with reference to a previously fully assigned requisition, you will be prompted to make an entry in the quantity field, as there is  nothing left on the requisition to pull from.  This should be an alert to the user that there are no selectable quantities available for the item.  This prevents double ordering.                                                                               
    If you want to prevent the requisition to be used again, you should set the closed indicator for the item in the requisition.  The closed indicator is never set automatically.  When creating a purchase order in reference to this requisition, you should select the 'open only' flag.  If the closed indicator has been set for the requisition, you will receive a message that no data satisfying selection criteria exist
    Thanks

  • Triggering an IDOC on Purchase Requistion creation

    I would like to trigger an IDOC upon purchase requistion create.   I seem to see only an idoc to create Purchase Reqs into SAP(inbound), nothing outbound.
    Basically, I want when a purchase req is created in SAP to trigger an IDOC.  I would then pick up that idoc to trigger an external business process flow.
    Thanks

    Hi
    Can you please elaborate on what business process you want to trigger??
    There is a way to trigger the follow-on processing for the purchase requisition using BADI ME_REQ_POSTED.
    Regards
    Prasad

  • Purchasing requistion dates are not reflecting in R/3

    Hi All,
    material created in R/3,here purchase requistion generated in R/3 & APO.
    Then in APO,after Rescheduling in detailed scheduling planning board new purchase requistion delievery date is not
    reflecting in R/3.
    Kindly revert back ASAP.
    Regards,
    Venkat.
    Edited by: venkat1215 on Jul 23, 2010 11:05 AM
    Edited by: venkat1215 on Jul 23, 2010 11:30 AM

    Venkat,
    You didn't answer my question.
    As a general rule of thumb, APO is much fussier about changing and synchronizing orders that were created in R/3.  If you have a choice, you should always create purchase reqs in APO (although cross-creation is supported, and can be made to work nicely if you are diligent).
    When you change an order in APO, and then publish the change to R/3, it is possible that the settings in R/3 will cause an issue with 'booking' the change.  One way to test this is to manually make the same change, but directly in R/3.  There should be no warnings or errors.
    Another thing to look at are the Application logs on both sides (SLG1) for possible failures that may give a clue.  Restrict to date and time interval where you know the proper update did not take place.
    Rgds,
    DB49

  • Without Purchase Requistion , Purchase Order should not be raised

    Dear All,
      Can any one tell me , How can i do the setting without purchase requisition , purchase order should not be raised.
    Regards
    Suresh

    Hi,
    1. Transcation code : OMET - Function authorization
    in that, there is one check box called REF TO PURCHASE REQUISTION under the section of possible reference object (2nd from top). Activate this check box.
    Assign this Function authorization key to the user profile.
    Now onwards, this specific user cann't create PO with out PR. 
    PR is mandatory for the PO creation for this user only. But other users can create PO, with out PR also.
    This is user level control
    2. Transcation: OMEC
    Select your document type and   note down some where filed selection key which is maintained for your document type.
    Transcation code :OMF4
    Navigation path : Spro-Materials Management-Purchasing-Purchase Order-Define Screen Layout at Document Level
    Select field selection key, which is identified in the first step and click on the details icon.
    Click on the "Reference data, item"
    set Purchase requisition as required (mandatory) entry.
    Now onwards, you cann't create PO with out PR number.
    This control is applicable for all the users. But for your document type only, which is used in the first step.
    For what are the document types used this field selection key, you can't create PO with out PR number.
    For other document types you can create PR with out PR number also.
    Regards
    KRK

  • Fixed ID indicator in Purchase Requistion

    Hi All ,
    Can any one please explain what is Fixed ID indicator in Purchase Requistion . Is there any impact on MRP if this indicator is not checked . I have a scenario where the STR Created from Sales Order is deleted but still requirement is getting generated at supplying Plant .
    Thanks

    Hi Laura
    The '*' is displayed on MD04 when a purchase requisition is considered firmed for MRP.
    A purchase requisition is firmed for MRP whtn the fixed indicator is set, however, there different circumstances where the purchase requisition can be firmed for MRP, even when the fixed indicator is not set.
    The following note describes under which circumstances a purchase requisition is firmed for MRP:
    2040378
    Fixed indicator in purchase requisition
    I'm copying the relevant information provided on this note below:
    If the Creation Indicator (ESTKZ) field is not 'B' (Material Requirements Planning), is not 'U' (Converted Planned order), and is not 'D' (Direct Procurement), the purchase requisition will be fixed automatically.
    If the Processing status (STATU) field is ‘B’ (PO Created) and the Quantity Ordered (BSMNG) field is greater than “0”, the purchase requisition will be fixed automatically.
    If the Processing Status (STATU) field is equal to 'A' (PO Created) and equal to 'L' (Created Scheduling Agreement), the purchase requisition will be fixed automatically.
    If the indicator “firmed for requirements planning” (t161s-fixbp) is set on the customizing of the release indicator assigned to this purchase requisition, it is considered fixed.
    If the Fixed indicator (FIXKZ) field is flagged, the purchase requisition will be fixed automatically.
    If the Version (REVNO) field is not blank, the purchase requisition will be fixed automatically.
    BR
    Caetano

  • Error while Creating PO from Purchase Requistion in Third Party  Sales

    Dear Team,
                          While Creating the Purchase Order from Purchase Requistion in Third Party Sales. When I am saving the PO I am getting the Error in GL Account Cannot be Used. I have disabled the field G/L Account in settings of Account Assignment Category of Third Party. Still I am facing that Error while Creating Purchase Order.  Can you guide me where we do this Assignment of G/L Account so that I can change the G/L Account.
    Thanks,
    Farhan.

    Dear Farhan,
    1. Go to T. Code: FS00 and enter GL number and Company Code and go to Tab: Create/bank/interest, write down the field status group.
    2. Go to T. Code: OBC4 and Select your Field Status Variant and Double Click: Field Status Group (From Left-hand Dialog Structure)
    Double-Click on to Field Status Group (as noted down from in Step 1).
    From Select group, Select Additional account assignments and make Earmarked Funds, as optional.
    Best Regards,
    Amit

  • Error in vendor selection while creating Purchase requistions

    Hi,
    I was using bapi_requestion_create to create purchase requistion with different quotas for different vendors.
    Ex: vendor A   with 60%
          vendor B   with 40%
    If the required quantity is 100 items then it has to split 60 items to vendor A and create seperate Puechase Requistion.
    and for 40items with another Purchase requsition.
    Currently iam able to split the noof purshcase requisiton but it was picking only with one vendor.
    MY Code :
    *******Split PRs with respect to Quota ************************
          data : lv_lines type i,
                 lv_qty type  p DECIMALS 4.
          lv_qty = it_oo-qty.
          DESCRIBE TABLE t_equp LINES lv_lines.
          IF lv_lines GT 1.
            clear : w_equp.
            loop at t_equp into w_equp
                          where qunum = w_equk-qunum.
              refresh : t_req_item.
              clear   : w_eord,
                        t_req_item[],
                        t_req_item.
              READ TABLE t_eord INTO w_eord
              WITH KEY matnr = it_oo_sum_purch-matnr_sap
                       werks = it_oo_sum_purch-plant
                       lifnr = w_equp-lifnr.
              if sy-subrc is initial.
                it_oo_purch-AGREE     = w_eord-EBELN. "To Fill ALV
                it_oo_purch-ITEM      = w_eord-EBELP. "To Fill ALV
                it_oo_purch-FORNEC    = w_equp-LIFNR. "To Fill ALV
                t_req_item-doc_type   = c_zbmr.
                t_req_item-pur_group  = it_oo-ekgrp.
                t_req_item-material   = it_oo_sum_purch-matnr_sap.
                t_req_item-plant      = it_oo_sum_purch-plant.
              t_req_item-AGREEMENT   = w_eord-EBELN.
              t_req_item-AGMT_ITEM   = w_eord-EBELP.
              t_req_item-FIXED_VEND  = w_equp-LIFNR.
              t_req_item-QUOTA_ARR   = w_equk-qunum.
              t_req_item-QUOTARRITM  = w_equp-qupos.
                t_req_item-gr_ind     = c_x.
                t_req_item-ir_ind     = c_x.
              t_req_item-MRP_CONTR   = 'NOV'.
                CONCATENATE it_oo_sum_purch-due_dte+4(4)
                            it_oo_sum_purch-due_dte+2(2)
                            it_oo_sum_purch-due_dte(2)
                            INTO t_req_item-deliv_date.
                t_req_item-QUANTITY   = ( w_equp-QUOTE / 100 ) * lv_QTY.
              endif.
    ********Rounding off values*******************
              data : lv_int(20) type c,
                     lv_dec(20) type c,
                     lv_tot(20) type c.
              clear : lv_int ,
                     lv_dec,
                     lv_tot.
              lv_tot = t_req_item-QUANTITY.
              split lv_tot at '.' into lv_int lv_dec.
              if lv_dec(1) ge '5'.
                lv_int = lv_int + 1.
              endif.
              t_req_item-QUANTITY = lv_int.
              APPEND t_req_item.
              clear : v_number.
      Create purchase requisition by group
              CALL FUNCTION 'BAPI_REQUISITION_CREATE'
                   IMPORTING
                        number            = v_number
                   TABLES
                        requisition_items = t_req_item
                        return            = t_return.
    ERRO
              IF t_return-type CO 'AE'.
                CLEAR: v_msg, v_x.
                CALL FUNCTION 'WRITE_MESSAGE'
                     EXPORTING
                          msgid = sy-msgid
                          msgno = sy-msgno
                          msgty = sy-msgty
                          msgv1 = sy-msgv1
                          msgv2 = sy-msgv2
                          msgv3 = sy-msgv3
                          msgv4 = sy-msgv4
                     IMPORTING
                          messg = v_msg.
                PERFORM zf_grava_log_erro_oo
                              USING it_oo_purch it_oo_sum_purch v_msg v_x.
    SUCESSO - Atualiza Tabela zsytmm_pr_po
              ELSE.
                CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
                     EXPORTING
                          WAIT = c_X.
                CLEAR: v_msg, v_x.
                CONCATENATE text-026  v_number INTO v_msg
                                      SEPARATED BY space.
                it_oo_sum_purch-QTY =    t_req_item-QUANTITY.
                PERFORM zf_grava_log_sucesso_oo
                          USING it_oo_purch it_oo_sum_purch v_msg v_x.
                CLEAR: zsytmm_pr_po.
                vl_item = c_00001.
                zsytmm_pr_po-banfn    = v_number.
                zsytmm_pr_po-bnfpo    = vl_item.
                zsytmm_pr_po-ebeln    = c_false.
                zsytmm_pr_po-ebelp    = c_false.
                zsytmm_pr_po-zshmode  = it_oo_purch-shipm.
                MODIFY  zsytmm_pr_po.
              ENDIF.
            endloop.

    Hi,
    You have to fill DES_VENDOR & FIXED_VEND of structure REQUISITION_ITEMS while calling BAPI.  But while going through your code,
    * t_req_item-FIXED_VEND = w_equp-LIFNR
    is commented, uncomment the same and add line for DES_VENDOR also.
    Regards
    Vinod

  • Error:-document is in transfer for purchase order..creation is not possible

    Hello,
    While doing confirmation of PO I am getting this error, saying "document is in transfer for purchase order..creation is not possible".
    can anyone please suggest me solution on this type of error?

    Hi,
    Is the PO in ORDERED status? Is there any confirmation posted for this PO which might be stuck (idoc failed to reach back end)?
    If it is a case of idoc failure, then reprocess the idoc and then do the next confirmation.
    regards,
    MRao

  • Purchasing: Restriction of creation of PO's on the basis of buyer / user

    Hi,
    We are currently working on a requirement in which the business is expecting to restrict the buyers / users from creating Purchase Orders of some specific GL natural accounts.
    Is there any functionality using which we can provide lock / check on this.
    As the business wants to achieve this lock, since the users (buyers) are using the same responsibility and those responsibilities might have their own independent locks on the usage of Balancing Segment Values and other Cross Validation Rules.
    But, we are looking for something specific which will restrict the creation of PO's based upon the login of user / buyer / PO Creator itself.
    Any inputs in this regard shall be of great help.
    Regards,
    Saurabh Singhal.
    Bangalore, India.

    Pl do not post duplicates - Purchasing: Restriction of creation of PO's on the basis of buyer / user

  • User Exit -- To include purchase requistion/purchase order in COOIS report

    In a MTO envirnoment, trying to include purchase requistion/purchase order
    with requested delivery date information in COOIS report. Is there a
    user exit for this ?

    Hi,
    Please follow this an Example:-
    The COOIS report (Order Info System) gives the complete information regarding Production Order like header report, Operation report, Component Report, document report. 
    This document deals with the addition of extra fields in the output display of COOIS. 
    For the demo purpose, I have added the material group (MATKL) for the production order material for header report. 
    BADI Name: WORKORDER_INFOSYSTEM
    Method: TABLES_MODIFY_LAY 
    In the method TABLES_MODIFY_LAY there are many table parameters for different data display of the production order .In this scenario only the header detail structure is being extended with append structure. 
    Add the extra fields to be displayed to through append structure to IOHEADER_TAB, here MATKL. 
    In the method write the code for updating the field value. 
    DATA : BEGIN OF st_matkl,
               matkl TYPE matkl,
               END OF st_matkl.
      DATA : st_header TYPE ioheader.
      LOOP AT ct_ioheader INTO st_header.
        IF NOT st_header IS INITIAL.
          SELECT SINGLE  matkl
                 FROM mara
                 INTO st_matkl
                 WHERE matnr = st_header-matnr.
        ENDIF.
        st_header-matkl = st_matkl-matkl.
        MODIFY ct_ioheader FROM st_header.
      ENDLOOP.
    Regards,
    Ravi

  • How to configure purchase requistion in third party sale pls send me detail

    dear expert
    how to configure purchase requistion in third party sale pls send me details. waiting your valuable reply
    vicky

    you can find the details in the below links
    Re: THird party sales complete scenario
    http://wiki.sdn.sap.com/wiki/display/ERPLO/PROCEDURETOCREATETHIRDPARTY+SALES
    http://www.sap-img.com/sap-sd/process-flow-for-3rd-party-sales.htm
    Regards

  • Unable to create a PO via Purchase Requistion

    Hi Gurus ,
    I am facing a Problem while creating a Purchase order with ref. to a Purchase Requistion.
    System is showing an error "Purchase requisitions  of   document_type  ZVS or item category L may not  be  assigned to purchase orders of   document type ZVS or item   category L".
    Doc. type of Pur. Req. & PO is ZVS
    Item Category for PR & PO is L
    Kindly Guide.
    Regards
    Honey

    Goto
    SPRO-> Materials Management -> Purchasing -> Purchase order -> Define Document Types
    Select your document type ZVS and click on allowed item categories & check whether item category L is assigned.
    Then select link purchase requisition - document type. Here check whether your purchase requisition document type ZVS and item category L combination is maintained.

  • Planned order and Purchase requistion both is generating in MRP

    Dear All,
    At the time of MRP explosion for Finished material, system is generating Planned order and purchase requistion, both,  for detailed material, (e.g. the BOM is a single level BOM). Whereas, I want to generate Purchase requistion for all. I am not getting that for which logic it generating Planned order as well as purchase requisition.
    Pl. explain.
    Thanks,
    Prasun.

    Hi Prasun
    The procurement proposal indicator dependes on the procurement type assigned in material master. If you assign prod Type F it will automatically generate PR. If the procurement type is E or X the system will generate plan order .
    This configured in Plan order type LA means it should be for in house production E.
    There are two ways of solving this. If you want always PR for FERT. Assign Proc type F in material master MRP view. It will always generate PR for that particular material.
    Or
    You can run MRP with planning mode 3 create PR in front screen.
    Regards
    J . Saravan

  • Planned order to purchase requistion

    Dear gurus,
                     I have configured the purchase requsition number ranges.While running MRP and while making manual purchase requistions i am getting the correct number range.but my pblm is while converting planned order to purchase requistion.i am getting the different number range.i checked in omi3.it is client specific number range.My requirement is in corresponding plant if i convert planned order to purchase req i should get the same number range as of mrp generated prs in that plant.
          Gurus please through some light
                                                      -guna

    Hi,
    Goto tcode OPPQ , select your plant .
    Select the number range field. Here you can find pur. req.
    Check this no range by selecting display icon.
    If the no range is different goto tcode OMI2 (for planning run)not OMI3 (manual), change your no range.
    Now run mrp & check the no. range.
    Regards,
    Dharma

Maybe you are looking for