Unable to update Qty for outbound Delivery using BAPI_OUTB_DELIVERY_CHANGE

Hi Experts,
I am unable to update the Outbound Delivery quantity using FM BAPI_OUTB_DELIVERY_CHANGE. I am getting error in BAPI Return "Error in document &1 item &2 (quantity consistency check)".
Here is my sample program to update Quantity
*& Report  ZTEST_BAPI                                                  *
REPORT  ZTEST_BAPI                              .
tables : lips.
parameters : v_vbeln like likp-vbeln,
             v_posnr like lips-posnr.
data : it_item type BAPIOBDLVITEMCHG occurs 0,
       wa_item type BAPIOBDLVITEMCHG,
       it_return type BAPIRET2 occurs 0,
       i_head type BAPIOBDLVHDRCTRLCHG,
       i_hdata type BAPIOBDLVHDRCHG,
       wa_conf type BAPIOBDLVITEMCTRLCHG,
       it_conf type BAPIOBDLVITEMCTRLCHG occurs 0.
start-of-selection.
select single * from lips into lips where
                  vbeln = v_vbeln
                  and posnr = v_posnr.
if sy-subrc eq 0.
move lips-vbeln to I_hdata-DELIV_NUMB.
*append wa_hdata to i_hdata.
move lips-vbeln to wa_item-DELIV_NUMB.
move lips-posnr to wa_item-DELIV_ITEM.
move lips-matnr to wa_item-MATERIAL.
move lips-charg to wa_item-BATCH.
lips-LFIMG = lips-LFIMG + 20.
move  lips-LFIMG to wa_item-DLV_QTY.
move  lips-LGMNG to wa_item-DLV_QTY_IMUNIT.
move  lips-VRKME TO wa_item-SALES_UNIT.
MOVE  'KGM'      TO WA_ITEM-SALES_UNIT_ISO.
MOVE LIPS-MEINS  TO WA_ITEM-BASE_UOM.
MOVE 'KGM'  TO WA_ITEM-BASE_UOM_ISO.
append wa_item to it_item.
move lips-vbeln to wa_conf-DELIV_NUMB.
move lips-posnr to wa_conf-DELIV_ITEM.
move 'X' to wa_conf-CHG_DELQTY.
append wa_conf to it_conf.
endif.
CALL FUNCTION 'BAPI_OUTB_DELIVERY_CHANGE'
  EXPORTING
    HEADER_DATA               = i_hdata
    HEADER_CONTROL            = i_head
    DELIVERY                  = v_vbeln
  TECHN_CONTROL             =
  TABLES
  HEADER_PARTNER            =
  HEADER_PARTNER_ADDR       =
  HEADER_DEADLINES          =
   ITEM_DATA                 = it_item
   ITEM_CONTROL              = it_conf
  ITEM_SERIAL_NO            =
  SUPPLIER_CONS_DATA        =
  EXTENSION1                =
  EXTENSION2                =
    RETURN                    = it_return
  TOKENREFERENCE            =
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
I need to update Qty to the outbound delivery for an given item.
Thanks for your quick response.
With Regards,
Bala Sankar
9900433488

Hi Bala,
make sure you are setting...
itemdata-dlv_qty
itemdata-dlv_qty_imunit
itemdata-fact_unit_nom     e.g = 1.
itemdata-fact_unit_denom  e.g = 1.
Rgds
Glenn

Similar Messages

  • Batch splitting for Outbound delivery using BAPI_OUTB_DELIVERY_CHANGE

    Hi all,
    Let me explain the scenario first.
    We are going to create a delivery in SAP with some line items and send it to a non-sap third party WMS.  They will pick the goods and send the delivery confirmation back to SAP.  In SAP we need to delivery confirmation and PGI.
    The problem is when the third Part WMS does a batch split for a particular line item, we need to update the same in SAP and then do the PGI.  For this I was trying to use BAPI_OUTB_DELIVERY_CHANGE to create split batches.  It is splitting the batches but the overall pick status is becoming B (Partially picked).  SO it is not allowing to do the PGI.
    Can anyone solve my problem

    Hi Bala,
    make sure you are setting...
    itemdata-dlv_qty
    itemdata-dlv_qty_imunit
    itemdata-fact_unit_nom     e.g = 1.
    itemdata-fact_unit_denom  e.g = 1.
    Rgds
    Glenn

  • Error while doing PGI for Outbound delivery using BAPI BAPI_GOODSMVT_CREATE

    Hi All,
    I am getting an below error while doing PGI for outbound delivery using the BAPI BAPI BAPI_GOODSMVT_CREATE:
    Goods movement not possible with mvmt type 601
    Can anyone suggest me what will be the solution for it?
    Regards,
    Raghuraman.k

    I tried with the above BAPI but it is not working.
    In my case a delivery has one line item with batch split and other line item without batch split.
    Below is my code :
    DATA : gwa_header_data TYPE bapiobdlvhdrcon,
           gwa_header_ctrl TYPE bapiobdlvhdrctrlcon,
           lv_delivery     TYPE bapiobdlvhdrcon-deliv_numb,
           git_item_data TYPE STANDARD TABLE OF bapiobdlvitemcon,
           gwa_item_data TYPE bapiobdlvitemcon,
           git_item_ctrl TYPE STANDARD TABLE OF bapiobdlvitemctrlcon,
           gwa_item_ctrl TYPE bapiobdlvitemctrlcon,
           git_return    TYPE STANDARD TABLE OF bapiret2,
           gwa_return    TYPE bapiret2.
    *Header data
    gwa_header_data-deliv_numb = '0808000002'.
    *Header Control data
    gwa_header_ctrl-deliv_numb = '0808000002'.
    gwa_header_ctrl-post_gi_flg = 'X'.
    *Delivery Number
    lv_delivery = '0808000002'.
    *Item data and its corresponding control data
    gwa_item_data-deliv_numb      = '0808000002'.
    gwa_item_data-deliv_item      = '900002'.
    gwa_item_data-dlv_qty         = 4.
    gwa_item_data-dlv_qty_imunit  = 4.
    gwa_item_data-fact_unit_nom   = 1.
    gwa_item_data-fact_unit_denom = 1.
    APPEND gwa_item_data TO git_item_data.
    gwa_item_ctrl-deliv_numb      = '0808000002'.
    gwa_item_ctrl-deliv_item      = '900002'.
    gwa_item_ctrl-chg_delqty      = 'X'.
    APPEND gwa_item_ctrl TO git_item_ctrl.
    gwa_item_data-deliv_numb      = '0808000002'.
    gwa_item_data-deliv_item      = '900003'.
    gwa_item_data-dlv_qty         = 6.
    gwa_item_data-dlv_qty_imunit  = 6.
    gwa_item_data-fact_unit_nom   = 1.
    gwa_item_data-fact_unit_denom = 1.
    APPEND gwa_item_data TO git_item_data.
    gwa_item_ctrl-deliv_numb      = '0808000002'.
    gwa_item_ctrl-deliv_item      = '900003'.
    gwa_item_ctrl-chg_delqty      = 'X'.
    APPEND gwa_item_ctrl TO git_item_ctrl.
    gwa_item_data-deliv_numb      = '0808000002'.
    gwa_item_data-deliv_item      = '000020'.
    gwa_item_data-dlv_qty         = 10.
    gwa_item_data-dlv_qty_imunit  = 10.
    gwa_item_data-fact_unit_nom   = 1.
    gwa_item_data-fact_unit_denom = 1.
    APPEND gwa_item_data TO git_item_data.
    gwa_item_ctrl-deliv_numb      = '0808000002'.
    gwa_item_ctrl-deliv_item      = '000020'.
    gwa_item_ctrl-chg_delqty      = 'X'.
    APPEND gwa_item_ctrl TO git_item_ctrl.
    BREAK-POINT.
    CALL FUNCTION 'BAPI_OUTB_DELIVERY_CONFIRM_DEC'
      EXPORTING
        header_data    = gwa_header_data
        header_control = gwa_header_ctrl
        delivery       = lv_delivery
      TABLES
        item_data      = git_item_data
        item_control   = git_item_ctrl
        return         = git_return.
    BREAK-POINT.
    IF git_return IS INITIAL.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    ENDIF.

  • Unable to update WADAT_IST in Outbound Delivery via iDoc WHSCON (DELVRY03)

    Processing iDoc WHSCON (DELVRY03) to update an Outbound Delivery and post Goods Issue, the field ACTUAL GI DATE (WADAT_IST) is not updated. I am using segment E1EDT13 of iDoc WHSCON to inform dates.
    Can anyone tell me if there is any other segment, field or qualifier in the structure of of iDoc WHSCON to inform WADAT_IST?
    Thanks in advance.
    Best regards.

    I dont think it is possible to achieve this.  For more information, have a look at the following note:-
    Note 1839738 - Error HUSELECT005 occurs when using existing HU in SHPCON (WHSCON)
    G. Lakshmipathi

  • BAPI_GOODSMVT_CREATE update VBFA or not for Outbound Delivery?

    Dear Gurus,
    When I try to use BAPI_GOODSMVT_CREATE to do the goods receipt for the outbound delivery as the replacement for MIGO transaction, I use 01 as movement code and the bapi create material document and updating MSEG. But it doesn't update VBFA so the items is still showed in MIGO and cannot post there (because it is already moved in BAPI in program.)
    Anybody have any suggestion for this situation? Thanks a lot and points will be rewarded.

    Hello,
    When you use BAPI_GOODSMVT_CREATE  to post Goods Receipt for outbound delivery, reference documents at header and line items should be delivery number and line numbers (BAPI2017_GM_HEAD_01-REF_DOC_NO, BAPI2017_GM_ITEM_CREATE-DELIV_NUMB_TO_SEARCH & BAPI2017_GM_ITEM_CREATE-DELIV_ITEM_TO_SEARCH). Then only document flow will be updated.
    Thanks,
    Venu

  • Goods Receive for Outbound Delivery Without Reference using MIGO

    Dear Colleague ...
    We might need your insight on the case below related to Goods Receive of Outbound Delivery without Reference using MIGO:
    (1) In the current SAP Enjoy screen of MIGO, we are allowed to select the reference document (e.g. = PO, Material Document, Inbound Document, Outbound Document, etc.)
    (2) We did 3 (three) kind of test set: GR for Inbound Delivery, GR for Outbound Delivery with STO and GR for Outbound Delivery without reference.
    (3) The first 2 (two) cases work just find with MIGO.  We believe it is because the receiving plant is pretty much determined in the reference document, which is PO (case 1) or STO (case 3)
    (4) However, the last case came up with the error message "Goods receipt not possible for delivery 8000610236: error code 5".  We believe that this is the standard design of SAP, that the receiving plant is required and it is not defined explicitly in the delivery document.
    (5) Moreover, we also believe that that's the reason why SAP (via the Logistic Execution module) provide the Handling Unit and Shipment, which can be used to perform such receive function, which will imply the MM posting (goods issue and goods receive) IF there is stock transfer involved.
    Appreciate for any thoughts or input on the above.  Many thanks,
    Alvon Sibarani

    use transaction mb0a it will work for the scenario.

  • Create outbound delivery using VL10B for Stock Tranfer order

    Hi ALL gurus,
    I had created STO stock transfer order (UB order type ) and release the STO using ME21N and ME29N
    When try create a outbound delivery using VL10B, the STO not show, i remove all check and blank in all seclection. The STO still not show.
    Anyone can help ?? where going wrong ???
    Rejoice

    Hi
    There are two processes for STO , that is with shipping & without shipping.
    For Without Shipping there is no config required.
    For STO with shipping You need to configure in
    SPRO-> IMG-> Materials Management-> Purchasing-> Purchase Order-> Set up Stock Transport Order
    Please go through the link on all types fo STO's
    http://help.sap.com/saphelp_erp2004/helpdata/EN/4d/2b90dc43ad11d189410000e829fbbd/content.htm
    Thanks & Regards
    Kishore
    Edited by: Kishore Kumar Chiluka on Jul 2, 2008 8:25 AM

  • Create TO automatic by using wave pick for outbound delivery NLC (STPO)

    Dear all,
    In Cross company code process, we have to create TO automatic by using wave pick for outbound delivery NLC (delivery type NLCC). Time data in outbound delivery NLC have been fulfilled, but there is no TO created, what is wrong in this? pls help.
    Thanks

    Hi Kishor,
    Is there any requirement of TO when ECC system is Interfaced to EWM.
    As per my understanding we have terminology WT & WO in EWM.
    Regards,
    Rock

  • Input parameters for BAPI_GOODSMVT_CREATE --MIGO--GR for Outbound Delivery

    Hi Friends,
      We have to create a Goods Receipt against an Outbound Delivery ( movement type "101" ) using the BAPI <b>BAPI_GOODSMVT_CREATE</b>.
    In online the user is using <b>MIGO</b> transaction for the same. There he will choose the GOODS RECEIPT for OUTBOUND DELIVERY and enters the delivery number. The movement type "101" is used.
      Could you please tell me the GM code and the required fields to be passed for the above scenario.
    I have gone through the example program in the link...
    http://www.sap-img.com/abap/bapi-goodsmvt-create-to-post-goods-movement.htm
    <b>but unable to find how to use this BAPI for simulating MIGO transaction.</b>
    <b>The fields available are with us are...</b>
    Delivery. No. --- Doc. Date - Posting Date-Quantity-Storage Location-
    Reason for movement-External qty-External qty unit-Goods recipient-Excise Selection
    Are these fields sufficient for doing MIGO with this BAPI or do we require more fields???
    Thanks and Regards,
    Bharat

    see the following code. it may be useful.
      LOOP AT I_TAB.
          count = sy-tabix.
          SELECT SINGLE * FROM ZMM_GR_UPLOAD1
                                    WHERE SOLOMON_GR = I_TAB-SOLOMON_GR AND
                                    SOLOMON_GRDAT = I_TAB-SOLOMON_GRDAT.
          IF SY-SUBRC = 0.
            I_TAB-FLAG = 'C'.
            modify i_tab index count.
            concatenate 'File Name : ' name into i_msg1.
            append i_msg1.
            CONCATENATE 'ERROR  PO : ' I_TAB-SOL_PONO
                '  WAS ALREADY UPLOADED' INTO I_MSG1.
            APPEND I_MSG1.
            CLEAR I_TAB-FLAG.
            CONTINUE.
          ELSE.
            REFRESH I_ITEMS.
            CLEAR I_ITEMS.
            CONCATENATE I_MAIN-SOLOMON_GRDAT+4(4)
                        I_MAIN-SOLOMON_GRDAT+2(2)
                        I_MAIN-SOLOMON_GRDAT+0(2) INTO G_DATE.
            gmhead-pstng_date = G_DATE.
            gmhead-doc_date = sy-datum.
            gmhead-pr_uname = sy-uname.
    "01 - MB01 - Goods Receipts for Purchase Order
            gmcode-gm_code = '01'.
            refresh itab.
            clear itab.
            SORT I_MAIN BY SOLOMON_GR.
            LOOP AT I_MAIN WHERE SOLOMON_GR = I_TAB-SOLOMON_GR.
              itab-move_type  = '101'.
              itab-mvt_ind    = 'B'.
              itab-plant      = I_MAIN-WERKS.
              itab-material   = I_MAIN-MATNR.
              itab-entry_qnt  = I_MAIN-ERFMG.
             itab-stge_loc   = 'OMR1'.
    itab-move_stloc = pcitab-recv_loc.
             itab-REF_DOC = 'exnum123'.
              itab-NO_MORE_GR = 'X'.
              itab-WITHDRAWN = ''.
              itab-stge_loc   = I_MAIN-LGOBE.
              itab-po_number  = I_MAIN-EBELN.
              itab-po_item    = I_MAIN-EBELP.
              itab-unload_pt  = I_MAIN-ABLAD2.
              append itab.
            ENDLOOP.
            if not itab[] is initial.
              call function 'BAPI_GOODSMVT_CREATE'
               exporting
                   goodsmvt_header             = gmhead
                   goodsmvt_code               = gmcode
                 *   TESTRUN                     = ' '
              IMPORTING
                  goodsmvt_headret            = mthead
             *   MATERIALDOCUMENT            =
      MATDOCUMENTYEAR             =
               tables
                 goodsmvt_item               = itab
      GOODSMVT_SERIALNUMBER       =
                return                      = errmsg.
              clear errflag.
              loop at errmsg.
                if sy-tabix = 1.
                  concatenate 'File Name : ' name into i_msg1.
                  append i_msg1.
                  concatenate 'Sol PO : ' I_TAB-SOL_PONO ' '
                   I_TAB-SOL_PODT into i_msg1.
                  append i_msg1.
                endif.
                if errmsg-type eq 'E'.
                  write:/'Error in function', errmsg-message.
                  errflag = 'X'.
                else.
                  write:/ errmsg-message.
                endif.
                move errmsg-message to i_msg1.
                append i_msg1.
              endloop.
              if errflag is initial.
                CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
              EXPORTING
                WAIT          =
              IMPORTING
                RETURN        =
               commit work and wait.
                if sy-subrc ne 0.
                  write:/ 'Error in updating'.
                  exit.
                else.
                  concatenate 'File Name : ' name into i_msg1.
                  append i_msg1.
                  concatenate 'Sol PO : ' I_TAB-SOL_PONO ' '
                   I_TAB-SOL_PODT into i_msg1.
                  append i_msg1.
                  write:/ mthead-mat_doc, mthead-doc_year.
                  ZMM_GR_UPLOAD1-SOLOMON_GR = I_TAB-SOLOMON_GR.
                 CONCATENATE I_TAB-SOLOMON_GRDAT+4(4)
                       I_TAB-SOLOMON_GRDAT+2(2)
                       I_TAB-SOLOMON_GRDAT+0(2) INTO
                        ZMM_GR_UPLOAD1-SOLOMON_GRDAT.
                  ZMM_GR_UPLOAD1-SOLOMON_GRDAT = I_TAB-SOLOMON_GRDAT.
                  INSERT ZMM_GR_UPLOAD1.
                  COMMIT WORK.
                  I_TAB-FLAG = 'C'.
                  MODIFY I_TAB INDEX COUNT.
                  CONCATENATE mthead-mat_doc  mthead-doc_year
                             into i_msg1.
                  append i_msg1.
                 perform upd_sta.
                endif.
              endif.
            endif.
          ENDIF.
        ENDLOOP.

  • Post Goods Receipt for Inbound Delivery using WHSCON IDoc

    Dear All
    Currently I am working on a big project dealing with EDI connections to our logistics partner for the Export business. The entire message flow between Lindt and our partner should be via EDI. Our SAP release is (still) 4.6c.
    We will create two kinds of despatch advice messages, one for inbound deliveries and one for outbound deliveries for customers.
    I would appreciate your support in the following problem that I am facing with the inbound delivery scenario:
    We create stock transport orders (purchase orders, POs) for the goods intended to be delivered into the plant at our partner
    We create a delivery (type NL = replenishment delivery) for this POs
    As soon as we post the goods issue we send the despatch advice (as EANCOM D96A DESADV message) to our partner.
    At this point the delivery is basically completed, i.e. packing status (PS) and goods movement status (GM / GS) are equal to 'C' (= completed).
    Our logistics partner uses the same EDI message to send us the goods receipts data, e.g.:
    We dispatched 50 units of a product => QTY:50:12
    The partner received indeed 50 units => QVR:50:66
    Please note that we do not use the QVR segment for the quantity difference (between despatched and received quantity) but it contains the received units. This way we avoid negative values in the QVR segment.
    When the logistics partner sends back the DESADV message containing the received quantities (QVR segment) we want to make
    the goods receipts for the products in the original stock transport order and
    upate the message flow in the delivery
    My idea was to transform the incoming DESADV message into a WHSCON.DELVRY03 IDoc based on the documentation in: [Delivery Interface|http://help.sap.com/saphelp_crm40/helpdata/en/e2/654b15a9f411d184ec0000e81ddea0/content.htm]
    In the delivery header control E1EDL18 I used QUALF = 'PGI' (Post goods issue).
    I prepared an inbound WHSCON IDoc according to the documentation mentioned below. I managed to get some feedback from the Idoc processing implying that the system tried to do the goods receipt in the PO but failed.
    To make a long story short here are my questions:
    Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
    Does anybody have an example on how to fill the WHSCON IDoc?
    Or is my approach a cul-de-sac ?
    Kind Regards
       Uwe
    PS: A related question can be found here: Goods Receipt in PO AND Message Flow Update in Inb. Delivery using WMMBXY

    Hi Uwe,
    Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
    The binary answer would be no. You should use WMMBXY or MBGMCR instead.
    But if we are doing goods receipt against Inbound delivery then answer is YES with additionally E1EDL18-QUALF = 'PIC' populated. But please remember no partial receipt is possible against Inbound Delivery.
    We should populate E1EDL20-VBELN with our Inbound delivery number and line item info should go to E1EDL24.
    I have done a similar interface recently where we are doing receipt against Inbound delivery. But our case was a bit complex because we had to support against Inbound delivery. So we had to go for a custom solution on top of IDOC_INPUT_DELVRY.
    Hope this helps. Let me know if you have more questions.
    Regards,
    Rudra

  • BAPI for GR for Outbound delivery

    Hi Gurus,
       I need to create a Goods Receipt against an Outbound Delivery ( movement type "101" ) using the BAPI BAPI_GOODSMVT_CREATE
    user is using MIGO transaction for the same. There he will choose the GOODS RECEIPT for OUTBOUND DELIVERY and enters the delivery number. The movement type "101" is used.
    I tried passing gm_code = 01 and mvt_type = 101 and mvt indicator as u2018Bu201D , but  Iu2019m getting an error message  'ENTER PURCHASE ORDER NUMBER'.
    I donu2019t have PO number . I just have shipment number from which I have found open outbound deliveries and now I need to do GR for each of the Outbound delivery.
    Please let me know if Iu2019m passing the right gm_code and mvt indicator to the BAPI or if Iu2019m missing any parameters. Iu2019m passing the following parameters to the BAPI ?
    Delivery. No. , delivery item, Doc. Date , Posting Date , ref document num , Quantity, Storage Location, External qty, External qty unit, matnr, werks .
    Your help is greatly appreciated.
    Thanks in advance.

    Thanks for replying. I went through the entire BAPI documentation but did not found anything related to GR for outbound deliveries.
    I searched some older posts in sdn related to this problem but almost all are unanswered question.
    I'm passing gm_code = 01 , mvt_type = 101 and have tried all movement indicator like 'B' , 'F' and blank.
    here is what I'm passing in my Bapi.Please let me know if I'm missing something or if I'm passing something incorrectly.
    gm_header-pstng_date = sy-datum.
          gm_header-doc_date   = sy-datum.
          gm_header-ref_doc_no =  wa_lips-vbeln. "The Outbound delivery Number
          gm_code-gm_code      = '01'.
         MOVE '101'              TO     gm_item-move_type.
          gm_item-material             = wa_lips-matnr . "Material Number from the Delivery.
          gm_item-plant                = wa_lips-werks . "Receiving Site.
          gm_item-stge_loc             = wa_lips-lgort. "Receiving Storage Location.
          gm_item-entry_qnt            = wa_lips-lfimg.
         gm_item-entry_uom           = wa_lips-vrkme.
          gm_item-ENTRY_UOM_ISO        = wa_lips-vrkme.
          gm_item-mvt_ind              = 'B ' .
          gm_item-deliv_numb           = wa_lips-vbeln.
          gm_item-deliv_item           = wa_lips-posnr.
          gm_item-DELIV_NUMB_TO_SEARCH = wa_lips-vbeln.  "delivery number
          gm_item-DELIV_ITEM_TO_SEARCH = wa_lips-posnr. "delivery item
    if I donot pass any value in mvt indicator the error I'm getting is 'Update control of movement type is incorrect (entry 101 X X)'
    if I pass 'B' in mvt indicator error is 'Material document data and PO data do not match (Plant)'
    if i pass 'F' , erro ris 'Order  not found or not permitted for goods movement'.
    Please help me. This is kind of critical issue. or please suggest if I can do GR for outbound delv in any other way.
    Thanks...!!!!

  • Issue while creating Outbound Delivery using Standard BAPI

    Hi all,
    I am trying to create an outbound delivery for a Sales order using the Standard BAPI - BAPI_OUTB_DELIVERY_CREATE_SLS.
    After giving the valid inputs for Sales order no and doc no, am getting an error as "No instance of object type OutboundDelivery has been created. External reference:" But when trying to create manually there is no problem. Please suggest what may be the issue and how to correct it?
    Regards,
    Vimala P

    Hi Vimala,
    I am trying to create outbound delivery using BAPI_OUTB_DELIVERY_CREATE_SLS & BAPI_DELIVERYPROCESSING_EXEC. But no success. Getting "No instance of object type outbound delivery has been created" in return.
    1) Delivery Type
    2) Delivery selection date
    Needs to be passed in import parameters.
    Could you please tell me what are all the parameters to be passed under tables tab in RV_DELIVERY_CREATE?
    Thanks in Advance..
    Regards,
    Rajasekar .M

  • Goods Receipt in PO AND Message Flow Update in Inb. Delivery using WMMBXY

    Dear All
    This question is related to a previous one posted in:
    Post Goods Receipt for Inbound Delivery using WHSCON IDoc
    We have a stock transport order (PO) for which we create an inbound delivery. The despatch advice (EANCOM D96A DESADV) is sent to our logistics partner who returns the same EDI message with the received quantities (goods receipt).
    Using the inbound IDoc WMMBID02.WMMBXY I have successfully posted the goods receipt for the original PO. However, the message flow in the delivery is not updated. When we post the goods receipt (transaction MIGO) in dialog for the delivery we see the GR in the message flow.
    I have used the following values with the segments of WMMBID02.WMMBXY (SAP release = 4.6c):
    E1MBXYH:
    Reference = <number of delivery>
    Transaction code = 'MIGO'
    E1MBXYI:
    Movement type = '101'
    Purchasing doc. = <number of PO>
    Item = <Item no. in PO>
    Movement ind. = 'B'
    I am not sure about the correct movement indicator but failed when using a value different from 'B':
    The movement indicator is derived from the transaction code.
    Permitted values:
    '' Goods movement w/o reference
    'B' Goods movement for purchase order
    'F' Goods movement for production order
    'L' Goods movement for delivery note
    'K' Goods movement for kanban requirement (WM - internal only)
    'O' Subsequent adjustment of "material-provided" consumption
    'W' Subsequent adjustment of proportion/product unit material
    QUESTION: Does anybody know if and how inbound WMMBID02.WMMBXY can be used for both the goods receipt in the purchase order AND the message flow in the inbound delivery?
    Regards
       Uwe

    Hello Everybody
    My initial mapping of the WMMBXY IDoc proved to be correct.
    For more details please refer to:
    [Note 833603 - EDI: Goods receipt for stock transport order|https://service.sap.com/sap/support/notes/833603]
    Regards
      Uwe

  • Dynamic Calculation of SLED for Outbound Delivery

    All,
    I have a situation to pick batches at the time of outbound delivery using batch determination. We have a situation where we have some materials which are expiration date managed and some which are not.
    I have set up the batch search strategy with batch status LOBM_ZUSTD (batch is set to released). in the selection criteria
    For Dynamic selection of SLED date i have maintained the selection criteria as LOBM_VFDAT, LOBM-RLZ>0 d. No changes made to the object dependency.
    The Batch Class for Finished goods has LOBM_VFDAT, and no LOBM_RLZ and LOBM_LFDAT.
    In OVM1 i have set the message VL 415 as an error . ' Invalid batch according to batch determination'
    When i am doing a picking of batches for the outbound delivery the strategy analysis gives the SLED > Del. date + Min rem. shelf life e.g Del. date is 4/30 and Min Rem Shelf Life is >0 d.
    When i pick a restricted batch it gives me the correct error message.
    When i pick a batch with unrestricted batch status and an expired batch it gives me an error message.
    When i try to pick a batch which is unrestricted batch with no SLED date it gives me an error message. What is the method to allow picking of batches with no SLED date .
    Thanks for your help with this.

    If you can distinguish between the materials with and w/o shelf life management through a field which is available in the field set of the condition tables (e.g material group, product hierarchy), you could use that field for your condition table and define two condition records in VCH1 - one with selection criteria and one without.
    (you can also consider adding such field to the field cataloge [and then to the condition table], if you have a clear and sensible rule [pls note that adding a field to the field cataloge requires also development to populate the field of the communication structure with value during the program run]).
    It is also possible to influence the batch determination, e.g. via user exit EXIT_SAPLV01F_002 (e.g. you can replace the search procedure [KALSM] for materials w/o SLED and determine different strategy).

  • LSMW for Outbound Delivery

    Hi,
    I am not able to find an LSMW for creating GR for outbound delivery. I tried using recording in MIGO but it did not work. Also MB1C is not working for outbound delivery. Please help.
    Regards,
    Anubhav

    Hi
    I think it is better to write a Z program/ BDC to have a mass GR creation of an outbound delivery.
    or
    You have an Auto Goods receipt using confimations. If we activate Auto GR in customizing for Confirmation control key. Once confirmations(ASN) is created a GR will be created automatically.
    Hope this helps
    Regards,
    Sasi

Maybe you are looking for