During cancellation of delivery document using VL09

Hi,
I want to cancel only 3 items out of 5 items from the delivery document at the time of cancellation by using VL09..
How can i do that??
Rgds,
Pavan.

No. Not other way out. The method suggested above is the best possible method.
As PGI is done for whole Delivery Document, Cancel / reverse of PGI is also done for the whole Delivery Document. You cannot cancel / Reverse partial Line items in Delivery.
Hope this clarifies,
Thanks,
Jignesh Mehta

Similar Messages

  • How 2 creat report for displaying the details of a Delivery Document using

    how to create report for displaying the details of a Delivery Document using the tables LIKP, LIPS
    thank you
    regards,
    jagrut bharatkumar shukla
    points will be rewarded

    HI
    I AM GIVING YOU MY DELIVERY DOCUMENT CODE...MODIFY IT ACCORDING TO YOUR REQUIREMENT
    *& Report  ZDELIVERY                                *
    report  zdelivery  message-id z9bhu          .
    types: begin of t_likp,
               vbeln type likp-vbeln,      "Delivery
               erdat type likp-erdat,      "Date for rec creation
    *           LFDAT TYPE LIKP-LFDAT,      "Delevery Date
    *           WAERK TYPE LIKP-WAERK,      "Currency
               kunnr type likp-kunnr,      "Ship-To Party
               kunag type likp-kunag,      "Sold-to party
               traty type likp-traty,      "Means-of-Transport
           end of t_likp.
    types: begin of t_lips,
               vbeln type lips-vbeln,      "Delivery
               posnr type lips-posnr,      "Delivery item
               matnr type lips-matnr,      "Material Number
               arktx type lips-arktx,      "Short Text for Sales Order Item
               lfimg type lips-lfimg,      "Actual quantity delivered
               netpr type lips-netpr,
    *           MEINS TYPE LIPS-MEINS,      "Base Unit of Measure
               vgbel type lips-vgbel,      "Doc no of the reference document
            end of t_lips.
    types: begin of t_vbpa,
               vbeln type vbpa-vbeln,      "SD DocumenT Number
               posnr type vbpa-posnr,      "Item number
               parvw type vbpa-parvw,      "Partner function
               kunnrb type vbpa-kunnr,      "Customer Number 1
           end of t_vbpa.
    types: begin of t_kna1,
               kunnr type kna1-kunnr,      "Customer Number 1
               name1 type kna1-name1,      "Name 1
               ort01 type kna1-ort01,      "City
               adrnr type kna1-adrnr,      "Address
           end of t_kna1.
    types: begin of t_li_vbpa,
               vbeln type likp-vbeln,      "Delivery
               erdat type likp-erdat,      "Date for rec creation
    *           LFDAT TYPE LIKP-LFDAT,      "Delevery Date
    *           WAERK TYPE LIKP-WAERK,      "Currency
               kunnr type likp-kunnr,      "Ship-To Party
               kunag type likp-kunag,      "Sold-to party
               traty type likp-traty,      "Means-of-Transport
               vbeln1 type lips-vbeln,      "Delivery
               posnr type lips-posnr,      "Delivery item
               matnr type lips-matnr,      "Material Number
               arktx type lips-arktx,      "Short Text for Sales Order Item
               lfimg type lips-lfimg,      "Actual quantity delivered
               netpr type lips-netpr,      "Net Price
    *           MEINS TYPE LIPS-MEINS,      "Base Unit of Measure
               vgbel type lips-vgbel,      "Doc no of the reference document
               vbeln3 type vbpa-vbeln,     "SD DocumenT Number
               parvw type vbpa-parvw,      "Partner function
               kunnrb type vbpa-kunnr,      "Customer Number 1
           end of t_li_vbpa.
    types: begin of t_final,
               vbeln type likp-vbeln,      "Delivery
               erdat type likp-erdat,      "Date for rec creation
               kunnr type likp-kunnr,      "Ship-To Party
               kunag type likp-kunag,      "Sold-to party
               traty type likp-traty,      "Means-of-Transport
               vbeln1 type lips-vbeln,      "Delivery
               posnr type lips-posnr,      "Delivery item
               matnr type lips-matnr,      "Material Number
               arktx type lips-arktx,      "Short Text for Sales Order Item
               lfimg type lips-lfimg,      "Actual quantity delivered
               netpr type lips-netpr,      "Net Price
               vgbel type lips-vgbel,      "Doc no of the reference document
               vbeln3 type vbpa-vbeln,     "SD DocumenT Number
               parvw type vbpa-parvw,      "Partner function
               kunnrb type vbpa-kunnr,     "Customer Number 1
               name1 type kna1-name1,      "Name 1
               ort01 type kna1-ort01,      "City
               adrnr1 type kna1-adrnr,     "Address
               name2 type kna1-name1,      "Name 1
               ort02 type kna1-ort01,      "City
               adrnr2 type kna1-adrnr,     "Address
               name3 type kna1-name1,      "Name 1
               ort03 type kna1-ort01,      "City
               adrnr3 type kna1-adrnr,     "Address
           end of t_final.
    *            D A T A  D E C L A R A T I O N
    *&*********Internal Table Declaration****************&*
    data: it_likp type standard table of t_likp.
    data: it_lips type standard table of t_lips.
    data: it_vbpa type standard table of t_vbpa.
    data: it_kna1 type standard table of t_kna1.
    data: it_li_vbpa type standard table of t_li_vbpa.
    data: it_li_vbpa_temp type standard table of t_li_vbpa.
    data: it_final type standard table of t_final.
    *&*********Work Area Declaration********************&*
    data: wa_likp type t_likp.
    data: wa_lips type t_lips.
    data: wa_vbpa type t_vbpa.
    data: wa_kna1 type t_kna1.
    data: wa_li_vbpa type t_li_vbpa.
    data: wa_li_vbpa_temp type t_li_vbpa.
    data: wa_final type t_final.
    *&*********Data Declaration************************&*
    data: d_vbeln type likp-vbeln.
    data: flag type i value 0.
    *           S E L E C T I O N  S C R E E N   D E C L A R A T I O N
    selection-screen begin of block block2 with frame title text-001.
    select-options: s_vbeln for d_vbeln obligatory.    "Delivery no
    selection-screen end of block block2.
    *            A T  S E L E C T I O N - S C R E E N   E V E N T S
    *AT SELECTION-SCREEN.
    *PERFORM VALIDATE_DATA.
    *            S T A R T   O F  S E L E C T I O N     E V E N T S
    start-of-selection.
    perform fetch_data.
    perform merge_data_kna1.
    *INCLUDE Z9BT_SH_***4_FORMS.
    call function 'OPEN_FORM'
    exporting
    *   APPLICATION                       = 'TX'
    *   ARCHIVE_INDEX                     =
    *   ARCHIVE_PARAMS                    =
        device                            = 'PRINTER'
    *   DIALOG                            = 'X'
    *   FORM                              = ' '
       language                          = sy-langu
    *   OPTIONS                           =
    *   MAIL_SENDER                       =
    *   MAIL_RECIPIENT                    =
    *   MAIL_APPL_OBJECT                  =
    *   RAW_DATA_INTERFACE                = '*'
    *   SPONUMIV                          =
    * IMPORTING
    *   LANGUAGE                          =
    *   NEW_ARCHIVE_PARAMS                =
    *   RESULT                            =
    exceptions
       canceled                          = 1
       device                            = 2
       form                              = 3
       options                           = 4
       unclosed                          = 5
       mail_options                      = 6
       archive_error                     = 7
       invalid_fax_number                = 8
       more_params_needed_in_batch       = 9
       spool_error                       = 10
       codepage                          = 11
       others                            = 12
    if sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    sort it_final by vbeln.
    loop at it_final into wa_final.
    call function 'START_FORM'
    exporting
    *   ARCHIVE_INDEX          =
       form                   = 'Z9BT_DELIVERY'
       language               = sy-langu
    *   STARTPAGE              = ' '
    *   PROGRAM                = ' '
    *   MAIL_APPL_OBJECT       =
    * IMPORTING
    *   LANGUAGE               =
    exceptions
       form                   = 1
       format                 = 2
       unended                = 3
       unopened               = 4
       unused                 = 5
       spool_error            = 6
       codepage               = 7
       others                 = 8
    if sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    call function 'WRITE_FORM'
    exporting
       element                        = 'ITEM_LIST'
       function                       = 'SET'
       type                           = 'BODY'
       window                         = 'MAIN'
    * IMPORTING
    *   PENDING_LINES                  =
    * EXCEPTIONS
    *   ELEMENT                        = 1
    *   FUNCTION                       = 2
    *   TYPE                           = 3
    *   UNOPENED                       = 4
    *   UNSTARTED                      = 5
    *   WINDOW                         = 6
    *   BAD_PAGEFORMAT_FOR_PRINT       = 7
    *   SPOOL_ERROR                    = 8
    *   CODEPAGE                       = 9
    *   OTHERS                         = 10
    if sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    call function 'END_FORM'
    * IMPORTING
    *   RESULT                         =
    exceptions
       unopened                       = 1
       bad_pageformat_for_print       = 2
       spool_error                    = 3
       codepage                       = 4
       others                         = 5
    if sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    endloop.
    call function 'CLOSE_FORM'
    * IMPORTING
    *   RESULT                         =
    *   RDI_RESULT                     =
    * TABLES
    *   OTFDATA                        =
    exceptions
       unopened                       = 1
       bad_pageformat_for_print       = 2
       send_error                     = 3
       spool_error                    = 4
       codepage                       = 5
       others                         = 6
    if sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    *&      Form  VALIDATE_DATA
    *       text
    *  -->  p1        text
    *  <--  p2        text
    form validate_data .
    select single vbeln into wa_likp-vbeln
                        from likp where vbeln in s_vbeln.
    append wa_likp to it_likp.
    if sy-subrc <> 0.
    flag = 1.
    endif.
    endform.                    " VALIDATE_DATA
    *&      Form  FETCH_DATA
    *       text
    *  -->  p1        text
    *  <--  p2        text
    form fetch_data .
    select a~vbeln
           a~erdat
           a~kunnr
           a~kunag
           a~traty
           b~vbeln
           b~posnr
           b~matnr
           b~arktx
           b~lfimg
           b~netpr
           b~vgbel
           c~vbeln
           c~parvw
           c~kunnr
             into table it_li_vbpa
                    from likp as a
                    left outer join lips as b on a~vbeln = b~vbeln
                    inner join vbpa as c on b~vgbel = c~vbeln
                    where a~vbeln in s_vbeln and
                    c~parvw = 'RE'.
    endform.                    " FETCH_DATA
    *&      Form  MERGE_DATA_KNA1
    *       text
    *  -->  p1        text
    *  <--  p2        text
    form merge_data_kna1 .
    if it_li_vbpa[] is not initial.
    it_li_vbpa_temp[] = it_li_vbpa[].
    sort it_li_vbpa_temp by kunnr.
    delete adjacent duplicates from it_li_vbpa_temp comparing kunnr.
    loop at it_li_vbpa into wa_li_vbpa.
    read table it_li_vbpa_temp into wa_li_vbpa_temp with key kunnr =
    wa_li_vbpa-kunag.
    if sy-subrc <> 0.
    wa_li_vbpa_temp = wa_li_vbpa.
    append wa_li_vbpa_temp to it_li_vbpa_temp.
    endif.
    read table it_li_vbpa_temp into wa_li_vbpa_temp with key kunnr =
    wa_li_vbpa-kunnrb.
    if sy-subrc <> 0.
    wa_li_vbpa_temp = wa_li_vbpa.
    append wa_li_vbpa_temp to it_li_vbpa_temp.
    endif.
    endloop.
    endif.
    if it_li_vbpa_temp[] is not initial.
    select  kunnr
            name1
            ort01
            adrnr into table it_kna1 from kna1
                        for all entries in it_li_vbpa_temp
                        where kunnr = it_li_vbpa_temp-kunnr.
    endif.
    loop at it_li_vbpa into wa_li_vbpa .
    wa_final-vbeln = wa_li_vbpa-vbeln.
    wa_final-erdat = wa_li_vbpa-erdat.
    *it_final-LFART = it_li_vbpa-LFART.
    wa_final-kunnr = wa_li_vbpa-kunnr.
    wa_final-kunag = wa_li_vbpa-kunag.
    *it_final-VSTEL = it_li_vbpa-VSTEL.
    wa_final-traty = wa_li_vbpa-traty.
    wa_final-vbeln1 = wa_li_vbpa-vbeln.
    wa_final-posnr = wa_li_vbpa-posnr.
    wa_final-matnr = wa_li_vbpa-matnr.
    wa_final-arktx = wa_li_vbpa-arktx.
    wa_final-lfimg = wa_li_vbpa-lfimg.
    wa_final-netpr = wa_li_vbpa-netpr.
    *wa_final-GEWEI = it_li_vbpa-GEWEI.
    *it_final-VOLUM = it_li_vbpa-VOLUM.
    *it_final-VOLEH = it_li_vbpa-VOLEH.
    wa_final-vgbel = wa_li_vbpa-vgbel.
    wa_final-vbeln3 = wa_li_vbpa-vbeln.
    *wa_final-PARVW = wa_li_vbpa-PARVW.
    wa_final-kunnrb = wa_li_vbpa-kunnrb.
    read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunnr.
    if sy-subrc = 0.
    wa_final-name1 = wa_kna1-name1.
    wa_final-ort01 = wa_kna1-ort01.
    wa_final-adrnr1 = wa_kna1-adrnr.
    endif.
    read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunag.
    if sy-subrc = 0.
    wa_final-name2 = wa_kna1-name1.
    wa_final-ort02 = wa_kna1-ort01.
    wa_final-adrnr2 = wa_kna1-adrnr.
    endif.
    read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunnrb.
    if sy-subrc = 0.
    wa_final-name3 = wa_kna1-name1.
    wa_final-ort03 = wa_kna1-ort01.
    wa_final-adrnr3 = wa_kna1-adrnr.
    endif.
    append wa_final to it_final.
    clear wa_final.
    endloop.
    endform.

  • Error during Cancelation Credit memo document in trasaction MR8M

    Hi experts,
    I have a problem in the transaction MR8M during cancelation credit memo document. The error message no. F5808 occured: The value for field "Part. Bank" in the interface to Financial Accounting is an initial value but you are required to make an entry in the field selection for G/L account "160000" in company code "XXXX" linked to the field selection for posting key "31".
    I checked the field status group for the G/L account 160000, but there is no mandatory field for "Part. Bank". In the posting key 31 is mandatory field "Part. Bank", but problem is, that for the posting key 21 - Credit memo should system use the Reversal posting key 32, which is adjusted in the transaction OB41. I don´t know why the system want to use posting key 31 by reversing credit memo intead of posting key 32, which is in customizing.
    Moreover, I tried to post simple document in FI module with posting key 21 and by reversing this document system used the correct posting key 32, where the field "Part. Bank" is suppress field.
    Do you have any ideas?
    Thanks a lot
    Miroslav

    we just had the same error message F5808 giving the same wrong posting key 31 for credit note cancellation instead of 32.
    We solved the issue like this:
    -access the follow-on document in accounting by FB02
    -complete the field which is said to be mandatory as per the error message
    The change in the FI document is of course not transferred back to the original LIV document but after having "completed" the follow-on document we were able to cancel the LIV document with MR8M without the error message we had before.
    I'll keep Pablos breakpoint (thanks!) in mind if this happens again with a field that cannot be accessed in FB02.
    Regards
    Mark

  • Create delivery document using bapi_deliveryprocessing_exec

    Can any one send me the sample code to create delivery document using BAPI_DELIVERYPROCESSING_EXEC BAPI.

    Hi,
    Use the fm:     'SHP_VL10_DELIVERY_CREATE_PARA' for creatting the delivery.
    The below code creates the delivery document:
    *& Report  ZSTATUS
    REPORT  zstatus.
    DATA: t_vbak LIKE vbak   OCCURS 0 WITH HEADER LINE.
    DATA: t_vbap LIKE vbapvb OCCURS 0 WITH HEADER LINE.
    DATA: t_vbep LIKE vbepvb OCCURS 0 WITH HEADER LINE.
    DATA: t_vbkd LIKE vbkdvb OCCURS 0 WITH HEADER LINE.
    DATA: t_vbpa LIKE vbpavb OCCURS 0 WITH HEADER LINE.
    DATA: t_vbuk LIKE vbukvb OCCURS 0 WITH HEADER LINE.
    DATA: t_vbup LIKE vbupvb OCCURS 0 WITH HEADER LINE.
    DATA: t_vbfa LIKE vbfavb OCCURS 0 WITH HEADER LINE.
    DATA: c_vbfa LIKE vbfavb OCCURS 0 WITH HEADER LINE.
    DATA: ls_sd_keys     TYPE sales_key.
    DATA : key      TYPE shp_sales_key_t,
           sd_order TYPE shp_vl10_sd_order.
    p_vbeln(sales doc no) = '5000006100'.
      AT END OF vbeln.
        REFRESH: t_vbak, t_vbap,
                 t_vbep, t_vbkd,
                 t_vbpa, t_vbuk,
                 t_vbup.
        CLEAR : t_vbak, t_vbap,
                t_vbep, t_vbkd,
                t_vbpa, t_vbuk,
                t_vbup.
        REFRESH: key.
        ls_sd_keys-vbeln = p_vbeln.
        APPEND ls_sd_keys TO key.
        CLEAR:ls_sd_keys.
        CLEAR: sd_order.
        CALL FUNCTION 'SHP_GET_SD_DATA'
          EXPORTING
            it_vbak_key = key
          CHANGING
            cx_sd_order = sd_order.
        APPEND LINES OF sd_order-vbak TO t_vbak.
        APPEND LINES OF sd_order-vbap TO t_vbap.
        APPEND LINES OF sd_order-vbep TO t_vbep.
        APPEND LINES OF sd_order-vbuk TO t_vbuk.
        APPEND LINES OF sd_order-vbup TO t_vbup.
        APPEND LINES OF sd_order-vbkd TO t_vbkd.
        APPEND LINES OF sd_order-vbpa TO t_vbpa.
        APPEND LINES OF sd_order-vbfa TO c_vbfa.
        LOOP AT c_vbfa WHERE vbtyp_n = 'J'.
          MOVE c_vbfa TO t_vbfa.
          APPEND t_vbfa.
          CLEAR t_vbfa.
        ENDLOOP.
        CLEAR: sd_order.
        CLEAR: key.
        CALL FUNCTION 'SHP_VL10_DELIVERY_CREATE_PARA'
          EXPORTING
            if_ledat              = sy-datum
            if_nur_vorgabe_pos    = ' '
          TABLES
            it_vbak               = t_vbak
            it_vbap               = t_vbap
            it_vbep               = t_vbep
            it_vbuk               = t_vbuk
            it_vbup               = t_vbup
            it_vbkd               = t_vbkd
            it_vbpa               = t_vbpa
           it_vbfa               = t_vbfa
          EXCEPTIONS
            system_failure        = 1
            communication_failure = 2
            RESOURCE_FAILURE      = 3
            OTHERS                = 4.
        IF sy-subrc = 0.
       WRITE:/ 'delivery completed'.
        ENDIF.
      ENDAT.
    If it is helpful rewards points.
    Regards
    Pratap.M

  • 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

  • Cancellation of Delivery Document

    Hi everyone,
    I would like to ask if there is a way to correct a posted Delivery document without having to re-create the reference Sales Order document. Here's the scenario: Upon creation of a Delivery document, the user has forgot to change the delivery quantity before posting it. (human error)
    Example:
    Sales Order Qty = 10
    Delivery Qty = 8 (Partial Delivery)
    The Delivery Document has been posted in B1 with 10 as the quantity. If we try to create a Return Document for the 2 quantity which was not served, we cannot anymore create a new Delivery Document for the remaining 2 because the reference Sales Order document is already closed. Is there a way we can serve the remaining 2 without having  to create a new Sales Order and just used the same Sales Order? Any suggestions will be appreaciated (either thru SDK or thru a workaround)
    Thanks in advance.
    Malu

    Hi Malu,
    There is no workaround either you make a return of 2 and again delivered 2 directly or return 10 and create a new sales order of 10 quantity a better option will be to return 10 and create new sales order.
    I hope SAP will come up with solution on this as these is a commen scenerio required.
    Thanks
    Kamlesh

  • Delivery Quantity change during creation of Delivery Document

    Hi Friends,
       I have a requirement of creating a Partial delivery when not much stock is available.
       For this I am using a BADI 'LE_SHP_DELIVERY_PROC' method Save_Document_Prepare.
       I am changing the contents of CT_XLIPS-lfimg in the method and also keeping UPDKZ as 'I', but still
       the quantity is not changing.
    Pls Suggest.
    Arpit

    Check, "Outline agreement message" in Document type details in VOV8- (eg: CQ- Quantity Contract) under Transaction flow view.
    Use Indicator:A- Check at Header level.
    Then system pop ups the message saying " Already Contract is open for this Customer" - ( Assume, SOld to party already have Open Contract)
    similarly, for Material, for this you should use  Indicator" B- Check at Item Level.
    Hope it helps

  • During cancelation of MIRO document giving error message "RG23 Part II post

    Dear guru's,
    I am facing a tipical issue while i am going to reverse the MIRO document it is giving error "RG23 Part II posting not yet done" .
    Senario is -- user has created MIGO  with Myp103  and then 105, system promted excise tab and excise ref.  and excise date is their .
    But no Part1 generated.
    So no part2 .
    Now A/c has passed the bill and fi doc generated.  Now we want revrse this bill (MIRO) and respectively MIGO (105/103 ) and again capture it with correct excise entry.
    we want to understand, How this happned at 105 why part1 not generated and with out part2 how bill passed.
    now waht can bo done to reverse this.
    thanks in advance.
    Ajeet

    Hello,
    Please check the status of excise invoices if they are "In process" stage. Unless the status is "Posted" you will not be allowed to do MIRO. Further, select only those line items which belong to excise invoice.
    Another possibillity of the error could be that the user must have changed the excise invoice date after it was referred in MIGO.
    If so, to avoid such issues and to stop the users from doing the above, please review the notes : 1285986, 1346926, 1406505.
    I hope this helps.
    Thanks and regards,
    Suresh.

  • Cancellation of multiorder delivery document.

    Hi Experts,
    I have generated one delivery document from ten sales orders by using the collective processing ( VL10A ).
    Now when I am going to cancel the delivery document from the T-code- 'VL09', system is not allowing me to do it.
    Can any one please suggest how can I cancell this delivery document.
    Thanks & regards,
    Rupam.
    Edited by: RUPAM KR SEN on Jul 29, 2010 1:42 PM

    Hi Rupam,
    I checked this scenario.
    After invoice creation, I cancelled the invoice in VF11, then did PGI reversal in VL09 and then deleted the delivery in VL02N.
    When I deleted the Delivery, it gave a warning saying that the invoice number exists, but it allowed me to delete the delivery.
    Consequently, the sales order now has the Open status.
    The invoice has the delivery document number in the document flow, however the delivery number is not available in the system.
    This will be the same case for you also if you try this scenario. I dont see any problem in this. If you are ok with this process, you can execute this for the problamatic sales orders.
    Hope this helps

  • Delivery document creation using vl01n

    Hi,
    I want to create a delivery document using VL01n.i need to create the doc for a particular selected item if there are many items for the order.i want to delete the remaining documents.
    how to handle this in BDC.

    just mention along with order ...
    from item
    as well as
    to item fields ....

  • We want to cancell Intercompany Billing document

    We want to cancel intercomapny billing documents, update the sales order and rebill
    Amit Mahajan
    Edited by: mahajan.amit.s on Oct 19, 2010 3:13 AM

    Hi,
    What is the problem here.
    I think you can cancel any invoice type in VF11 as long as it is enabled for cancellation with a cancellation document type in VOFA. For intercompany billing type it is IVS.
    You can cancel the IV document using IVS in VF11 and then rectify your problem in the sales order (only invoice related, not delivery related. If you are changing delivery related information, you have to cancel the delivery also including  PGI, Picking etc) and then create the invoice once again.

  • Delivery document archieved

    For a stock transfer invoice, dellivery document cancelled without cancelling the excise invoice. Is there any solution to prevent from cancelling the delivery document without cancelling the excise invoice

    Hi,
    I think you can still cancel the excise document.
    However, if you need a check here, you need to put the same through a user exit at Delivery change/delete level. Take help of an ABAPer for the same. 
    Regards,
    Peeyoosh.

  • Adding Item managed by serial no.s to Delivery Document

    Hello Experts,
    Can you please help me in the following?
    I'll appreciate your help.
    I want to add items managed by Serial Number to delivery document (using DI API).
    We have a set of internal serial numbers to be used for those items.
    For E.g, we have to add an item with code A0001, quantity of 2, with internal serial numbers to be used 00080,00090
    to the delivery document.
    (We allow the user to specify the internal serial numbers to be used).
    I'm not sure how to get the system serial number for this item.
    I believe OSRI has the Serial No/Internal serial no. for each item, w.r.t the marketing documents. (Is each item has its own set of system serial nos & internal serial no.s? From where we need to take it?)
    Can you please post if you have any sample code?
    (If possible, can you please explain me the relationship between OSRI and marketing documents, and oitem)
    Thanks a lot.
    Regards,
    Geetha
    Code that I'm using:
    Private Function UpdateSerialNumbers(ByRef objSerialNumbers As SAPbobsCOM.SerialNumbers, ByVal strShpReqNm As String, ByVal strShpReqRw As String) As Boolean
    'Get the values of Internal Serial numbers from our table, into this RS.
    If objRS.RecordCount > 0 Then
    objRS.MoveFirst()
    Dim i As Integer
    If objSerialNumbers.Count <= 0 Then SerialNumbers.Add()
    For i = 0 To objRS.RecordCount - 1
      Dim strTmp As String
      strTmp = objRS.Fields.Item(0).Value() & ""
      objSerialNumbers.SetCurrentLine(i)
      objSerialNumbers.InternalSerialNumber = strTmp 'e.g 00080
    'Need your help in this step
      objSerialNumbers.SystemSerialNumber =     objCommon.GetNextKeyValue("OSRI", "SysSerial")
      objRS.MoveNext()
      If Not objRS.EoF Then
        SerialNumbers.Add()
      End If
    Next
    End If
    End If
    return true
    End Function
    Function CallingFn() as boolean
    UpdateSerialNumbers(objDLDoc.Lines.SerialNumbers, objHeaderInfo.ShipReqNum, strTmp)
    objDLDoc.Add
    End Function

    Geetha,
    let me explain you shortly how the serial data is stored in the database
    OSRI - Serial Numer for Items
    SRI1 - Serial No. Trans. for Item
    OSRI and SRI1 are "connected" by SysSerial
    SRI1 is connected to the Document Tables Lines (INV1, DLN1, ...)
    with BaseType, BaseNum and BaseLinNum to the Document
    a Serial Number is Unique - 1 SerialNr = 1 Quantity (thats the difference to Batches)
    regards
    David

  • Delivery document is not updated " update was terminated"

    Hi all,
    I have a problem with creating delivery order using vl01n. When i'm creating delivery it is successfully saved and system giving delivery number also but problem is when i'm opend my delivery using vlo2 sytem not displaying my delivery. And one more thing while i saving the delivery document using vl01n after saving document i'm receiving message delivery is not updated; Express document " update was terminated" received from author DDIC. What is mean that i unable to solve this problem. Please solve my problem as eraly as possible.
    Thanks & regards
    kesav

    vi 110:delivery type FA
    For the above error message, if the system could not determine the partner function Sold To Party, system will throw this error. 
    So please check your partner function assignment.
    thanks
    G. Lakshmipathi

  • BAPI to change delivery document data

    Hi,
    I want to update the fields lifex, empst, in delivery document using any BAPI, can any one suggest me is there any standard BAPI to update this. Kindly suggest .
    Regards,
    Venkat

    Hi
    Try this BAPI 'BAPI_OUTB_DELIVERY_CHANGE' or 'BAPI_STOREORDER_CHANGE'
    Thanks
    Vasudha

Maybe you are looking for