Overpicking- L_TO_CREATE_DN vs LT03

Hi all,
im creating a new Z transaction that will have to create a transfer order for each item in the delivery. For that I have used FM 'L_TO_CREATE_DN' , however when I want to do overpicking I get the message E199. When I do the same thing using transaction LT03 I do not get this message.
Can anyone help???
thanks

Hi Rohit...
I am not sure that you will be able to suggest overpick in WM at the transfer order creation stage...have you tried this function using using standard LT03?
Normally you could only do this if the delivery requirement quantity is increased by the relevant amount.
You probably need to look at a user exit or develop some code within a new function module so that the system review WM stock first and determine whether an overpick can be satisfied for a specific customer. If the stock allows then the delivery requirement quantity could be increased by the relevant tolerance amount.
Alternatively you could leave the overpick to take place within the transfer order confirmation. This way a difference indicator could be used to post more actual stock
Sorry, not sure of any other alternatives at the moment
Regards
Steve

Similar Messages

  • LT03 (FM L_TO_CREATE_DN)_Overpicking Delivery within Tolerance Limit.

    Hi Experts,
    Need some urgent input. I am using L_TO_CREATE_DN to create TO for Delivery. Certain deliveries have Over-Tolerance Limit such as 10%, 20% etc which means that Picking should be allowed even if the Pick qty is greater than delivery qty but less than over-tolerance limit.
    Example
    If a Delivery has Delivery Qty (in VL03N) = 1000. and Tolerance Limit = 10%. so Maximum Possible pick is (1000*10/100) + 1000 = 1100.
    So in case I have already picked quantity of 900 from the delivery and the next HU I am picking has quantity 150 inside it then total pick would be 1050.
    1050 > 1000 (Delivery Qty) but 1050 < 1100 (Qty within Tolerance) so it should go through.
    But L_TO_CREATE_DN is giving error "Total for assigned quantities exceeds quantity to be removed".
    Any thoughts on whether there is a particular setting in this FM to let it go through? Or is there a different FM available to perform this task?
    Please HELP.
    Thanks,
    Rohit.

    Hi!
    I had the same problem yesterday. How do you solve it?
    I had the message Total for assigned quantities exceeds quantity to be removed
    Regards,
    LB

  • Error while uploading data in LT03?

    Dear All,
    I am uploading data in LT03 transaction and I am getting an error message 'System cannot find source storage bin'.
    I am using BAPI  'L_TO_CREATE_DN'.
    Even same error  I am getting in recording.
    This is happened in the case of Partial delivery not for full delivery.
    Thanks and Regards
    Steve

    Hi,
    Search SCN before posting a query...
    System cannot find source storage bin
    Regards
    Praveen

  • User  exit for LT03 - Creation of transfer order.

    Hi All,
    In LT03 while creating a transfer order for delivery the system picks the storage unit in ascending order(FIFO - First in first out). Is there any badi available to change this picking order into descending order(LIFO- Last in first out). I have tried all the user exit related to transaction LT03, but nothing has served the purpose,has anybody faced this issue please share your views on this.
    Regards
    Sathya

    Hi Saravanan,
    you can try one of these FMs. It might be helpful:
    L_TO_CREATE_2_STEP_PICKING
    L_TO_CREATE_DN
    L_TO_CREATE_DN_MULTIPLE
    L_TO_CREATE_MOVE_SU
    L_TO_CREATE_MULTIPLE
    L_TO_CREATE_POSTING_CHANGE
    L_TO_CREATE_SINGLE
    L_TO_CREATE_TR .

  • Bapi/fm for LT03

    hi!
    is there any bapi or FM for creating transfer order (LT03)?
    REGARDS
    YIFAT

    check any one of these function modules based on your requirement.
    L_TO_CREATE_2_STEP_PICKING                                                     
    L_TO_CREATE_DN - Create a transfer order for delivery note       
    L_TO_CREATE_DN_MULTIPLE                                                        
    L_TO_CREATE_MOVE_SU - Create transfer order for moving storage units  
    L_TO_CREATE_MULTIPLE                                                           
    L_TO_CREATE_POSTING_CHANGE - Create transfer order for posting change        
    L_TO_CREATE_SINGLE - Create a transfer order with one item           
    L_TO_CREATE_TR - Create a transfer order for transfer requirement
    Thanks,
    Suryaprakash

  • IDoc for L_TO_CREATE_DN

    Hello All,
    We are trying to implement an interface process with an external WMS system to our ECC 6.0. We are looking for a standard iDoc that we can receive to 6.0 to create a Transfer Order similar to LT03 or FM L_TO_CREATE_DN. I've identified WMTORD to create transfer orders, but it will not let me reference it to an outbound delivery/delivery line like the L_TO_CREATE_DN function module. Is there any standard iDoc that will create a TO for an outbound delivery?

    Here are the message types:
    WMPIHU     Pick HU
    WMRREF     Release reference number
    WMSUMO     Move storage unit
    WMTOCO     Confirm transfer order
    WMTORD     Transport Request
    WMTREQ     Create/cancel transfer order
    You can set the IDOCs and function modules to process them in OMKY transaction.
    Hope that helps
    Thanks
    Vinod.

  • Problem creating TO using Function Module L_TO_CREATE_DN

    Hi Gurus,
    I am trying to create TO using the Function Module L_TO_CREATE_DN. Its creating TO for deliveries for materials which are not batch split, however when I am taking delivery consisting of Batch Split material, its not creating and throwing a error with sy-subrc = 15. The error which I am experiencing is Item not handled in batches and batch split item cannot be edited. How to overcome this issue and create the TO.
    Regards,
    Avik
    Edited by: avik2005uitbu on Dec 15, 2011 8:10 PM

    Hi,
    Please check the WM config for the Warehouse / Movement type(Tx. OMLX) . There we have option to give as immediate confirmation. This may be the reason for TO getting confirmed when created.
    U can this by creating a transfer order for the same movement type manually in TX. LT03. After you save if the To is confirmed then its a config setup @ Warehouse / Movement type.
    Regards,
    Bhargava

  • L_TO_CREATE_DN failing

    Hi guys,
    need help with respect to L_TO_CREATE_DN function module.
    My scenerio is that LT03 tansaction is failing to create TO for the entered HU(pallet number).
    It is randomly picking pallet available for delivery note and preparing a TO.
    L_TO_CREATE_DN function module is failing and throwing exception "input error" can anyone give me some sample code/data that they have used so that i can know what all i have to enter and take data from my system for this and also let me know if this function module will work for above scenerio.
    also WS_LM_TRANSFER_ORDER_CREATE function module for above scenerio is failing.
    Can anyone suggest some other function module.
    rewards will be given.

    There may be problem in customization setting
    rgds
    rajesh

  • L_TO_CREATE_DN function module for creating TO for a delivery

    Hi,
    I am using L_TO_CREATE_DN function module to create a TO for a delivery and it is working fine as long as the HU, I am picking has quantity less than the delivery quantity or equal to delivery qty. But whenever I try to pick a HU whose qty is little more than the delivery quantity, its throwing an error. Also, there is tolerance set on the delivery line item (and the qty I want to pick is within the tolerances). When I am trying to do it manually using LT03, it throws a popup about conversion error and is creating the TO taking the rouding into account. Here is the example of the above scenario.
    Delivery Qty = 1300 LB (pounds, base unit of measure)
    Alternate Unit of measure for this material is Roll (RL)
    I am trying to pick a HU which is 1350 LB.
    Manual Case : When I use LT03 it throws a popup (saying conversion error) and accepts only
    0.963 RL which is equal to 1300 LB and creates a TO. when I see the delivery after creating the TO, the picked qty is 1300LB.
    Function Module : When I use the function module, it does throw me the same popup but does not create the TO. Rather it throws an error "Available quantity in bin is zero".

    hi , it will create only 1 TO with multiple line items
      CALL FUNCTION 'l_to_create_multiple'
        EXPORTING
          i_lgnum                      = ls_9001_scrn-lgnum
          i_bwlvs                      = lc_bwartwa
          i_bname                      = sy-uname
        IMPORTING
          e_tanum                      = ltak-tanum
        TABLES
          t_ltap_creat                 = li_ltap_creat
    ls_9001_scrn-lgnum = warehouse number
    lc_bwartwa = movement type
    li_ltap_creat = itab containing the line items with diff material
    Just check if it helps
    Thanks

  • L_TO_CREATE_DN and HU/SU management

    Hi,
    I'm using this FM in order to create a TO with reference to a delivery <b>AND</b> I also need source/destination SU info to be passed in this TO. Unfortunatelly, each time is my Destination SU overwritten by a blank value and no Quant is created (?!).
    If however I execute LT03 manually filling in SU data - everything works fine.
    Anyone knows how to handle this?
    Helpfull answers will be rewarded, of course.
    Cheers!

    Hi,
    have a look at this code:
    Generate TO
      CLEAR:   tlips, wa_tlips.
      REFRESH: tlips.
      SELECT SINGLE * FROM likp WHERE vbeln = likp-vbeln.
      SELECT  * FROM lips INTO TABLE tlips
        WHERE vbeln = likp-vbeln.
      IF NOT tlips[] IS INITIAL.
        CLEAR: it_delit, l_wa_delit.
        REFRESH it_delit.
    Delete positions with status that is not  A or B
        LOOP AT tlips INTO wa_tlips.
          CLEAR l_kosta.
          SELECT SINGLE kosta FROM vbup INTO l_kosta
            WHERE vbeln = wa_tlips-vbeln
            AND posnr = wa_tlips-posnr.
          IF l_kosta NA 'AB'.
            DELETE tlips.
          ENDIF.
        ENDLOOP.
        CLEAR:   tlips, wa_tlips.
        IF NOT tlips[] IS INITIAL.
          LOOP AT tlips INTO wa_tlips.
    Check again the status of the position
            CLEAR l_kosta.
            SELECT SINGLE kosta FROM vbup INTO l_kosta
              WHERE vbeln = wa_tlips-vbeln
              AND posnr = wa_tlips-posnr.
            CHECK l_kosta CA 'AB'.
            CLEAR: lv_tanum, lv_teilk.
            CLEAR: l_wa_delit, it_delit.
            REFRESH it_delit.
    Quantity
            SELECT SINGLE * FROM lqua
              WHERE lgnum = rm07m-lgnum
              AND lenum = lein-lenum.
            CHECK lqua-matnr = wa_tlips-matnr.
            l_wa_delit-anfme = lqua-verme.
    position
            l_wa_delit-posnr = wa_tlips-posnr.
    alternative unit of measure
            l_wa_delit-altme = lqua-meins.
    Batch
            l_wa_delit-charg = lqua-charg.
    *--destination--
            l_wa_delit-nltyp = '916'.
            l_wa_delit-nlber = '001'.
            l_wa_delit-nlpla = wa_tlips-vbeln.
            l_wa_delit-letyp = lqua-letyp.
    *--source--
            l_wa_delit-vltyp = lqua-lgtyp.
            l_wa_delit-vlber = '001'.
            l_wa_delit-vlpla = lqua-lgpla.
            l_wa_delit-vlenr = lqua-lenum.
            APPEND l_wa_delit TO it_delit.
            CALL FUNCTION 'L_TO_CREATE_DN'
              EXPORTING
                I_LGNUM                          = rm07m-lgnum
                I_VBELN                          = likp-vbeln
                I_COMMIT_WORK                    = con_x
                I_BNAME                          = SY-UNAME
                IT_DELIT                         = it_delit
             IMPORTING
               E_TANUM                          = lv_tanum
               E_TEILK                          = lv_teilk
             EXCEPTIONS
               FOREIGN_LOCK                     = 1
               DN_COMPLETED                     = 2
               PARTIAL_DELIVERY_FORBIDDEN       = 3
               XFELD_WRONG                      = 4
               LDEST_WRONG                      = 5
               DRUKZ_WRONG                      = 6
               DN_WRONG                         = 7
               SQUIT_FORBIDDEN                  = 8
               NO_TO_CREATED                    = 9
               TEILK_WRONG                      = 10
               UPDATE_WITHOUT_COMMIT            = 11
               NO_AUTHORITY                     = 12
               NO_PICKING_ALLOWED               = 13
               DN_HU_NOT_CHOOSABLE              = 14
               INPUT_ERROR                      = 15
               OTHERS                           = 16.
          ENDLOOP.
      ENDIF.
    Best regards.

  • Message in L_TO_CREATE_DN

    Hi all,
    When creating a transfer order for a delivery note in WM, we are using L_TO_CREATE_DN FM instead of using a BDC call on trn. LT03. We start having problems in partial pickings, so we applied OSS note 769744 and they were solved, but now another message arises when creating de TO:
    <i>Transfer order must have at least one item</i>
    We have been stucked on that all the day... searched OSS, SAPFans, Google, SDN... and nothing out there...
    We are filling parameters I_LGNUM, I_VBELN and I_TEILK (for partial pickings) and tables T_LTAK and T_LTAP_VB.
    We are in 4.6C.
    Any ideas will be VERY VERY appreciated.
    Manuel

    Hi Rebeca,
    Have you seen this paragraph in parameter IT_DELIT documentation?
    "Item specifications are not allowed for Handling Unit items when you create transfer orders for outbound deliveries. The system issues an error message."
    Despite this, as you can see in the original post, when we worked with the FM L_TO_CREATE_DN we were in 4.6C therefore parameter IT_DELIT wasn't available. At that time, the workarround we used was to export HU's data to shared memory before calling the FM, and then implement UE MWMTO004 for importing the data and processing it there.
    I really don't know about improvements of the FM in later releases (we are now on ECC 6.0, but don't re-analize this process)
    Hope it helps!
    Regards,
    mr.

  • No transfer of Unit of Measure using L_TO_CREATE_DN.

    Hi everybody,
       I have the following problem: when I create a TO using LT03, I can enter a unit of measure like PLG for example. When the TO is created, SAP determines that it is in fact 20 COLL (1 PLG <-> 20 COLL), determines the correct batches etc etc and creates the TO. When I look at the TO I can see that I entered 1 PLG.
    Now we are getting to the problem: when I try to create the TO with fm L_to_create_dn, I can enter the 1 PLG like mentioned before in structure it_delit (anfme and altme), but, the final TO that is created, only contains the recalculated amount of 20 COLL. I can't find the fact that I entered 1 PLG!
    Why this kind of behaviour when I use the fm?
    The funcional consultants can't find it in customizing.
    Any hints or tips?
    Cheers and thanks!
    Laurens

    The problem with using an isolated FM like this is that you don't know if there are FMs that should run before or after it to do other processing. If you look at BAPI_WHSE_TO_CREATE_STOCK, I think you'll see what I mean. A comment in this BAPI says not to use it, so please don't. I think your options are BDC or call transaction.
    Rob

  • Creating TO using L_TO_CREATE_DN with SLED or Expiry Date????

    Hi Team,
    I am writing a Ztcode program for the TO creation using function module L_TO_CREATE_DN function module. But my requirement needs VFDAT (Expiry Date ) to be saved for the Trading Order which we create using tcode LT03, Were SLED, Shelf Expiry Date is required during creation with screen.
    Can anybody help how to create TO using FM with expiry date...
    Thanks in adavance, Help is as soon as possible would be grateful.
    Regards,
    Gaurav Patwari
    919967053678
    Edited by: GauravPa on Jun 13, 2011 1:47 PM

    please check the wm status in the inbound delivery, by this error message looks like plant+sloc is not wm managed ?also if possible Please share the screenshot of the putaway tab of delivery

  • BAPI for LT03

    Hi all,
    Which BAPI can i use for LT03 trx.?
    FM WS_LM_TRANSFER_ORDER_CREATE seems to be successfull, but i couldn't let it work. If it was the right BAPI, is there any example with it??
    Thanks a lot..
    Kaan

    Hi Kaan,
    Function Module 'L_TO_CREATE_DN' should do it.
    Example:
    DATA lt_ltak  TYPE STANDARD TABLE OF ltak_vb WITH HEADER LINE.
        "TO Header
        DATA lt_ltap1  TYPE STANDARD TABLE OF ltap_vb WITH HEADER LINE.
        "TO Items
        DATA lt_msg TYPE STANDARD TABLE OF wmgrp_msg WITH HEADER LINE.
        DATA lt_delit TYPE TABLE OF l03b_delit.
        DATA lt_wa_delit TYPE l03b_delit.
        "TO Items with Pallet data
        DATA lv_tanum TYPE ltak-tanum. "TO Number
        LOOP AT t_pallet.
          MOVE t_pallet-posnr    TO lt_wa_delit-posnr.
          MOVE t_pallet-curr_qty TO lt_wa_delit-anfme.
          MOVE t_pallet-vrkme    TO lt_wa_delit-altme.
          MOVE t_pallet-charg    TO lt_wa_delit-charg.
          MOVE t_pallet-lgtyp TO lt_wa_delit-vltyp.
          MOVE t_pallet-lgpla TO lt_wa_delit-vlpla.
          UNPACK t_pallet-lenum TO lt_wa_delit-vlenr.
          APPEND lt_wa_delit TO lt_delit.
          CLEAR  lt_wa_delit.
        ENDLOOP.
    Bapi to Create the TO
        CALL FUNCTION 'L_TO_CREATE_DN'
          EXPORTING
            i_lgnum                    = t_user-lgnum
            i_vbeln                    = zmilk_zlm26_str-vbeln
            i_squit                    = c_true
            it_delit                   = lt_delit
          IMPORTING
            e_tanum                    = lv_tanum
          TABLES
            t_ltak                     = lt_ltak
            t_ltap_vb                  = lt_ltap1
            t_wmgrp_msg                = lt_msg
          EXCEPTIONS
            foreign_lock               = 1
            dn_completed               = 2
            partial_delivery_forbidden = 3
            xfeld_wrong                = 4
            ldest_wrong                = 5
            drukz_wrong                = 6
            dn_wrong                   = 7
            squit_forbidden            = 8
            no_to_created              = 9
            teilk_wrong                = 10
            update_without_commit      = 11
            no_authority               = 12
            no_picking_allowed         = 13
            dn_hu_not_choosable        = 14
            input_error                = 15
            OTHERS                     = 16.

  • When performing the LT03 for a delivery order

    The system runs forever; then ABAP dumps.  None of us here are experts in ABAP at all.  This is not happening in our QA client only in the production client so I am at a lsot as to why.  My initial though was due to changing serialization level from one to none but when I tried to duplicate the error in QA, it works,  Below is the message ...anyone with advice?
    Short text
    Time limit exceeded.
    What happened?
    The program "SAPLZAF_MM_SERIAL" has exceeded the maximum permitted runtime
    without
    interruption and has therefore been terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    After a specific time, the program is terminated to make the work area
    available to other users who may be waiting.
    This is to prevent a work area being blocked unnecessarily long by, for
    example:
    - Endless loops (DO, WHILE, ...),
    - Database accesses with a large result set
    - Database accesses without a suitable index (full table scan)
    The maximum runtime of a program is limited by the system profile
    parameter "rdisp/max_wprun_time". The current setting is 1800 seconds. If this
    time limit is
    exceeded, the system attempts to cancel any running SQL statement or
    signals the ABAP processor to stop the running program. Then the system
    waits another 60 seconds maximum. If the program is then still active,
    the work process is restarted.
    How to correct the error
    Programs with long runtime should generally be started as background
    jobs. If this is not possible, you can increase the system profile
    parameter "rdisp/max_wprun_time".
    Depending on the cause of the error, you may have to take one of the
    following measures:
    - Endless loop: Correct program;
    - Dataset resulting from database access is too large:
    Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
    (for example);
    - Database has unsuitable index: Check index generation.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TIME_OUT" " "
    "SAPLZAF_MM_SERIAL" or "LZAF_MM_SERIALU01"
    "ZAF_MM_SERIAL"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "WIC-PD-ECCSCS"
    Network address...... "10.200.1.245"
    Operating system..... "Linux"
    Release.............. "2.6.16.60-0.39.3-smp"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "WIC-PD-ORC-01"
    Database type..... "ORACLE"
    Database name..... "ECP"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Aug 23 2009 20:22:37"
    create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 221
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Linux 2.6"
    Memory consumption
    Roll.... 16192
    EM...... 20949240
    Heap.... 0
    Page.... 57344
    MM Used. 10428296
    MM Free. 2138248
    User and Transaction
    Client.............. 400
    User................ "TNIDA"
    Language key........ "E"
    Transaction......... "LT03 "
    Transactions ID..... "4C7C27CEFAB745B2E10000000AC801F1"
    Program............. "SAPLZAF_MM_SERIAL"
    Screen.............. "SAPML03T 0102"
    Screen line......... 68
    Information on where terminated
    Termination occurred in the ABAP program "SAPLZAF_MM_SERIAL" - in
    "ZAF_MM_SERIAL".
    The main program was "SAPML03T ".
    In the source code you have the termination point in line 33
    of the (Include) program "LZAF_MM_SERIALU01".
    Source Code Extract
    Line SourceCde
    3 ""Local Interface:
    4 *" IMPORTING
    5 *" REFERENCE(LGORT) TYPE LGORT_D OPTIONAL
    6 *" REFERENCE(WERKS) TYPE WERKS_D OPTIONAL
    7 *" REFERENCE(MATNR) TYPE MATNR OPTIONAL
    8 *" REFERENCE(SERNR) TYPE GERNR OPTIONAL
    9 *" REFERENCE(LGNUM) TYPE LGNUM OPTIONAL
    10 *" EXPORTING
    11 *" REFERENCE(LGPLA) TYPE LGPLA
    12 *"----
    13
    14
    15 REFRESH: it_objk, it_ser03, it_lqua.
    16
    17 * Select serial number for all material documents
    18 SELECT * FROM objk
    19 INTO TABLE it_objk
    20 WHERE taser = 'SER03'
    21 AND sernr eq sernr
    22 AND matnr eq matnr.
    Select documents details for serial numbers.
    25 SELECT * FROM ser03
    26 INTO TABLE it_ser03
    27 FOR ALL ENTRIES IN it_objk
    28 WHERE obknr = it_objk-obknr
    29 AND werk = werks
    30 AND lagerort = lgort.
    31
    32 * Select storage bin details for all selected materials documents.
    >>>>> SELECT * FROM lqua
    34 INTO TABLE it_lqua
    35 FOR ALL ENTRIES IN it_ser03
    36 WHERE wenum = it_ser03-mblnr
    37 AND lgnum = lgnum.
    38 * AND lgpla = lgpla.
    39
    40
    41 * Populate the output table
    42 LOOP AT it_objk INTO wa_objk.
    43 READ TABLE it_ser03 INTO wa_ser03 WITH KEY obknr = wa_objk-obknr.
    44 IF sy-subrc = 0.
    45 READ TABLE it_lqua INTO wa_lqua WITH KEY wenum = wa_ser03-mblnr
    46 matnr = wa_objk-matnr.
    47 IF sy-subrc = 0.
    48 wa_ser-werks = wa_lqua-werks.
    49 wa_ser-lgort = wa_lqua-lgort.
    50 wa_ser-matnr = wa_lqua-matnr.
    51 wa_ser-sernr = wa_objk-sernr.
    52 wa_ser-lgnum = wa_lqua-lgnum.
    Contents of system fields
    Name Val.
    SY-SUBRC 0
    SY-INDEX 1
    SY-TABIX 10
    SY-DBCNT 33702
    SY-FDPOS 40
    SY-LSIND 0
    SY-PAGNO 0
    SY-LINNO 1
    SY-COLNO 1
    SY-PFKEY 31
    SY-UCOMM TATB
    SY-TITLE Create Transfer Order for Delivery: Generate TO Item
    SY-MSGTY E
    SY-MSGID L9
    SY-MSGNO 202
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO 0
    SY-DATUM 20100831
    SY-UZEIT 084745
    SY-XPROG SAPCNVE
    SY-XFORM CONVERSION_EXIT

    I managed to remove the serial numbers from the delivery and then tried LT03.  It ran for a long time however; I did manage to get it thru that way.  Added the serial numbers back in vlo02n and post goods issue just fine.
    Still curious as why the system is lagging so long and woul ABAP out if a serial numebr is in the LT03 when trying to create a TO...please any clues would be good.

Maybe you are looking for