Delivery a/c doc.

In delivery a/c document the business area has been determinedfrom the sale order, I want this to be stoped and use a particular business area to be determined in this a/c document. Can anyone tell me how this can be done?
TAP

You mean,
         Business area from SO, should not be determined in Delivery a/c'g & it should be some other business area.
Here can you confirm-
How you want the business area to be determined in Del a/c'g?
Are you expecting different Business areas in SO & Del a/c' doc?
As we all know the business area determination rules in SO.
1- Plant /Div
2- sales area
3- Sales Org + Dist Channel & Item Div.
You can check in Tcode:OMJ7 as well.

Similar Messages

  • How to get balance qty. of delivery in del. doc.

    Dear Friends,
    S.O's qty=100
    Delivery doc. added qty=50
    Now if i will open delivery doc.
    shall i get information like.
    ordered=100
    Delivered=50
    Balance to deliver=50
    Regards,
    MAhesh.

    Hi
    In S.O u will get two fields in Form settings like Delivered Qty and Open QTy( Yet to deliver), u can use this in ur so.
    In Delivery u will get two fields in FS like QTY to Ship , Ordered qty.
    Giri

  • PRINTING DELIVERY CHALLEN - MATERIAL DOC OF 541

    We have a requirement of printing Delivery challen which is Material document of 541 movement type.
    Now I have to link the Material document line item to P.O line item. for this I was referring MSEG table where I have P.O No but not the line item no. Without which I am not able to link P.O with material document.
    I am taking this linking  to display the receiving material (Subcontracted material) on Delivery challen.
    Can anybody tell me how to link this.
    Thanks
    Dhananjay

    For subcontracted material we issue input material to vendor through MB1B (Mov type-541)
    My client want take printout of this material document which should have the material issued to vendor and the receiving material against this issued material (Which is subcontracting material / Converted material).
    Now To fetch the subcontracting material / Converted material code having material document with me I use MSEG where I will get P.O no but line item no is not available which is required to link material doc with P.O.
    Is there any other way fetch the subcontracted material code based on MB1B material doc.
    Hope it is more clear.
    Thanks
    Dhanu

  • Print Delivery after PGI (Doc is Partially Processed ? )

    Hi All,
    We are trying to print the Delivery doc on completing PGI. The config has been set up with routine 1 and it's working correctly and creates a output line with appropriate output type.
    The issue is the output line in the output determination in VL02N is 'Partially Processed' (yellow indicator). We want to get it in 'Completely Processed' (Green) automatically as soon as we complete the PGI.
    For the output type we have used 'Dispatch time' = 4 (Send Immediately)
    Any suggestion is welcome.
    Thanks,
    Ashok

    Before i give you a solution, i want you to first run RSNAST00 program for the delivery in question. Check if after executing this program for the delivery, the yellow status turns to green.
    Note:- Object key should be prefixed with zeros - for instance 0080000123 and application = V2

  • Delivery doc is deleted in R/3, but not in BW

    I've a situation that a delivery was deleted in Logistics dep in R/3, nevertheless it is still in my BW. It was deleted like 2 months ago from R/3 and i use a standard 2LIS extraction. And the weird thing is
    In 2LIS_12_VCITM it was deleted because is not in the DSO that is filled from 2LIS_12_VCITM
    But the DSO that is filled by 2LIS_12_VCHDR still has this delivery!?
    Could you explain me plz how all the deleting concept works?
    What happens when a delivery or any doc is deleted in Logistics, how it gets eliminated in BW?

    It sounds really weird to me that SAP is incapable to register the deleted record!! In FI it's impossible to delete anything, but in MM the deleting of delivery documents is a standard procedure, so, i just don't believe that a standard extractor isn't capable to register the standard procedure of deleting a record!!??

  • Delivery document creation after Posting of Goods through Purchase Order

    Dear All,
    Could you please help me out by letting me know how to create a delivery document flow i.e. entry in VBFA table after Posting of Goods through PO, I have Inbound delivery document that I know & also a succssfull Material document that is created and can be viewed through Purchase order history BY USING ME23N transaction code.
    so please let me know is there any way to create a delivery by inputing delivery no., Material Doc & Material Doc year
    Thanks,
    Sanjay

    Additonally:
    At the time of GR the inbound delivery ican be updated in MIGO also if you set the suitable indicator in:
    SPRO > LE > Shipping > Basic Shipping Functions > Configure Global Shipping Data (V_TVSHP-SPE_INB_VL_MM)
    (see OSS note 1050944)
    Even though you implement this change or w/o this change post the GR in VL32N, you won't get the document flow in table VBFA.
    You can use table EKBE to get the necessary information.
    Regards,
    Csaba

  • Error while creating a delivery from a sales order

    Hi Folks,
    when i try to create delivery of a sales order, i am getting following error:
    " Item 000030: delivery split due to conflicting header data (FKARV: ZF2C <-> F8) "
    please help me in correcting this error.
    thanks in advance.

    Hi,
    The field FKARV is for Proposed billing type for a delivery-related billing doc.
    Now here in your case billing document if ZF2C and another is F8 so it is splitting, check this
    Kapil

  • Canceling a billing doc for which accounting doc not yet generated

    Hello,
    I have strange issue in canceling billing doc. What happened user created Intercompany billing doc IV against a delivery and accounting doc also released to FI. After that he found that value in that IV doc is not correct so he went and cancelled that doc IV and he created internal credit memo IG .But for this IG the accounting doc not generated due to FI period closing. Because the IV is created in the month of Oct and IG is created in the month of Nov'07.Due to this issue Accounting document not generated for this IG doc.
    But unfortunately by mistake he went cancelled the IG doc and it created IV again. Now what happened both IG and new IV created are showing in cancelled status. This is because if we cancel a billing doc for which accounting doc not created, then both doc will turning into cancelled status in doc flow. This is confirmed similar situation in my quality box and confirmed.
    Now can anybody come across this kind of issue and tell me what is the best approach to handle this kind of situation.
    Thanks
    Mathi

    Hi Nina
    As you are doing Delivery and then billing  with the service item category ZTAD , so go to VOV7 and check wheather the Billing Relevance ( Delivery related billing ) has been maintained or not .
    Also check wheather in VTLA & VTFL copy controls  ,  ZTAD item category has been maintained or not
    Regards
    Srinath

  • Delivery copy control Issue

    Dear All,
    I created a new order type, Item category, Delivery type and delivery item category. Maintain copy controls  too.
    But system is not allowing to do delivery.Error Message '
    Copying is not poss.because an entry is missing in Table TVCPL; ZTAN- LF.
    I searched in forum too no solution in most of the cases. Entry is reflecting in Table TVCPL.
    May you pls advise
    Regards,
    DP

    Hello,
    If you need your flow to be a Z*** order-> Z*** delivery, then it is correct not to maintain a copy control from Z*** order->LF delivery.
    What I can suggest is to:
    1. Remove your copy control from Z*** order->LF delivery.
    2. Review your entry in transaction VTLA ans make sure that  you have only now the copy control from Z*** order-> Z*** delivery.
    2.1. Make sure you have the item category/(ies) from the order in the configuration of the item level in transaction VTLA
    2.2. If you need a new item category in the delivery, you can make a new item category determination.  But in most cases, this is just copied from the sales order (see documentation in SPRO path for copying control for deliveries).
    Sample Entries in TVCPL
    Delivery Type//Sales Doc Type//Item Category
    ZEBB             //ZBR2                                          <-this is my copy control header level
    ZEBB             //ZBR2                //ZB70               <-this is my copy control item level; ZB70 is the item category as determined in the preceding Sales Order ZBR2
    3. Make sure you also have the proper copying requirements and data transfer routines depending on the business requirement.
    Good luck,
    Eva

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

  • Copying Exchange rate from sales Doc to billing doc

    Hello,
    I have an issue with the update of the exchange rate in the billing document.
    In fact when i create a sales order then the delivery associated. then i change the exchange rate in the sales order.
    When i go to create the billing doc, the exchange rate is not updated in the billing document.
    I guess because it is not defined in the copy rule requirement from Sales doc to delivery, and from delivery to billing doc? can you please confirm if it is the case?
    Thanks
    Regards

    Hi
    First of all check weather exchange rate has been maintained between the currencies from which you are changing (Ex : INR to EUR). If the currency conversion has been maintained then check in VTFL copy control weather PricingExchange rate type field has been maintained or not. If not maintained then maintain the PricingExchange rate type feild as per your requirement and then do the complete cycle again.
    Regards
    Srinath

  • From which tables i would find the delivery and billing document field..??

    I need to create an ALV report which displays the following details in the output.
    Order No  Item No     Material     Order Qty     Item Category     Plant     Delivery     Billing Document     Sales Org     Dist Channel     Division     Created By     Created On      Changed On
    For(Order No  Item No     Material     Order Qty     Item Category     Plant) i took the fields from vbap and
    for(Sales Org     Dist Channel     Division     Created By     Created On      Changed On)i took the fields from vbak..
    From which tables i would find the delivery and billing document field related to sales document.??
    need help...
    Moderator message : Requirements dumping not allowed, thread locked.
    Edited by: Vinod Kumar on Mar 6, 2012 2:53 PM

    i am new to abap...so i dont have idea about sd table relationship.
    so please reply how to add delivery and billing doc in my coding below..
    *& Report  ZINAA_SD
    REPORT  zinaa_sd.
    TABLES: vbap, vbak, vbfa.
    TYPE-POOLS: slis.
    CONSTANTS: c_x TYPE char1 VALUE 'X'.
    TYPES:
            BEGIN OF st_vbap,
             vbeln TYPE vbap-vbeln,
             posnr TYPE vbap-posnr,
             matnr TYPE vbap-matnr,
             pstyv TYPE vbap-pstyv,
             kwmeng TYPE vbap-kwmeng,
             werks TYPE vbap-werks,
            END OF st_vbap,
            BEGIN OF st_vbak,
              vbeln TYPE vbak-vbeln,
              erdat TYPE vbak-erdat,
              ernam TYPE vbak-ernam,
              vkorg TYPE vbak-vkorg,
              vtweg TYPE vbak-vtweg,
              spart TYPE vbak-spart,
              aedat TYPE vbak-aedat,
            END OF st_vbak, 
           BEGIN OF st_final,
             vbeln TYPE vbap-vbeln,
             posnr TYPE vbap-posnr,
             matnr TYPE vbap-matnr,
             pstyv TYPE vbap-pstyv,
             kwmeng TYPE vbap-kwmeng,
             werks TYPE vbap-werks,
             erdat TYPE vbak-erdat,
             ernam TYPE vbak-ernam,
             vkorg TYPE vbak-vkorg,
             vtweg TYPE vbak-vtweg,
             spart TYPE vbak-spart,
             aedat TYPE vbak-aedat,
           END OF st_final.
    DATA:
          lt_vbap TYPE TABLE OF st_vbap,
          ls_vbap TYPE st_vbap,
          lt_vbak TYPE TABLE OF st_vbak,
          ls_vbak TYPE st_vbak,
          lt_final TYPE TABLE OF st_final,
          ls_final TYPE st_final,
          lt_fieldcat TYPE slis_t_fieldcat_alv,
          ls_fieldcat TYPE slis_fieldcat_alv,
          layout TYPE slis_layout_alv,
          lt_sort TYPE slis_t_sortinfo_alv,
          ls_sort TYPE slis_sortinfo_alv.
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    SELECT-OPTIONS: s_vbeln FOR vbap-vbeln,
                    s_erdat FOR vbap-erdat.
    SELECTION-SCREEN END OF BLOCK b1.
    PERFORM select_data.
    PERFORM loop_final.
    PERFORM sort.
    PERFORM a USING:
          'VBELN' TEXT-002,
          'POSNR' TEXT-003,
          'MATNR' TEXT-004,
          'KWMENG' TEXT-005,
          'PSTYV' TEXT-006,
          'WERKS' TEXT-007,
          'VKORG' TEXT-008,
          'VTWEG' TEXT-009,
          'SPART' TEXT-010,
          'ERNAM' TEXT-011,
          'ERDAT' TEXT-012,
          'AEDAT' TEXT-013.
    PERFORM display.
    *&      Form  SELECT_DATA
          text
    FORM select_data.
      SELECT
       vbeln
       vkorg
       vtweg
       spart
       ernam
       erdat
       aedat
       INTO CORRESPONDING FIELDS OF TABLE lt_vbak
       FROM vbak
       WHERE vbeln IN s_vbeln AND erdat IN s_erdat.
      IF sy-subrc = 0.
        SORT lt_vbak by vbeln.
      ENDIF.
      SELECT
       vbeln
       posnr
       matnr
       kwmeng
       pstyv
       werks
       INTO CORRESPONDING FIELDS OF TABLE lt_vbap
       FROM vbap
       FOR ALL ENTRIES IN lt_vbak
       WHERE vbeln = lt_vbak-vbeln.
      IF sy-subrc = 0.
        SORT lt_vbap by vbeln.
      ENDIF.
    ENDFORM.                    "SELECT_DATA
    *&      Form  LOOP_FINAL
          text
    FORM loop_final.
      LOOP AT lt_vbap INTO ls_vbap.
        ls_final-vbeln = ls_vbap-vbeln.
        ls_final-posnr = ls_vbap-posnr.
        ls_final-matnr = ls_vbap-matnr.
        ls_final-kwmeng = ls_vbap-kwmeng.
        ls_final-pstyv = ls_vbap-pstyv.
        ls_final-werks = ls_vbap-werks.
        READ TABLE lt_vbak INTO ls_vbak WITH KEY vbeln = ls_vbap-vbeln BINARY SEARCH.
        ls_final-vkorg = ls_vbak-vkorg.
        ls_final-vtweg = ls_vbak-vtweg.
        ls_final-spart = ls_vbak-spart.
        ls_final-ernam = ls_vbak-ernam.
        ls_final-erdat = ls_vbak-erdat.
        ls_final-aedat = ls_vbak-aedat.
        APPEND ls_final TO lt_final.
        CLEAR ls_final.
      ENDLOOP.
      ENDFORM.                    "LOOP_FINAL
    *&      Form  SORT
          text
    FORM sort.
      ls_sort-spos = '01' .
      ls_sort-fieldname = 'VBELN'.
      ls_sort-tabname = 'LT_FINAL'.
      ls_sort-up = c_x.
      ls_sort-subtot = c_x.
      APPEND ls_sort TO lt_sort .
    ENDFORM.                    "SORT
    *&      Form  A
          text
         -->FNAME      text
         -->SELTEXT    text
         -->EMPHA      text
    FORM a USING fname TYPE string seltext TYPE string.
      IF fname = 'KWMENG'.
        ls_fieldcat-do_sum =  c_x.
      ENDIF.
      ls_fieldcat-fieldname = fname.
      ls_fieldcat-seltext_m = seltext.
      APPEND ls_fieldcat TO lt_fieldcat.
      CLEAR ls_fieldcat.
    ENDFORM.                    "A
    *&      Form  ALV
          text
    FORM display.
      layout-zebra = c_x.
      layout-colwidth_optimize = c_x.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
      I_INTERFACE_CHECK                 = ' '
      I_BYPASSING_BUFFER                = ' '
      I_BUFFER_ACTIVE                   = ' '
       i_callback_program                = sy-repid
      I_CALLBACK_PF_STATUS_SET          = ' '
      I_CALLBACK_USER_COMMAND           = ' '
      I_CALLBACK_TOP_OF_PAGE            = ' '
      I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
      I_CALLBACK_HTML_END_OF_LIST       = ' '
      I_STRUCTURE_NAME                  =
      I_BACKGROUND_ID                   = ' '
      I_GRID_TITLE                      =
      I_GRID_SETTINGS                   =
        is_layout                         = layout
        it_fieldcat                       = lt_fieldcat
      IT_EXCLUDING                      =
      IT_SPECIAL_GROUPS                 =
        it_sort                           = lt_sort
      IT_FILTER                         =
      IS_SEL_HIDE                       =
      I_DEFAULT                         = C_X
      I_SAVE                            = ' '
      IS_VARIANT                        =
      IT_EVENTS                         =
      IT_EVENT_EXIT                     =
      IS_PRINT                          =
      IS_REPREP_ID                      =
      I_SCREEN_START_COLUMN             = 0
      I_SCREEN_START_LINE               = 0
      I_SCREEN_END_COLUMN               = 0
      I_SCREEN_END_LINE                 = 0
      I_HTML_HEIGHT_TOP                 = 0
      I_HTML_HEIGHT_END                 = 0
      IT_ALV_GRAPHICS                   =
      IT_HYPERLINK                      =
      IT_ADD_FIELDCAT                   =
      IT_EXCEPT_QINFO                   =
      IR_SALV_FULLSCREEN_ADAPTER        =
    IMPORTING
      E_EXIT_CAUSED_BY_CALLER           =
      ES_EXIT_CAUSED_BY_USER            =
        TABLES
        t_outtab                          = lt_final
    EXCEPTIONS
      PROGRAM_ERROR                     = 1
      OTHERS                            = 2
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    "ALV

  • Return Delivery problem

    Dear Experts,
    When doing UD and posting the stock to return delivery through movement 122 system is displaying the following error message .
    *' 1 no return delivery ( reason )  Purshase doc no / Item no / 0002 '
    ' 1 No incorrect posting back to vendor ' and
    ' Enter stor.location ' *
    How to post the return delivery and UD?
    Thanks.

    Hello
    1) Please maintain the reason for return to vendor. This ca be done by clicking against Document  adjacent to Return delivery stock tab
    2) PLease check whether 122 is made available for QA11 in config. if not it wont allow the posting
    This can be checked in OMJJ> Movement type> allowed transactions
    Regards
    Gajesh

  • Splitting Delivery per line item in Sales order

    Hi All,
    We have a requirement of splitting the delivery per every line item on the sales order Is there a way to achieve this
    So eg. if we have 10 line items with X quantity each, it should create 10 deliveries.
    Suggestions awaited.

    Hi,
    You may have to change your copy control to work the way u want it to. In Tcode VTLA, for the say OR to LF you will have to write the condition at header (for copying the header data) and item level (to split the items into a new delivery) in such a way that, once the delivery is created for the first line item (I think the status of the table VBUP for the item number changes and that can be retrived), the new delivery gets created for the second and the same follows.
    BTW, what is the scenario you are dealin with. If you have this kind of a scenario, then, in real time, it becomes very difficult to really have a track of all the sales orders, deliveries and invoices. Also, from system point, the delivery tables will get filled up very fast and so as the VBFA table. So, acrchiving will have a problem. Returns is another thing you may have to look into.... So, as I have seen, normally, one sales order, one delivery, one billing doc is created always so that it is easy to track and archiving becomes very easy.
    Hope this helps
    Regards,
    Mukund S

  • Temporary text on billing document and delivery

    Dear all,
    I have the following question:
    Is it possible to add a temporary text on the billing doc and delivery doc? For example:
    'Closed between Christmas & New year'
    thanks,
    Ton

    hi,
    goto VOTXN t.code and configure a text as Christmas. at the delivery and invoice level enter the required greetings against this text id and you will get the same printed on your delivery and invoice doc's. Take the help of your abaper to capture that text into the required output types.
    regards

Maybe you are looking for