TO confirmation : L_TO_CONFIRM

Hi ,
I am using function module -L_TO_CONFIRM , to confirm the TO in custom code . but not able to handle the the partial quantity confirmations. i mean if there is a actual quantity of 45 and I need to confirm only 12 units , it confirms the complete item . Not sure , if I am missig something in passing the values .
CALL FUNCTION 'L_TO_CONFIRM'
      EXPORTING
           i_lgnum       = it_ltap-lgnum
           i_tanum       = it_ltap-tanum
           i_squit       = 'X'
           i_qname       = sy-uname
           i_commit_work = 'X'
      TABLES
           t_ltap_conf   = i_ltap_conf
Passing the itab with below data:
TANUM          0000005957
TAPOS           0001
SQUIT           X
PARTI           X
please suggest ....
Thanks

Hi
Check this link it may help You..
Partial Confirmation not working through Backorder Processing in GATP

Similar Messages

TO 2-step confirmation using either L_TO_CONFIRM or L_TO_CONFIRM_SU

Hi,
I've created a TO using the L_TO_CREATE_MOVE_SU function module. I then need to confirm the TO but through a 2-step confirmation. I've both the L_TO_CONFIRM_SU and L_TO_CONFIRM function modules but have only got errors.
Parameters used for these function modules are as below :
L_TO_CONFIRM_SU
Exporting I_LENUM = <storage unit number>
               I_QUKNZ = '1'
Tables     T_LTAP_CONF = <TO items taken from LTAP>
Error returned - Warehouse number does not exist (new selection required)
L_TO_CONFIRM
Exporting I_LGNUM = <warehouse number>
               I_TANUM = <TO created from the L_TO_CREATE_MOVE_SU FM above>
               I_QUKNZ = '1'
Tables     T_LTAP_CONF = <TO items taken from LTAP>
Error returned - Movement type 000 is not allowed (check your entry)
With both these FMs, I've also tried populating the T_LTAP_CONF_HU tables but the same errors were returned. Can anyone please help with some example on how to use these function modules properly?
Note : The purpose of these function modules is to carry out the functions in transaction LT13 (firstly to pick, and then to transfer)
Thanks and regards,
Adeline.

Hi Maen,
Thanks for your reply.
Firstly, I did try all sorts of combinations, especially with the T_LTAP_CONF and T_LTAP_CONF_HU tables in both the function modules, so yes, I did more than enough trial and error but which still returned the same results.
Now, to answer your guesses :
1. Nope, I did not enter a wrong warehouse number. If you look at L_TO_CONFIRM_SU, you can see that there are no import parameters for warehouse, and warehouse also does not exist within the T_LTAP_CONF nor T_LTAP_CONF_HU tables, so I definitely did not enter a wrong warehouse number by mistake.
2. The TO was created with movement type 999 and again, if you look at L_TO_CONFIRM, there isn't an import parameter which takes in movement type nor does this exist in the T_LTAP_CONF nor the T_LTAP_CONF_HU tables which I've also used.
Can anyone else provide an insight into this?
Thanks and regards,
Adeline.

How to use L_TO_CONFIRM to confirm transport order

Hello friends,
I am using function L_TO_CONFIRM to confirm transport order in my program.
But it is not working. I have copied the main fields from table ltak and ltap. However it is still not working. May be some other parameters need to be filled.
Can anybody of you tell me as how can I use this function module to confirm transport order.
Regards,
Navin

Hi,
loop at gc_vbfa.
clear il_ltap_conf.
refresh il_ltap_conf.
il_ltap_conf-tanum = gc_vbfa-vbeln.
il_ltap_conf-tapos = gc_vbfa-posnn.
il_ltap_conf-nista = 0.
il_ltap_conf-ndifa = gc_vbfa-rfmng.
il_ltap_conf-altme = gc_vbfa-meins.
append il_ltap_conf.
Confirm TO
if s_fct_vars-peak_user = space.
l_ename = sy-uname.
else.
l_ename = s_fct_vars-peak_user+0(12).
endif.
l_tanum2 = gc_vbfa-vbeln.
CALL FUNCTION 'L_TO_CONFIRM'
EXPORTING
I_LGNUM = l_lgnum
I_TANUM = l_tanum2
I_SQUIT = ' '
I_QUKNZ = ' '
I_SUBST = ' '
I_QNAME = SY-UNAME
I_ENAME = L_ENAME
I_SOLEX = 0
I_PERNR = 0
I_STDAT = INIT_DATUM
I_STUZT = 0
I_ENDAT = INIT_DATUM
I_ENUZT = 0
I_ISTWM = 0
I_KOMIM = ' '
I_EINLM = ' '
I_TBELI = ' '
I_UPDATE_TASK = ' '
I_COMMIT_WORK = 'X'
I_AUSFB = ' '
TABLES
T_LTAP_CONF = il_ltap_conf
T_LTAP_CONF_HU =
T_LTAP_CONF_HU_SERIAL = il_ltap_serial
EXCEPTIONS
TO_CONFIRMED = 1
TO_DOESNT_EXIST = 2
ITEM_CONFIRMED = 3
ITEM_SUBSYSTEM = 4
ITEM_DOESNT_EXIST = 5
ITEM_WITHOUT_ZERO_STOCK_CHECK = 6
ITEM_WITH_ZERO_STOCK_CHECK = 7
ONE_ITEM_WITH_ZERO_STOCK_CHECK = 8
ITEM_SU_BULK_STORAGE = 9
ITEM_NO_SU_BULK_STORAGE = 10
ONE_ITEM_SU_BULK_STORAGE = 11
FOREIGN_LOCK = 12
SQUIT_OR_QUANTITIES = 13
VQUIT_OR_QUANTITIES = 14
BQUIT_OR_QUANTITIES = 15
QUANTITY_WRONG = 16
DOUBLE_LINES = 17
KZDIF_WRONG = 18
NO_DIFFERENCE = 19
NO_NEGATIVE_QUANTITIES = 20
WRONG_ZERO_STOCK_CHECK = 21
SU_NOT_FOUND = 22
NO_STOCK_ON_SU = 23
SU_WRONG = 24
TOO_MANY_SU = 25
NOTHING_TO_DO = 26
NO_UNIT_OF_MEASURE = 27
XFELD_WRONG = 28
UPDATE_WITHOUT_COMMIT = 29
NO_AUTHORITY = 30
LQNUM_MISSING = 31
CHARG_MISSING = 32
NO_SOBKZ = 33
NO_CHARG = 34
NLPLA_WRONG = 35
TWO_STEP_CONFIRMATION_REQUIRED = 36
TWO_STEP_CONF_NOT_ALLOWED = 37
PICK_CONFIRMATION_MISSING = 38
QUKNZ_WRONG = 39
HU_DATA_WRONG = 40
NO_HU_DATA_REQUIRED = 41
HU_DATA_MISSING = 42
HU_NOT_FOUND = 43
PICKING_OF_HU_NOT_POSSIBLE = 44
NOT_ENOUGH_STOCK_IN_HU = 45
SERIAL_NUMBER_DATA_WRONG = 46
SERIAL_NUMBERS_NOT_REQUIRED = 47
NO_DIFFERENCES_ALLOWED = 48
SERIAL_NUMBER_NOT_AVAILABLE = 49
SERIAL_NUMBER_DATA_MISSING = 50
TO_ITEM_SPLIT_NOT_ALLOWED = 51
OTHERS = 52
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
S_FCT_VARS-FCT_MSG_AREA = sy-msgid.
S_FCT_VARS-FCT_MSG_ID = sy-msgno.
S_FCT_VARS-FCT_RTN_CODE = 8.
S_FCT_VARS-FCT_MSG_VAR1 = SY-MSGV1.
S_FCT_VARS-FCT_MSG_VAR2 = SY-MSGV2.
S_FCT_VARS-FCT_MSG_VAR3 = SY-MSGV3.
S_FCT_VARS-FCT_MSG_VAR4 = SY-MSGV4.
S_FCT_VARS-FCT_MSG_LEVEL = 'E'.
else.
IF L_POST_MSG_SUCCESS = 'MSG_ON'.
S_FCT_VARS-FCT_MSG_AREA = 'ZPKUK01STD'.
S_FCT_VARS-FCT_MSG_ID = '209'.
S_FCT_VARS-FCT_RTN_CODE = 0.
S_FCT_VARS-FCT_MSG_LEVEL = 'S'.
S_FCT_VARS-FCT_MSG_VAR1 = gc_vbfa-vbeln.
S_FCT_VARS-FCT_MSG_VAR2 = gc_vbfa-posnn.
ENDIF.
Document logging
IF L_DOCUMENT_LOGGING = 'Y'.
concatenate gc_vbfa-vbeln
gc_vbfa-posnn
into L_TARGET_DOCUMENT separated by '-'.
L_SOURCE_DOCUMENT = gc_vbfa-vbeln.
PERFORM PST1700_DOCUMENT_LOGGING
USING 'PICKING'
L_SOURCE_DOCUMENT
L_TARGET_DOCUMENT
'TOIT'
'L_TO_CONFIRM'
L_TXN_DESC
L_EVNT_ERROR.
ENDIF.
endif.
endloop. " gc_vbfa
commit work AND WAIT.
loop at gc_vbfa.
gd_vbfa-vbelv = gc_vbfa-vbelv.
gd_vbfa-posnv = gc_vbfa-posnv.
append gd_vbfa.
endloop. " gc_vbfa
sort gd_vbfa by vbelv posnv.
delete adjacent duplicates from gd_vbfa comparing vbelv posnv.
loop at gd_vbfa.
if s_fct_vars-fct_rtn_code = 0.
L_VBKOK-VBELN_VL = gd_vbfa-vbelv.
clear l_vbpok.
refresh l_vbpok.
l_vbpok-vbeln_vl = gd_vbfa-vbelv.
l_vbpok-posnr_vl = gd_vbfa-posnv.
l_vbpok-lips_del = c_x.
append l_vbpok.
set update task local.
call function 'WS_DELIVERY_UPDATE'
exporting
vbkok_wa = l_vbkok
commit = ' '
delivery = gd_vbfa-vbelv
tables
vbpok_tab = l_vbpok
exceptions
others = 0.
commit work and wait.
Refer below link:
https://forums.sdn.sap.com/click.jspa?searchID=4082151&messageID=3039845
<b>Reward points</b>
Regards

Confirm Transfer order using FM L_TO_CONFIRM

Dear All,
I need to confirm a transfer order.
I am using this FM 'L_TO_CONFIRM' to do that, but i think there is some issue in populating the tables parameter (T_LTAP_CONF & T_LTAP_CONF_HU) of this FM, so i am not getting the sy-subrc to 0.
Can anyone who used the above fm, please post the code - from fetching values from tables to populating the parameters of this FM.
This would be really helpful.
Thanks,
Hima

Is WS_LM_TRANSFER_ORDER_CREATE a better option for my desired results?

Confirm TO Query (ref:L_TO_CONFIRM)

HI Everyone,
I have a query regarding TO confirmation that I'd appreciate some advice on. I implemented a custom RF transaction to confirm TO for putaway using the function module L_TO_CONFIRM. To my mind it's working as it should but my client has reported what they think is an error. Bascially when the TO is created from the goods receipt it's creating entries as follows . e.g
Material Batch   QTY
1234      ABC     1
1234      ABC    1
Now when the client uses the RF transasction they scan in the details for material batch and quantiy and perform the confirm action. In the example above they enter Quantity as 2 so they expect both lines above to be confirmed. Currently it just confirms one of these lines. My question is this:
Why have two different lines on the TO/GR with the same material and batch instead of just one line with a quantity two ?
and
Can the function module L_TO_CONFIRM handle the above scenario ?
Any help or advise is greatly appreciated.
Thanks for your time
DK

More or less what J put. Presumably you've got two TO items as there are two destination bins. On that basis confirming a quantity of 2 is incorrect if that is against a single TO item. In fact you should probably have some form of feedback given to the operator to that effect i.e. an 'error' or 'warning' sound and msg as quantity input does not match quantity expected, for your custom RF tx.
You've got two issues:
1. Understand why quantity split over two items and possibly correct settings
2. Consider how to present the information to the operator so the operator understands the expected quantity and is alerted to entry of a quantity that doesn't match.

L_TO_CONFIRM - TO for Confirm an HU into another HU

Hello,
I would try to replicate through FM the following situation that I can create (do) withstandard transactions
LT01 - LT12: Confirm a WM HU within another HU.
I have 2 source HU WM within the same bin block location , the same batch, same qty, all equal.
I Create with LT01, a TO with generic TMV 999, qty sum (QTA1 + QTA2) of the two source hu and I specific that the destination HU NLENR and NLQNR must be one of the two source HU that already exists in warehouse (finding on LENUM AND NLQNR in LQUA) .
When I confirm the OT created with LT12, I go on confirm internally, do 'X' on Confirm and insert the other source HU (not inserted as NLENR) then 'fetch in foreground' and save .
The result is that I have a only HU now with both quantities.
I tried to replicate L_TO_CONFIRM, CONFIRM_TO but I can not find the right configuration.
The OT created with LT01 is the same of L_TO_CREATE
Do you have tips?

Hi Rohit,
Can you tell me how u used this FM and what field should be filled.
Kind regards,
John Nijburg.

Confirming TO with 2-step confirmation using L_TO_CONFIRM

I have been using function module L_TO_CONFIRM in several programs with good results, but now I have a scenario where 2-step confirmation is enabled, which means that the TO is confirmed in two steps (with manual confirmation using LT12 you first confirm the "pick" and then in a second confirmation the "transfer").
I have not found a way to do this with L_TO_CONFIRM. The documentation (long text for structure LTAP_CONF) talks about many variants, and even mentions 2-step confirmations in connection with TO splitting, but it never explains how to actually perform the 2-step confirmation. Anyone that has any experience with this? Useful answers will of course be rewarded.
/Leif

I am interested in configuring the 2-step confirmation, but seem to be missing something in config. Can you give me the required config items for this functionality? Thanks.

TO Confirmation Error using FM L_TO_CONFIRM

Hi Gurus,
I am using L_TO_CREATE_DN to create TO for delivery. And using that TO created in L_TO_CONFIRM to confirm the TO. But i am getting an error that 'Transfer order does not exist in warehouse number (check entry)'. But when i an taking that TO which is created by FM L_TO_CREATE_DN in LT12 is there. I think i have to call some other FM in between to clear the buffer or some thing else.
Please let me know what should be done to correct this.
Thanks in Advance.
Sharat Chandra
Gurus,
Above probelm is solved Actually in FM L_TO_CONFIRM if we activate the
i_update_task = 'X'
, then its confirming the TO.
Thanks for the intrust shown.
Regards
Sharat

Have already updated the Answer.

Soniya here!! need help.... Creation of transfer Order. and confirmation.

Hi all ,
I am in need of a fuction module to create a transfer order ( LT03 ) where i am able to pass / specify the source storage unit / handling unit from which the materials can be taken for the TO.
I also need a function module where i can confirm this TO in LT12.
Thank you in advance.
Ponits for sure!!!

Hi,
Use FM : L_TO_CONFIRM to confirm the transfer order.
MOVE wa_to_tab4-tanum TO g_confirm_tab-tanum.
MOVE wa_to_tab4-tapos TO g_confirm_tab-tapos.
MOVE wa_to_tab4-altme TO g_confirm_tab-altme.
MOVE wa_to_tab4-nista TO g_confirm_tab-pickm.
IF NOT wa_to_tab4-vlenr IS INITIAL.
    MOVE wa_to_tab4-vlenr TO g_confirm_tab-lenum.
ELSE.
    MOVE g_vscfld TO g_confirm_tab-lenum.
ENDIF.
MOVE 'X' TO g_confirm_tab-parti.
IF NOT wa_to_tab4-nlpla_old IS INITIAL AND
     NOT wa_to_tab4-nltyp_old IS INITIAL.
    MOVE wa_to_tab4-nlpla TO g_confirm_tab-nlpla.
    g_confirm_tab-squit = 'X'.
ENDIF.
IF wa_to_tab4-nistm > wa_to_tab4-nista.
    l_diff = 'X'.
    g_confirm_tab-kzdif = wa_to_tab4-kzdif.
ENDIF.
PERFORM get_bint_param USING g_lgnum wa_to_tab4-vltyp
                         CHANGING l_returns.
CASE l_returns.
    WHEN '1' OR '3'.
      IF l_diff EQ 'X'.
        MOVE wa_to_tab4-nista TO g_confirm_tab-nista.
        g_confirm_tab-ndifa = wa_to_tab4-vsolm - wa_to_tab4-nista.
      ELSE.
        MOVE wa_to_tab4-nista TO g_confirm_tab-nista.
      ENDIF.
    WHEN '2'.
      IF l_diff EQ 'X'.
        g_confirm_tab-diffm = wa_to_tab4-verme - wa_to_tab4-nista.
        g_confirm_tab-restm = 0.
      ELSE.
        g_confirm_tab-restm = wa_to_tab4-verme - wa_to_tab4-nista.
        g_confirm_tab-diffm = 0.
      ENDIF.
      g_confirm_tab-pickm = wa_to_tab4-nista.
      CONCATENATE '00' wa_to_tab4-vlenr INTO g_confirm_tab-lenum.
ENDCASE.
APPEND g_confirm_tab.
CALL FUNCTION 'L_TO_CONFIRM'
EXPORTING
    i_lgnum                              = wa_to_tab4-lgnum
    i_tanum                              = wa_to_tab4-tanum
I_SQUIT                              = ' '
I_QUKNZ                              = ' '
I_SUBST                              = ' '
i_qname                              = sy-uname
i_ename                              = sy-uname
I_SOLEX                              = 0
I_PERNR                              = 0
I_STDAT                              = INIT_DATUM
I_STUZT                              = 0
I_ENDAT                              = INIT_DATUM
I_ENUZT                              = 0
I_ISTWM                              = 0
I_KOMIM                              = ' '
I_EINLM                              = ' '
I_TBELI                              = ' '
I_UPDATE_TASK                        = ' '
   i_commit_work                        = 'X'
I_AUSFB                              = ' '
TABLES
    t_ltap_conf                          = g_confirm_tab
T_LTAP_CONF_HU                       =
T_LTAP_CONF_HU_SERIAL                =
EXCEPTIONS
   to_confirmed                         = 1
   to_doesnt_exist                      = 2
   item_confirmed                       = 3
   item_subsystem                       = 4
   item_doesnt_exist                    = 5
   item_without_zero_stock_check        = 6
   item_with_zero_stock_check           = 7
   one_item_with_zero_stock_check       = 8
   item_su_bulk_storage                 = 9
   item_no_su_bulk_storage              = 10
   one_item_su_bulk_storage             = 11
   foreign_lock                         = 12
   squit_or_quantities                  = 13
   vquit_or_quantities                  = 14
   bquit_or_quantities                  = 15
   quantity_wrong                       = 16
   double_lines                         = 17
   kzdif_wrong                          = 18
   no_difference                        = 19
   no_negative_quantities               = 20
   wrong_zero_stock_check               = 21
   su_not_found                         = 22
   no_stock_on_su                       = 23
   su_wrong                             = 24
   too_many_su                          = 25
   nothing_to_do                        = 26
   no_unit_of_measure                   = 27
   xfeld_wrong                          = 28
   update_without_commit                = 29
   no_authority                         = 30
   lqnum_missing                        = 31
   charg_missing                        = 32
   no_sobkz                             = 33
   no_charg                             = 34
   nlpla_wrong                          = 35
   two_step_confirmation_required       = 36
   two_step_conf_not_allowed            = 37
   pick_confirmation_missing            = 38
   quknz_wrong                          = 39
   hu_data_wrong                        = 40
   no_hu_data_required                  = 41
   hu_data_missing                      = 42
   hu_not_found                         = 43
   picking_of_hu_not_possible           = 44
   not_enough_stock_in_hu               = 45
   serial_number_data_wrong             = 46
   serial_numbers_not_required          = 47
   no_differences_allowed               = 48
   serial_number_not_available          = 49
   serial_number_data_missing           = 50
   to_item_split_not_allowed            = 51
   OTHERS                               = 52
Regards
Kannaiah

With Scanning call RFC of create TO and confirm TO W/O SAP WM confg--------

Hello expert,
We are using SAP WM functionality. Client is using scanning device for scanning a bar code. Can I integrate scanning with SAP WM to create TO and confirm TO with RFC? We do not want to use RF transaction/SAP RF configuration. Is it possible to call RFC with scanning? If yes how?
Thanks
Milind

Hello,
With my understanding .....For any pick in WM with RF, will be using the functional module "L_to_confirm" for confirmation of picking. In general WH worker scans first the TO bar code/Ship bar code/any bar code that directs him to go to the bin location with the RFGUN based on his que and use to scan the bin location verification bar code and make sure that that is the right location and picks the qty's that shows in the TO and then confirms immediately.
Now coming to your process you said in the last reply that "TO is already created and worker reaches the place and scan barcode". This is a standard way of doing pick with RF. You said once "he reached the place" it means he should know by scanning pick lable or reading pick sheet a person goes to the location and then you said scan the bar code i.e bin verification barcode and then he confirms the pick. If i understand some thing else.. i don't know... only i know is you need to have a Zprogram thriugh config the RF menu Tcode and that RF screen program will guide you to confirm the TO with GUN.
thanks... tkreddy

Two step confirmation for warehouse tasks in EWM

Hello everybody,
I am working on an internal prototyp to evaluate SAP EWM. Therefore it is essential that we use "two step confirmation" for warehouse tasks. Step one: confirm pick up of a pallet; Step two: confirm transportation of a pallet. Like it is used in SAP WM (Parameter I_QUKNZ in function module L_TO_CONFIRM and in standard SAP).
I haven't found anything similar to that in EWM so far. I searched in the official EWM SAP Press book and also in google. But right no I don't have any idea.
Do you guys have any hints on how to achieve two step confirmation somehow?
Many thanks in advance!
Stef

Hi Jürgen.
Thanks for your input! You are right, it works with RF!
But it works kind of strange. Deleting source storage bin, creating another position etc.
I will have a look how to adapt this.
Thanks!

L_TO_CONFIRM not updating VBBE. Are there alternatives?

We are using L_TO_CONFIRM to confirm TOs via RF in our warehouse. We have also recently upgraded from 6.04/7.01sp5 to 6.17sp5/7.40sp7.
Since the upgrade, L_TO_CONFIRM no longer updates VBBE for the source delivery when confirming a TO with difference. This is causing issues when dealing with constrained product.
I have opened an OSS message, but SAP has basically responded by telling me to go away because L_TO_CONFIRM is not released for customer use.
I have read through the documentation for L_TO_CONFIRM but don't see any options related to this.
Has anyone else faced this issue? How did you deal with it? Is there an alternative to L_TO_CONFIRM that I should be using instead?

Hi Bryan,
i´ve the same issue!
Since the upgrade L_TO_CONFIRM no longer update table VBBE.
If i use the standard to confirm a to it is working....
I have to debug the issue.

Running L_TO_CONFIRM getting Error Message L3 025

All;
I am running L_TO_CONFIRM for confirming a TO.
CALL FUNCTION 'L_TO_CONFIRM'
    EXPORTING
      i_lgnum                              = gv_lgnum
      i_tanum                              = gv_tanum
    TABLES
      t_ltap_conf                          = gt_iltapc
   EXCEPTIONS
I am getting an error L3 025 "Act.quantities and diff.quantities are not target quantities. Check entry"
Any ideas what might be causing this problem?   I am not changing ANY quantities. I am pulling information direct from LTAP and mapping into GT_ILTAPC. I tried using CONFIRM_TO, but it seemed even worse.
I am trying to mimic an LT12 transaction with a straight forward TO.
Any help would be greatly apprecaited.

when you are confirming a TO without differences in quantity, you have to set a parameter SQUIT at the item level in T_LTAP_CONF. Please try after setting this parameter.
Hope this helps.
Rajiv..

L_TO_CONFIRM

Hi Guyz,
what are all the parameters needs to pass to confirm TO into the function module(L_TO_CONFIRM)...im passing warehouse number and transfer order number ..Iam getting the exception 'NOTHING TO DO' (NO ITEM FOR CONFIRMATION(CHECK YOUR ENTRY).. i know why this is happening coz the table T_LTAP_CONF type LTAP_CONF is not populated in the   PERFORM QUITTIERUNG_PRUEFEN..
plz advise..
regards
Edited by: BrightSide on Oct 13, 2008 4:54 PM

Hi,
You have to pass t_ltap_conf internal table with the TO line populated in it.
MOVE <TO NO> TO t_ltap_conf-tanum.
                MOVE <TO ITEM NO> TO t_ltap_conf-tapos.
                MOVE <SU NUMBER> TO t_ltap_conf-lenum. "If the
     "storage type is SU managed only otherwise do not pass.
                MOVE 'X'          TO t_ltap_conf-vquit.
CALL FUNCTION 'L_TO_CONFIRM'
    EXPORTING
      i_lgnum                        = i_ltap-lgnum
      i_tanum                        = i_ltap-tanum
      i_qname                        = sy-uname
      i_commit_work                  = 'X'
    TABLES
      t_ltap_conf                    = t_ltap_conf
    EXCEPTIONS
      to_confirmed                   = 1
      to_doesnt_exist                = 2
      item_confirmed                 = 3
      item_subsystem                 = 4
      item_doesnt_exist              = 5
      item_without_zero_stock_check = 6
      item_with_zero_stock_check     = 7
      one_item_with_zero_stock_check = 8
      item_su_bulk_storage           = 9
      item_no_su_bulk_storage        = 10
      one_item_su_bulk_storage       = 11
      foreign_lock                   = 12
      squit_or_quantities            = 13
      vquit_or_quantities            = 14
      bquit_or_quantities            = 15
      quantity_wrong                 = 16
      double_lines                   = 17
      kzdif_wrong                    = 18
      no_difference                  = 19
      no_negative_quantities         = 20
      wrong_zero_stock_check         = 21
      su_not_found                   = 22
      no_stock_on_su                 = 23
      su_wrong                       = 24
      too_many_su                    = 25
      nothing_to_do                  = 26
      no_unit_of_measure             = 27
      xfeld_wrong                    = 28
      update_without_commit          = 29
      no_authority                   = 30
      lqnum_missing                  = 31
      charg_missing                  = 32
      no_sobkz                       = 33
      no_charg                       = 34
      nlpla_wrong                    = 35
      two_step_confirmation_required = 36
      two_step_conf_not_allowed      = 37
      pick_confirmation_missing      = 38
      quknz_wrong                    = 39
      hu_data_wrong                  = 40
      no_hu_data_required            = 41
      hu_data_missing                = 42
      hu_not_found                   = 43
      picking_of_hu_not_possible     = 44
      not_enough_stock_in_hu         = 45
      serial_number_data_wrong       = 46
      serial_numbers_not_required    = 47
      no_differences_allowed         = 48
      serial_number_not_available    = 49
      serial_number_data_missing     = 50
      to_item_split_not_allowed      = 51
      input_wrong                    = 52
      OTHERS                         = 53.
Regards,
Rudra

L_TO_CONFIRM error L3 854

Hi
Im facing lot of issues while confirming the TO using the FM L_TO_CONFIRM.
My scenario is , the delivery quantity is 10 KG, I am doing an under picking using multi level Handling units. (9 KG).
I have 3 level HU's, i.e., a pallet, inside that there are 3 shipper bags, each shipper bag has 3 shipper boxes. The total HU quant is 27 KG , with 3 shipper bags of 9 KG each. Now i am trying to confirm 1 shipper bag(9 KG) using the FM.
Its giving me error HU withdrawal with difference quantity is not possible with nested HU. I am not able to understand the issue.
Im passing parameters as below.
tanum = '105'.
tapos = 1
T_LTAP_CONF
nista = 9KG
ndifa = 1Kg
altme = kg
kzdif = 2.
T_LTAP_CONF_HU
VONHU = shipper bag exidv number
nachu = pick HU created
huent = 'X'
menge = 9
altme = Kg
dmgea = 1
funny thing is ,i can confirm the TO with shipper boxes,pls suggest if im missing anything,
Thanks

We are facing the same issue. Do you have the solution?
We are using leanwarehouse.
Thanks

TO confirmation : L_TO_CONFIRM

Similar Messages

Maybe you are looking for