- SAP Managed Tags:
Hello.
In my application I have an inbound delivery, where I have to:
- carry out batch split
- detect packing material
- pack the split position using the external HU number I get from scanning the label
- later post the material movement
I have looked at and tried various examples in the forums, the code below is a (horrible) work-in-progress of the best result I have until now: split is correct, packing is done BUT the numbering of the HU is internal and the assigned type is A (even if I pass B in the proposal).
Correct would be for example: 435958083154001398 type B, actual is:
The code looks like this:
FORM pack_pallet
CHANGING ps_pallet TYPE ty_pallet.
CONSTANTS: lc_inbound_del TYPE c LENGTH 2 VALUE '03',
lc_delnotif TYPE c VALUE '7'.
DATA: ls_erefid TYPE vpobjkey,
lt_eheader TYPE hum_hu_header_t,
lt_eitem TYPE hum_hu_item_t,
lt_emsg TYPE huitem_messages_t,
lt_ehus TYPE STANDARD TABLE OF vekpvb,
lt_ret TYPE bapirettab,
l_packmat TYPE matnr,
l_clenum LIKE rlmob-clenum.
DATA: ls_vbkok_wa TYPE vbkok,
lt_verko TYPE STANDARD TABLE OF verko,
lt_verpo TYPE STANDARD TABLE OF verpo,
lt_repack TYPE STANDARD TABLE OF hum_repack,
lt_prot TYPE TABLE OF prott.
* Custom function here: looks up packing material and changes l_packmat
* Lot numbers: required for packing, optional for posting
* In case of packing, we must create it else it will fail.
CALL FUNCTION 'BAPI_BATCH_CREATE'
EXPORTING
material = ps_pallet-matnr
batch = ps_pallet-charg
plant = ps_pallet-werks
IMPORTING
batch = ps_pallet-charg
TABLES
return = lt_ret[].
IF ps_pallet-charg IS INITIAL.
gs_msg-msgid = lt_ret[ type = 'E' ]-id.
gs_msg-msgno = lt_ret[ type = 'E' ]-number.
gs_msg-msgv1 = lt_ret[ type = 'E' ]-message_v1.
gs_msg-msgv2 = lt_ret[ type = 'E' ]-message_v2.
gs_msg-msgv3 = lt_ret[ type = 'E' ]-message_v3.
gs_msg-msgv4 = lt_ret[ type = 'E' ]-message_v4.
* Custom error handling goes here
ENDIF.
ls_vbkok_wa-vbeln_vl = ps_pallet-vbeln.
ls_vbkok_wa-vbtyp_vl = 7.
* ls_vbkok_wa-wabuc = 'X'. "FIXME posting will be done later!
* ls_vbkok_wa-spe_auto_gr = 'X'. "FIXME posting will be done later!
ls_vbkok_wa-kzebu = 'X'.
INSERT INITIAL LINE INTO lt_verko INDEX 1 ASSIGNING FIELD-SYMBOL(<fs_verko>).
<fs_verko>-venum = ps_pallet-exidv.
<fs_verko>-exidv = ps_pallet-exidv.
* FIXME this may NOT be empty, else the packing fails!
<fs_verko>-exida = 'B'. "Number assigned by customer (no HU management)
FIXME test if internal number assignment depends on material type...
SELECT SINGLE magrv
INTO <fs_verko>-magrv
FROM mara
WHERE matnr = l_packmat.
<fs_verko>-werks = ps_pallet-werks.
<fs_verko>-status = '0010'.
<fs_verko>-vhilm = l_packmat.
INSERT INITIAL LINE INTO lt_verpo INDEX 1 ASSIGNING FIELD-SYMBOL(<fs_verpo>).
<fs_verpo>-venum = ps_pallet-exidv."FIXME no effect
<fs_verpo>-exidv_ob = ps_pallet-exidv."FIXME removing this is a bad idea, "HU not found"
<fs_verpo>-exidv = ps_pallet-exidv.
<fs_verpo>-velin = '1'.
<fs_verpo>-vbeln = ps_pallet-vbeln.
<fs_verpo>-posnr = '900001'. "FIXME was: ps_pallet-posnr.
<fs_verpo>-tmeng = ps_pallet-lfimg.
<fs_verpo>-vrkme = ps_pallet-vrkme.
<fs_verpo>-matnr = ps_pallet-matnr.
<fs_verpo>-charg = ps_pallet-charg.
<fs_verpo>-werks = ps_pallet-werks.
CALL FUNCTION 'WS_DELIVERY_UPDATE_2'
EXPORTING
vbkok_wa = ls_vbkok_wa
delivery = ps_pallet-vbeln
update_picking = abap_true
no_messages_update_1 = abap_true
synchron = abap_true
commit = space
nicht_sperren_1 = 'Y'
if_database_update_1 = '1'
if_error_messages_send = space
TABLES
prot = lt_prot
verko_tab = lt_verko
verpo_tab = lt_verpo
* FIXME enable block to suppress visible errors
* EXCEPTIONS
* error_message = 1
* OTHERS = 2
.
IF sy-subrc = 0.
* FIXME notify results
ELSE.
ROLLBACK WORK.
* FIXME custom error handling
ENDIF.
ENDFORM.Since this is an unreleased function (thanks SAP! /s) I have tried fiddling with the input parameters but I couldn't get rid of this last issue.
The functional consultant for the customer is checking for possible issues regarding the customizing, in the meanwhile my question is: does the numbering / type error depend on some wrong coding on my part?
Thanks,
Andrea.
- SAP Managed Tags:
Hello c5e08e0478aa4727abc4482f5be390b2
Calling WS_DELIVERY_UPDATE_2 function is inherently complex as there is no official documentation. The approach that works for me is to use Delivery Interface IDocs to update deliveries. The IDocs are processed by WS_DELIVERY_UPDATE_2. So once I get the result I need with the IDocs, I can put a break point in the function and figure out how it should be called for a specific scenario.
I might not be able to give you a full solution, but let me share a couple comments on how you call the function:
- <fs_verko>-venum - leave it empty or put $1 but don't put HU number from the label there. VENUM is a sequential, internal number of a HU, it is not a number from the label
- <fs_verko>-exida - I think the value should be H "SSCC18 or GTL from vendor"
- <fs_verpo>-venum - leave it empty. To my knowledge the field may be used if nested HUs are created
- <fs_verpo>-exidv - leave it empty. It is used to identify a handling unit number that is packed into a higher level HU. You are packing a product into a HU, not a HU into a higher level HU
Best regards
Dominik Tylczynski
