Delivery Document GI date

Beng a newbie I had a few questions on delivery document. When is/should a delivery document be created in the life of a sales order? Is this delivery GI date considered a committed date or still a planned? Will the GI date also show on schedule line if it is different than what system had planned since sometimes I see duplicate lines in schedule lines?

hi
Once a sales order is creaed, if the material is available it will give MAD (material availability date)
now considering the packing, picking and loading time , planned GI date is calculated. When the delivery is created, it will be checking Planeed GI date is in te horizon we have maintianed in VL04 variant.
Once delivery created it will have planned gi date and delivery date. Now when PGI happens actual GI date is updated. This is considered as base date for billing.
DUplicate schedule lines means one is non confirmed one and other is confirmed one. The confirmed will be always using forward scheduling where as the first one which is unconfirmed will be backward sceduling.
Reward if helpful
Kind regards
Sandeep
Edited by: Sandeep Markandeya on Mar 17, 2008 11:22 PM

Similar Messages

  • Delivery document data transfer to non sap server.

    Hi,
    My requirement is ,when i created delivery label (vl01), this delivery document should be  sent to FTP server instead of printer in flat file format.
    Normally for delivery document printing we use VL71 t.code,but in my requirement i  have to create new program and configure this program in NACU tcode for particular output type.
    How we approach this scenario, please help me.(for data down load to flat file and transfer to server).
    Thanks in advance.

    Hi,
    I think you are mixing different concepts. UD connect , DB connect and Web services are methods to upload data from non-SAP source systems to BW. Ud connect is to loada data from SQL tables , DB connect from oracle table.
    If you want to transfer data to other systems Open hub is the easiest way. You can put the data in a flat table throught the open hub. You can fill the table with delta method.
    Open hub allows to load data from, infocubes, dso, or infoobjects.
    I hope it helps.

  • Delivery Date in Inbound delivery document not correct

    Dear all,
    I have a question with regards to the wrong delivery date appear in our inbound delivery.
    Our inbound delivery is created via EDI output in the outbound delivery of a standard SAP cross company stock transport order. The delivery date in the inbound delivery is not correct from a business point of view.
    +The correct delivery date in the inbound delivery document should be [the Actual GI date field in the outbound delivery] + [transport time (i.e. route field) in the outbound delivery].+
    Either way (i.e. the Actual GI date field is later/earlier than the planned GI in the outbound delivery), the delivery date in the inbound delivery is also wrong.
    Do you have any idea?  We have tried to change the inbound delivery type EL by setting a flag (i.e. X) in the rescheduling (TVLK-NEUTE), and it still doesnu2019t work.
    Please help.
    Thanks.
    Tuff

    Does anyone know this problem?
    appreciate some feedback.

  • Any one knows how to change "TransptnPlanng date" in delivery document?

    Deal All,
    Could any one provide the BAPI/FM that can change "TransptnPlanng" date/time in inbound/outbound delivery documents?
    I need to update the dates only in ABAP program based on external information.
    I tried WS_DELIVERY_UPDATE with the following parameters setup:
    VBKOK_WA-VBELN_VL = target delivery number
    VBKOK_WA-TDDAT = "12/12/2009"
    VBKOK_WA-TDUHR = "12:12:12"
    (for the other fields in structure VBKOK_WA, I leave them blank)
    DELIVERY = target delivery number
    After run the FM in test mode, no error returns but no data updated in the delivery... (dates not change)
    Do I need to specify all the other fields for the delivery (like delivery date, line item details etc) even though I just want to update two fields in the header of the delivery?
    Thanks & Regards,
    Wenling

    BAPI_OUTB_DELIVERY_CHANGE works in this case (just to change the date)
    Need to put "X" on the date field on structure BAPIOBDLVHDRCTRLCHG and need to use table BAPIDLVDEADLN with correct date type to update.
    Thank you all for your replies.

  • Pricing date in delivery document and billing document

    Hi All,
    Pricing date in billing document can be controlled by copy control between order and billing document. This config is done in the field Pricing source. If i its set as "order", then my pricing date in billing doc will be same as that of order document pricing date. Tell me if i am right???
    Where can i maintain the setting for determining the pricing date in delivery document.???

    Hi Tushar
    Where do you find Pricing date in Delivery and Billing ?
    Pricing date is in Sales order, system takes rate of the pricing conditions valid on this date, from their condition record.
    Are you talking of Pricing in Billing document, whether it will be copied from sales order, or delivery document etc , Right?
    It is controlled from the "Pricing source" field (D- delivery, Blank- order,E - delivery/order etc.) in the copy control table at item level (VTFL).
    Suppose, the value is E, that means Pricing data will be copied from order aswell as delivery(if any).
    The copied will be copied as it is or Tax will be redermined or Freight will be redetermined etc will be decided from the "Pricing type "field.

  • Delivery Document creation using buffered data?

    We're using BAPIs to create an STO with estimated volumes/dates.
    But, when the Actual information comes in, we first update the STO with actual volume, then create a delivery document. The problem is that the delivery document is using the estimated volume even though we've committed the volume change and can pull up the STO to see it prior to Delivery create.
    For STO, we're using:
    BAPI_PO_CREATE1 and
    BAPI_PO_CHANGE
    For Delivery creation, we're using:
    BAPI_OUTB_DELIVERY_CREATE_STO
    It seems that the Delivery is reading buffered information rather than what's actually been committed to the DB. Is there a way to bypass the buffer when calling this BAPI?
    thanks,
    Robert

    Found a note that has addressed the issue
    2008537 - Short dump while changing a replenishment delivery multiple times in one transaction

  • Print Layout Designer:Due date in Delivery document

    In print layout designer in 2005 version for Delivery document when they preview the document in document printing it compute an automatic due date but if the preview was done in the delivery document itself the due date is the same as posting date.
    And as to delivery document in SAP no due date will be computed because due date will be determine upon invoice. But upon checking on their database, the same layout/template was used in the preview of the document in the delivery itself and in the document printing. The due date used in the layout was delivery due date.
    They want to apply the scenario of having automatic computation of due date in Delivery document in the print layout designer in their 2007 version. All details created in the Print layout designer in 2005 version are defined already in their 2007 version but when the document was preview in document printing no computation of due date.
    Is the layout used in the preview of delivery document itself was different when i used the document printing and select the same document and preview it? Is it possible to compute the due date in delivery document?
    Can someone help me?

    Hi Paul,
    Yes, we already informed our customer that in delivery document no due date will be computed. But my question is it is possible that the print layout used in the preview of delivery document itself was different when the preview is done in the document printing window? To preview the document in document printing, select or highlight one transactions and click preview.
    When we check the customer database and preview the delivery document itself the due date is
    the same as posting date but when i preview the document in the document printing when you check the
    field due date it was not the same as posting date.
    We check the layout and the field is Database Delivery: Due date. The layout name was also the same when we preview
    the transactions in delivery document itself and in the document printing.
    Can someone tell me if the layout was different in the document printing window under Sales A/R module?
    Thanks,
    Janice

  • Settings in Actual Goods Issue Date for Delivery Document

    Hi Masters,
    We have a Requirement in Which the client wants that while Creating Delivery Document through VL01N the Actual PGI Date Entered should not be before the Panned GI Date it should be only After the Planned GI Date. If the user Tries to Enter the Actual GI Date which is before the Planned GI Date the System should not Accept it and should give and Error.Please tell how to Configure this.
    Thanks in Advance.

    Hi,
    Pls make use of Status profile for the user as well as maintain proper schedule lines
    regards
    DSR

  • How to find closing date for a delivery document

    I nedd to fin closing date for a delivery document. I tried with clsdate but didnt work
    If someone can help me with this

    Hi.............
                 Better and simplest way you can get it through a simple qury report. Create a query by joining two tables ODLN and OINV. OINV's docdate means the closing date of delivery challan.
    Regards,

  • Credit data refresh on delivery document

    Hi
    I've noticed that the credit data (Risk category / Customer credit group etc) on an SD delivery document is copied over from a sales order.
    Is it possible to have the credit data refreshed from the credit master when a delivery document is created?
    This is required in cases when the risk category is changed after an order is created and before a delivery document is created.
    Sequence:
    VA01: Order is created (VBAK-CTLPC = 01 for example)
    FD32: Risk category is changed (from 01 to 02 for example)
    VL01n: Delivery is created (As per current settings, CTLPC on the delivery is 01, it is required that we get 02 instead)
    Kindly suggest any solutions
    Thanks,
    VH

    Dear Vicky,
    I doubt that if it can be achieved through configuration, although with the help of an ABAPer you can write a requirement in copy control to compare the existing Risk Category and if found different overwrite with the one recently maintained.
    Hope solves your problem
    Regards,
    Paresh

  • 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

  • Finding delivery documents between specific data

    Hi,
        I want to find all the GI/ Material documents and their corresponding delivery documents for a particulat period. Can you please let me know how to do it. Shall I  have to use goods movement type 601 in MSEG or its not required?
    Thanks and regards,
    Vamsi

    Hi Vamsi,
    As you rightly said you can use the table MSEG to get the material document numbers. Copy these numbers and use table VBFA. Here put these Nos. in field VBELN along with VBTYP_N as "R" and VBTYP_V as "J". You will get all the delivery nos for the material document nos.
    Hope this meets your requirement.
    REWARD if it helps you!!
    Regards,
    Ajinkya

  • Open Sales order, Delivery docuement, Billing document, Item

    Hi Gurus,
    Kindly help to view the following items for a particular customer.
    1) Open sales order value
    2) Open Delivery docuement value
    3) Open Billing document value
    4) Open item.
    I presume for viewing open sales order VA05N and to view Open item FBL5N would suffice. Please correct me if i am wrong and let me know about points 2 and 3.
    This is required because, my client is facing some figure mismatch while executing F.35 tcode. I am trying to analyze the differnce of figures while doing a Static and dynamic credit check.
    Thanking you in advance
    ficoguy.

    Dear ficoguy,
    1) Open sales order value
    Tcode: VA05 (select OPEN SALES ORDERS)
    optional method: SE11/ TABLE VBAK/ INPUT customer code as KUNNR, fetch the list.
    Input the VBELN in VBUK and filter with RFSTK='A'
    2) Open Delivery document value
    Tcode: VF04 (OUTPUT DATA FOR BATCH PROCESSING-->CHECK LIST DISPLAY)
    DOCUMENT TO BE SELECTED = DELIVERY RELATED
    optional method:(same as above except the FIRST TABLE)
    SE11/ TABLE LIKP/ INPUT customer code as KUNNR, fetch the list.
    Input the VBELN in VBUK and filter with RFSTK='A'
    3) Open Billing document value
    TCode: VF05
    Selection criteria : OPEN BILLING DOCUMENTS
    4) Open item.
    Tcode : FBL5N
    Check and revert back.
    Thanks & Regards,
    Hegal K Charles

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

  • Delivery document not getting updated

    Dear Experts,
    Till date our client was using VL04 for creating DA for only domestic sales, now they
    are asking to provide facility to created DA for export shipment in VL04 and we have done customization for the same.
    Now there are two separate (delivery document number)  number ranges generated for
    domestic and export sales.
    Now my problem is :  delivery document number generated for export sales is not getting
    updated in database table VTRDI 
    Have any idea ??
    Please advice
    R.Karthik
    Edited by: Karthik R on Sep 30, 2009 5:31 PM
    Edited by: Karthik R on Sep 30, 2009 6:39 PM

    Hi Lakshmipathi  ,
    Thank you so much.....for ur valuable advice !!
    I have checked the table LIKP and LIPS ...and the export delivery number is getting saved
    in these two tables...
    But my problem is with creating shipment in VT01...as delivery number generated for export is not
    getting picked in VT01 but for normal domestic orders it is getting picked.
    I could not figure out where I went wrong??
    could you please guide me on this issue.
    R.Karthik
    Edited by: Karthik R on Oct 5, 2009 8:46 AM

Maybe you are looking for