Help on Indent Sales Order Creation - Missing Items in Purchase Requisition

Hi Experts,
We have Indent Sales setup where when we create Indent Sales Orders it will also create Purchase Requisitions. But we have encountered a lot of of missing items in the Purchase Requisition that are in Indent Sales. Have you encountered this kind of behavior? What are the usual suspects (configuration-wise) for this scenario?
Thanks for your Help!

hi,
please check the SCHEDULE LINES for those PR is getting generated and also for not generating.
PLEASE CHECK THE SCHEDULE LINE CATEGORY CONTROL FEATURES on the same
hope this clears your issue
balajia

Similar Messages

  • Sales order creation, Line item error

    Hi....
    Iam created one sales order with BAPI techniue.i.e type stand alone order.
    After creation VBELN generated successfully.
    Now, if i save the order from VA02 it was displaying following message in popup window...
    LINE ITEMS HAVING NO QUOTA OR TERM ATT
      Item   Material           Description
        10   1111-0             ABCD FR
    And.,
    In the conditions tab of the line items I want to insert a row i.e contract type and amount..,
    But..,
    for this Iam paaing entries as input to BAPI but not mapping on screen..,
    Also if i try to add them mannually showing following error..
    Requirements are not fulfilled for condition <given type>.
    As an abaper Iam not able to solve this problem, also functional people not availble here..,
    Any updates.......
    Thanks,
    Naveen.I

    Hi,
    This is due to the requirement routine assigned to the condition type in pricing procedure.
    Goto Tcode V/08.
    Here enter you pricing procedure. You can find it in sales order header : Tab - Sales (Pric. procedure)
    Enter this pricing proc in V/08
    When you select the procedurew & double click on control the procedure will be displyed
    Now look for you condition type & look in the colium "Reqt".
    Some number must be assigned, look for the logic inside the routine. If the requireemnt in logic is noit met the condition will not be populated
    Hope this helps you
    Regards
    Dhananjay

  • Relation btwn Sales order creation and automatically created Purchase Requi

    Hello Experts,
    The Purchase requisation is creating from Sales order, meaning, as soon as Sales order is SAVEing (say, SO_1), automatically a Purchase requisation (say, PR_1) will be created in the system. There is a Indicator filed in (PR) EBAN table, if its V, then this PR has been created from a Sales order. But, pls. let me know that,
    How I can know that PR_1 is created from SO_1? meaning, I want to know the link btwn these 2 corresponding docs! I hv seen VBFA table, but, did not find any!!
    thank you

    Hi,
    There is table called VBEP where U find Both fields
    i.e  VBEP- VBELN  sales order number  &
         VBEP-BANFN  Purchase requsition number.
    Regards,
    Sachin

  • Mass sales order creation using BAPI

    Dear All,
    Can anyone help in  mass sales order creation using Bapi BAPI_SALESORDER_CREATEFROMDAT2.
    For example if i want to create 3 sales order with three item per order . i am populating
    HEADER = 3 Records
    Item   = 9 records
    schedule = 9 records
    partner  = 1 record.
    Then after populating the records I am calling Bapi BAPI_SALESORDER_CREATEFROMDAT2
    to create order. It should have created three order but unfortunately it creates
    only one sales order. I debugged and found that records are correct both in header,
    item, scheudle and partners.
    Could you please guide me what I am missing for creation of mass orders.
    I appreciate your time and many thanks in advance.
    cheers
    chandra

    Hi Chandra,
    Do like this.
    Loop at Header table into wa_header.
    *-- Move BAPI Header data
    Loop at item table into wa_item where condition.
    *--  in this move all Item and Schedule line item  to the BAPI.
      At end of item .
    Use the below function modules.
    BAPI_SALESORDER_CREATEFROMDAT2
    BAPI_TRANSACTION_COMMIT.
    Endloop.
    Endloop.
    Regards,
    Balavardhan.K

  • Condition types in Sales order creation process

    Hi Friends...
    While creating the sales order with BAPI,
    What is the condition type i have to pass for pricing procedure...
    There many condition types for my pricing procedure, which one o have to select...
    Some of them are mannual, and other reuired, which one I have to pass?
    I want the information related to this condition types.., as here no SD consultant availble for me.
    Sales order creation, Line item error
    Thanks,
    Naveen.I

    Hi Friends...
       Please let me know is it mandatory to give condtion type while creating the sales order...?
    I am using BAPI_SALESORDER_CREATEFROMDAT2  to create my sales order...
    http://www.sap-img.com/abap/bapi-salesorder-createfromdat2.htm
    Thanks,
    Naveen.I

  • Sales Order quantity Must not exceed Purchase order quantity

    Dear Experts,
    My requirement is when i am creating a Purchase order giving referenece as Sales Order .. system must not allow the user to enter  more than Sales order quantity.
    Ex : Sales Order 1234
            Material : AAAA
            Quantity : 100
    while creating a Purchase order for Mat AAAA giving  reference of Sales order i.e 1234 and quantity 150 system must not allow user to enter more than sales order quantity . If user wants to create PO for 150 he must have to ammend the sales order from 100 to 150  is it possible.
    Kindly do the needful
    Regards
    abhi

    Dear Abhinav,
    First of all, Purchase Order will get created with reference to Purchase requisition (T. Code: VOV7 --> Item Cat.: TAS --> Tab: Transaction Flow --> Field: Automatic PO Creation), and not with reference to Sales Order.
    This is Purchase requisition, which gets created with reference to Sales Order; based upon settings in:
    T. Code: VOV6 --> Schd. Line Cat.: CS
    Order Type            NB    Purchase Requisition
    Item Category         5     Third-party
    Acct Assgt Cat.       X     All aux.acct.assgts.
    Now, coming to your requirement (based up on my inputs),
    My requirement is when i am creating a Purchase order giving referenece as Sales Order .. system must not allow the user to enter more than Sales order quantity.
    To Restrict Purchase requisition quantity in PO, then in T. Code: OMCQ
    Or, Path: SPRO > img > MM > Purchasing > Environment Data > Define Attributes of System Messages
    Here make following messages as Error;
    06 076 Materials of requisition & item & alr. ordered in full
    06 254 Order quantity greater than requisition quantity
    Now,  in Purchase Requisition, if it is created for 100 qty (with ref. to Sales Order) and if you adopt the same in Purchase Order and try to change the qty to 150, then system will not allow you change and throws the error.
    Best Regards,
    Amit

  • Create ecatt script for one sales order creation with multiple line items

    Hi ,
    I want to create a ecatt script for one sales order creation with multiple line items. Preferably SAP GUI.
    This selection of data will be from an external file/ variants which will have only one row of data in it.
    Firstly: I have to sort the external file having same PO Numbers in an order.Group them together.
    Second: I have to create sales order for those many line items having same PO Number.
    Best Regard
    Taranum

    Hi Micky
    Firstl you should upload the Line items for a particular sales Order in an Internal table
    and then pass that internal table to your BAPI during your coding corresponding to a particu;lar sales order
    In case of any issues pls revert back
    Reward points if helpful
    Regards
    Hitesh

  • Automatic Single Item multi-level planning on sales order creation

    Hi all,
    I am using strategy 50 and want planning for single item to be carried out at the time of sales order creation to avoid MRP run everytime sales order is created..In order to achieve it i checked Automatic Planning Indicator in "OVZG" for the requirement class "045" which is requirement class for sales order of strategy 50. But still unable to achieve the desired result..
    Please guide me through.
    best regards,
    shah

    HI shah,
    in sales order go to Procurement tab there u will get the requirement type. system will determine requirement class based upon following criteria
    1) by strategy group in material master
    2) if strategy group not there then MRP group
    3) if mrp group not there then material type
    4) by this also not able to fine the requirement type then special rule is used with the help of item category and mrp type
    5) if this also fails then it will go with item category only
    6) this also fails then it will give any requirement type
    hope this is clear
    regards
    ramakant

  • Creation of sales order from idoc; items referencing to different contracts

    Hi All,
    My requirement is to create sales order from an idoc.
    IF a sale order contains multiple items , then the order should be created with contract referenced
    -at the So item level, the valid contract found for each material is different
    hence am not able to use the following bapis
    BAPI_SALESORDER_CREATEFROMDAT2  is not triggering the copy controls.
    BAPI_SALESDOCUMENT_COPY  i can give only one reference document
    Please help
    Thanks
    Deepa

    Hi Deepa,
    Following link can help you for creating sales order with reference
    http://msdn.microsoft.com/en-us/library/cc185190.aspx
    http://www.sap-img.com/fu036.htm
    Award points if useful
    Thanks,
    Ravee..

  • The material account assignment group is missing in sales Order creation

    Hi Gurus,
    When creating the sales order the material account assignment group is not copied in the sales order line item. 
    For eg: when the sales order has 5 line item for one of the line item the material account assignment group is not getting copied. 
    I checked the material master - A/C assignment group was maintained.
    I checked the revenue account determination every entry is maintained with respect to GL account. 
    But even though while creating the sales order the line item does not have account assignment group. Due to this i could not able to release the billing doc to accounting.
    Please if any one can help in this regard to solve why the account assignment group is not copying in the sales order line item while creating.
    Thanks in advance.
    Jack

    Hi,
    May be the system is not updating the data. Try creating a new sales order to check. Also check the division of the product for which the acct *** grp is not showing.
    Check whether the acct assgt group which you have maintained in the matl master and that in the acct determination (VKOA) is the same.
    Reward points if solution helps.
    Regards,
    Allabaqsh G. Patil

  • Sales Order creation/ change date for the items

    I have a unique scenario and i need to get a Report for this
    A sales order is created for 4 line items.
    Out of these , for 2 line items a delivery is created. I need the sales order creation date and time  for these 2 items in a custom report
    Now the other 2 items go in to some kind of block- Now these are released by going in the sales order VA02 and after releasing the delivery is created. Again for these two items , i need the sales order change date as after a user goes and changes the sales order to remove the block only then delivery is created for these two items
    Also another scenario is the 2 line items go for back order and when we get stock  at tht time system confirms the stock and then the delivery is created for these. So also for this when this change occured i need to get the date for these 2 line items
    Can any one please suggest how to get this data  from the scenarios?
    I dont want to get the date when the delivery is created as i can get tht from the LIKP table. I need the sales order create and change dates for these.

    You may be aware, any changes to a document will be recorded in CDHDR (for header changes) and CDPOS (for item changes).  You can explore these two tables.
    thanks
    G. Lakshmipathi

  • User Exit during Sales Order Creation - New Line Item needed

    I have a situation during the process of sales order creation. If a Material in a line item has say 27 EA and the Base Unit is EA. But the Sales Unit is CSE. Then whenever the user enters 27 EA and presses enter he should get two line items.
    The first line item needs to convert to maximum number of CSE posible and the rest will be the second line item with the remaining EA. The order isn't important but that is what is needed. Question is how do I approach this problem and code my user exit accordingly and where do I code it.
    I was looking at SAPMV45A and saw the program MV45AIZZ which is meant as a user exit for any PAI event handling. If anybody has encountered this kind of requirement can you please share your view on this.
    I will definitely reward points for useful answers.
    Clark

    Hello Mahendra
    The requirement is as follows :
    PART 1:
    Sales Order Enter: 
    1.     When a line item is entered on a sales order (VA01 or VA02), at enter, check the sales unit of measure (VBAP-VRKME).
    •     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP.  TANN are free goods that should not be considered for consolidation.  TAPS & ZTAP are lower level materials as a result of product selection.  They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
    •     Do not check items where VRKME <> EA
    2.     If VRKME = EA, go to MARM for MATNR.
    3.     Go to record where alternate unit of measure (MEINH) = CSE, get the value from the numerator field (UMREZ).
    4.     Divide the order quantity (VBEP-WMENG) by UMREZ.
    5.     If the result is greater than 1.0, the customer has ordered more than one case and a new line item needs to be added to the sales order for the case quantity.
    6.     Add a new line to VBAP for the same material with the case quantity.  If not a whole value, the remainder of eaches (bottles) should update the qty on the first item on VBAP.
    •     Part 1 is relevant for order types ZCA, ZOR, ZSO, RE, ZSM
    PART 2:
    Batch Job to run prior to the Delivery Due List:
    1.     Read VBUK for Delivery Status (LFSTK) = A (delivery not processed).  Get all of the document numbers (VBELN).
    2.     Go to VBEP for those document numbers to get the goods issue date for the order.  There will be many records in VBEP for the same sales order.  Look at all orders with a goods issue date (WADAT) of next day.
    3.     Go to VBAK for those document numbers to see if there are multiple sales orders for the same Sold To party (KUNNR).
    4.     For customers who have more than one order in VBAK, search all line items (for all orders).  If there are no duplicate materials across sales orders, do nothing.
    •     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP.  TANN are free goods that should not be considered for consolidation.  TAPS & ZTAP are lower level materials as a result of product selection.  They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
    •     Do not check line items where reason for rejection (VBAP-ABGRU) is not blank
    5.     If there are duplicate materials, go through the same logic as in part 1.  If the quantity across the sales orders adds up to greater than one case, add the appropriate quantity to a new line item on the first sales order.   If there is a remainder qty, update the line item on the first sales order with this qty. In this case, the quantities on the second sales order needs to be closed out with a reason for rejection code of 50, ‘Line Item Consolidation’. If there is no remainder,  update the qty on this item directly.
    •     Part 2 is relevant for order types ZOR, ZCA, ZSM
    •     This batch job will have to be run manually for Day Pick orders.  The end of this program should automatically kick off the delivery due list for Day Pick orders, shipping condition 02.
    Business Justification:
    The business requires that like order line items be consolidated to one line item prior to the order going to the warehouse for picking.  This will aid in picking at the warehouse as well as result in the customer invoice not reflecting more than one line item for the same material.  In the case where the customer has truly ordered more than a case, i.e;, 1 case, 2 bottles, the documents in SAP will still reflect 2 lines.

  • Sales order creation for service items?

    Hi,
    My client is  a courier company and it wants to implement sap. You offer only  service how do you map in sap??.  can we create sales  order for service items.?. and how about the entire outbound process can be mapped?. Any ideas or insights or practical experience. Kindly share.
    Regards,
    Jothiswaran.

    Jothiswaran,
    I think it could be mapped with SAP CS - Sale of service functionality in R/3.
    Rough Idea:
    Create a Sales order  with Service product (Mumbai2chennai) with a Task list (Routing - for each stage). Let it triggers a Service order. Confirm each stage in Service order with Truck number for tracking. Once you complete the delivery, do TECO in Service order. May be advance billing or post billing.
    Try in SAP CS.
    Babu

  • BAPI - Problem in Sales order creation

    Hi Friends,
    I have problem in Sales order creation using BAPI ,I am getting a messsage - Error in creating document ,I have sent the code along with this mail ,can you help it out.
    Code:
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE kwmeng  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                             WITH HEADER LINE.
    Initialization.
    INITIALIZATION.
    v_text   = 'Order type'.
    v_text1  = 'Sales Org'.
    v_text2  = 'Distribution channel'.
    v_text3  = 'Division'.
    v_text4  = 'Sold-to'.
    v_text5  = 'Ship-to'.
    v_text6  = 'Material'.
    v_text7  = 'Quantity'.
    v_text9  = 'Plant'.
    Start-of-selection.
    START-OF-SELECTION.
    Header data
    Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    Partner data
    Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    Ship to
      partner-partn_role = 'WE'.
      partner-partn_numb = p_ship.
      APPEND partner.
    ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    Call the BAPI to create the sales order.
      CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
           EXPORTING
                sales_header_in     = header
                sales_header_inx    = headerx
           IMPORTING
                salesdocument_ex    = v_vbeln
           TABLES
                return              = return
                sales_items_in      = item
                sales_items_inx     = itemx
                sales_schedules_in  = lt_schedules_in
                sales_schedules_inx = lt_schedules_inx
                sales_partners      = partner.
    Check the return table.
      LOOP AT return WHERE type = 'E' OR type = 'A'.
        EXIT.
      ENDLOOP.
      IF sy-subrc = 0.
        WRITE: / 'Error in creating document'.
      ELSE.
    Commit the work.
        COMMIT WORK AND WAIT.
        WRITE: / 'Document ', v_vbeln, ' created'.
      ENDIF.
    Regards,
    Dinesh

    what messages u are gettting in RETURN ? Please check the RETURN tables data.
    [code]CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
    EXPORTING
    sales_header_in = header
    sales_header_inx = headerx
    IMPORTING
    salesdocument_ex = v_vbeln
    TABLES
    return = return
    sales_items_in = item
    sales_items_inx = itemx
    sales_schedules_in = lt_schedules_in
    sales_schedules_inx = lt_schedules_inx
    sales_partners = partner.
    Regards
    Prabhu

  • Sap afs - how to customize matrix grid in sales order creation

    Hello,
    can anyone help to understand how to customize the matrix grid shown at sales order creation/change (VA01 - AFS Item overview tab - Matrix entry pushbutton). Here system, starting from inserted material nr, shows all possible combination from material's sales grid. The requirement asks to manage the matrix grid before it is shown to the user.
    Thanks in advance for your help
    maurizio

    Hi
    It depends on master data of your material
    Max

Maybe you are looking for