Inbound delivery putaway quantity update

Dear experts
It is regarding the putaway quantity update in inbound delivery with WM transfer order.
I found the putaway quantity updated immediately once TO created.
I have confusion that the putaway quantity should be updated once TO confirmed not created.
Could you please let me know your comment? thanks!
Zhixian

That is standard SAP behavior however at the time of PGR system check the whether delivery quantity is matching with putaway qty or not, if it match then only it allows to perform PGR
also one more setting is helpful in this regard (this help to update the quantity in delivery)
LE ----WM---Interface---Shipping ---Define Shipping Control at the Movement Type Level

Similar Messages

Does the inbound delivery date get updated in the Purchase Order?

Dear Experts,
Here is the use case, The original delivery date in the purchase order is 01.11.2011. Accordingly, the supplier sends an ASN to my client against the PO with the same delivery date. However, now, store keeper of my client wants to receive the stock on 03.11.2011.
1) Can the store keeper/ goods recipient change the delivery date in the corresponding inbound delivery document to 03.11.2011?
2) Will the change of the intended delivery date be notified back to the supplier who has triggered the ASN?
3) Will the new delivery date be updated back in the purchase order?
Point 3 is particularly important for the client from vendor evaluation point of view as any delay from the client side should not affect the vendor performance for ontime delivery.
Thanks in advance,
Ranjan
Ranjan Sutradhar

for point 2 not the dates wont be sent back to supplier untill unless you have any logic writen for that and if there is a Interface designed for it and I dont there will be any since ASN is sent from Vendor and if you are changing the dates in ASN .
for point 3 no its not going to change the delivery date in PO at item level but at the item detial level in PO history tab the scheduled date and delivery date as per ASN will be mentioned
its better you run the case in system and check it....this wont take much time

Error when creating inbound delivery - insufficient quantity

Hello all,
after creating a purchasing scheduling agreement (ME31L), I want to create an inbound delivery (VL31N).
But when saving the inbound delivery, I get the following error message:
Insuff stk qty ( 0.000) for line item000001
The stock for the material on the scheduling agreement is empty. But why does it not let me do an inbound delivery?
Thanks
Anne

In the config of Define Internal Confirmation Categories
is
2 shipping notification is assign to 10 or LA if it LA than it will allow you to create the inbound delivery
The delivery is created in my system
i got message
Notified quantity exceeds quantity still to be notified 15.000- CS Message no. ME160
but it is warning not error.

Inbound Delivery Idoc not update PIC and PGI with split batch.

Dear Experts,
Delivery outbound with split batch send to third party Warehouse to PIC and PGI from SAP, then receive the delivery inbound IDOC to update the PIC and PGI in SAP from third party. Basic Idoc DELIVERY03 it's works fine with out split batch, with split batch it's not updating PIC and PGI at the same time no error. Please advice on this
E1EDL24-HIPOS = "HIGHER LEVEL ITEM NUMEBR"
E1EDL24-HIEVW = "VALUE 1"
E1EDL19-QALF = "BAS"
Thanks and Regards,
Thiru.

Hi,
You also have to create a segment with following data as well (for batches).
E1EDL19-QUALF = "QUA".
Cheers,

How to skip the Inbound Delivery while updating LA confirmations via EDI

Hi Experts,
I have a requirement wherein I dont want to create Inbound Delivery automatically when updating the LA (or a copied Conf Cat of LA) confirmation via EDI. When we are using the message type DESADV, LA confirmations are being updated, but simultaneously, the Inbound delivery also being created. My client desires that Inbound Delivery should not happen and only LA confirmation should be updated via EDI.
Is there anyway, by which we can skip the Inbound Delivery while updating the LA confirmations in the PO?
Thanks in advance
Regards
Radha Krishna

Hi Prabhaharan,
Thanks for your quick response.
My requirement is to have both AB and LA confirmations. I have included these two in a new the conf control So, your suggestion will not work.
Is there any other way out to fulfill my requirement?
Thanks & Regards
Radha Krishna

Document flow in Inbound delivery not updated as in PO History for the SA

Hi,
We have an SA with 2 line items. All GR's & IR's have been reversed for the line items in SA.
The document flow incorresponding Inbound delivery is not updated correctly for these line items.
The GR have all been reversed with correct quantities. But, Document flow in Inbound delivery is not updated correctly.
Hence, the goods movement status for these shows as Partially processed and completely processed.
There is an inconsistency here.
Please advice

Hi
Have you post the GR through VL32N and reverse VL09?
Regards
Eduardo

Issue at the time of creation of transfer order for inbound delivery

Hello,
I am facing one issue at the time of creation of transfer order for inbound delivery.
If I create inbound delivery for purchase order with account assignment as 'M' (Ind. cust. w/o KD-CO), inbound delivery is not updated. Also document flow for inbounde delivery s not updated. I can create N number of transfer orders for on inbound delivery. Need help to resolve issue.
If I create inbound delivery for purchase order with account assignment other than 'M' (Ind. cust. w/o KD-CO), inbound delivery and document flow is updated.
Thanks and Regards,
Nikhil

Hi
In OMS2 t-code
for your material type and plant ,you have to mark value based and qunaity based updation mark
Regards
kailas Ugale

Post goods receipt against a Inbound Delivery(VL32N) FM or BAPI Method

Hi Expert,
I am looking for a Function Module or BAPI Method to Confirm the Inbound Delivery i.e. that can post Goods Movement Against a Delivery Document.
My scenario is Create PO-> create Inbound delivery-> post Goods Receipt.
Regards,
Kapil.
Edited by: Kapil Kumar Gupta on May 5, 2011 2:46 PM

In OSS note 520813 it is said:
16. Question:
Which goods movements should I not post using the BAPI_GOODSMVT_CREATE BAPI?
Answer:
You should not post the goods receipt for the inbound delivery using BAPI_GOODSMVT_CREATE BAPI because the document base and the status of the inbound delivery are not updated. See Note 199703.
If you check OSS note 199703 you can see that it is valid from release 45 to release 500.
Assigned to this note you can find another: 1050944 (it's worth of reading!!!).
I feel there are contradictions here - it might possible that the first note (520813) is not updated properly. (As far as I remember in my case this BAPI was working properly too).
In my opinion you should send a message to OSS and ask them whether the statement in note 520813 is still valid or not - you should also tell them that the referred note (199703) is not applicable to ECC6.0.
(there's a setting in ECC6.0 which enables that document flow is updated if GR is posted via MIGO with reference to IBD - V_TVSHP-SPE_INB_VL_MM)
I would like to ask you if you have a reply from them, please update this thread - it may be helpful for us.
Edited by: Csaba Szommer on May 9, 2011 2:34 PM
One more remark: (based on OSS note 1050944) it seems that you cannot use it only in case of packing (IBD with HU).
Edited by: Csaba Szommer on May 9, 2011 3:05 PM

IDoc or BAPI for inbound delivery creation with reference to PO.

Hi
I have requirement to create a inbound delivery, I will get a ASN from external system with PO, Vendor Material number & batch. I want to know is there any BAPI or IDoc that can be used to create inbound delivery in R/3. I used BBP_INB_DELIVERY_CREATE to create inbound delivery and I was successful but problem is that inbound delivery was not updated with Vendor Material number & Batch. Can some one suggest me any other BAPI or IDoc ?
Thanks in advance
Nagendra P Boggarapu
Edited by: Nagendra P Boggarapu on May 6, 2010 4:06 PM

Use Delvry0* IDOC.
Reddy

BAPI For Inbound Delivery using Purchase Order Number

Hi All,
Is there any BAPI for posting Inbound Delivery (VL31N) using Purchase Order as reference.
thanks
bobby

Not sure what it has to do with enhancements and modifications, but there is no such BAPI:
http://tech.groups.yahoo.com/group/ABAP/message/38307
http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/bapi-for-inbound-delivery-creation-and-update-vl31n-1201265
FYI all BAPIs may be viewed in BAPI transaction.

Production date in inbound delivery in batch split

Hi,
I have a issue with production date update in inbound delivery.
I have created a inbound delivery for 10 PC. The inbound delivery has only one line item and there are no batch details on it. As soon as the inbound delivery is created a message is sent to the 3PL . Once the 3PL receives the goods from vendor he send us a message with the batch details. Say the 3PL has received multiple batches from the vendor. So he send us back an SHPCON message with multiple batch details. That is batch A with QTY 6 and batch B with QTY 4. He also send us the production date for each batch via the shpcon idoc. say batch A has production date as 10.02.2011 and batch B has production date as 21.03.2011.
The IDOC is created successfully in our system and the inbound delivery is also updated correctly with the batch split details with correct QTY. That is line item 10 has batch split line items 900001 with batch as A and QTY as 6 and line item 900002 with batch as B and QTY as 4. The issue is only with updation of date of production for each of the above batch. Both batch A & B are updated with date of production as 21.03.2011. Instead of batch A being updated with date of production as 10.02.2011 it is updated with the batch B date of production. I checked in the idoc. In the idoc each batch has correct production date. only when updating the inbound delivery it has updated wrongly.. Has any one come across similar kind of situation. ? How did u manage it?
Ram

I found out the issue and the approriate changes has been made in the message handling

Inbound delivery quantity update with the confirm putaway quantity

even if i set up the update indicator (1or 2) during a TO confirmation, the system do not update the inbound delivery with the quantity confirmed, especialy in case of difference.
this option is possible during the TO creation, but not works with during the TO confirmation, could you help me?

It works with the outbound delivery only.
Though updating quantities in inb. delivery would be very useful for quantity difference handling.

Update GR quantity in Inbound delivery using 'BAPI_INB_DELIVERY_CHANGE'

Hello SDNs,
I have a requirement to update quantity delivered post GR in the Inbound delivery. I'm using 'BAPI_INB_DELIVERY_CHANGE' to do the updation in program. The database is not updated with new quantity.
BAPI returns error message in "Return" table with ID VLBAPI . I'm unable to detect where the problem is.
Below is my code. Please help me resolve it.
loop at it_final.
    CLEAR g_delivery.
    g_delivery = it_final-text(10).
*   g_delivery = '0180000221'.
    g_del_item = it_final-text+10(6).
*    g_del_item = '10'.
    g_material = it_final-text+16(18).
    g_dlv_qty = it_final-text+34(13).
    select single * from lips into wa_lips
        where vbeln = g_delivery
          and posnr = g_del_item
          and matnr = g_material.
    if sy-subrc eq 0.
      wa_lips-lfimg = g_dlv_qty.
      modify lips from wa_lips.
      check sy-subrc eq 0.
    endif.
    CLEAR gt_header_data.
    REFRESH gt_header_data.
    gt_header_data-deliv_numb = g_delivery.
    gt_header_data-volumeunit = wa_lips-voleh.
    APPEND gt_header_data.
    CLEAR gt_header_ctrl.
    REFRESH gt_header_ctrl.
    gt_header_ctrl-deliv_numb = g_delivery.
*    gt_header_ctrl-no_lock = 'Y'.
    APPEND gt_header_ctrl.
    clear gt_tech_ctrl.
    refresh gt_tech_ctrl.
    gt_tech_ctrl-UPD_IND = 'X'.
    gt_tech_ctrl-DLV_TYPE = 'EL'.
    append gt_tech_ctrl.
    CLEAR gt_data.
    REFRESH gt_data.
    gt_data-deliv_numb = g_delivery.
    gt_data-deliv_item = g_del_item.
    gt_data-material = g_material.
    gt_data-dlv_qty = wa_lips-lfimg.
    gt_data-sales_unit = wa_lips-vrkme.
    gt_data-base_uom = wa_lips-meins.
    gt_data-dlv_qty_imunit = g_dlv_qty.
*   gt_data-base_uom_iso =
*    gt_data-
    APPEND gt_data.
    REFRESH gt_ctrl.
    gt_ctrl-deliv_numb = g_delivery.
    gt_ctrl-deliv_item = g_del_item.
* gt_ctrl-del_item   = ' '.
    gt_ctrl-CHG_DELQTY = 'X'.
    APPEND gt_ctrl.
    CALL FUNCTION 'BAPI_INB_DELIVERY_CHANGE'
      EXPORTING
        HEADER_DATA                = gt_header_data
        HEADER_CONTROL             = gt_header_ctrl
        DELIVERY                   = g_delivery
        TECHN_CONTROL              = gt_tech_ctrl
      TABLES
*   HEADER_PARTNER             =
*   HEADER_PARTNER_ADDR        =
*   HEADER_DEADLINES           =
       ITEM_DATA                  = gt_data
      ITEM_CONTROL               = gt_ctrl
*   ITEM_SERIAL_NO             =
*   EXTENSION1                 =
*   EXTENSION2                 =
        RETURN                     = return
*   TOKENREFERENCE             =
*   HANDLING_UNIT_HEADER       =
*   HANDLING_UNIT_ITEM         =
*   PARTIAL_GR_OBJECTS         =
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT = ' '.
endloop.
Thanks
Shruti

Please check the inbound delivery you are trying to delete is not having goods receipt status as 'completed' OR not having HANDLING UNITS assigned to it.
In any of the above case, please reverse the goods receipt first, then unassign the handling units and then try to delete the inbound delivery. In my opinion, there should be no need to change the qty to 0 and just delete the inbound delivery should work.
In case you still encounter an error, try deleting the delivery using VL32n and you should get a clear error/problem for your case.

Update Delivery Qty of Inbound Delivery using BAPI_INB_DELIVERY_CHANGE

Hi Experts,
I'm trying to use BAPI_INB_DELIVERY_CHANGE to update the delivery quantity of a line item in an Inbound Delivery. However, I keep on getting this error:
Type: E
ID: VLBAPI
Number: 004
Text: Error in document &1 item &2 (quantity consistency check)
Below is my test program. Any input will be much appreciated.
REPORT ztest.
DATA: deadlines LIKE bapidlvdeadln OCCURS 0.
DATA: wa_deadlines LIKE bapidlvdeadln.
DATA: header_data_t LIKE bapiibdlvhdrchg OCCURS 0.
DATA: wa_header_data LIKE bapiibdlvhdrchg.
DATA: header_control_t LIKE bapiibdlvhdrctrlchg OCCURS 0.
DATA: wa_header_control LIKE bapiibdlvhdrctrlchg.
DATA: item_data LIKE bapiibdlvitemchg OCCURS 0.
DATA: wa_item_data LIKE bapiibdlvitemchg.
DATA: item_control LIKE bapiibdlvitemctrlchg OCCURS 0.
DATA: wa_item_control LIKE bapiibdlvitemctrlchg.
DATA: header_data_t_con LIKE bapiibdlvhdrcon OCCURS 0.
DATA: wa_header_data_con LIKE bapiibdlvhdrcon.
DATA: header_control_t_con LIKE bapiibdlvhdrctrlcon OCCURS 0.
DATA: wa_header_control_con LIKE bapiibdlvhdrctrlcon.
DATA: item_data_con LIKE bapiibdlvitemcon OCCURS 0.
DATA: wa_item_data_con LIKE bapiibdlvitemcon.
DATA: item_control_con LIKE bapiibdlvitemctrlcon OCCURS 0.
DATA: wa_item_control_con LIKE bapiibdlvitemctrlcon.
DATA: return TYPE STANDARD TABLE OF bapiret2.
CLEAR: wa_header_data, wa_header_control.
wa_header_data-deliv_numb = '0180000545'.
wa_header_data-gross_wt = '3001.000'.
*wa_header_data-NET_WEIGHT = '3001.000'.
wa_header_data-unit_of_wt = 'KG'.
wa_header_data-volume = '1500.5'.
wa_header_data-volumeunit = 'M3'.
APPEND wa_header_data TO header_data_t.
wa_header_control-deliv_numb = '0180000545'.
wa_header_control-NET_WT_FLG = 'X'.
wa_header_control-volume_flg = 'X'.
wa_header_control-gross_wt_flg = 'X'.
*wa_HEADER_CONTROL-DELIV_DATE_FLG = 'X'.
APPEND wa_header_control TO header_control_t.
CLEAR: wa_item_data.
wa_item_data-deliv_numb = '0180000545'.
wa_item_data-deliv_item = '000020'.
wa_item_data-dlv_qty = '3000'.
wa_item_data-dlv_qty_imunit = '3000'.
wa_item_data-sales_unit = 'KG'.
wa_item_data-sales_unit_iso = 'KG'.
wa_item_data-base_uom = 'KG'.
wa_item_data-base_uom_iso = 'KG'.
wa_item_data-gross_wt = '3000'.
wa_item_data-unit_of_wt = 'KG'.
wa_item_data-volume = '1500'.
wa_item_data-volumeunit = 'M3'.
APPEND wa_item_data TO item_data.
CLEAR: wa_item_control.
wa_item_control-deliv_numb = '0180000545'.
wa_item_control-deliv_item = '000020'.
wa_item_control-chg_delqty = 'X'.
wa_item_control-VOLUME_FLG = 'X'.
wa_item_control-NET_WT_FLG = 'X'.
wa_item_control-GROSS_WT_FLG = 'X'.
APPEND wa_item_control TO item_control.
CALL FUNCTION 'BAPI_INB_DELIVERY_CHANGE'
EXPORTING
header_data = wa_header_data
header_control = wa_header_control
delivery = '0180000545'
* TECHN_CONTROL =
TABLES
* HEADER_PARTNER =
* HEADER_PARTNER_ADDR =
* HEADER_DEADLINES = deadlines
item_data = item_data
item_control = item_control
* ITEM_SERIAL_NO =
* EXTENSION1 =
* EXTENSION2 =
return = return
* TOKENREFERENCE =
* HANDLING_UNIT_HEADER =
* HANDLING_UNIT_ITEM =
* PARTIAL_GR_OBJECTS =
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

Hi,
Pls try to use the other structure
ORDER_SCHEDULES_INX type BAPISCHDLX bcoz it is used to update the required field.
Now for the date field add the required days to set it as future date.
ex:
l_date = l_date + 12. // it will be set to future or requred date.
Reward if helpful.
Regards
Chandralekha

Use WS_DELIVERY_UPDATE_2 for Inbound Delivery HU Update?

Hello all,
I have used WS_DELIVERY_UPDATE_2 to successfully update Handling units to Outbound delivery and also perform batch split.
Can the same FM be used to update Inbound delivery with Handling units. I will be uploading the HU's through excel file.
Please advice.
Thanks,
Subba

Hi,
Below is code for Inbound Delivery With HU, it worked for me.
gs_head-DELIV_DATE = sy-datum.
gs_head-DELIV_TIME = sy-uzeit.
gs_item-DELIV_ITEM = p_item1.
gs_item-MATERIAL = p_matnr1.
gs_item-DELIV_QTY = p_quan.
gs_item-UNIT = 'EA'.
gs_item-PO_NUMBER = p_po.
gs_item-PO_ITEM = 10.
APPEND gs_item TO gt_item.
CLEAR:gs_item.
CALL FUNCTION 'BBP_INB_DELIVERY_CREATE'
EXPORTING
    IS_INB_DELIVERY_HEADER = gs_head
IMPORTING
    EF_DELIVERY            = gv_vbeln
TABLES
    IT_INB_DELIVERY_DETAIL = gt_item
    RETURN                 = gt_ret1.
gs_refobj-OBJECT = 03.
gs_refobj-OBJKEY = gv_vbeln.
gs_humain-vhilm = p_matnr2.
GS_HUMAIN-HU_STATUS_INIT = 'A'.
gs_humain-STATUS = '0010'.
gs_itempr1-VELIN = 1.
gs_itempr1-QUANTITY = p_quan.
gs_itempr1-meins = 'EA'.
gs_itempr1-matnr = p_matnr1.
gs_itempr1-werks = p_plant.
CALL FUNCTION 'PROCESS_HU_INBOUND_DLVRY'
EXPORTING
    I_HU_ID               = gv_huid (Blank)
    I_NEW_HU              = 'X'
    I_UPDATE_DB           = 'X'
    I_CREATE_HU           = 'X'
    I_REFERENCE_OBJECT    = gs_refobj
    I_HU_HEADER_MAIN      = gs_humain
    I_SAVE_STEP           = 'ITEM'
    I_PACK_ACTIVITY       = 'MAT'
    I_DELIVERY_TYPE       = '7'
    I_PACKING_ACTIVITY    = 'PACK'
    I_PACK_TYPE           = 'MAT'
    IS_ITEM_PROPOSAL      = gs_itempr1
IMPORTING
    O_HU_REF_ID           = gs_erefid
    O_HU_HEADER           = gt_eheader
    O_HU_ITEMS            = gt_eitem
    O_HU_MESSAGES         = gt_emsg[]
TABLES
    ET_CREATED_HUS        = gt_ehus[]
EXCEPTIONS
    INPUT_MISSING         = 1
    NOT_POSSIBLE          = 2
    HEADER_ERROR          = 3
    ITEM_ERROR            = 4
    SERIAL_NR_ERROR       = 5
    FATAL_ERROR           = 6
    OPERATION_FAILED      = 7
    DELIVERY_UPDATE_ERROR = 8
    OTHERS                = 9.
IF SY-SUBRC EQ 0.
CLEAR:gs_vekp.
SELECT SINGLE * FROM vekp INTO gs_vekp WHERE VPOBJKEY = GV_VBELN.
ls_vbkok_wa-vbeln_vl = gv_vbeln.
ls_vbkok_wa-vbeln = gv_vbeln.
ls_vbkok_wa-VBTYP_VL = 7.
ls_vbkok_wa-wabuc = 'X'.
ls_vbkok_wa-spe_auto_gr = 'X'.
ls_vbkok_wa-kzebu = 'X'.
lt_verko-exidv = gs_vekp-exidv.
lt_verko-exida = 'E'.
lt_verko-magrv = 'YB01'.
lt_verko-werks = p_plant.
lt_verko-STATUS = '0010'.
APPEND lt_verko.
lt_verpo-venum = gs_vekp-venum.
lt_verpo-exidv_ob = gs_vekp-exidv.
lt_verpo-exidv = gs_vekp-exidv.
lt_verpo-velin = '1'.
lt_verpo-vbeln = gv_vbeln.
lt_verpo-POSNR = p_item1 .
lt_verpo-TMENG = p_quan.
lt_verpo-VRKME = 'EA'.
lt_verpo-MATNR = p_matnr1.
lt_verpo-werks = p_plant.
APPEND lt_verpo.
lt_vbpok-vbeln_vl = gv_vbeln.
lt_vbpok-posnr_vl = p_item1.
lt_vbpok-vbeln = gv_vbeln.
lt_vbpok-posnn = p_item1.
lt_vbpok-pikmg = p_quan.
lt_vbpok-matnr = p_matnr1.
lt_vbpok-werks = p_plant.
lt_vbpok-pstyv = 'ELP'.
APPEND lt_vbpok.
lt_repack-SOURCEHU = gs_vekp-exidv.
lt_repack-DESTHU = gs_vekp-exidv.
lt_repack-PACK_QTY = p_quan.
lt_repack-BASE_UOM = 'EA'.
lt_repack-MATERIAL = p_matnr1.
lt_repack-PLANT = p_plant.
lt_repack-DELIV_NUMB = gv_vbeln.
lt_repack-DELIV_ITEM = p_item1.
APPEND lt_repack.
CALL FUNCTION 'WS_DELIVERY_UPDATE_2'
    EXPORTING
      VBKOK_WA               = ls_vbkok_wa
      DELIVERY               = gv_vbeln
      update_picking         = 'X'
      no_messages_update_1   = 'X'
      synchron               = 'X'
      commit                 = ' '
      NICHT_SPERREN_1        = 'Y'
      if_database_update_1   = '1'
      if_error_messages_send = 'X'
    TABLES
      PROT                   = lt_prot
      VERKO_TAB              = lt_verko
      VERPO_TAB              = lt_verpo
      IT_REPACK = lt_repack.
COMMIT WORK and WAIT.
Thanks,
Shankar Darbha

Inbound delivery putaway quantity update

Similar Messages

Maybe you are looking for