IDOC for outbound delivery

Hi All,
I need to generate an outbound IDOC when DO is created in VL01N.
I searched in SDN and it returns me a lot of different results that really confusing.
I found some using IDOC_OUTPUT_DESADV01, some using IDOC_OUTPUT_DELVRY.
I do look into the codes in these FM. The IDOC_OUTPUT_DELVRY appears to use the LIKP and LIPS table, and in DOC_OUTPUT_DESADV01 using VBDKL and VBDPL after calling this FM 'SD_DELIVERY_VIEW'.
Can someone please explain to me what is the difference between these two FM and which one should I use if I just need to generate an outbound IDOC once DO created.
Thanks a lot.
Best Regards,
JL

By the way, what message type and basic type can be used for these FM?
I also found a lot of opinion from here, some say DELVRY03. some say DELVRY04, some say DELVRY05.
Is it no problem with using which basic type here as long as it fits the data that u want in the IDOC?
Please advice.
Thanks.
Best Regards,
JL

Similar Messages

  • Automatic generation of Idoc for outbound delivery

    Hi Experts,
    I need to generate Idoc automatically for each outbound delivery created in VL01n. I just wanted to know that whether we need to asign output type for each delivery number manually or is there any automated process available to generate Idoc for all the outbound deleveries automatically. Could some one share the information regarding the above matter and other information if there is any.

    Hi,
    U wont manuallly assign the output type for every delivery u create.
    There will be Customization part which will be done by Functional  guys and they will do that configuration.
    This will auotomaticcaly set the Output type, medium..
    Ones the configuration is done u just need to create partner profiles ( port and rfc by Basis people) .
    Rvert back if any issues,
    regards,
    Naveen

  • BAPI for outbound delivery without order reference???????????????????

    hello folks
    i want to a bapi for transaction <b>VL01NO</b>. this transaction is used for creating outbound delivery <b>wihtout a order reference</b>. I did a search but was not able to find a bapi pls help.

    Hi,
    Could you please send me the sample code for BAPI_DELIVERYFREE_PROXY_CREATE? I am using the IDOC for outbound delivery w/o order reference. I didnt find any standard process code for this..
    Any suggestions on the same??
    Thanks,
    Prasad

  • Plan order created for Outbound delivery

    Hi Gurus,
    For some materials, When MRP is run it generates plan order for Outbound material with same qty as that of outbound delivery.
    What setting should be done as not to generate plan order for outbound delivery.
    thnx in advance.

    Hi,
    There is nothing in message control tab for outbound parameter(we20) and even there are multiple changes in delivery.
    What we do is as soon as the delivery is created .  Z trnx is executed  which changes the dec whse status A(Relevent ) to  B (distribution) simulteneously outbound Idoc is created and delivery details send to whse.
    Normally there will be one outbound idoc per delivery , but in this case there are 2 (duplicate)

  • 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.

  • Condition table for outbound delivery

    Hi guys
    Is it possible to create a new condition table for outbound delivery output type with a field „sold-to”, although this field is available in the field catalogue , it does not show up during a table creation in the FieldCatlg,why?
    Your quick response appreciated .
    Regards
    Dominik

    Hi Dominik,
    You need to Append the new fields which you want to see in the Field Catelog to create a condition table.
    Please follow the following process
    Got to T. Code SE11 andGive the Table name
    Then click on the Button Append Structure and
    Key in the name of you append starting with letter 'Z'.
    Add fields whcih you want.
    Activate the table.
    Hope this is clear.
    Reward if helpful.
    Thanks,
    Praveen

  • 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.

  • Automatic goods issue for outbound delivery, during the transfer order confirmation

    Hello,
    Could you please advise how to realize automatic goods issue for outbound delivery, during the transfer order confirmation in the WMS.
    Now after creation of outbound delivery, i can't post the goods issue. Before i have to make the transfer order and confrim it and only after this i can post the goods issue in the VL02 t-code.
    Could you please advise - what i have to customize that to make automatic GI for outb. delivery (i mean with creation material document) during the TO confrimation.
    Thanks in advance.

    Hi Iiya
    Check the below setting, might be helpful

  • 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

  • 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...!!!!

  • 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

  • BAPI for posting equivalent of MIGO GR (101) for OUTBOUND DELIVERY (R05)

    Hi everyone
    I am looking for a BAPI or function module to do the above; it is the second leg of an STO posting between plants, the first leg being where the goods issue is posted against the outbound delivery into in-transit stock (IM movement 641), with the second being to GR this stock with a 101, which will take it out of in-transit and into unrestricted stock at the destination plant.
    I have tried BAPI_GOODSMVT_CREATE from every angle but have come to the conclusion it does not cater for this. I also tried to do the GR against the STO (P/O) from which the delivery was created, but this does not work as the follow-on documents for the delivery will not be updated.
    Any suggestions?
    Thanks
    Andrew

    hi,
    i try to doing posting goods issue for outbound delivery out fo the regular progression.
    the posting is automaticly as part of outside program.
    thanks alot,

  • 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.

  • BAPI for Outbound Delivery Creation with reference to Sales Order - VL01N

    Hi Everybody,
           We are in ECC 5.0 version.
           I want to create a enhancement for Outbound Delivery Creation with reference to a Sales Order.
           Is any BAPI available for this ?
           Any input on this will be very much helpfull.
           Please suggest any BAPI available for this, or should I go for BDC using VL01N or VL04 ?
           Thanks in advance.
    regards,
    Nagarajan.J

    Hi Nagarajan,
    The BAPI BAPI_DELIVERYPROCESSING_EXEC meets your requirement. You can create delivery with reference to sales order.
    The below is the sample code...
      data:lt_request      like bapideliciousrequest
                                    occurs 0 with header line,
           lt_createditems like bapideliciouscreateditems
                                    occurs 0 with header line,
           lt_return       like bapiret2
                                    occurs 0 with header line.
        lt_request-document_type      = 'A'.
        lt_request-document_numb      = vbeln.
        lt_request-document_item      = posnr.
      lt_request-material           = matnr.
      lt_request-plant              = werks.
      lt_request-stge_loc           = lgort.
      lt_request-quantity_base__uom = base_uom_qty.
      lt_request-delivery_date      = sy-datum.
      append lt_request.
      call function 'BAPI_DELIVERYPROCESSING_EXEC'
      EXPORTING
        DELIVERY_EXTEND       =
        TECHN_CONTROL         =
        tables
          request               = lt_request
          createditems          = lt_createditems
          return                = lt_return.
      loop at lt_return where type = 'A'
                          or  type = 'E'.
        exit.
      endloop.
      if sy-subrc <> 0.
    Use the BAPI for Commit
        call function 'BAPI_TRANSACTION_COMMIT'
             exporting
                  wait = 'H'.
      endif.
    Thanks
    Ramakrishna

  • BAPI for Outbound Delivery Creation with reference to Sales Order

    Dear all,
    I'm on R/3 4.6B platform and to develop an RFC for outbound Delivery creation instead of using the standard VL01N transaction.
    I've review BAPI for Outbound Delivery Creation with reference to Sales Order - VL01N thread which suggest BAPI_DELIVERYPROCESSING_EXEC .
    However, in 4.6B, that function module doesn't exist. Appreciate any suggestion and or workaround.
    Thanks.
    Steven
    Edited by: Steven Khoo on Mar 25, 2010 7:13 AM
    Edited by: Steven Khoo on Mar 25, 2010 7:14 AM

    Not required anymore

Maybe you are looking for

  • How to install Mac OS 10.4.8 on 4 new WD Raptors?

    Hello, just got my Mac Pro delivered with 1 x 250 GB drive. Now I want to replace this drive with 4 WD 74GB Raptor's in a RAID 0 configuration. How can I do this? For the moment I have only the Install CD's and the 4 Raptor's. They are not yet format

  • In the paragraph after a conditional build tag, an inline image gets wrapped in a div tag

    Hi, TCS5, so FM 12 and RH11. I have successfully applied some conditional build tags by turning off the apply conditional build tag setting and using the Conditional Build Expression in the WebHelp properties instead. In RoboHelp, everything looks co

  • Apple Tv Mirror from iPad

    We are planing to go on a cruise very soon, and done some reading, but not 100% one 1 thing. If i load up my ipad 3 (the wifes got ipad 2) then connect up the Apple Tv via hdmi cable, would i be able to mirror whats on our ipads on the TV? The room w

  • Does the Finder support reading and burning blu-ray discs?

    Assuming I have an external firewire blu-ray burner (recommendations for this also welcome - which make/model is good, and can I buy an internal model and fit it to a regular DVD external case?) I'd like to keep a few backup discs of my 1TB ReadyNAS

  • Reg: replacement of i-way with PI in ECC 6.0

    Hello Experts currently we are using R/3 4.7 version and middle ware we are using is i-way and we are planning to upgrade to ECC 6.0 and i would like to know how compatible is i-way is with SAP ECC 6.0 and is there any neccessity to replace the same