Error in BAPI_OUTB_DELIVERY_CHANGE

HI All..
I developed a program to upload serial no's for a delivery no and the serial nos data will be in a text file. by passing this file we have to upload data..
program is working fine and it is uploading data into vl02n
but for some times its througing an error like error type E class IO no 299(Batch for serial number &1 (&2) differs from document batch &3).
in a text file i have 2 item no's for each item i have batch and each batch having no of serial nos for the first item its uploading successfully and for the next item its showing the above error.
i thought that those serial no's have already uploaded for any other delivery so i checked in objk table serial number field those serial no's of second item doesnot exist..
what could be the problem???
can any one please help me???

HI Santhosh,
Did you check with this issue with functional people.
Regards,
Madhu.

Similar Messages

Error while using BAPI_OUTB_DELIVERY_CHANGE

Hi Friends,
I m using BAPI_OUTB_DELIVERY_CHANGE to change the delivery. But I m getting error - Error in document &1 item &2 (quantity consistency check).
I m changing the delivered qty in batch-split and
delivered qty in header level.
Is there any problem in code
Some code snaps is:
loop at itab.
    item_data1-DELIV_NUMB = s_vbeln.
    item_data1-DELIV_ITEM = 10.
    item_data1-DLV_QTY = itab-nt_qty.
       item_data1-UNIT_OF_WT = itab-unit.
    append item_data1.
endloop.
ITEM_CONTROL1-DELIV_NUMB = s_vbeln.
item_control1-DELIV_ITEM = 10.
    item_control1-CHG_DELQTY = 'X'.
append item_control1.
CALL FUNCTION 'BAPI_OUTB_DELIVERY_CHANGE'
EXPORTING
    HEADER_DATA               = header_data1
    HEADER_CONTROL            = header_control1
    DELIVERY                  = s_vbeln
TECHN_CONTROL             =
TABLES
HEADER_PARTNER            =
HEADER_PARTNER_ADDR       =
HEADER_DEADLINES          =
    ITEM_DATA                 = item_data1
    ITEM_CONTROL              = item_control1
ITEM_SERIAL_NO            =
SUPPLIER_CONS_DATA        =
EXTENSION1                =
EXTENSION2                =
    RETURN                    = ret .
Please help me.

Hi friends, this can be solved setting values for the following additional parameters of structure ITEM_DATA.
FACT_UNIT_NOM = 1.
FACT_UNIT_DENOM = 1.
This works for me, please let me know if this works for you!
Regards
Leonardo

Error E/VL/280 (Required field in interface to delivery update missing &1 &2 &3 &4) using BAPI_OUTB_DELIVERY_CHANGE

Hi,
I am trying to change delivery quantity using BAPI_OUTB_DELIVERY_CHANGE. When I tested the BAPI by giving values in the parameters
HEADER_DATA, DELIVERY, ITEM_DATA and ITEM_CONTROL it is working fine.
However when I use the same BAPI in program and when I am trying to test it I am receiving error 'E/VL/280' (
Required field in interface to delivery update missing &1 &2 &3 &4).
Request to please help me out on how to resolve.
Much Appreciated.

Hi Nagarjuna,
Can you please check the program in debugging mode, &1 &2 &3 &4 are the place holders specifies some information. Might be missing some information while changing delivery document.
Check the place holders in debugging mode.
Thanks,
Ashok.

BAPI_OUTB_DELIVERY_CHANGE returns error - E |VLBAPI |004 | and W |VL |268

Hi buddies,
FYI, I had gone through the SDN but could not get the answer for my question.
I am facing problem in calling BAPI BAPI_OUTB_DELIVERY_CHANGE.
The RETURN parameter returns the following two messages without any message detail.
E |VLBAPI |004 | and
W |VL |268
I have to update net weight (Item data) and BOL (shipment) (tracking no. and box no.) in t code VL02n .
Pls help ! What parameter is required to pass to this BAPI for my scenario.
Thanks,
Vinish.
Edited by: vinish kumar on May 26, 2009 6:43 PM

Hi Nagarjuna,
Can you please check the program in debugging mode, &1 &2 &3 &4 are the place holders specifies some information. Might be missing some information while changing delivery document.
Check the place holders in debugging mode.
Thanks,
Ashok.

Problem when updating delivery quantity using 'BAPI_OUTB_DELIVERY_CHANGE'

Hi experts,
I have a requirement in which i need to update the material's delivery quantity in VL03N transaction.   For this im trying the BAPI
'BAPI_OUTB_DELIVERY_CHANGE' and im passing the following values.
HEADER_DATA : Delivery no.
DELIVER : Delivery no.
ITEM_DATA : Delivery no,
item no,
DLV_QTY quantity(changed),
FACT_UNIT_NOM ( default to value '1')
FACT_UNIT_DENOM ( default to value '1')
ITEM_CONTROL : Delivey no,
item no,
CHG_DELQTY ( value "X")
Then i use 'BAPI_TRANSACTION_COMMIT' for updating the changes.
Here the problem is, the BAPI is working fine for some quantity , say if i enter the DLV_QTY as 2 in ITEM_DATA, it is gettting updated. But if i pass some other quantity , say 12, it is returning the folowing error.
T ID                   NUM MESSAGE
E VL                   363
Pls tell why this error comes. and how to successfully update the delivery quantity for a set of material?
Regards,
Shanthi

not answered

Some quetions about BAPI_OUTB_DELIVERY_CHANGE.

HI~all.
   I change serial number in a outbound delivery use this bapi,
but have a question which it will create a new Object list number when i run this bapi at a time ,you can find them from SER01 TABLE,what's happend?PLZ tell me if you know the problem ,thank you very much ~
following is my code.
*& Report ZDN_MOD
REPORT ZDN_MOD.
DATA:BEGIN OF it_lips OCCURS 1,
           vbeln LIKE lips-vbeln,
           posnr LIKE lips-posnr,
           matnr LIKE lips-matnr,
           werks LIKE lips-werks,
           lfimg LIKE lips-lfimg,
           umvkz LIKE lips-umvkz,
           umvkn LIKE lips-umvkn,
     END OF it_lips.
DATA:IT_OBJK LIKE OBJK OCCURS 0 WITH HEADER LINE.
data:l_OBKNR like SER01-OBKNR.
DATA: v_delivery LIKE bapiobdlvhdrchg-deliv_numb,
       wa_header   LIKE bapiobdlvhdrchg,
       wa_header_x LIKE bapiobdlvhdrctrlchg,
       WA_TECHN   LIKE BAPIDLVCONTROL,
       it_return   LIKE bapiret2 OCCURS 0 WITH HEADER LINE,
       it_item     LIKE bapiobdlvitemchg OCCURS 0 WITH HEADER LINE,
       it_item_x   LIKE bapiobdlvitemctrlchg OCCURS 0 WITH HEADER LINE,
       it_spl      LIKE /spe/bapiobdlvitemchg OCCURS 0 WITH HEADER LINE,
       it_SER_NO like BAPIDLVITMSERNO OCCURS 0 WITH HEADER LINE,"序列号内表
       d_vbeln like likp-vbeln,
       msgtxt(100) type c .
data:it_CWM_ITEM_DATA LIKE /CWM/BAPIOBDLVITEM OCCURS 0 WITH HEADER LINE.
SELECT SINGLE OBKNR INTO L_OBKNR FROM SER01 WHERE LIEF_NR = '0080000040' AND POSNR = '000010'.
select * from OBJK into table it_OBJK where OBKNR = l_OBKNR.
D_VBELN = '0080000040'.
wa_header-deliv_numb = d_vbeln.
wa_header_x-deliv_numb = d_vbeln.
*wa_header_x-SIMULATE    = 'X'.
v_delivery = D_VBELN.
WA_TECHN-UPD_IND = 'X'.
SELECT vbeln posnr matnr werks lfimg umvkz umvkn into
       TABLE it_lips FROM lips
     WHERE vbeln = d_vbeln
     AND   POSNR = '000010'.
LOOP AT it_lips.
it_item-deliv_numb = it_lips-vbeln.
it_item-deliv_item = it_lips-posnr.
it_item-material   = it_lips-matnr.
it_item-dlv_qty    = it_lips-lfimg.
it_item-fact_unit_nom = it_lips-umvkz.
it_item-fact_unit_denom = it_lips-umvkn.
it_item-CONV_FACT = '1'.
it_item-SALES_UNIT = 'SET'.
APPEND it_item. CLEAR it_item.
loop at it_OBJK.
    it_SER_NO-DELIV_NUMB = it_lips-vbeln.
    it_SER_NO-ITM_NUMBER = it_lips-posnr.
    it_SER_NO-SERIALNO   = it_OBJK-EQUNR.
    APPEND it_SER_NO.
endloop.
it_item_x-deliv_numb = it_lips-vbeln.
it_item_x-deliv_item = it_lips-posnr.
it_item_x-CHG_DELQTY = 'X'.
APPEND    it_item_x .CLEAR    it_item_x.
ENDLOOP.
CALL FUNCTION 'BAPI_OUTB_DELIVERY_CHANGE'
EXPORTING
    header_data    = wa_header
    header_control = wa_header_x
    delivery       = v_delivery
    TECHN_CONTROL = WA_TECHN
TABLES
    item_data      = it_item
    item_control   = it_item_x
    ITEM_SERIAL_NO = it_SER_NO
    return         = it_return
    item_data_spl = it_spl.
READ TABLE it_return WITH KEY type = 'E'.
BREAK IBM-ZHANGDQ.
IF sy-subrc NE 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.
ELSE.
CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
      id        = it_return-id
      lang      = '-D'
      no        = it_return-number
      v1        = it_return-message_v1
      v2        = it_return-message_v2
      v3        = it_return-message_v3
      v4        = it_return-message_v4
    IMPORTING
      msg       = msgtxt
    EXCEPTIONS
      not_found = 1
      OTHERS    = 2.
WRITE:msgtxt.
ENDIF.
FREE:it_return,it_spl,it_item,it_item_x.
CLEAR:it_return,it_spl,it_item,it_item_x,wa_header,
      wa_header_x,v_delivery.

Hello Srinivas
I am still on this and felt I must continue updating this message thread so that someone with a similar requirement can get a complete picture of what the possibilities are and benefit from it.
I am trying out your suggested solution but am unsure of the FM which needs to be attached to the event tcode with the LIKP event CHANGED. That is one area I will need your feedback and help. Might be very helpful if I had your case scenario too and the FM code to see if it can be reused.
Also I didn't understand the reason for the new field flag?
xlips-zfield = 'X'.   " new FLAG.
Did you mean for me to add a new field to LIPS to keep track of pick omit line items? And kind of use it like a flag and reset it once I am done processing or something like that?
In the TCode SWETYPV
BOR Object Type     LIKP CHANGED       WS12300004 No errors
BOR Object Type     LIKP CREATE_IBDLV WS12300004 No errors
But not sure if that is the right way. I am trying to look up more documentation on this but not finding any.
Meetings within the department have definitely given a deeper view of the requirements....
While updating the pick omits delv. qty is the first step the next step is to rej the line item with a reason code. The discussions also revealed more points which were seeming to fit into this jigsaw with a little addition. The additional functionality is to consolidate all like items to one line item, prior to order going to warehouse for picking. This will aid in picking at the warehouse as well as in the customer invoice not reflecting more than one line item for the same material. In the case where the customer has truly ordered more than 1 case and additional 2 EA (eaches) the documents in SAP will still reflect 2 lines.
Regards

Regarding bapi to issue PGI BAPI_OUTB_DELIVERY_CHANGE,sample code please

Can you send me the sample code of this bapiBAPI_OUTB_DELIVERY_CHANGE ,if any one have used this.it's urgent please..

Hi,
BAPI_OUTB_DELIVERY_CHANGE - BAPI for Change to Outbound Delivery
BAPI_INB_DELIVERY_SAVEREPLICA - Create Inbound Delivery
RV_DELIVERY_CREATE - Create Delivery
GN_DELIVERY_CREATE - Create an Outbound Delivery
Код:
FORM xkomdlgn_fill USING p_open_qty LIKE ekpo-menge
                                       p_eindt LIKE eket-eindt
                                       p_licha LIKE eket-licha
                                       p_charg LIKE eket-charg
                                       p_uzeit LIKE eket-uzeit.
STATICS: h_grkor LIKE lips-grkor,
h_bsmng LIKE ekpo-menge.
CLEAR t_xkomdlgn.
CHECK t_ekpo-uptyp NE '5' " Lot
AND t_ekpo-uptyp NE '6' " Display
AND t_ekpo-uptyp NE '7' " VK-Set
AND t_ekpo-uptyp NE 'H'. " GT-Stuckliste
IF t_ekpo-uebpo IS INITIAL AND t_ekpo-upvor CA '1I'.
    CHECK 1 = 2.
ENDIF.
IF NOT ekko-lifnr IS INITIAL.
    CALL FUNCTION 'VENDOR_MASTER_DATA_SELECT_12'
      EXPORTING
        pi_lifnr       = ekko-lifnr
        pi_ekorg       = ekko-ekorg
      IMPORTING
        pe_lfm1        = lfm1
      EXCEPTIONS
        no_entry_found = 1
        OTHERS         = 2.
    t_xkomdlgn-vsbed = lfm1-vsbed.
ELSE.
    CLEAR t_xkomdlgn-vsbed.
ENDIF.
t_xkomdlgn-adrnr_li = ekko-adrnr.
t_xkomdlgn-lifnr = ekko-lifnr.
t_xkomdlgn-inco1 = ekko-inco1.
t_xkomdlgn-inco2 = ekko-inco2.
t_xkomdlgn-exnum = ekko-exnum.
t_xkomdlgn-bukrs_best = ekko-bukrs.
t_xkomdlgn-matnr = t_ekpo-matnr.
t_xkomdlgn-werks = t_ekpo-werks.
*IF STORAGE LOCATION IS MISSING APPEND
*FG01 As storage location
IF t_ekpo-lgort IS INITIAL .
    t_xkomdlgn-lgort = 'FG01' .
ELSE .
    t_xkomdlgn-lgort = t_ekpo-lgort.
ENDIF.
xkomdlgn-charg = ?
T_XKOMDLGN-VRKME = T_EKPO-MEINS.
t_xkomdlgn-meins = t_ekpo-lmein.
t_xkomdlgn-umvkz = t_ekpo-umrez.
t_xkomdlgn-umvkn = t_ekpo-umren.
IF t_ekpo-matnr EQ space.
    t_xkomdlgn-meins = t_ekpo-meins.
    t_xkomdlgn-umvkz = 1.
    t_xkomdlgn-umvkn = 1.
ENDIF.
t_xkomdlgn-insmk = t_ekpo-insmk.
t_xkomdlgn-kzfme = t_ekpo-kzfme.
t_xkomdlgn-kzvbr = t_ekpo-kzvbr.
t_xkomdlgn-lfimg = p_open_qty.
t_xkomdlgn-lfdat = p_eindt.
t_xkomdlgn-lfuhr = p_uzeit.
xkomdlgn-vstel = ?
XKOMDLGN-VKORG = ?
xkomdlgn-vtweg = ?
XKOMDLGN-SPART = ?
t_xkomdlgn-traid = t_ekpo-traid."CARRIER CODE
t_xkomdlgn-lifex = t_ekpo-lifex."External ID
t_xkomdlgn-bolnr = t_ekpo-bolnr."Bill Of Lading
t_xkomdlgn-xabln = t_ekpo-xabln."Goods Receipt/Issue Slip Number
t_xkomdlgn-vgbel = t_ekpo-ebeln.
t_xkomdlgn-vgpos = t_ekpo-ebelp.
t_xkomdlgn-lfart = gf_dlv_type.
t_xkomdlgn-vgtyp = 'V'.
t_xkomdlgn-kzazu = 'X'.
t_xkomdlgn-knttp = t_ekpo-knttp.
t_xkomdlgn-sobkz = t_ekpo-sobkz.
SELECT * FROM t163g WHERE bstae EQ t_ekpo-bstae
AND ebtyp EQ gf_ebtyp.
    EXIT.
ENDSELECT.
IF sy-subrc = 0.
    prufen, ob lieferavis we-zuordnung hat (vorauss. fur we uber vl32)
    und wepos prufen
    if t163g-wezuo eq space or t_ekpo-wepos eq space.
    t_xkomdlgn-nowab = 'X'.
ELSE.
    CLEAR t_xkomdlgn-nowab.
ENDIF.
ENDIF.
IF t_ekpo-matnr IS INITIAL OR t_ekpo-pstyp = '6'.
t_xkomdlgn-posar = 'B'.
ENDIF.
t_xkomdlgn-ematn = t_ekpo-ematn.
t_xkomdlgn-mfrnr = t_ekpo-mfrnr.
t_xkomdlgn-mfrpn = t_ekpo-mfrpn.
t_xkomdlgn-emnfr = t_ekpo-emnfr.
t_xkomdlgn-cuobj = t_ekpo-cuobj.
t_xkomdlgn-uebto = t_ekpo-uebto.
t_xkomdlgn-untto = t_ekpo-untto.
t_xkomdlgn-uebtk = t_ekpo-uebtk.
t_xkomdlgn-lichn = p_licha.
t_xkomdlgn-charg = p_charg.
t_xkomdlgn-bwtar = t_ekpo-bwtar.
t_xkomdlgn-kdmat = t_ekpo-idnlf.
t_xkomdlgn-arktx = t_ekpo-txz01.
t_xkomdlgn-mfrgr = t_ekpo-mfrgr.
t_xkomdlgn-gewei = t_ekpo-gewei.
t_xkomdlgn-voleh = t_ekpo-voleh.
t_xkomdlgn-ntgew = t_ekpo-ntgew * t_xkomdlgn-lfimg.
t_xkomdlgn-brgew = t_ekpo-brgew * t_xkomdlgn-lfimg.
t_xkomdlgn-volum = t_ekpo-volum * t_xkomdlgn-lfimg.
t_xkomdlgn-ean11 = t_ekpo-ean11.
t_xkomdlgn-podrel = t163l-podrel.
t_xkomdlgn-aktnr = t_ekpo-aktnr.
t_xkomdlgn-abeln = t_ekpo-abeln.
t_xkomdlgn-abelp = t_ekpo-abelp.
xkomdlgn-ltssf = only SORT criteria IN vl31n
T_XKOMDLGN-AUREL = T_EKPO-AUREL.
t_xkomdlgn-idnlf = t_ekpo-idnlf.
t_xkomdlgn-matkl = t_ekpo-matkl.
leergut-stuckliste ubernehmen
clear t_xkomdlgn-grkor.
CLEAR t_xkomdlgn-kmpmg.
CLEAR t_xkomdlgn-uepos.
CLEAR t_xkomdlgn-uepvw.                                     "549736
IF t_ekpo-upvor CA '3X'.
h_grkor = h_grkor + 1.
t_xkomdlgn-grkor = h_grkor.
h_bsmng = t_ekpo-menge.
ENDIF.
IF NOT t_ekpo-uebpo IS INITIAL AND
t_ekpo-uptyp CA '3X'.
t_xkomdlgn-uepvw = 'G'.                                   "549736
t_xkomdlgn-uepos = t_ekpo-uebpo.
t_xkomdlgn-grkor = h_grkor.
IF h_bsmng NE 0.
    t_xkomdlgn-kmpmg = t_ekpo-menge / h_bsmng.
ENDIF.
ENDIF.
IF t_ekpo-pstyp EQ '2'.
t_xkomdlgn-sobkz = 'K'.
ENDIF.
kontierungsfelder
if t_ekpo-sobkz eq 'E' or t_ekpo-sobkz eq 'Q'.
CALL FUNCTION 'MMPUR_EKKN_READ_EBELN_EBELP'
EXPORTING
    pi_ebeln             = t_ekpo-ebeln
    pi_ebelp             = t_ekpo-ebelp
    pi_bypassing_buffer = pi_refresh_buffer
    =
tables
    pto_ekkn_po          = xekkn
EXCEPTIONS
    no_records_requested = 1
    OTHERS               = 2.
IF sy-subrc EQ 0.
READ TABLE xekkn INDEX 1.
t_xkomdlgn-ps_psp_pnr = xekkn-ps_psp_pnr.
t_xkomdlgn-vbelv = xekkn-vbeln.
t_xkomdlgn-posnv = xekkn-vbelp.
ENDIF.
ENDIF.
APPEND t_xkomdlgn.
ENDFORM. "xkomdlgn_fill
LOOP AT t_xkomdlgn.
set default parameter
t_xkomdlgn-vgtyp = 'V'.
t_xkomdlgn-kzazu = 'X'.
IF t_xkomdlgn-lfart IS INITIAL.
t_xkomdlgn-lfart = 'EL'.
ENDIF.
MODIFY t_xkomdlgn.
ENDLOOP.
SELECT SINGLE * FROM tvsa WHERE smart = xvbsk-smart.
IF sy-subrc 0.
Error Handling To be Done
Meldung ins Protokoll
ENDIF.
l_nrnr = tvsa-numki.
CALL FUNCTION 'NUMBER_GET_NEXT'
EXPORTING
nr_range_nr = l_nrnr
object      = 'RV_SAMMG'
IMPORTING
number      = xvbsk-sammg
EXCEPTIONS
OTHERS      = 1.
IF sy-subrc 0.
error hadling tbd
meldung ins protokoll
endif.
CALL FUNCTION 'GN_DELIVERY_CREATE'
EXPORTING
no_commit = 'X'
vbsk_i = xvbsk
if_no_deque = 'X'
IF_MASS_READ_MAT_SW = 'X'
vbls_pos_rueck = 'X'
TABLES
xkomdlgn = t_xkomdlgn
xvbfs = xvbfs
xvbls = xvbls
xxlips = xlips.
get informatioin from ekpo table and fill T_xkomdlgn

Problem with BAPI_OUTB_DELIVERY_CHANGE to update serial numbers

hi All,
I am using BAPI_OUTB_DELIVERY_CHANGE to update serial numbers. i am executing this directly in se37 giving delivery number alone in import parameters header_data, header_control and delivery.
and giving delivery numer, item no and random serial no in tables ITEM_SERIAL_NO. when i execute it is not throwing any errors. how ever the delivery is not updated with the serial no's.Return parameters is also nor showing any values.
Any pointers to solve this would be appreciated.
Regards,
Sreekanth.

Hi,
You need to use BAPI_TRANSACTION_COMMIT just after BAPI_OUTB_DELIVERY_CHANGE .
Mark WAIT = 'X' in the IMPORT parameter of BAPI_TRANSACTION_COMMIT.
For testing if it is working or not:
Goto SE37 --> click on FUNCTION MODULE --> TEST -->TEST SEQUENCES
First give BAPI_OUTB_DELIVERY_CHANGE and then BAPI_TRANSACTION_COMMIT.
Click on EXECUTE. Execute BAPI_OUTB_DELIVERY_CHANGE then 'BACK' and then BAPI_TRANSACTION_COMMIT with proper data.
Goto the transaction from where you can check entry has been created or not.
Regards

Delete delivery document, use: BAPI_OUTB_DELIVERY_CHANGE

hi friends,
I want to delete a delivery document. I think BAPI_OUTB_DELIVERY_CHANGE will be useful for my purpose but I cannot find any field indicating the operation type like 'U'pdate, 'D'elete etc.
is it the right bapi function or should i use a different one?
thanks,
- ferudun

I have tried this way but nothing has happened. The return table was containing a row with error E VL 302 and empty message texts. (Delevery document doesn't exist)
    header_control-dlv_del = 'X'.
    CALL FUNCTION 'BAPI_OUTB_DELIVERY_CHANGE'
      EXPORTING
        HEADER_DATA              = header_data
        HEADER_CONTROL       = header_control
        DELIVERY                      = delivery_no
      TABLES
        RETURN                        = return.
I see the delivery document from VL03 tcode.
what is wrong? what data should i supply?
thanks,
- ferudun
Message was edited by:
        Ferudun ATAKAN

Help in BAPI_OUTB_DELIVERY_CHANGE

Hi
i try to change the quantity for a distributed quantity
The code :
*Local data --> Start
DATA: LWA_HEADER_DATA LIKE BAPIOBDLVHDRCHG,
        LWA_HEADER_CONTROL LIKE BAPIOBDLVHDRCTRLCHG,
        LT_ITEM_DATA LIKE TABLE OF BAPIOBDLVITEMCHG,
        LWA_ITEM_DATA LIKE LINE OF LT_ITEM_DATA,
        LV_OLD_DELIV LIKE GWA_SD_DOCUMENT-VBELN,
        LV_NEW_DELIV LIKE GWA_SD_DOCUMENT-VBELN,
        LV_OLD_MATNR LIKE GWA_SD_DOCUMENT-MATNR,
        LV_NEW_MATNR LIKE GWA_SD_DOCUMENT-MATNR,
        LV_OLD_SHIP LIKE GWA_SD_DOCUMENT-TKNUM,
        LWA_TECHN LIKE BAPIDLVCONTROL,
        LT_ITEM_CONTROL LIKE TABLE OF BAPIOBDLVITEMCTRLCHG,
        LWA_ITEM_CONTROL LIKE LINE OF LT_ITEM_CONTROL,
        LV_NEW_SHIP LIKE GWA_SD_DOCUMENT-TKNUM,
        LT_RETURN LIKE TABLE OF BAPIRET2.
*Local data --> End
LWA_TECHN-UPD_IND = GC_DEFAULT.
LOOP AT GT_SD_DOCUMENT INTO GWA_SD_DOCUMENT.
      LWA_ITEM_DATA-DELIV_NUMB = GWA_SD_DOCUMENT-VBELN.
      LWA_ITEM_DATA-DELIV_ITEM = GWA_SD_DOCUMENT-POSNR.
      LWA_ITEM_DATA-MATERIAL = GWA_SD_DOCUMENT-MATNR.
      LWA_ITEM_DATA-DLV_QTY = GWA_SD_DOCUMENT-LFIMG_R.
      LWA_ITEM_DATA-DLV_QTY_IMUNIT = GWA_SD_DOCUMENT-LFIMG_R.
      LWA_ITEM_DATA-SALES_UNIT = GWA_SD_DOCUMENT-VRKME.
      LWA_ITEM_DATA-BASE_UOM   = GWA_SD_DOCUMENT-MEINS.
      APPEND LWA_ITEM_DATA TO LT_ITEM_DATA.
      LWA_ITEM_CONTROL-DELIV_NUMB = GWA_SD_DOCUMENT-VBELN.
      LWA_ITEM_CONTROL-DELIV_ITEM = GWA_SD_DOCUMENT-POSNR.
      LWA_ITEM_CONTROL-CHG_DELQTY = GC_DEFAULT.
      APPEND LWA_ITEM_CONTROL TO LT_ITEM_CONTROL.
      CALL FUNCTION 'BAPI_OUTB_DELIVERY_CHANGE'
        EXPORTING
          HEADER_DATA    = LWA_HEADER_DATA
          HEADER_CONTROL = LWA_HEADER_CONTROL
          DELIVERY       = LV_OLD_DELIV
        TABLES
          ITEM_DATA      = LT_ITEM_DATA
          ITEM_CONTROL   = LT_ITEM_CONTROL
          RETURN         = LT_RETURN.
   ENDLOOP.
I get message "Error in document &1 item &2 (quantity consistency check)"
What is the problem?
Thanks

Hi,
BAPI_OUTB_DELIVERY_CHANGE
Regards
Sudheer

Regarding using of EXTENSION1 and EXTENSION2 in BAPI_OUTB_DELIVERY_CHANGE

Hi,
Can any one please help me how to code for zfields in EXTENSION1 and EXTENSION2 in BAPI_OUTB_DELIVERY_CHANGE
Thanks,
Nethaji.

I had a requirement to change a Z field in LIKP by a BAPI call and found this thread.
Although the original participant probably have found alternative ways, I hope this can be helpful for others search for a solution to this.
These are my findings u2013 please correct me if I am wrong. The EXTENSION1 & EXTENSION2 can NOT be used to change LIKP Z-fields. These doesnu2019t do anything in themselves, but can be imported in BADI IF_EX_SMOD_V50B0001~EXIT_SAPLV50I_010 (Thereu2019s a corresponding CMOD in older versions).
However, the data available here are :
CS_VBKOK
CT_VBPOK
CT_VBSUPCON
EXTENSION1
EXTENSION2
So, for changes to delivery header, only fields in structure CS_VBKOK can be changed. As VBKOK does not have any customer appends, this is not possible. Furthermore is the BAPI BAPI_OUTB_DELIVERY_CHANGE only calling WS_DELIVERY_UPDATE anyway, so the BAPI can not do any magic the FM canu2019t. So what is the purpose with EXTENSION1/ EXTENSION2 ?
As I see it, itu2019s a handy way to transfer data to the BADI, so you can build logic to manipulate any of the existing CS_VBKOK fields. You could have done the same with a Memory export/import anyway.
/END-BAD-NEWS
/BEGIN-GOOD-NEWS
After some trial and error, I managed to use BAPI_OUTB_DELIVERY_CHANGE to change Z fields in LIKP. Before the call, I export the desired content to a memory ID, which I then import in MV50AFZ1, BAPI_OUTB_DELIVERY_CHANGE
See this working demonstration code :
Calling program :
*& Report ZTEST_BAPI_DELIVERY_CHANGE
report ztest_bapi_delivery_change.
data : gs_bapiobdlvhdrchg        type bapiobdlvhdrchg.
data : gs_bapiobdlvhdrctrlchg    type bapiobdlvhdrctrlchg.
data : gs_bapidlvcontrol         type bapidlvcontrol.
data : gt_bapireturn type standard table of bapiret2.
data : gs_bapireturn type bapiret2.
data : gs_likp type likpvb.
data : ld_zzhuload   type erlkz.
constants: gc_x(1)     type c value 'X'.
parameter : p_vbeln like likp-vbeln.
Get relevant LIKP fields
select * from likp
into corresponding fields of gs_likp
where vbeln = p_vbeln.
endselect.
Fill header data - convert to BAPI format
call function 'MAP2E_LIKPVB_TO_BAPIOBDLVHDRCH'
exporting
    likpvb          = gs_likp
changing
    bapiobdlvhdrchg = gs_bapiobdlvhdrchg.
Field to set as LIKP Z-field
ld_zzhuload = 'X'.
Memory-ID imported in MV50AFZ1
export ld_zzhuload to memory id 'ZZHULOAD'.
call function 'BAPI_OUTB_DELIVERY_CHANGE'
exporting
    header_data           = gs_bapiobdlvhdrchg
    header_control        = gs_bapiobdlvhdrctrlchg
    delivery              = gs_bapiobdlvhdrchg-deliv_numb
    techn_control         = gs_bapidlvcontrol
tables
    return                = gt_bapireturn
exceptions
    communication_failure = 1
    system_failure        = 2
    others                = 3.
if gt_bapireturn[] is initial.
call function 'BAPI_TRANSACTION_COMMIT'
    exporting
      wait = gc_x.
else.
loop at gt_bapireturn into gs_bapireturn
    where type = 'E'.
    message id gs_bapireturn-id type 'S'
    number gs_bapireturn-number with
    gs_bapireturn-message_v1
    gs_bapireturn-message_v2
    gs_bapireturn-message_v3
    gs_bapireturn-message_v4.
    exit.
endloop.
endif.
MV50AFZ1, form USEREXIT_SAVE_DOCUMENT_PREPARE
data : ld_zzhuload   type erlkz.
if xlikp-vbtyp = 'J' " outbound delivery
and t180-trtyp = 'V'. " Change
Memory-ID exported from program ZZZ...
import ld_zzhuload from MEMORY ID 'ZZHULOAD'.
if sy-subrc is initial
and not ld _zzhuload is initial.
    LOOP AT xlikp.
      xlikp-zzhuload = ld_zzhuload.
      MODIFY xlikp transporting zzhuload.
    ENDLOOP.
    free MEMORY ID 'ZZHULOAD'.
endif.
endif.
I hope someone will find this helpful. Obviously I can not take responsibility for the functionality
Sorry for the format, I can not get the tags to work.....

Batch Job Error Messages

Hi Gurus,
I have a program with rounddown quantities in deliveries notes. This program is run in background with all other programs. When we checked the batch job error log, we found out that when it gets to this Rounddown program, there are some SAP generated errors messages (examples are listed below).
This issue is there is no way to know exactly which deliveries the error is generated from and if the program actually rounddown the quantities of all the deliveries passed to it and so on, because this error messages are not specific enough (like we can see below).
This program passed this new rounddown quantity number from the internal table using a BAPI.
Is there a way to change this SAP generated error messages to be specific enough like stating which actual delivery number is been affected or even stop at the error and send an email to the user to change the delivery or something in that manner, OR is there a way we can replace this SAP generated error messages with our own messages and send email out to the user.
Error Messages:-
01/16/2008 01:40:40 Step 005 started (program ZSDSO_DELIVERY_QTY_ROUNDDOWN, variant , user ID AUTOSYSUSER
01/16/2008 01:51:35 Item 000020 belongs to delivery group 001
01/16/2008 01:52:13 Item 000020 belongs to delivery group 001
01/16/2008 01:52:15 Item 000030 belongs to delivery group 001
01/16/2008 01:52:19 Item 000020 belongs to delivery group 001
01/16/2008 01:52:29 Dynamic credit check has been exceeded                              23,984.52 USD
01/16/2008 01:52:30 Item 000020 (change quantity manually to             400 PC because of complex struct
01/16/2008 01:52:30 Item 000030 (change quantity manually to             400 PC because of complex struct
01/16/2008 01:52:30 Quantity correlation for dependent items has been carried out
01/16/2008 01:52:30 Item 000020 belongs to delivery group 008
01/16/2008 01:52:30 Item 000030 belongs to delivery group 008
01/16/2008 01:52:31 Dynamic credit check has been exceeded                              23,984.52 USD
01/16/2008 01:52:32 Delivery quantity must be entered for the item
01/16/2008 01:52:34 Dynamic credit check has been exceeded                              23,984.52 USD
01/16/2008 01:53:05 Item 000020 belongs to delivery group 001
01/16/2008 01:54:40 Dynamic credit check has been exceeded                              15,501.88 USD
01/16/2008 01:55:53 Item 000020 belongs to delivery group 001
Thanks.
Points will be awarded.

This is the Subrouting Form code.
FORM call_bapi_delivery_change TABLES p_i_lips LIKE i_lips.
DATA: w_header_data TYPE bapiobdlvhdrchg,
        w_header_control TYPE bapiobdlvhdrctrlchg,
        w_delivery TYPE bapiobdlvhdrchg-deliv_numb.
DATA: i_item_data TYPE STANDARD TABLE OF bapiobdlvitemchg,
        w_item_data TYPE bapiobdlvitemchg,
        i_item_control TYPE STANDARD TABLE OF bapiobdlvitemctrlchg,
        w_item_control TYPE bapiobdlvitemctrlchg,
        i_return TYPE STANDARD TABLE OF bapiret2,
        w_return TYPE bapiret2.
LOOP AT p_i_lips INTO w_lips.
    w_item_data-deliv_numb = w_lips-vbeln.
    w_item_data-deliv_item = w_lips-posnr.
    w_item_data-material = w_lips-matnr.
    w_item_data-batch = w_lips-charg.
    w_item_data-dlv_qty = w_lips-lfimg.
    w_item_data-dlv_qty_imunit = w_lips-lfimg.
    w_item_data-fact_unit_nom = 1.
    w_item_data-fact_unit_denom = 1.
    APPEND w_item_data TO i_item_data.
    CLEAR w_item_control.
    w_item_control-deliv_numb = w_lips-vbeln.
    w_item_control-deliv_item = w_lips-posnr.
    IF w_lips-delete NE 'X'.
      w_item_control-chg_delqty = 'X'.
    ELSEIF w_lips-delete EQ 'X'.
      w_item_control-del_item = 'X'.
    ENDIF.
    APPEND w_item_control TO i_item_control.
ENDLOOP.
w_header_data-deliv_numb = w_lips-vbeln.
w_header_control-deliv_numb = w_lips-vbeln.
w_delivery = w_lips-vbeln.
CALL FUNCTION 'BAPI_OUTB_DELIVERY_CHANGE'
    EXPORTING
      header_data               = w_header_data
      header_control            = w_header_control
      delivery                  = w_delivery
TECHN_CONTROL             =*
    TABLES
HEADER_PARTNER            =*
HEADER_PARTNER_ADDR       =*
HEADER_DEADLINES          =*
      item_data                 = i_item_data
      item_control              = i_item_control
ITEM_SERIAL_NO            =*
SUPPLIER_CONS_DATA        =*
EXTENSION1                =*
EXTENSION2                =*
      return                    = i_return
TOKENREFERENCE            =*
IF sy-subrc EQ 0.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        wait = 'X'.
    w_zbdcopendn-otce706 = 'X'.
    MODIFY i_zbdcopendn FROM w_zbdcopendn TRANSPORTING otce706
    WHERE delivery EQ w_deliveries-vbeln.
ELSE.
    CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
    DELETE i_zbdcopendn WHERE delivery EQ w_deliveries-vbeln.
   DELETE i_deliveries WHERE vbeln EQ w_lips-vbeln.*
    w_bad_delv-vbeln = w_deliveries-vbeln.
    APPEND w_bad_delv TO i_bad_delv.
ENDIF.
ENDFORM.                    " call_bapi_delivery_change
Thanks again.

Add the new item through the Bapi 'bapi_outb_delivery_change'

I want to add the new item to the existing outbound delivery.How to add the new item in the bapi 'bapi_outb_delivery_change'. Please provide me the code for the bapi 'BAPI_OUTB_DELIVERY_CHANGE' to add the new item.

Hi Kyndal,
I have a requirment to add new items in a delivery which will refer to the higher items in the same delivery itself.
I am trying to use the BAPI BAPI_OUTB_DELIVERY_CHANGE for the purpose.
Could u pls give some clue on how to tried to do it?
I am constantly getting a error VL216.
Also I tried passing the reference document and item : same delivery number and the higher level item in the delivery
VBTYP_N = J

IDoc SHP_OBDLV_CHANGE01 / BAPI_OUTB_DELIVERY_CHANGE

I want to make a batch split on an outbound delivery.
I can't find documentation on IDoc SHP_OBDLV_CHANGE01 or BAPI_OUTB_DELIVERY_CHANGE on which fields to fill.
I have a delivery with 1 item - posnr 10. On this item I wan't to update the quantity and make a batch spilt.
When I try the quantity on the main position is updated but the batch spilt item is not beeing added and I get an errormessage : Text ID language not found

FYI
BAPI_OUTB_DELIVERY_CHANGE
You can BAPI to the extradition change functionality with this method both in the Enterprise-Resource-Planning-system (ERP-system) and in the decentralized Warehouse-management-system (World Cup) extradition after its distribution at the decentralized World Cup change. They can such a change both in the central ERP-system and in the decentralized World Cup carry out. The interface places adjust identically are certainly, that that for one planned extradition data also after a retroactive change in both systems. Change of head data: You delete can delete weight (gross weight and net weight) volume gate delivery appointment delivery priority route Incoterms Abladestelle delivery deliveries only then in the decentralized system and transmit this cancellation at the central SAP-ERP-system if the decentralized World
Cup is a strange system. Set in addition the mark DLV_DEL in the parameter HeaderControl. Change of position data: Quantity of weight (gross weight and net weight) volume decay date position delete change of partner data: Partners to a partner roll change or delete change address of a partner if you would like to change partner data, tests the system in the customizing of the respectively other system whether such a change is permitted. Change flow 1. they change retroactively an extradition in the central ERP-system or in the decentralized World Cup after it was distributed at the decentralized World Cup. 2. If it concerns in the decentralized World Cup a SAP-system, the system blocks the corresponding extradition in the partner system as soon as you call the change transaction. 3. If you secure the change
of the extradition, the system sends a synchronic change request at the connected partner system.
4. The partner system the change simulates based on the synchronic change request and accepts the change request or leans it off. 5. If the partner system rejects the change request, you cannot carry out the change. The system interrupts the preparation and brings a corresponding error message. 6. If the partner system accepts the change request, the system secures the extradition change in the system, in which you carried out the change, and an Asynchronous change request sends at the partner system. 7. Based On the Asynchronous change request, the partner system updates the extradition data. 8. The system the systemübergreifende barrier cancels for the changed extradition. Example if you would like to change for a distributed extradition the quantity, are the following statements for the transmission at the connected system necessary:
in the parameter head data of the extradition (HEADER_DATES) the delivery number (DELIV_NUMB) in the parameter position data of the extradition (ITEM_DATES) the delivery number (DELIV_NUMB) the delivery position (DELIV_ITEM) the delivery quantity in sale quantities unit (DLV_QTY) the Lieferistmenge in basis quantities unit (DLV_QTY_IMUNIT)
the sale quantities unit (SALES_UNIT) the ISO-code of the sale quantities unit (SALES_UNIT_ISO) the basis quantities unit (BASE_UOM) that Make, receives the system the material number, the work, the quantities statement as a floating decimal number, the volumes, the weights and its units out of the underlying extradition record.
References changes of the pack data are not synchronized in the central ERP-system.
In the retroactive change of a distributed delivery, the following prerequisites must be fulfilled:
All positions of the distribution relevant delivery have a joint decentralized administered warehouse number. They generate a distribution model for deliveries. You find generate further information in the introduction (IMG) under Logistics Execution -> integration decentralized World Cup -> headquarters settlement -> distribution -> distribution model. They have define determined in the customizing of the delivery under deliveries -> delivery type -> distribution mode whether the system should distribute the delivery either automatically after record creation or whether the distribution is supposed to be held back, so that you can activate the distribution over the delivery monitor. If you use a strange system as decentralized World Cup, must be guaranteed on sides of the decentralized World Cup over a barrier draft that you cannot process a delivery simultaneously in both systems. You find further information to the systemübergreifenden barrier in the SAP-library under basis -> client-server-technology -> Cross-system curl (CSL). If you use the Asynchronous interface for the actual transmission of the extradition change, (IDoc-type SHP_OBDLV_CHANGE), you note the correct IDoc-Strukturdefinition in the construction of the change-IDocs. Eighth you above all on that to exchange the segment sequence not.
Chargensplit in the decentralized World Cup if you change an appointment lower position of a distributed extradition in the decentralized World Cup, is this appointment lower position in the central ERP-system already available. The fields HIERARITEM and USEHIERITM are empty. The system receives the appointment lower position into the field DELIV_ITEM. If you change the quantity of an appointments head position of a distributed extradition in the decentralized World Cup, this appointments head position in the central ERP-system is already available. The fields HIERARITEM and USEHIERITM are empty. The system receives the appointment lower position into the field DELIV_ITEM. If you carry out in the decentralized World Cup a Chargensplit for a distributed extradition, only the appointments head position is at this time available in the central ERP-system. If you design for example two appointment lower positions, emerge for the transmission at the central ERP-system three
Position segment ItemData: The position segment for the appointments head position HIERARITEM is empty. The delivery quantity and the basis quantity are empty. Per appointment lower position, a position segment with the following fields emerges: DELIV_ITEM contains the number of the appointment lower position. HIERARITEM contains the number of the appointments head position. USEHIERITM indicates the use of the lower position with the value 1 as an appointment lower position. The quantities fields correspond to the quantities in the appointment lower positions. The central ERP-system carries out corresponding to the Chargensplit retroactively for the distributed extradition.
Parameter HEADER_DATES HEADER_CONTROL DELIVERY TECHN_CONTROL HEADER_PARTNER HEADER_PARTNER_HEADER
HEADER_DEADLINES ITEM_DATES ITEM_CONTROL ITEM_SERIAL_ITEM SUPPLIER_CONS_DATES EXTENSION1 EXTENSION2 RETURN
TOKENREFERENCE Exceptions function group V50I
Hope thisll give you idea!!
Pl... award the points.
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

BAPI_OUTB_DELIVERY_CHANGE

Hi,
Can any one pls help me with an example code for BAPI_OUTB_DELIVERY_CHANGE for batch splits?
Thanks

Hi Prabha,
    You can use this BAPI to change outbound deliveries in both the
    Enterprise Resource Planning system (ERP system) and the decentralized
    Warehouse Management System (WMS), according to their respective
    distribution to the decentralized WMS. You can make these changes in the
    central ERP system and in the decentralized WMS. The interface ensures
    that outbound delivery data planned for a comparison is identical in
    both systems, even after subsequent changes.
Changing Header Data:
    o   Weight (gross weight and net weight)
    o   Volume
    o   Door
    o   Delivery date
    o   Delivery priority
    o   Route
    o   Incoterms
    o   Unloading point
    o   Delete delivery
        You can only delete deliveries in the decentralized system and copy
        this deletion to the central SAP ERP system, if the decentralized
        WMS is an external system. For this, set the DLV_DEL indicator in
       the HeaderControl parameter.
Changing Item Data:
   o   Quantity
   o   Weight (gross weight and net weight)
   o   Volume
   o   Expiration date
   o   Delete item
Changing Partner Data:
   o   Change or delete partner for a partner function
   o   Change a partner's address
       If you want to change partner data, the system checks the
       Customizing settings of the other system, to see whether this type
       of change is permitted.
   Change Process Flow
   1. You subsequently change an outbound delivery in the central ERP
       system or the decentralized WMS, after the delivery was distributed
       to the decentralized WMS.
   2. If the decentralized WMS is an SAP system, the system blocks the
       relevant outbound delivery in the partner system as soon as you call
       the change transaction.
   3. When you save the changes to the outbound delivery, the system sends
       a synchronous change request to the connected partner system.
   4. The partner system uses the synchronous change request to simulate
       the change, then either accepts or rejects the change request.
   5. If the partner system rejects the change request, you cannot make
       the change. The system cancels processing and displays a relevant
       error message.
   6. If the partner system accepts the change request, the system saves
       the changes to the outbound delivery in the system in which you have
       made the changes. It then sends an asynchronous change request to
       the partner system.
   7. This asynchrounous change request causes the partner system to
       update the outbound delivery data.
   8. The system removes the cross-system lock for the changed outbound
       delivery.
xample
   If you want to change the quantity for a distributed quantity, then
   following entries are required for the transfer to the connected system:
   o   In the header data of outbound delivery parameter (HEADER_DATA)
       -   The delivery number (DELIV_NUMB)
   o   In parameter item data of outbound delivery (ITEM_DATA)
       -   The delivery number (DELIV_NUMB)
       -   The delivery item (DELIV_ITEM)
       -   The delivery quantity in sales unit (DLV_QTY)
       -   The actual delivery quantity in base UoM (DLV_QTY_IMUNIT)
       -   The sales unit (SALES_UNIT)
         -   The ISO code for the sales unit (SALES_UNIT_ISO)
         -   The base unit of measure (BASE_UOM)
         -   The ISO code for the base unit of measure (BASE_UOM_ISO)
     o   In the control of the outbound delivery at item level parameter
         (ITEM_CONTROL)
         -   The delivery number (DELIV_NUMB)
         -   The delivery item (DELIV_ITEM)
         -   The Change Delivery Quantity indicator(CHG_DELQTY)
     If you do not make any further entries, the system copies the material
     number, plant, quantities as floating point numbers, volumes, weights,
     and their units from the original outbound delivery document.
Notes
     Changes to the packing data are not synchronized in the central ERP
     system.
     For subsequent changes to a distributed inbound delivery, the following
     prerequisites must be fulfilled:
     o   All items in the distribution-relevant inbound delivery have the
         same decentrally-managed warehouse number.
     o   You have generated a distribution model for inbound deliveries. For
         more information, see the implementation guide (IMG) under Logistics
         Execution -> Decentralized WMS Integration -> Central Processing ->
         Distribution -> Generate Distribution Model.
     o   In Customizing for Shipping under Deliveries -> Define Delivery
         Types -> Distribution Mode, you have specified whether the system
         should distribute the delivery automatically after document
         creation, or whether distribution should be suppressed so that you
         can trigger distribution yourself using the delivery monitor.
     o   If you use an external system as the decentralized WMS, you must
         ensure that there is a blocking system for the decentralized system,
         which prevents a delivery from being processed in both systems at
         the same time. For more information on the cross-system lock, see
         the SAP Library under Basis -> Client-Server Technology ->
         Cross-System Lock (CSL).
     If you use the asynchronous interface for the actual transfer of the
     outbound delivery changes (IDoc category SHP_OBDLV_CHANGE), you must
     make sure that the structure definition of the IDoc is correct as you
     construct the IDoc. You should take particular care not to switch the
     segment sequence.
     Batch Split in the Decentralized WMS
     o   If you change a batch subitem from a distributed outbound delivery
         in the decentralized WMS, then this batch subitem already exists in
         the central ERP system.
         The fields HIERARITEM and USEHIERITM are empty. The system copies
         the batch subitem in the DELIV_ITEM field.
     o   If you change the quantity of a batch main item from a distributed
         outbound delivery in the decentralized WMS, then this batch main
         item already exists in the central ERP system.
         The fields HIERARITEM and USEHIERITM are empty. The system copies
         the batch subitem into the DELIV_ITEM field.
     o   If you perform a batch split for a distributed outbound delivery in
         the decentralized WMS, only the batch main item exists at that time
         in the central ERP system.
If, for example, you create two batch subitems, three item segments
ItemData are generated for transmission to the central ERP system:
-   The item segment for the batch main item HIERARITEM is empty.
     The delivery quantity and base quantity are empty.
-   For each subitem, the system generates an item segment with the
     following fields:
     DELIV_ITEM contains the number of the batch subitem.
     HIERARITEM contains the number of the batch main item.
     USEHIERITM with value 1 shows that the subitem is used as a
     batch subitem.
     The quantity fields match the quantities in the batch subitems.
The central ERP system performs the batch split subsequently for the
distributed outbound delivery.
Regards,
Hemant

Error in BAPI_OUTB_DELIVERY_CHANGE

Similar Messages

Maybe you are looking for