L_TO_CREATE_DN

Hi,
in my code i have:
SELECT        * FROM lips INTO TABLE tlips WHERE vbeln = likp-vbeln.
IF NOT tlips[] IS INITIAL.
    CLEAR: it_delit, l_wa_delit.
    REFRESH it_delit.
    LOOP AT tlips INTO wa_tlips.
Compruebo el estatus de la posición
    CLEAR l_kosta.
    SELECT SINGLE kosta FROM vbup INTO l_kosta
      WHERE vbeln = wa_tlips-vbeln
      AND posnr = wa_tlips-posnr.
      CHECK l_kosta <> 'C'.
    CLEAR: lv_tanum, lv_teilk.
      CLEAR: l_wa_delit, it_delit.
      REFRESH it_delit.
posición
      l_wa_delit-posnr = wa_tlips-posnr.
cantidad
      l_wa_delit-anfme = wa_tlips-lfimg.
ud. medida alternativa
      l_wa_delit-altme = wa_tlips-meins.
ua
      l_wa_delit-vlenr = lein-lenum.
Tipo alm.procedencia
      l_wa_delit-vltyp = lein-lgtyp.
Área de almacén de procedencia
     l_wa_delit-vlber = '001'.
Ubic.proced.
      l_wa_delit-vlpla = lein-lgpla.
Posición en la ubicación de procedencia
     l_wa_delit-vppos = wa_ltap-vppos.
      APPEND l_wa_delit TO it_delit.
    break-point.
    CALL FUNCTION 'L_TO_CREATE_DN'
      EXPORTING
        I_LGNUM                          = rm07m-lgnum
        I_VBELN                          = likp-vbeln
        I_COMMIT_WORK                    = '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.
    BREAK-POINT.
    IF lv_tanum IS INITIAL.
      READ TABLE messtab WITH KEY msgtyp = 'E'.
      message_id      = sy-msgid.
      message_number = sy-msgno.
      message_v1      = sy-msgv1.
      message_v2      = sy-msgv2.
      message_v3      = sy-msgv3.
      message_v4      = sy-msgv4.
      perform error_message_screen using '9999'
                                          message_id
                                          message_number
                                          message_v1
                                          message_v2
                                          message_v3
                                          message_v4.
      LEAVE TO SCREEN sy-dynnr.
    ELSE.
      COMMIT WORK AND WAIT.
      PERFORM confirm_to
        USING rm07m-lgnum lv_tanum wa_tlips-matnr wa_tlips-charg.
    ENDIF.
ENDLOOP.
    LEAVE TO TRANSACTION 'ZOTUA'.
ENDIF.
this code creates a TO and this TO has several positions.
what i want IS to create a TO from a delivery (LIKP-VBELN)and a Storage Unit Number (LEIN-LENUM).
My problem is that although the TO gets created OK, it cantains several positions whereas i only want just the position containing my Storage Unit Number (LEIN-LENUM).
Best regards.

Hi Pablo,
I wondered how you resolved this issue?
Thanks

Similar Messages

I can't print a form immediately from L_TO_CREATE_DN

Hello,
I only speak a litte englis so I wait that you can understandme.
I use a fm L_TO_CREATE_DN and this fm print a sapscript. I see tha I can send the name of print but I can't send the tput Immediately. When I execute the fm the form don't print and it keep in the spool. Can I make anything to obligate to print inmediately?
Thank you very much.

Hi,
Check this
CALL FUNCTION 'L_TO_CREATE_DN'
    EXPORTING
      i_lgnum                          = gs_lipov-lgnum
      i_vbeln                          = gv_input
I_REFNR                          = ' '
I_SQUIT                          = ' '
I_NIDRU                          = ' '
I_DRUKZ                          = ' '
I_LDEST                          = ' '
I_KOMIM                          = ' '
I_EINLM                          = ' '
I_EINTA                          = ' '
I_NOSPL                          = ' '
I_UPDATE_TASK                    = ' '
     i_commit_work                    = 'X'
     i_bname                          = sy-uname
     i_teilk                          = lv_teilk
I_SOLEX                          = 0
I_PERNR                          = 0
IT_DELIT                         =
   IMPORTING
     e_tanum                          = ls_ltak-tanum
E_TEILK                          =
   TABLES
     t_ltak                           = lt_ltak
T_LTAP_VB                        =
T_WMGRP_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
pass the above parameters

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.

Missing parameters for L_TO_CREATE_DN (Transfer Order Creation)

Hi,
Though i am passing T_LTAP_VB-LETYP, i am getting an error message as 'Enter the storage unit type', could you please let me know what i am missing here.
I am passing the following fields to the function module (L_TO_CREATE_DN):
I_LGNUM
I_VBELN
I_COMMIT_WORK = 'X'.
I_BNAME = User name.
T_LTAK-LGNUM
T_LTAP_VB-LGNUM
T_LTAP_VB-LETYP
T_LTAP_VB-NLTYP
T_LTAP_VB-NLPLA
T_LTAP_VB-NSOLM
T_LTAP_VB-NLENR
Thanks
Satya
Edited by: Satya suresh Donepudi on Aug 18, 2010 4:37 PM

Hi,
This function module does create problems in passing the data.
We had a similar situation and finally ended up exporting to memory and importing it in an enhancement implementation inside the function module.
We implemented it here IF_EX_SCM_TRM_RELEVANCE_D~TRM_RELEVANCE_CHECK (before endmethod)
But perhaps it can be done outside this call as well.

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

Over picking not allowed for L_TO_CREATE_DN

Hi experts,
Can anybody help me doing over picking of delivery quantity when creating TO using BAPI L_TO_CREATE_DN ?
My requirement is such that:
Create a TO with 300 quantity against a delivery number that having 200 quantity and I need to set "Adopt pick quantity" = 1, i.e. i_KOMIN = 1.
I tried it with passing it_delit table having values pf POSNR,ANFME,ALTME. and i_lgnum,i_vbeln, i_komim = 1,i_nospl = 1, i_commit_work = X.
But it throws exception with msg "Total for assigned quantities exceeds quantity to be removed".
How can I acieve this reqmt?Pls help.
Thanks in advance,
Samy.

Finally I solved this issue by adding some enhncement point to the various subroutines called by this BAPI.
1. Inside include ML03TF50_LTAPA_AUFBAUEN_DN
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(1 ) Form LTAPA_AUFBAUEN_DN, Start                                                                                D
$$-Start: (1 )----
$$
ENHANCEMENT 85 ZES_TO_2611_2.    "active version
if sy-tcode eq 'CO11'.
    DATA: lv_flag TYPE char1.
    lv_flag = '1'.
    EXPORT lv_flag FROM lv_flag TO MEMORY ID 'Z2611_FLAG'.
ENDIF.
ENDENHANCEMENT.
"and
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(2 ) Form LTAPA_AUFBAUEN_DN, End                                                                                D
$$-Start: (2 )----
$$
ENHANCEMENT 84 ZES_TO_2611_2.    "active version
IF sy-tcode eq 'CO11'.
    DATA: lv_menge TYPE LTAP_VSOLM.
    IMPORT lv_menge TO lv_menge FROM MEMORY ID 'Z2611_MENGE'.
    LOOP AT ILTAPA.
      ILTAPA-ANFML = lv_menge.
      MODIFY ILTAPA INDEX sy-tabix FROM ILTAPA TRANSPORTING ANFML.
    ENDLOOP.
    CLEAR lv_menge.
    FREE MEMORY ID 'Z2611_MENGE'.
ENDIF.
ENDENHANCEMENT.
2. Inside include FL000F00
(inside form UMRECHNEN_ALTME_MEINS)
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(1 ) Form UMRECHNEN_ALTME_MEINS, End                                                                                D
$$-Start: (1 )----
$$
ENHANCEMENT 2 ZES_TO_2611_1.    "active version
if sy-tcode eq 'CO11'.
    DATA: lv_menge TYPE LTAP_VSOLM,
          lv_flag TYPE char1.
    IMPORT lv_flag TO lv_flag FROM MEMORY ID 'Z2611_FLAG'.
    IF lv_flag eq '1'.
      lv_menge = P_MENGE.
      EXPORT lv_menge FROM lv_menge TO MEMORY ID 'Z2611_MENGE'.
      P_MENGE = 0.
      CLEAR lv_flag.
      FREE MEMORY ID 'Z2611_FLAG'.
    ENDIF.
ENDIF.
ENDENHANCEMENT.
(inside form UMRECHNEN_MEINS_ALTME)
ENHANCEMENT 1 ZES_TO_2611_1.    "active version
if sy-tcode eq 'CO11'.
    DATA: lv_menge TYPE LTAP_VSOLM,
          lv_flag TYPE char1.
    IMPORT lv_flag TO lv_flag FROM MEMORY ID 'Z2611_FLAG'.
    IF lv_flag eq '1'.
      lv_menge = P_MENGE.
      EXPORT lv_menge FROM lv_menge TO MEMORY ID 'Z2611_MENGE'.
      P_MENGE = 0.
      CLEAR lv_flag.
      FREE MEMORY ID 'Z2611_FLAG'.
    ENDIF.
ENDIF.
ENDENHANCEMENT.

L_TO_CREATE_DN for quantity that is over outbound delivery quantity.

Hi all,
I use l_to_create_dn to create to's for shipments. If the qty entered is lower then the quantity needed all works fine because the option komim is used in the call. The quantity is updated to the quantity the was put in t_delit. The problem is, if m'I quantity is higher than the outbound delivery the exception 15 is returned. The customizing is done for batch split.
I saw that there's an oss note 855729. But I'm not convinced that it will help the situation.
Regards!
Curtis

Hi all,
I implemented the note and this does not correct m'I problem.
The exception 15 is raised if qty picked is greater the outboud delivery qty.
No userexit, no enhancement available.
Please help.
Regards!
Curtis

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.

What do i have to populate in L_TO_CREATE_DN??

Hi, I'm having some problems with the function module L_TO_CREATE_DN. I need to create transfer orders with some items, but I don't know what do I have to complete in the FM. I am populating I_LGNUM and I_VBELN in the importing, but after that I don't know where I can populate the charasteristic of each item. I think is in the IT_DELIT, but there I can't populate things like MATNR, WERKS, LGORT, ... Does anybody how to do it???
Many thanks.

Hey
I m not in front of the system,
but first go and check in the FM L_TO_CREATE_DN what kind of input it can take ?
Go to SE37 and see the Imporing parameter and Tables TAB and see the structure Then declare your's own structure. You have to go as per the defined rules. If you can'extract MATNR using this FM then you have to use some SELECT queries using the ouput of this FM.
hope this wll help.
Thanks
Ashwani

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.

Problem with FM L_TO_CREATE_DN.

Hi everyone!
I've been using FM L_TO_CREATE_DN for splittng TO's, so here's my problem:
I am splitting TO's based on field MLGN-LHMG1, and this quantity is the maximum articles a TO could have. Here's an example:
In my delivery I have to pick 9000 units of material 111, and my maximum quantity is 2000, so, I need to split that material (because there are other materials in my delivery) into 5 individual TO's:
4 TO with 2000 units
1 TO with 1000 units
5 TO with 9000 units
But when I call function L_TO... I have this message: "There are still delivery positions to treat." (Or something like that, because my sistem is in spanish, so I try to tranmslate it).
I don't know what to do. Here's my piece of code where I call this function:
CALL FUNCTION 'L_TO_CREATE_DN'
        EXPORTING
          i_lgnum       = vl_vblk-lgnum
          i_squit       = space
          i_vbeln       = vl_vblk-vbeln
          i_bname       = sy-uname
          i_commit_work = 'X'
          it_delit      = tl_deli
         i_nospl       = 'X'
         i_teilk       = 'X'
        IMPORTING
          e_tanum       = vl_tanu.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
I have no problems qith import & export params, I've already debugged, but the problem is still there, maybe it's a configuration trouble, but I don't know...
Hope you can help me.
Best regards.

LOOP AT L_TAB INTO S_TAB.
          READ TABLE XLIPS WITH KEY POSNR = S_TAB-POSNR.
          WA_DELIT-POSNR = S_TAB-POSNR.
          WA_DELIT-ANFME = S_TAB-VEMNG.
          WA_DELIT-ALTME = xLIPS-MEINS.
          WA_DELIT-CHARG = xLIPS-CHARG.
          WA_DELIT-VLENR = S_TAB-LENUM.
          APPEND WA_DELIT TO IT_DELIT.
        ENDLOOP.
   CALL FUNCTION 'L_TO_CREATE_DN'
          EXPORTING
            I_LGNUM                          = WHS_ID
            I_VBELN                          = DELV_ID
          I_REFNR                          = ' '
          I_SQUIT                          = ' '
          I_NIDRU                          = ' '
          I_DRUKZ                          = ' '
          I_LDEST                          = ' '
          I_KOMIM                          = ' '
          I_EINLM                          = ' '
          I_EINTA                          = ' '
          I_NOSPL                          = ' '
          I_UPDATE_TASK                    = ' '
           I_COMMIT_WORK                    = 'X'
          I_BNAME                          = SY-UNAME
          I_TEILK                          = 'X'
          I_SOLEX                          = 0
          I_PERNR                          = 0
           IT_DELIT                         = IT_DELIT
         IMPORTING
           E_TANUM                          = TANUM
          E_TEILK                          =
         TABLES
           T_LTAK                           = T_LTAK
          T_LTAP_VB                        =
          T_WMGRP_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
This is the code which i used and it worked for me.

Storage Unit stays after L_TO_CREATE_DN

Hi,
I use L_TO_CREATE_DN to pick SUs (Storage Unit) and post goods movements. I give the parameter "KOMIM = 2".
The WM Stock (LQUA table) lines disappear as expected, but the SU header data (LEIN table) stays without any change. It causes many problems.
Any ideas ?
Regards,

Hi.
By using L_TO_CREATE_DN, you are creating and confirming TO?
When you create a TO you should get your SU assigned to it (if your storage type is not bulk or open storage etc.)... I gues that works for you since you have automated the process... So after confirming the TO, this SU should disappear (check in LS33 for your SU if it exists), but it doesn't necessarily have to disappear - e.g. if your SU has 100 cs and you picked 50 cs from it. It should still exist with qty of 50 cs.
Instead of looking at table LEIN, check if your SU is showing in LS33.
Regards,
Mihailo

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

L_TO_CREATE_DN

Similar Messages

Maybe you are looking for