[BAPI] Reading outbound deliveries including item data

I'm looking for the correct BAPI to read all outbound deliveries that need to be picked including the item data (material, batch, quantity).
Thanks in advance

Hi,
I believe there is no BAPI for reading the outbound delivery details..Atleast in my system..(4.6C)..
You can create a custom RFC FM and call the below function module for the delivery details..
SD_DELIVERY_VIEW
Thanks,
Naren

Similar Messages

  • Passing Item data to BAPI BAPI_REQUIREMENTS_CREATE

    Hello Experts,
    Requirement to upload data from xcel sheet to SAP. Upload of Planned independent requirement(PIR) in the Plant
    Please help as i am not able to pass values into BAPI  EXPORT PARAMETER "requirements_item" and TABLE PARAMETER "requirements_schedule_in"
    my test data is:
    COKE1     2012-2013     20120201     10     TON
                                       20120301        35     TON
    COKE2     2012-2013     20120201     10     TO
                                         20120301     35     TO
    ..CODE
    form BAPI_REQUIREMENTS_CREATE.
    LOOP AT lt_export_data INTO wa_export_data.
       CLEAR wa_t5.
       CLEAR wa_t4.
             wa_t5-MATERIAL    = wa_export_data-MATERIAL.
             wa_t5-PLANT       = 'ES01'.
             wa_t5-REQU_TYPE   = 'VSF'.
             wa_t5-VERSION     = 'AB'.
             wa_t5-REQ_NUMBER  = wa_export_data-Req_Num.
             APPEND wa_t5 to lt_t5.
             wa_t4-DATE_TYPE   = '3'.         "Monthly
             wa_t4-REQ_DATE    = wa_export_data-Date.
             wa_t4-REQ_QTY     = wa_export_data-Quantity.
             wa_t4-UNIT        = wa_export_data-UNIT.
             APPEND wa_t4 to lt_t4.
             CLEAR wa_export_data.
    ENDLOOP.
    CALL FUNCTION 'BAPI_REQUIREMENTS_CREATE'
               EXPORTING
                 requirements_item                 = wa_t5
               TABLES
                 requirements_schedule_in    = lt_t4
                 return                                     = lt_return.
    I have the values in lt_t5 and lt_t4, now how to pass them to get desired result.
    Regards.
    Puneet Jham

    Try this.
    i got the sucess result as i want.
    DATA: I_BAPISITEMR TYPE STANDARD TABLE OF BAPISITEMR WITH HEADER LINE.
      " Item data
      DATA: I_CM60R TYPE STANDARD TABLE OF CM60R WITH HEADER LINE.
      " Requirements parameters
      DATA: I_BAPISSHDIN TYPE STANDARD TABLE OF BAPISSHDIN WITH HEADER LINE.
      " Schedule line data input
      DATA: I_BAPIRETURN1 TYPE STANDARD TABLE OF BAPIRETURN1 WITH HEADER LINE.
      " Return parameter
      DATA: I_MRP_AREA TYPE STANDARD TABLE OF BAPISITEMR WITH HEADER LINE.
    **If requirement already Exist then UPDATE those Req.
      DATA: U_REQUIREMENTS_SCHEDULE_IN TYPE STANDARD TABLE OF BAPISSHDIN WITH HEADER LINE.
      DATA: U_BAPIRETURN1 TYPE STANDARD TABLE OF BAPIRETURN1 WITH HEADER LINE.
    **If requirement already Exist then UPDATE those Req.
    *local data declaration
      DATA: ZREQ_DATE TYPE SY-DATUM .
      DATA: ZREQ_NUM TYPE STRING.
      DATA: ZYEAR_DATA TYPE STRING ,
            ZMONTH_DATA TYPE STRING .
      ZYEAR_DATA = ZYEAR.
      ZMONTH_DATA = ZMONTH.
      DATA: I_MATERIAL TYPE MARA-MATNR ,
            I_IN_ME1 TYPE MARA-MEINS ,
            I_OUT_ME1 TYPE MARA-MEINS ,
            I_MENGE1 TYPE EKPO-MENGE .
      DATA: OUT_E_MENGE TYPE EKPO-MENGE .
      DATA: W_SINGLE TYPE MEINS .
      CONCATENATE ZYEAR_DATA ZMONTH_DATA INTO ZREQ_NUM SEPARATED BY '-' .
      LOOP AT IT_FINAL INTO WA_FINAL.
        I_MATERIAL = WA_FINAL-ZMATERIAL.  "Read from internal table
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            INPUT  = I_MATERIAL
          IMPORTING
            OUTPUT = I_MATERIAL.
        SELECT SINGLE MEINS FROM MARA INTO W_SINGLE WHERE MATNR EQ I_MATERIAL .
        I_IN_ME1 = WA_FINAL-ZQTY_UNIT . " read from internal table
        I_OUT_ME1 = W_SINGLE  .  "fetch from query
        I_MENGE1 = WA_FINAL-ZPL_QTY . "read from internal table
        CALL FUNCTION 'MD_CONVERT_MATERIAL_UNIT'
          EXPORTING
            I_MATNR              = I_MATERIAL
            I_IN_ME              = I_IN_ME1
            I_OUT_ME             = I_OUT_ME1
            I_MENGE              = I_MENGE1
          IMPORTING
            E_MENGE              = OUT_E_MENGE
          EXCEPTIONS
            ERROR_IN_APPLICATION = 1
            ERROR                = 2
            OTHERS               = 3.
        IF SY-SUBRC <> 0.
          CONTINUE.
        ENDIF.
        I_BAPISITEMR-MATERIAL = WA_FINAL-ZMATERIAL .
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            INPUT  = I_BAPISITEMR-MATERIAL
          IMPORTING
            OUTPUT = I_BAPISITEMR-MATERIAL.
        I_BAPISITEMR-PLANT = WA_FINAL-ZPLANT.
        I_BAPISITEMR-MATERIAL_VERSION = '00' .
        I_BAPISITEMR-REQ_NUMBER  = ZREQ_NUM.
        I_BAPISITEMR-VERSION = '00'.
        I_BAPISITEMR-REQU_TYPE = 'LSF' .
        I_BAPISITEMR-VERS_ACTIV = 'X'.
    *I_BAPISITEMR-MRP_AREA =  '1110' .
    I_BAPISITEMR-VERS_ACTIV = ''.
        APPEND I_BAPISITEMR.
        I_BAPISSHDIN-REQ_QTY = OUT_E_MENGE.
        I_BAPISSHDIN-DATE_TYPE = '3'.   "Date type (day, week, month, interval) 3 = Month
        CONCATENATE ZYEAR_DATA ZMONTH_DATA '01' INTO ZREQ_DATE.
        I_BAPISSHDIN-REQ_DATE = ZREQ_DATE.   "Schedule line date
        I_BAPISSHDIN-UNIT = W_SINGLE.
        APPEND I_BAPISSHDIN.
        CALL FUNCTION 'BAPI_REQUIREMENTS_CREATE'
      EXPORTING
        REQUIREMENTS_ITEM              = I_BAPISITEMR
       REQUIREMENT_PARAM              = I_CM60R
         DO_COMMIT                      = 'X'
      UPDATE_MODE                    = ''
      REFER_TYPE                     = ''
      PROFILID                       = ''
    IMPORTING
      MATERIAL                       = I_BAPISITEMR-MATERIAL
      PLANT                          = I_BAPISITEMR-PLANT
      REQUIREMENTSTYPE               = I_BAPISITEMR-REQU_TYPE
      VERSION                        = I_BAPISITEMR-VERSION
      REQMTSPLANNUMBER               = I_BAPISITEMR-REQ_NUMBER
      MRP_AREA                       = I_BAPISITEMR-MRP_AREA
      TABLES
        REQUIREMENTS_SCHEDULE_IN       = I_BAPISSHDIN
      REQUIREMENTS_CHAR_IN           =
        RETURN                         = I_BAPIRETURN1

  • How to header and item data of sales order using bapi interface

    hi friends,
       i am geetha, i having a problem like how to upload sales oder header and item data through va01 tcode using BAPI FUNCTION MODULES.
    i need bapi function modules for header adn item data  and brief explation on that , how to pass importing and tables  parameters to get exact output .
    regards
    geetha.

    Use : BAPI_SALESORDER_CREATEFROMDAT2
    Sales order: Create Sales Order
    Functionality
    You can use this method to create sales orders.
    You must enter at least sales order header data (via ORDER_HEADER_IN structure) and partner data (via the ORDER_PARTNERS table) as input parameters.
    Enter the item data via the ORDER_ITEMS_IN table. You can allocate item numbers manually, by filling in the relevant fields, or the system does it, according to the settings for Customizing, by leaving the relevant fields blank.
    If you have configurable items, you must enter the configuration data in the ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_PART_OF and ORDER_CFGS_VALUE tables.
    Credit cards can be transferred via the BAPICCARD structure, on the one hand, data for card identification, on the other, data for a transaction which has taken place in an external system.
    Once you have created the sales order successfully, you will receive the document number (SALESDOCUMENT field). Any errors that may occur will be announced via the RETURN parameter.
    If no sales area has been created in the sales order header, then the system creates the sales area from the sold-to party or ship-to party, who has been entered in the partner table. If a clear sales area cannot be created, you will receive a system message, and the sales order will not be created.
    Notes
    1. Mandatory entries:
    ORDER_HEADER_IN : DOC_TYPE     Sales document type
                       SALES_ORG    Sales organization
                       DISTR_CHAN   Distribution channel
                       DIVISION     Division
    ORDER_PARTNERS..: PARTN_ROLE   Partner role, SP sold-to party
                       PARTN_NUMB   Customer number
    ORDER_ITEMS_IN..: MATERIAL     Material number
    2. Ship-to party:
    If no ship-to party is entered, use the following: Ship-to party =
    sold-to party.
    3. Commit control:
    The BAPI does not have a database commit. This means that the relevant application must leave the commit, in order that can be carried out on on the database. The BAPI BAPI_TRANSACTION_COMMIT is available for this.
    4. German key words:
    The following key words must be entered in German, independantly of
    the logon language:
    DOC_TYPE     Sales document type, for example: TA for standard order
    PARTN_ROLE   Partner role, for example: WE for ship-to party
    Further information
    You can find further information in the OSS. The note 93091 contains general information on the BAPIs in SD.
    Parameters
    SALESDOCUMENTIN
    ORDER_HEADER_IN
    ORDER_HEADER_INX
    SENDER
    BINARY_RELATIONSHIPTYPE
    INT_NUMBER_ASSIGNMENT
    BEHAVE_WHEN_ERROR
    LOGIC_SWITCH
    TESTRUN
    CONVERT
    SALESDOCUMENT
    RETURN
    ORDER_ITEMS_IN
    ORDER_ITEMS_INX
    ORDER_PARTNERS
    ORDER_SCHEDULES_IN
    ORDER_SCHEDULES_INX
    ORDER_CONDITIONS_IN
    ORDER_CONDITIONS_INX
    ORDER_CFGS_REF
    ORDER_CFGS_INST
    ORDER_CFGS_PART_OF
    ORDER_CFGS_VALUE
    ORDER_CFGS_BLOB
    ORDER_CFGS_VK
    ORDER_CFGS_REFINST
    ORDER_CCARD
    ORDER_TEXT
    ORDER_KEYS
    EXTENSIONIN
    PARTNERADDRESSES
    Exceptions
    Function Group
    2032

  • HAVE TO Generate IDOC in badi ME_PROCESS_PO_CUST, UNABLE TO READ ITEM DATA

    ME_PROCESS_PO_CUST                "IMPLEMENTING CLASS
       IF_EX_ME_PROCESS_PO_CUST  " INTERFACE
         POST                                         "METHOD
    POST HAS TWO PARAMETERS
    IM_EBELN
    IM_HEADER TYPE REF TO IF_PURCHASE_ORDER_MM
    IF_PURCHASE_ORDER_MM   "INTERFACE
        GET_DATA                          "METHOD , WORKIG FINE
        GET_ITEMS            "METHOD
    GETI_ITEMS HAS PARAMETER REITEMS
    REITEMS IS TABLE TYPE PURCHASE_ORDER_ITEMS
    WHICH IS LINE TYPE PURCHASE_ORDER_ITEM
    AND THIS LINE TYPE HAS FIELD
    ITEM WHICH IS TYPE IF_PURCHASE_ORDER_ITEM_MM
    AND AGAIN IN THIS INTERFACE THERE IS METHOD GET_DATA TO GET ITEM DATA.
    PLEASE SUGGEST ME HOW TO ACCESS  ITEM DATA ,
    IF POSSIBLE PLEASE WRITE THE CODE AS I AM VERY POOR  AT 'OOPS' AND ITS VERY VERY URGENT.
    THANKS AND REGARDS
    Edited by: TRY-N-TRY on Jan 7, 2008 6:23 PM

    Hello
    If you had searched the SDN forums you would have found plenty of answers to your question.
    Following is some sample coding:
    method IF_EX_ME_PROCESS_PO_CUST~POST.
    DATA:
        ls_header TYPE mepoheader,
      lt_items   TYPE purchase_order_items,
      ls_item   TYPE purchase_order_item,
      ls_item TYPE mepoitem.
      ls_header = im_header->get_data( ).
      lt_items = im_header->get_items( ).
      LOOP AT items INTO ls_item.
        ls_item = line_item-item->getdata( ).
        " process item data...
      ENDLOOP.
    ENDMETHOD.
    Regards,
      Uwe
    PS: Do not use such kind of pseudonyms instead of your real name. Because my impression is that a nobody (in term of ABAP development competence) tries to claim to be a somebody who fills his knowledge gaps via SDN. Using pseudonyms significantly decreases your changes to get any answers at the SDN forums.

  • BAPI or FM for create  delivery in header data & item data

    Hi All,
             In my requriment  i am downloading delivery data  i.e header data and item data . When  i am uploadinng the Modification data  through BAPI  or FM.
    Thank you,
    Dinesh Reddy

    Hi,
    If you are looking for BAPI to create delivery check the following BAPIs
    BAPI_OUTB_DELIVERY_CREATE_SLS
    BAPI_OUTB_DELIVERY_CREATE_STO
    BAPI_OUTB_DELIVERY_SAVEREPLICA
    Regards
    Prasenjit

  • BAPI or FM for geting  all sales master data, header data , item data etc

    Hi experts,
          In my requirement  i need a BAPI  (or) Function module for getting all "Sales information" data means header data , item
    data, scheduled data  etc    .
    Thank you,
    Dinesh Reddy.

    Hi,
    check BAPI_SALESORDER_GETLIST
    I hope it helps you....
    Regards,
    NaPPy

  • In VL06O while selecting the tab LIST OUTBOUND DELIVERIES, no line item

    Hi,
    In VL06O while selecting the tab LIST OUTBOUND DELIVERIES, no line item is showing under item overview for a particular Delivery no but I can see the line items in VL03 for that delivery no.
    So why the line item is not getting display in VL06O.
    Can any one give the proper suggestion on this.
    Waiting for quick response.
    Best Regards.
    BDP

    are you sure that the current setting is activated?
    try to get help from an ABAPer
    check as well OSS note 384304 - Input help for material number does not work (EKPO-MATNR)
    Edited by: Jürgen L. on Dec 23, 2008 8:33 PM

  • BAPI / FM to change Sales order item data

    Hi,
    I need a BAPI or FM to update the following fields of VBAP (Sales Document Item Data)
    KZWI2 - Subtotal 2 from pricing procedure for condition
    KZWI3 - Subtotal 3 from pricing procedure for condition
    KZWI4 - Subtotal 4 from pricing procedure for condition
    KZWI5 - Subtotal 5 from pricing procedure for condition
    I found FM: ISM_SALES_ITEM_CHANGE for this, but when I use it, it gives me dump for some data object 'XJKNBK'.
    Does any one have idea on how to use this FM or if any other FM is there please let me know?
    Thanks & Regards,
    Sunanda.

    hi Sunanda..
    I think you can try the Bapi 'BAPI_SALESORDER_CHANGE'. You can make use of its Tables Parameter CONDITIONS_IN and CONDITIONS_INX.
    example:
    How to change pricing Conditions in Sales order in change sales order bapi
    thanks,
    Padma

  • BAPI_SHIPMENT_CREATE - Shipment without outbound deliveries

    Hello experts,
    I am implementing bapi BAPI_SHIPMENT_CREATE for generating shipment number (VT01N). The user inputs are (1) outbound delivery number (2) shipment type and (3) forwarding agent. BAPI is generating shipment number in simulation and when called in abap program but without outbound deliveries (and Net Value calculation). Along with three user input parameters, i am also populating relavant
    1--> TRANS_PLAN_PT, SHIPMENT_ROUTE, status flags, SERVICE_AGENT_ID of Header data.
    2.->STAG_SEQ, INCOTERM, LEG_INDICATOR, ORG_SHIPP_DPMNT, plant of departure, dest. plant of STAGEDATA table (optional)
    3.-->outbound delivery number in ITEMDATA table (optional)
    4.--> corresponding fields of tables STAGEDEADLINE, ITEMONSTAGE, HDUNHEADER/ITEM (optional)
    After populating these fields, RETURN parameter shows the shipment number but without attached outbound delivery (after clicking stage tab -- deliveries) and net value calulation.
    Any help or suggestion in this regard will be of greate help.
    Thanks,
    Harish

    BAPI_SHIPMENT_CREATE is for creating only, if existi, then you should execute BAPI_SHIPMENT_CHANGE

  • Get Item data at ME23n or ME22N after implementing MM06E005

    Dear Experts,
    I have implemented user exit MM06E005 (Customer fields in purchasing document) for ME21N.
    1. Add 1 filed to custom include structure CI_EKKODB in EKKO table.
    2. Add my coding to function module EXIT_SAPMM06E_012 for validation.
    *&  Include           ZXM06U43
      DATA: BEGIN OF ITAB OCCURS 0,
      YYFORMCODE LIKE ZEKKO_FORM-YYFORMCODE,
      YYFORMINFO LIKE ZEKKO_FORM-YYFORMINFO,
      END OF ITAB.
      SELECT * FROM ZEKKO_FORM INTO CORRESPONDING FIELDS OF TABLE ITAB
      WHERE YYFORMCODE  = EKKO-YYFORMCODE.
      IF SY-SUBRC <> 0.
        MESSAGE E000(ZFORMMSG).
        EXIT.
      ENDIF.
    3. Add my coding to function module EXIT_SAPMM06E_013 to update ekko table.     
    *&  INCLUDE           ZXM06U44
      DATA: BEGIN OF ITAB OCCURS 0,
            YYFORMCODE LIKE ZEKKO_FORM-YYFORMCODE,
            YYFORMINFO LIKE ZEKKO_FORM-YYFORMINFO,
            END OF ITAB.
      SELECT * FROM ZEKKO_FORM INTO CORRESPONDING FIELDS OF TABLE ITAB
      WHERE YYFORMCODE  = EKKO-YYFORMCODE.
      IF SY-SUBRC <> 0.
        MESSAGE E000(ZFORMMSG).u201D Error Message
        EXIT.
      ELSE.
        IF SY-TCODE = 'ME21N' .
          IF EKKO-YYFORMCODE  = ' '.
            MESSAGE E000(ZFORMMSG). u201D Error Message
            EXIT.
          ELSE.
            LOOP AT ITAB.
              IF EKKO-YYFORMCODE EQ ITAB-YYFORMCODE.
                MOVE ITAB-YYFORMCODE TO I_EKKO-YYFORMCODE.
                MOVE-CORRESPONDING I_EKKO TO EKKO.
                MODIFY EKKO FROM EKKO.
              ELSE.
                CONTINUE.
              ENDIF.
            ENDLOOP.
          ENDIF.
        ENDIF.
      ENDIF.
    4. Add my coding to function module EXIT_SAPMM06E_014 to display data to ME22N and ME23N.
    5. Create a  Z-Table  with one filed and create search help to get Values for field in ME21n
    Data get updated to EKKO table along with my added field customer fields.
    Data get updated to EKPO table along with my added field customer fields.
    But My problem is that When I want to display that PO in ME22N or ME23N (which I have created) only header data get display But not Item Data.
    Please give me some hint regarding this problem.
    If any other clarification require please tell..

    Hi Suyog,
    Try with the below code:
    IF SY-TCODE = 'ME21N'  or SY-TCODE = 'ME22N'  or SY-TCODE = 'ME23N' .
    Then ur Validation...
    ENDIF.
    Thanks.
    Note:Reward points if you find useful.

  • Line Item Data?

    Hi experts,
                   What is Line Item Data? Can somebody give me an example to understand better the use of Line item data from the reporting prospective?
    thanks in advance
    regards,
    dubbu

    Hi
    I think ur question releted to LINE ITEM DIMENSION
    Line Item and High Cardinality
    Use
    When compared to a fact table, dimensions ideally have a small cardinality.  However, there is an exception to this rule. For example, there are InfoCubes in which a characteristic document is used, in which case almost every entry in the fact table is assigned to a different document. This means that the dimension (or the associated dimension table) has almost as many entries as the fact table itself. We refer here to a degenerated dimension. In BW 2.0, this was also known as a line item dimension, in which case the characteristic responsible for the high cardinality was seen as a line item. Generally, relational and multi-dimensional database systems have problems to efficiently process such dimensions. You can use the indicators line item and high cardinality to execute the following optimizations:
           1.      Line item: This means the dimension contains precisely one characteristic. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes on the role of dimension table. Removing the dimension table has the following advantages:
    ¡        When loading transaction data, no IDs are generated for the entries in the dimension table.  This number range operation can compromise performance precisely in the case where a degenerated dimension is involved. 
    ¡        A table- having a very large cardinality- is removed from the star schema.  As a result, the SQL-based queries are simpler. In many cases, the database optimizer can choose better execution plans.
    Nevertheless, it also has a disadvantage: A dimension marked as a line item cannot subsequently include additional characteristics. This is only possible with normal dimensions.
           2.      High cardinality: This means that the dimension is to have a large number of instances (that is, a high cardinality). This information is used to carry out optimizations on a physical level in depending on the database platform. Different index types are used than is normally the case. A general rule is that a dimension has a high cardinality when the number of dimension entries is at least 20% of the fact table entries. If you are unsure, do not select a dimension having high cardinality.
    Note: In SAP BW 3.0, the term line item dimension from SAP BW 2.0 must a) have precisely one characteristic and b) this characteristic must have a high cardinality. Before, the term line item dimension was often only associated with a). Hence the inclusion of this property in the above.  Be aware that a line item dimension has a different meaning now than in SAP BW2.0.

  • Table name in which return item data is stored of a PO

    Can some please specify the table name in which return item data is stored of a PO?
    Thanks in advance;

    Hi,
    Let me explain what exactly I need. In a PO there is a checkbox "Retun Item". If we check that checkbox for an item that item becomes a retun item.
    I need to fetch all the data of this return Item. The commitment data goes to table COOI but this return item records doesn't get stored in COOI table. I need all the data of this entry including the Network Activity, Project, WBS element etc.
    Please let me know if you could help me.
    Thanks.

  • AP open items data

    Hi gurus,
             Here i have to extract data related to ACCOUNTS PAYBLE OPEN ITEM DATA for that i have to extract Header data , item data, and vendor data, bank details.....so pls advice me from how many tables i have to  take data ...
    I knew some thing like BKPF,BSEG,BSIK,LFA1,LFBK,,,,is this correct or
    i have to take from BSIK for open items ,,some of the fields are avilabel in BSIK,but again i have to go to BSEG,,,,,,some fileds avilabe in this table ....pls ADVICE ME.....
    Thanks
    KRISNA

    Hi Krisna,
    Even in std transdaction code FBL1N, you need to provide comp. code,vendor #, keydate.
    But since you have company code only, you can retrive all the relevant vendors for that comp. code using select from table LFB1.
    You can pass these vendors alongwith the given comp. code to the BAPI through a loop.
    For keydate, by default it should be current system date so set it to system date.
    Hope this would be of help.
    Cheers,
    Vikram
    Mark for helpful replies!!

  • Multiple outbound deliveries in STO

    Hi
    We have created a new purchase order document type for intercompany stock transport order.  If a PO has two line items, system is creating two outbound deliveries, though shipping point is same for both the line items.
    Am I missing any config step
    please advice
    regards
    satyaprasad

    Hi
    Use the solution from note  377501 to solve the issue. please read this one
    regards,
    Ramana

  • Multiple Outbound Deliveries

    Hi,
    How can I create multiple outbound deliveries for a Stock Transfer Order? The STO has more than a thousand items, which makes one outbound delivery with a thousand line items quite difficult to process with our current warehouse. I need to cut the Stock Transfer by number of line items...for example the STO with 1000 line items will create 20 outbound deliveries with 50 line items each.
    Thanks,
    Lee

    Dear Lee,
    First of all you can not save the STO with 1000 line items as limit for any sales/sto is 499. You may wonder why this? Because for each line item there will be 2 financial entries Debit and Credit and in 1 FI documents you can post maximum 999 entries.
    so it will be better to process 3 to 4 documents say with 250 line items and then create delivery.
    Also if you want to create automatic delivery for such documents then goto VOV8, select your document type, and in shipping data select IMMEDIATE Delivery as A Create delivery immediately
    But i will suggest you to create 4 documents.
    Hope this will help

Maybe you are looking for