L_to_create_multiple

hey I got one requirement to use the  L_TO_CREATE_MULTIPLE function module for "create transfer order Delete Vechicle WM" , "Create Transfer order for material" , "Create Transfer order for Vehicle" and create transer order,   what is the different logic I have to put in coding in these different cases by using this function module.  I think I should use Movement type for this to delete vechicle, so please help me, if any one knows the answer.
Edited by: lucky on Aug 5, 2008 9:03 PM

hey I got one requirement to use the  L_TO_CREATE_MULTIPLE function module for "create transfer order Delete Vechicle WM" , "Create Transfer order for material" , "Create Transfer order for Vehicle" and create transer order,   what is the different logic I have to put in coding in these different cases by using this function module.  I think I should use Movement type for this to delete vechicle, so please help me, if any one knows the answer.
Edited by: lucky on Aug 5, 2008 9:03 PM

Similar Messages

  • Error in using the FM 'L_TO_CREATE_MULTIPLE'

    Hi Gurus,
    I have a custom report, let's call it YREV, in ABAP that uses the FM 'L_TO_CREATE_MULTIPLE' and gives an error as follows:
    "(STOP) Material is not the same for confirmation and delivery"
    Note: (STOP) is an icon.
    The scenario is that YREV is called from a custom dialog program, which we will call SAPMYCUS, when the Reverse radiobutton is chosen and Enter button is pressed.
    This is used to reverse the posted GI of a given Outbound Delivery.
    The problem is that the error mentioned above is shown on screen and yet when I check, the reversal to the GI is done.
    Why is this so?
    The client who needs this program is complaining that the reversal is done but only partially.
    How do I check this "partial cancellation"?
    Is there any other FM that can replace this?
    According to [this|http://help.sap.com/saphelp_40b/helpdata/en/c6/f83a434afa11d182b90000e829fbfe/content.htm], these FMs were created so that it is easier compared to using batch input to process transfer orders.
    I'm starting to think otherwise.
    Hoping for your help regarding this matter.
    Thanks.
    ~ ric

    Hello Aditya,
    Thanks for showing interest in my question.
    To answer your question of what I am trying to do, I hope this can shed some light.
    I was given a PO number and an Outbound delivery number to work with.
    We have created a custom (module) program that handles transactions regarding outbound deliveries, and one feature of this program is to do a reversal of Outbound deliveries already posted.
    When using this reversal feature using the given PO as reference, the error message which I mentioned in my previous post, is displayed on screen.
    The user is curious why this happens and yet the posted outbound delivery involved is reversed.
    Additional info:
    • VL02n > Post Goods Issues - to process(?) given Outbound delivery
    • Custom program - to do the reversal process
    • VL02n does Mvt 641 while the reversal does Mvt 642.
    I apologize as to not being so clear but I am not so well versed with MM and its workings.
    Thanks.
    ~ ric

  • Creation of TO using  'L_TO_CREATE_MULTIPLE' greater then pallet quantity.

    Hello Friends,
      When we are trying to create a TO (transfer order ) using FM 'L_TO_CREATE_MULTIPLE' for greater then pallet quantity/size  of a material it is given me message in u201Cinsufficient quantityu201D. But there are many pallets for the material available in WH for picking.
    Ex: Material = A ; Pallet size = 100 units  when trying to create a TO for 1000 it gives me error mesg.
    On the other hand same thing works fine when we do it directly through Tcode LT01. LT01 creates a TO with multiple line items.Can any one please let me know why the FM is not working.
    Thank you,
    Prashanth  A.

    HI
    Check whether you have passed all of the required parameters. Here is the sample code.
    check this.
    CALL FUNCTION 'L_TO_CREATE_MULTIPLE'
            EXPORTING
              i_lgnum                = wa_tr_head-lgnum
              i_bwlvs                = c_bwlvs
              i_betyp                = c_betyp
              i_benum                = wa_tr_head-benum
              i_commit_work          = c_commitwork
              i_bname                = wa_tr_head-bname
              i_kompl                = c_kompl
              i_solex                = 0
              i_pernr                = 0
            IMPORTING
              e_tanum                = l_tanum
            TABLES
              t_ltap_creat           = t_ltap_creat
            EXCEPTIONS
              no_to_created          = 1
              bwlvs_wrong            = 2
              betyp_wrong            = 3
              benum_missing          = 4
              betyp_missing          = 5
              foreign_lock           = 6
              vltyp_wrong            = 7
              vlpla_wrong            = 8
              vltyp_missing          = 9
              nltyp_wrong            = 10
              nlpla_wrong            = 11
              nltyp_missing          = 12
              rltyp_wrong            = 13
              rlpla_wrong            = 14
              rltyp_missing          = 15
              squit_forbidden        = 16
              manual_to_forbidden    = 17
              letyp_wrong            = 18
              vlpla_missing          = 19
              nlpla_missing          = 20
              sobkt_wrong            = 21
              sobkt_missing          = 22
              sonum_missing          = 23
              bestq_wrong            = 24
              lgber_wrong            = 25
              xfeld_wrong            = 26
              date_wrong             = 27
              drukt_wrong            = 28
              ldest_wrong            = 29
              update_without_commit  = 30
              no_authority           = 31
              material_not_found     = 32
              lenum_wrong            = 33
              matnr_missing          = 34
              werks_missing          = 35
              anfme_missing          = 36
              altme_missing          = 37
              lgort_wrong_or_missing = 38
              OTHERS                 = 39.
    Thanks
    Renuka.

  • Function module L_TO_CREATE_MULTIPLE and commit

    Hi,
    Does anyone knows if in one report I call function module L_TO_CREATE_MULTIPLE with parameter I_COMMIT_WORK = SPACE and if in the main report after the call of the function module i do a commit command that allows that the transfer order is created ? And are the tables received if the call of L_TO_CREATE_MULTIPLE correct with the information of the created transfer order ?
    Or in other way if I really want to create the transfer order, I must pass the parameter I_COMMIT_WORK = 'X' ?
    Thanks in advance,
    Paulo Sousa

    Hi Paulo,
    The main Idea here is COMMIT should get called once the callto Function module L_TO_CREATE_MULTIPLE is executed so it really doesn't makes different if you call L_TO_CREATE_MULTIPLE with I_COMMIT = 'X'
    or you call L_TO_CREATE_MULTIPLE with I_COMMIT = SPACE and later to this call to Function module do COMMIT WORK, both are effectively same.
    One thing that needs to be taken care is if you are calling L_TO_CREATE_MULTIPLE in LOOP you have to do COMMIT after each call.
    Hope this helps!
    Regards
    Shital

  • L_TO_CREATE_MULTIPLE creates multiple SUs but VBFA not updated????

    Hi Experts,
    Need you help. Scenario is:
    I have developed one ZProgram which creates TO from Inbound Delivery and must create TO with multiple SUs. I am using Function module: L_TO_CREATE_MULTIPLE. It creates TO good.
    But the VBFA table doesn't got updates for the same.
    I tried using WS_DELIVERY_UPDATE function module (RFC) but it give an erros saying "Cannot be processed with this transaction." Message Class VL Number: 143.
    Can anybody help throwing some light on this. I have ztcode for this program. Is there anyotherway to update Delivery.
    Thank you in advance.
    Regards,
    Gaurav Patwari

    Dear Diane
        I have the same problem. Can you find the solution from this problem?
    Thank you,
    Nuttapon K.

  • L_TO_CREATE_MULTIPLE with split bins

    Hi,
    I need to create a transfer order without reference for multiple line items with split bin items.
    When using LT01, an item is split sucessfully over two bins when necessary and I need to do the same, but with multiple lines on the TO.
    Both L_TO_CREATE_MULTIPLE and LT01 use FM L_TO_CREATE_INT, but by the time this FM is called in LT01 there is a table TAP populated with the split items.  This table has not been populated when the FM is called via L_TO_CREATE_MULTIPLE.
    Does anyone have any understanding of how I can get this table populated before I call L_TO_CREATE_MULTIPLE ?
    Many Thanks
    Diane

    Dear Diane
        I have the same problem. Can you find the solution from this problem?
    Thank you,
    Nuttapon K.

  • L_TO_CREATE_MULTIPLE function module

    Hi,
    I want to create Transfer orders (TO) for 1 vendor (which may contain multiple material for that 1 vendor). I  want to use this function module L_TO_CREATE_MULTIPLE, in which i'm passing all the data's to the table T_LTAP_CREAT as internal table.
    My question is what will be the output(E_TANUM) . For eg. if 1 vendor contains 3 material, how many transfer order's will be created i..e one per material or one per vendor. If it creates one TO per material whether all the 3 TO's will be created in one pass. should I need to loop the internal table for all the materials per vendor?
    -Anbu.

    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_MULTIPLE, --- Fix Bin Problem

    Hi,
    I've used fix bin strategy in warehouse management,  and I set a fix bin B01 for the material 100-100,
    If I create a transfer order for this material via Tcode LT01 and assign a destination storage bin B02 to it, a <b>WARNING</b> message appeared, but I still can post the transfer order;
    But if I create a transfer order by function module L_TO_CREATE_MULTIPLE to do the same things above, the system gived me an<b> ERROR</b> message,
    So, what's the reason? Did I missed some parameters?  because it should be a warning message.
    Please kindly help.
    Thanks and best regards.

    hey I got one requirement to use the  L_TO_CREATE_MULTIPLE function module for "create transfer order Delete Vechicle WM" and I think I should use Movement type for this to delete vechicle, so please help me, if you know the answer.

  • L_TO_CREATE_MULTIPLE  storage Units

    hi,
    I'm trying to create a transfer order using function module L_TO_CREATE_MULTIPLE  but on certain cases I am getting error "Requested amount could not be supplied". I implemented the  user exit MWMTO004- Function module EXIT_SAPLL03A_005   to  assign differents  storage units onto T_QMAT internal table.
    Example:
    An example: Using FIFO when i am creating a TO for 100 pieces with these functions
    In the warehouse there is this stock:
    1000011358                  10           
    1000011348                  20
    1000011349                  20          
    1000011350                  20
    1000011351                  10           
    1000011352                  20
    How do  i need define my stock removal strategies? or How to solve it??
    Regards .
    Mireya A.

    Hi,
    Please try it in this way by passing only these many data to the function module.
    wa_lqua-werks TO wa_ltap_creat-werks,
         wa_lqua-lgort TO wa_ltap_creat-lgort,
         wa_lqua-matnr TO wa_ltap_creat-matnr,
         wa_lqua-charg TO wa_ltap_creat-charg,
         wa_lqua-bestq TO wa_ltap_creat-bestq,
         wa_lqua-sobkz TO wa_ltap_creat-sobkz,
         wa_lqua-sonum TO wa_ltap_creat-sonum,
         wa_lqua-verme TO wa_ltap_creat-anfme,
         wa_lqua-meins TO wa_ltap_creat-altme,
         wa_lqua-lqnum TO wa_ltap_creat-vlqnr,
         wa_lqua-lenum TO wa_ltap_creat-vlenr,
         wa_lqua-lgtyp TO wa_ltap_creat-vltyp,
         wa_lqua-lgpla TO wa_ltap_creat-vlpla.
    CALL FUNCTION 'L_TO_CREATE_MULTIPLE'
           EXPORTING
                i_lgnum                = lgnum
                i_bwlvs                = bwlvs
                i_commit_work          = c_x
           IMPORTING
                e_tanum                = tanum
           TABLES
                t_ltap_creat           = i_ltap_creat
           EXCEPTIONS
                error_message          = 99.
    Regards
    Hareesh Menon

  • Error "Available quantity in bin is zero" with FM: L_TO_CREATE_MULTIPLE

    Hi, all,    I encounter  one problem wtih BAPI:  L_TO_CREATE_MULTIPLE.
    I want to transfer 100 batches from P01 storage type to P02 storage type ,  this function module show error "Available quantity in bin is zero".  
    But the TO is created and this TO only include 30 batchs.
    Why this happen?
    Any one could help me? Tks.

    Hi Justin,
    I am facing the exact same problem.
    Can you please share the solution for this?
    Thanks in advance.
    Regards,
    Gayatri

  • Error with L_TO_CREATE_MULTIPLE

    Hi guys,
    I'm traying to use L_TO_CREATE_MULTIPLE but I get the next error: MANUAL_TO_FORBIDDEN, can anyone help me, please?
    This is the code that I'm using for:
    DATA: i_ltap_cr TYPE STANDARD TABLE OF ltap_creat WITH HEADER LINE,
          w_tanum   TYPE ltak-tanum,
          i_ltap_vb TYPE STANDARD TABLE OF ltap_vb WITH HEADER LINE.
    Set variables for Transfer Order Creation (material part)
    i_ltap_cr-matnr = 'SF196LEMQ'.
    i_ltap_cr-werks = 'F397'.
    i_ltap_cr-lgort = '0001'.
    i_ltap_cr-bestq = ' '.
    i_ltap_cr-letyp = '01'.
    i_ltap_cr-anfme = '1'.
    i_ltap_cr-altme = 'EA'.
    i_ltap_cr-vltyp = '001'.
    i_ltap_cr-vlpla = 'M051'.
    i_ltap_cr-vlqnr = '1'.
    i_ltap_cr-nlqnr = '1'.
    i_ltap_cr-nltyp = '001'.
    i_ltap_cr-nlpla = 'M086'.
    *i_ltap_cr-nlenr = wa_zekko_le-llenr.
    i_ltap_cr-squit = 'X'."This means automatically confirm
    APPEND i_ltap_cr.
    Now the Stillage must be added.
    i_ltap_cr-matnr = 'SF196LEMQ'.
    i_ltap_cr-werks = 'F397'.
    i_ltap_cr-lgort = '0001'.
    i_ltap_cr-bestq = ' '.
    i_ltap_cr-letyp = '01'.
    i_ltap_cr-anfme = '1'.
    i_ltap_cr-altme = 'EA'.
    i_ltap_cr-vltyp = '001'.
    i_ltap_cr-vlpla = 'M051'.
    i_ltap_cr-vlqnr = '1'.
    i_ltap_cr-nlqnr = '1'.
    i_ltap_cr-nltyp = '001'.
    i_ltap_cr-nlpla = 'M086'.
    *i_ltap_cr-nlenr = wa_zekko_le-llenr.
    i_ltap_cr-squit = 'X'."This means automatically confirm
    APPEND i_ltap_cr.
    Call FM to create Transfer Order (which also creates basic SU)
    CALL FUNCTION 'L_TO_CREATE_MULTIPLE'
      EXPORTING
        i_lgnum                = 'CBG'
        i_bwlvs                = '317'
        i_benum                = '2099'
        i_bname                = sy-uname
      IMPORTING
        e_tanum                = w_tanum
      TABLES
        t_ltap_creat           = i_ltap_cr
       t_ltap_vb              = i_ltap_vb
      EXCEPTIONS
        no_to_created          = 1
        bwlvs_wrong            = 2
        betyp_wrong            = 3
        benum_missing          = 4
        betyp_missing          = 5
        foreign_lock           = 6
        vltyp_wrong            = 7
        vlpla_wrong            = 8
        vltyp_missing          = 9
        nltyp_wrong            = 10
        nlpla_wrong            = 11
        nltyp_missing          = 12
        rltyp_wrong            = 13
        rlpla_wrong            = 14
        rltyp_missing          = 15
        squit_forbidden        = 16
        manual_to_forbidden    = 17
        letyp_wrong            = 18
        vlpla_missing          = 19
        nlpla_missing          = 20
        sobkz_wrong            = 21
        sobkz_missing          = 22
        sonum_missing          = 23
        bestq_wrong            = 24
        lgber_wrong            = 25
        xfeld_wrong            = 26
        date_wrong             = 27
        drukz_wrong            = 28
        ldest_wrong            = 29
        update_without_commit  = 30
        no_authority           = 31
        material_not_found     = 32
        lenum_wrong            = 33
        matnr_missing          = 34
        werks_missing          = 35
        anfme_missing          = 36
        altme_missing          = 37
        lgort_wrong_or_missing = 38
        OTHERS                 = 39.
    IF sy-subrc NE 0 OR w_tanum IS INITIAL.
    MESSAGE e999 WITH 'Failed to create transfer order'.
    ROLLBACK WORK.
    ENDIF.
    Regards...

    Hi,
    your movement type 317 does not allow manual creation of TO. You can check it in the table T333, field TBOBL. So you can change config for your movement type or you will have to use different one.
    Regards

  • Error in L_TO_CREATE_MULTIPLE

    Hi Experts,
    I'm using FM-- L_TO_CREATE_MULTIPLE to create the Transfer order for multiple items, i need to pass I_BETYP and I_BENUM values while creating transfer order. What values we need to pass in these parameters and from where we get these values.(I'm not able to use LTAK-BETYP and LTAK-BENUM values because once TO is created, then these fields updated, currently i have Handling Unit) . PLease suggest me.
    Thanks in advance.
    karthi

    Hello Aditya,
    Thanks for showing interest in my question.
    To answer your question of what I am trying to do, I hope this can shed some light.
    I was given a PO number and an Outbound delivery number to work with.
    We have created a custom (module) program that handles transactions regarding outbound deliveries, and one feature of this program is to do a reversal of Outbound deliveries already posted.
    When using this reversal feature using the given PO as reference, the error message which I mentioned in my previous post, is displayed on screen.
    The user is curious why this happens and yet the posted outbound delivery involved is reversed.
    Additional info:
    • VL02n > Post Goods Issues - to process(?) given Outbound delivery
    • Custom program - to do the reversal process
    • VL02n does Mvt 641 while the reversal does Mvt 642.
    I apologize as to not being so clear but I am not so well versed with MM and its workings.
    Thanks.
    ~ ric

  • Ltbp are not updated through 'L_TO_CREATE_MULTIPLE'.

    Hello,
    we are able to create TOs for TR created wth MB1B but which is not consistent .related table LTBP is not getting updated with TANUM created for the TR number .
    Please let  me know how to resolve this ..Thanlks a Lot.

    Hello ,
    Thanks for the reply , and below is my case .
    - I am creating Material Documents using MB1B which inturn creates Transfer Requirement .
    - With reference to the Transfer requirement created , I am trying to create Transfer Order using L_TO_CREATE_MULTIPLE function module by providing the Quants and Source Bins from where stoick has to be removed . Below is the code i m iusing .
    e_lgnum = gv_lgnum.
      e_benum = gv_tbnum.
      e_bwlvs = '311'.
      LOOP AT t_upload.
        t_ltap_creat-matnr = t_upload-matnr.
        t_ltap_creat-werks = <Plant>'.
        t_ltap_creat-lgort = '1000'.
        t_ltap_creat-anfme = t_upload-qty.
        t_ltap_creat-altme = t_upload-uom.
        t_ltap_creat-vltyp = <StType>
        t_ltap_creat-vlpla = t_upload-bin. ---BIN
        APPEND t_ltap_creat.
      ENDLOOP.
    Please advise what is missing in this ...or is there any other FM to do this .
    Thanks
      CALL FUNCTION 'L_TO_CREATE_MULTIPLE'
        EXPORTING
          i_lgnum                      = e_lgnum
          i_bwlvs                      = e_bwlvs
       I_BETYP                      = ' '
         i_benum                      = e_benum
      I_LZNUM                      = ' '
       I_NIDRU                      = 'X'
      I_DRUKZ                      = ' '
       I_NOSPL                      = 'X'
       I_UPDATE_TASK                = 'X'
         i_commit_work                = 'X'
         i_bname                      = sy-uname
         i_kompl                      = 'X'
      I_SOLEX                      = 0
      I_PERNR                      = 0
      I_MINWM                      = ' '
      I_AUSFB                      = ' '
       IMPORTING
         e_tanum                      = i_tanum
        TABLES
          t_ltap_creat                 =  t_ltap_creat
       T_LTAK                       = T_LTAK
       T_LTAP_VB                    = T_LTAP_VB
       EXCEPTIONS
         no_to_created                = 1
         bwlvs_wrong                  = 2
         betyp_wrong                  = 3
         benum_missing                = 4
         betyp_missing                = 5
         foreign_lock                 = 6
         vltyp_wrong                  = 7
         vlpla_wrong                  = 8
         vltyp_missing                = 9
         nltyp_wrong                  = 10
         nlpla_wrong                  = 11
         nltyp_missing                = 12
         rltyp_wrong                  = 13
         rlpla_wrong                  = 14
         rltyp_missing                = 15
         squit_forbidden              = 16
         manual_to_forbidden          = 17
         letyp_wrong                  = 18
         vlpla_missing                = 19
         nlpla_missing                = 20
         sobkz_wrong                  = 21
         sobkz_missing                = 22
         sonum_missing                = 23
         bestq_wrong                  = 24
         lgber_wrong                  = 25
         xfeld_wrong                  = 26
         date_wrong                   = 27
         drukz_wrong                  = 28
         ldest_wrong                  = 29
         update_without_commit        = 30
         no_authority                 = 31
         material_not_found           = 32
         lenum_wrong                  = 33
         matnr_missing                = 34
         werks_missing                = 35
         anfme_missing                = 36
         altme_missing                = 37
         lgort_wrong_or_missing       = 38
         OTHERS                       = 39
      IF sy-subrc <> 0.
      ENDIF.
    - Here I could able to see the Transfer Order created , but the Stock Levels for the Materials at WM Level are wrong .and moreover the link between Transfer Requirement and Transfer Order is not getting updated .I mean in table LTBP is getting updated with Transfer Order Number TANUM .

  • Creating Transfer Order for a Material document

    Hi,
    I am transferring the Unrestricted stock from one material to another material through Movement type 309.
    I am creating a material document through BAPI_GOODSMVT_CREATE. Once the Material document is created and if the stock is in multiple storage types or storage bins, then I need to perform LT06. Instead of doing BDC recording I am using L_TO_CREATE_MULTIPLE function module for creating the TO. I am passing all the necessary values to this FM. TO is getting created but the Material document is not reflecting in that TO.
    As per the configuration, movement type 309 will create the posting change only not the Transfer Requirement.
    Does anybody have encountered the same problem?. If so please let me know how you have resolved the issue.
    Regards,
    Kishore.

    Hello Kirankumar,
    It is possible to assign external number ranges for Storage unit, so maintain storage unit number range to assign SU number externally.
    Now when you create Transfer order for material document at that time you can assign SU number externally.
    Hope this helps.
    regards,
    Arif Mansuri

  • How can I catch a error in a BAPI?

    Hi,
    I use BAPI L_TO_CREATE_MULTIPLE. If, for example, I put a warehouse that not is the warehouse of the unit that I want to move, I receive an error that isn't in exceptions.
    In the program, I need, in the sy-subrc, catch this error, to do anything.
    In this case, the message is L3208.
    Thank you very much.

    Hello Jose
    BAPIs must not raise any exceptions. Why? Because they are intended for external use. However, if you raise an exception during a RFC call the connection will break down. Therefore BAPIs collect the error message in their (usually named) RETURN parameter.
    In order to evaluate a BAPI call you can simply code like this:
    " Assumption: RETURN parameter is an itab of type BAPIRET2
    LOOP AT return TRANSPORTING NO FIELDS
              WHERE ( type CA 'AEX' ).
      EXIT.
    ENDLOOP.
    IF ( syst-subrc = 0 ).
    " A(bort), E(rror) or X(dump) happened
    ENDIF.
    Regards
      Uwe

Maybe you are looking for