Summarized accounting document

hi all
i have a query. i created a sales order with 10 line items. i created the delivery and billing. when i saw the accounting entery it is creating 10 line items for each product. tax is comming for total 10 items in only one line item. my requirement is i want only one entry for all the 10 line items. how to do it? where will be the control?
regards
rag

Hi Rag,
I am actually facing the same situation... I've 900 line items in a Single Billing Document... I am unable to find the path mentioned by Mr. Dave to set Summarized Accounting Document. Can you pls send me the TCode for it or can you guide me the path again. I am using SAP ECC 6.0
Thanks

Similar Messages

  • Enhancement - Accounting Document from Billing Document - change line items

    Hi Experts,
           Our client has a requirement to display all line items(as shown in Billing document) along with the tax line in the Accounting document. I can explain it as below:
          In VF01 transaction code: enter the delivery number.
          Press enter to see the number of line items that will be populated in the Billing document.
          Click on save.
          Here in the Accounting Doc you'll find only 2 line items, one line item is the consolidation of WRBTR and quatity of all the line items in the Billing Document and the other line item is the tax.
          We are required to replace the consolidated line item in the Account Doc with all the actual lines as populated in the Billing Document.
          For this we tried various methods:
                 Searched for a BAPI - couldnt find any which will help in modifying the line items before creation of Account Doc
                 Checked UserExits - Found one SDVFX008 but it didnt have the table which is sent for population of Accounting doc hence there was no way we could modify any table to get the desired output.
                 Searched the VF01 Flow in Debugger to check when the Accounting Doc is updated, but it also didnt yield any fruits.
          Kindly please guide on a way this can be accomplished. Appreciate the help from you all...

    Hi
    I think that your requirement is related with summarization of items in the FI doc for the billing document. Please, see SAP Note 36353 - AC interface: Summarizing FI documents. See also Note 301077 - User exits for the interface to accounting.
    I hope this helps you
    Regards
    Eduardo

  • Merge revenue acc lines in invoice accounting document

    Dears,
      i have ZPR0 as basic price and ZD01 (%) as customer discount in my pricing procedure. i have entered a sales order with following info:
    Qty=1
    ZPR0=1000
    ZDI01=10%
    when i create invoice following accounting doc is created:
    account          amount
    customer          900
    Reven.              -1000
    Disc                 100
    i need to merge Reven. and Disc. accounts.
    so i assigned sames account key (ERL) to both ZPR0 and ZD01, following accounting is created:
    account          amount
    customer          900
    Reven.              -1000
    Reven               100
    but i need accounting to be created as following:
    account          amount
    customer          900
    Reven.              -900
    is there any solution?

    Hi
    You can do it with summarizing FI documents. Please see SAP Note 36353 - AC interface: Summarizing FI documents.
    I hope this helps you
    Regards
    Eduardo

  • Example program - posting accounting document,  Idoc ( ACC_DOCUMENT )

    Hi fellows developers,
    here is an example of  usage of the IDOC, directly in program for an accounting document
    (ALE message type ACC_DOCUMENT, bapi BAPI_ACC_DOCUMENT_POST )).
    It was inspired  by the lack of a flexible usage of this IDOC in LSMW
    (f.e. booking of Gl and Vendor from the same file).
    Both cases inbound and outbound are covered, although the outbound idoc was delivered in state
    for furthere dispatching and was further not tested.
    You can adapt this example to any idoc type (bapi type) and load data from anywhere ( file, table, etc.).
    If you have question please ask.
    On my system works !!!:)))
    I hope it will help you in your daily work.
    Regards,
    Miroslaw
    *& Report  Z_MKPR87
    *& Version 1.0 - creates idoc for accounting document with status
    *&  64 - inbound and 30 - outbound.
    *& Then you need to execute program RBDAPP01 for this message type (inbound),
    *& for outbound further dispatching with appropriate tool is required (not tested here).
    *& For inbound, complete booking of document was tested. For outbound
    *& only to the stage 30 - 'Idoc ready for dispatch'.
    *& Program does not require any additional DDIC objects.
    *& The solution gives you possibility for example to book document G/L + Vendor items,
    *& strictly speaking the whole power of this bapi in IDOC can be used. Unfortunately
    *& in LSMW its not the case.:)
    *& Data for idoc is takken from internal table, but can be loaded from anywhere.
    REPORT  Z_MKPR87.
    INCLUDE Z_MKPPR87_TOP.
    INCLUDE Z_MKPPR87_SEL.
    INCLUDE Z_MKPPR87_EVN.
    INCLUDE Z_MKPPR87_IDOC.
    *&  Include           Z_MKPPR87_TOP
    CONSTANTS:
    input structure for idoc ***
    Achtung! don't use BAPI input structures
    they are similar but not flat ( the casting cannot occure, since idoc
    needs flat data - see 'sdata' field in edidd )
    gc_idoc_structure1(27) TYPE c VALUE 'E1BPACHE09',
    gc_idoc_structure2(27) TYPE c VALUE 'E1BPACGL09',
    gc_idoc_structure3(27) TYPE c VALUE 'E1BPACCR09'.
    Structrures for IDOC : ALE message type - ACC_DOCUMENT
                         BAPI - BAPI_ACC_DOCUMENT_POST
    NOTE!  The E1BPXXXXXX structures are flat (char type), opposite to
    BAPI structures (BAPIACHE09. etc. )
    DATA:      gs_DOCUMENTHEADER  TYPE E1BPACHE09,
                    gt_ACCOUNTGL  TYPE TABLE OF E1BPACGL09,
               gt_CURRENCYAMOUNT  TYPE TABLE OF E1BPACCR09,
                gt_idoc_str_names TYPE TABLE OF char15,
                     gs_edidc     LIKE edidc,
               gt_idoc_data TYPE  TABLE OF       edidd,
               gt_comm_idoc_control TYPE TABLE OF edidc.
    *&  Include           Z_MKPPR87_SEL
    SELECTION-SCREEN BEGIN OF BLOCK bk2 WITH FRAME TITLE text-002.
    PARAMETERS:
              p_itype TYPE char15 DEFAULT 'ACC_DOCUMENT03',
    *'CREMAS04',
              p_mtype TYPE EDIDC-mestyp  DEFAULT 'ACC_DOCUMENT',
              p_rport TYPE EDIDC-rcvpor DEFAULT 'LSMW',
              p_rtype TYPE EDIDC-rcvprt DEFAULT 'US',
              p_rname TYPE EDIDC-rcvprn  DEFAULT 'Z_MKARAS',
              p_inbd    TYPE c DEFAULT 'X'.  " C - inbound (2), space - outbound (1)
    SELECTION-SCREEN END OF BLOCK bk2.
    *&  Include           Z_MKPPR87_EVN
    INITIALIZATION.
    PERFORM initialize_idoc_const.
    START-OF-SELECTION.
    PERFORM create_idoc.
    *&  Include           Z_MKPPR87_IDOC
    *&      Form  create_idoc
          text
    FORM create_idoc.
      PERFORM set_bussines_data
                  USING
                     gs_documentheader
                     gt_accountgl
                     gt_currencyamount.
      PERFORM build_idoc_from_bus_dat
                  USING
                     gs_documentheader
                     gt_accountgl
                     gt_currencyamount
                  CHANGING
                     gt_idoc_data.
    CASE p_inbd.
    WHEN 'X'.
       PERFORM create_inbound_idoc.
    WHEN space.
       PERFORM create_outbound_idoc.
    ENDCASE.
    ENDFORM.                    "create_idoc
    *&      Form  create_inbound_idoc
          text
    FORM create_inbound_idoc.
      PERFORM set_idoc_control_inbound CHANGING gs_edidc.
      CALL FUNCTION 'IDOC_WRITE_AND_START_INBOUND'
        EXPORTING
          i_edidc = gs_edidc
        TABLES
          i_edidd = gt_idoc_data.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ELSE.
       MESSAGE 'Inbound idoc(s) created, check in TAC WE02' TYPE 'I'.
      ENDIF.
    ENDFORM.                    "create_inbound_idoc
    *&      Form  create_outbound_idoc
          text
    FORM create_outbound_idoc.
      PERFORM set_idoc_control_outbound   CHANGING   gs_edidc.
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
        EXPORTING
          master_idoc_control        = gs_edidc
        TABLES
          communication_idoc_control = gt_comm_idoc_control
          master_idoc_data           = gt_idoc_data.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ELSE.
       MESSAGE 'Outbound idoc(s) created, check in TAC WE02' TYPE 'I'.
      ENDIF.
    ENDFORM.                    "create_outbound_idoc
    *&      Form  set_idoc_control_inbound
          text
         -->CT_EDIDC   text
    FORM set_idoc_control_inbound CHANGING cs_edidc LIKE gs_edidc.
      DATA: ls_edidc TYPE  edidc.
      cs_edidc-direct = '2'.
      cs_edidc-idoctp = p_itype.
      cs_edidc-mestyp = p_mtype.
      cs_edidc-rcvpor = 'SAPECI'.
      cs_edidc-rcvprt = p_rtype.
      cs_edidc-rcvprn = p_rname.
      cs_edidc-sndpor = p_rport.
      cs_edidc-sndprt = p_rtype.
      cs_edidc-sndprn = p_rname.
      cs_edidc-credat = sy-datum.
      cs_edidc-cretim = sy-uzeit.
    ENDFORM.                    "set_idoc_control
    *&      Form  set_idoc_control_outbound
          text
         -->CS_EDIDC   text
    FORM set_idoc_control_outbound CHANGING cs_edidc LIKE gs_edidc.
      DATA: ls_edidc TYPE  edidc.
      cs_edidc-direct = '1'.
      cs_edidc-idoctp = p_itype.
      cs_edidc-mestyp = p_mtype.
      cs_edidc-rcvpor = p_rport.
      cs_edidc-rcvprt = p_rtype.
      cs_edidc-rcvprn = p_rname.
      cs_edidc-sndpor = 'SAPECI'.
      cs_edidc-sndprt = p_rtype.
      cs_edidc-sndprn = p_rname.
      cs_edidc-credat = sy-datum.
      cs_edidc-cretim = sy-uzeit.
    ENDFORM.                    "set_idoc_control_outbound
    *&      Form  set_bussines_data
          text
         -->CS_DOCUMENTHEADER  text
         -->CT_ACCOUNTGL       text
         -->CT_CURRENCYAMOUNT  text
    FORM set_bussines_data USING cs_documentheader LIKE gs_documentheader
                                 ct_accountgl      LIKE gt_accountgl
                                 ct_currencyamount LIKE gt_currencyamount.
                            CHANGING ct_idoc_data LIKE edidd.
      DATA:
             ls_documentheader TYPE e1bpache09,
             ls_accountgl      LIKE LINE OF  gt_accountgl,
             ls_currencyamount LIKE LINE OF gt_currencyamount.
    HEADER **
      cs_documentheader-bus_act =  'RFBU'.
      cs_documentheader-username = 'RNOWAK'.
      cs_documentheader-comp_code = '1000'.
      cs_documentheader-doc_date = '20071205'.
      cs_documentheader-pstng_date = '20071205'.
      cs_documentheader-fisc_year =  '2007'.
      cs_documentheader-fis_period = '12'.
      cs_documentheader-doc_type = 'JE'.
    POSITIONS ***
    111111111 ****
      ls_accountgl-itemno_acc = '0000000001'.
      ls_accountgl-gl_account = '0000473110'.
      ls_accountgl-item_text = 'MIK test dokumentu GL z programu IUE'.
      ls_accountgl-comp_code = '1000'.
      ls_accountgl-tax_code = '0I'.
      ls_accountgl-costcenter = '0000001000'.
      ls_currencyamount-itemno_acc = '0000000001'.
      ls_currencyamount-currency = 'PLN'.
      ls_currencyamount-amt_doccur = '496'.
      APPEND ls_accountgl TO ct_accountgl.
      APPEND ls_currencyamount TO ct_currencyamount.
    2222222222 ****
      ls_accountgl-itemno_acc = '0000000002'.
      ls_accountgl-gl_account = '0000113302'.
      ls_accountgl-item_text = 'MIK test dokumentu GL z programu IUE'.
      ls_accountgl-comp_code = '1000'.
      ls_accountgl-tax_code = ''.
      ls_accountgl-costcenter = ''.
      ls_currencyamount-itemno_acc = '0000000002'.
      ls_currencyamount-currency = 'PLN'.
      ls_currencyamount-amt_doccur = '-496'.
      APPEND ls_accountgl TO ct_accountgl.
      APPEND ls_currencyamount TO ct_currencyamount.
    ENDFORM.                    "set_bussines_data
    *&      Form  build_idoc_from_bus_dat
          text
         -->IS_DOCUMENTHEADER  text
         -->IT_ACCOUNTGL       text
         -->IT_CURRENCYAMOUNT  text
         -->CT_IDOC_DATA       text
    FORM build_idoc_from_bus_dat USING is_documentheader LIKE gs_documentheader
                                            it_accountgl LIKE gt_accountgl
                                       it_currencyamount LIKE gt_currencyamount
                                   CHANGING ct_idoc_data LIKE gt_idoc_data.
      DATA:
      ls_documentheader LIKE is_documentheader,
      ls_accountgl     LIKE LINE OF it_accountgl ,
      ls_currencyamount LIKE LINE OF  it_currencyamount,
      ls_idoc_data LIKE LINE OF ct_idoc_data.
    Document header *****
      ls_documentheader = is_documentheader.
      ls_idoc_data-segnam = gc_idoc_structure1.
      ls_idoc_data-sdata = ls_documentheader.
      APPEND ls_idoc_data TO ct_idoc_data.
    Positions G/L part ************
      LOOP AT it_accountgl INTO ls_accountgl.
        ls_idoc_data-segnam = gc_idoc_structure2.
        ls_idoc_data-sdata = ls_accountgl.
        APPEND ls_idoc_data TO ct_idoc_data.
      ENDLOOP.
    Currency Items part ******
      LOOP AT  it_currencyamount INTO  ls_currencyamount.
        ls_idoc_data-segnam = gc_idoc_structure3.
        ls_idoc_data-sdata = ls_currencyamount.
        APPEND ls_idoc_data TO ct_idoc_data.
      ENDLOOP.
    ENDFORM.                    "build_idoc_from_bus_dat
    *&      Form  initialize_idoc_const
          text
    FORM initialize_idoc_const.
      APPEND gc_idoc_structure1 TO gt_idoc_str_names.
      APPEND gc_idoc_structure2 TO gt_idoc_str_names.
      APPEND gc_idoc_structure3 TO gt_idoc_str_names.
    ENDFORM.                    "initialize_idoc_const

    I summarized postings and posted again into the same system.  Yes, you can save an IDOC in your own system...There's an IDOC FM that will do just that...  In my case, I did:
    after receipt of IDOC and posting,
    process the idoc tables, rebuilding the input into tables.
    Summarize the tables, as needed.
    Create a new IDOC with a specific function code.
    Save the IDOC in my own system, using IDOC_INBOUND_ASYNCHRONOUS, as I recall.
    I had a custom process code that fired off the standard FM to process the JE posting.  I don't remember all the variables, but I have this stored as my example:
    DATA : p_sndprn TYPE edi_sndpn3.
    * Control Record Build.
      CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
        IMPORTING
          own_logical_system = p_sndprn
        EXCEPTIONS
          OTHERS             = 0.
      iedidc-direct   =  '2'.
      iedidc-idoctyp  =  'FIDCCP02'.
      iedidc-mestyp   =  'FIDCC2'.
      iedidc-mesfct   =  'ACC'.  <customer made up....used to control which process codes fire off when for standard message.
      iedidc-sndprt   =  'LS'.
      iedidc-sndprn   =   p_sndprn.
      iedidc-rcvprn   =   wa-rcvprn.
      iedidc-rcvprt   =  'LS'.
      iedidc-sndpor   =  'SAP_EDI_SC'.
      iedidc-credat   =  sy-datum.
      iedidc-cretim   =  sy-uzeit.
      APPEND iedidc.
    * IDOC store routine...must commit work
    * to get IDOC transferred to the IDOC processor.
      CALL FUNCTION 'IDOC_INBOUND_ASYNCHRONOUS'
        TABLES
          idoc_control_rec_40 = iedidc
          idoc_data_rec_40    = iedidd.
    ENDFORM.                    " send_idoc
    Edited by: DaveL on Oct 25, 2011 8:15 PM

  • Routine / User exit in SD to create an Accounting Document

    Hi Everybody,
    Anybody please tell me the Routine / User exit in SD to create Accounting Document from an SD billing document.
    Also need the user exit that will split the accounting document into as many documents as required.
    The problem I am facing is like the splitter program fails to copy the document header text into all the accounting documents produced as a result of the splitter program. Appreciate your help.
    Thanks,
    Neethu.

    Hi Neethu,
    Sorry, I don't understand very well your requirements.
    Do you have problems with splitting in billing? If yes, see SAP Note 11162 - Invoice split criteria in billing document and search posts with the string ZUKRI.
    To change data in the interface to FI from billing, see Note 301077 - User exits for the interface to accounting, but I think that you cannot create new FI documents with these enhancements.
    Other question, see SAP Note 36353 - AC interface: Summarizing FI documents, perhaps your problem can be solved with the advices of this note.
    I hope this helps you
    Regards
    Eduardo

  • Summarizing FI documents

    Dear All,
    Summarizing FI documents, can you deactivate it if you want to stop using the functionality?
    Regards,
    Caroline

    Hi:
          Please check the FI Document summarization for related area in ,IMG>Financial Accounting>General Ledger Accounting>Periodic Processing>Integration for relevant area e.g SD,MM and you can deactivate it there too.
    Regards

  • For BSID- Accounting Document Number corresponding PO Number is required

    Hi Gurus,
                 I have got a requirement to develop a report similiar to 'FBL5N' . I am getting the details of open and cleared items of a customer from BSID and BSAD tables respectively. My requirement is also to fetch the corresponding PO number of the LINE items displayed in the report.
                Can any one suggest how can I fetch PO number with Accounting document number(BSID-BELNR)  or (BSAD-BELNR).
               Your efforts in this matter are deeply appreciated and <<removed_by_moderator>>.
    Thanking You,
    ZIa.
    Edited by: Vijay Babu Dudla on Jan 28, 2009 11:07 PM

    If you have fields BSID-VBEL2 and BSID-VPOS2 are populated with the sales order, than access VBKD with the Sales Order to get the Customer PO (VBKD-BSTKD)
    Or
    First, You need to get the Billing document. Access BKPF with the BSID-BELNR to get the AWKEY where AWTYP = 'VBRK'
    Now, you can go to SD document flow with the billing document to find out the Sales Document. Access VBKD with the Sales document to get the Customer PO
    Regards,
    Naimesh Patel

  • Error while creating a billing (no accounting document gnerated)

    hi gurus,
    while saving a billing document in vf01 error pops up no accounting document generated and when i go to account determination analysis in billing  tax condition is missing
    kindly help me out
    thanks

    hi
    then goto VF02 and from the menu Environment--Account determination analysis-revenue acccounts
    find here whether any assignment is missing
    check u r VKOA settings whether the g/l ACCOUNT HAS  assigned or not for that tax condition type
    regards

  • Generate accounting document for cancel of credit memo

    Hii Guy,
    Need your help to solve this problem.
    My user have perform VK11 to cancel of credit memo. in the sales order document flow, the status is OPEN.
    my user cannot perform creating of accounting document for this cance of credit memo. what are the tcode to generate accounting document ?

    Nizamkz wrote:Hi,
    >
    > Hii Guy,
    >
    > Need your help to solve this problem.
    >
    > My user have perform VK11 to cancel of credit memo. in the sales order document flow, the status is OPEN.
    Are you sure its VK11???? I guess for the cancellation if billing document its VF11......
    Try to do the manual release to accounitng....by going to VF02 and pressing the Green Flag button after entering the cancellation document number. Or Else Try to reverse the posting with FB08.
    Thanks,
    Raja

  • Changing the field content of 'wrbtr' in accounting document during Post Goods Issue in VL02N

    Hi Experts,
         I have requirement ,where I need to  change the 'amount in document currency value (wrbtr)' in line item of a accounting document, which is created as part Post Goods issue through VL02N.
              I have already check BADI's below as follows:-.
    1) LE_SHP_GOODSMOVEMENT- No accounting document information flows in this BADI.
    2) AC_DOCUMENT - Field 'WRBTR' is not available in substitutable fields list.
    3) BTE-1050 - This BTE is not getting triggered while doing PGI.
            Please suggest any other possibilities to make the change.
    Thanks & Regards,
    Suganth.

    Hi Kartik,
                I have checked the enhancement you specified, but it didn't trigger during PGI. Can u please let me know is there any other possibilities to make the change.
    Thanks
    Suganth.

  • Enhancement for MB1C/MB1A before creation of an Accounting Document

    Hello everyone,
    Actually I want to get the material document number(MBLNR) before the creation of an accounting document when using the transaction MB1C or MB1A.
    I will have to use the value 'MBLNR' to update a field during the creation of an accounting document(the field SGTXT should be updated with the MBLNR).
    I have already tested the following BADI's which provide me the value of the material document number:
    - MB_DOCUMENT_BADI  (BAdIs During Creation of a Material Document)
    - MB_DOCUMENT_BADI_SAP (BADI for Creation and Changing of a Material Document)
    and I am using the BaDi 'AC_DOCUMENT' to update the required field with the material document number(MBLNR).
    The problem is that the BADI's 'MB_DOCUMENT_BADI ' and 'MB_DOCUMENT_BADI SAP' are call after the creation of the accouting document(after the BADI 'ACDOCUMENT') meaning that I can't used these BADI's as the value MBLNR is not available before.
    My idea was to export the value to memory ID before the creation of accounting document and import the value in memory ID in the BADI's 'AC_DOCUMENT' to update the field SGTXT.
    I am currently looking for other enhancements or BADI's which can help me to solve this issue.
    After much research on the internet, I did not succeed in finding a suitable hint which can help me.
    I would be grateful if someone could guide me(even a small hint will help me a lot as am I am new in the world of BADI's) on how to find a suitable way to get the document number(MBLNR) before the creation of an accounting document(before calling the BADI 'AC_DOCUMENT').
    Thanks a lot in advance for you help.
    Kind Regards,
    Bryan

    Hi
    I had a look through the program and found an enhancement spot ES_SAPMM07M available through out. Sadly i am not able to create a material document in my system some master data issue but there are various enhancement points in this enahcmenet and you need to debug on save and find the right enhancement point to export the value.
    Put a break point in the following includes which have only one subroutine in them
    MM07MFF9_F_SEGMENTE_BEWERTEN
    MM07MFF9_F_SEGMENTE_ERSTELLEN---> In this accounting item are created. If stops here and in debugger change the value if it works then there are various enhancement spot for the same.
    MM07MFF9_F_SEGMENTE_ERZEUGEN
    MM07MFF9_F_SEGMENTE_GENERIEREN
    Hope it helps
    Nabheet
    Edited by: nabheetmadan09 on Feb 1, 2012 3:49 PM

  • Unable to cancel Billing due to cleared accounting document for Free Goods

    Hi,
    I have a case as described below:
    I.                    SALES ORDER CREATION
    Transaction VA01 à Sales order is created for the following details:
    1.       Material Normal  (TAN) : 100 CAR
    2.       Free Goods (TANN) : 10 CAR
    II.                  Subsequent processing of sales order 
    a.       Delivery(1) and Billing (1) creation for the SO with the following details :
    Material Normal (TAN) : 100 CAR
    Free Goods (TANN) : 5 CAR
    Status of accounting document after releasing billing document to Accounting: Not cleared
                    Accounting Journal:
                    A/R                                                                     xxxx
                    Sales discount                                                     xxxx
                                    General Domestic Sales                                        xxxx
                                    VAT u2013 Out(TAX)                                                    xxxx
    b.      Delivery (2) and Billing (2) is then being made for the leftover item of the Sales Order:
    Free Goods (TANN) = 5 CAR  
    Status of Accounting document after releasing billing document to Accounting: CLEARED
    Accounting Journal
    Dr. Sales Discount                                        xxxx
                            Cr. General Domestic Sales                  xxxx
    III.                Reversal of Billing (2) needs to be done
    Activities conducted:
    a.       Go to VF11 and enter Billing (2) document number
    b.      Execute!
    System response:
    Error Log:
    1)      Data inconsistency during processing of document xxxxxxx
    2)      The Billing Document xxxxxxx  is already cleared
    From the error found, we tried to reverse the cleared accounting document by using t-code FBRA:  
    System response:
    Document xxxxxx IS NOT  a clearing document
    Question:
    We have to reverse the clearing document first in order to cancel the related billing document but we keep finding this error, do Anyone have any advice to solve this issue?
    We have simulated similar transaction in IDES and no problem is found, is there any specific setting in customizing that can allow cancellation of billing document regardless of its accounting document status (Cleared or Not Cleared) ?
    Thanks in Advance,
    Indro

    Thanks a lot for the reply,
    It answers my question, I found the copying requirement using routine 029 was defined in the cancellation document section of the Billing type to be cancelled
    After removing, the billing document can be cancelled
    Thanks,
    Indro

  • Report to display accounting documents

    What is the report to display accounting documents
    Moderator: Please, avoid asking basic questions

    S_ALR_87012287 - Document Journal
    S_ALR_87012289 - Compact Document Journal

  • RSEG Accounting document no

    Hi
    I  want to get the purchase order wise payment  (check no),I have already get the miro document no in rseg,pls tell me how to get the miro accounting document no

    try to make use of this FM
    AC_DOCUMENT_RECORD.
    or
      call function 'FI_DOCUMENT_RECORD'
        exporting
          i_awtyp            =  'RMRP'
          i_awref            =  w_awref1 --->IR numner of PO
          i_aworg            =  w_gjahr1----.year
        I_AWSYS            = ' '
        I_AWTYP_INCL       = ' '
        I_AWTYP_EXCL       = ' '
        I_BUKRS            = ' '
        tables
          t_documents        = t_doc.
    <b>MIRO numner is Nothing but IR numner ? just pass this along with year .</b>
    Regards
    Prabhu
    Message was edited by: Prabhu Peram

  • Accounting Document not posted for Cancelled Invoice -error in FI interface

    Hi,
    When I create a billing document then an accounting document gets created automatically in the background and then when I cancel the billing document no accounting document gets generated and the field Posting Status in header Detail of Billing document updated as "Errors in Financials Interface.
    I tried to release it for Posting via VFX3 but failed due to below error message in Log:
    "Incorrect doc.no.: 4900000005. Select document number between 3000000000 and 3099999999"
    I have checked the Number range assignments to the Invoice type and Accounting type.
    The number range is same for both Invoice type (Y0F2) and Cancelled Invoice type (Y0S1).
    The Accounting document type (RV) is also same for both the cases. But it is working fine for Y0F2 (Acounting document generated and cleared automatically). But not working fine for Cancelled Invoice (Y0S1).
    Can anybody please help me find out a solution to the issue.
    Thanks, Ram.

    Hi,
    The error message F5151 refers to the number range of the FI document.
    Please have a look at the note 1259505: FAQ: New cancellation procedure in SD, which covers this issue in detail.
    Question 5:
    Q5. What is the FI document type, generated by the cancellation ?
    In the old cancellation procedure, the FI document type is always
    determined in SD, and passed to FI (the same when a normal invoice  -
    not a cancellation -  is transferred to accounting).
    In transaction VOFA there is the field 'Document type' (TVFK-BLART).
    If this field is filled, then the FI document will have the document
    type maintained here.
    If TVFK-BLART is empty, then the FI document will get the default
    document type 'RV'.
    If the new cancellation procedure is performed, the FI document type is
    always determined in FI, based on the document type of the FI document
    to be reversed.
    In transaction OBA7 the FI document type has assigned the field 'Reverse
    document type' (T003-STBLA).
    If it is filled, then the FI cancellation document will get the document
    type maintained here.
    If T003-STBLA is empty, then the FI document cancellation will get the
    same document type as the cancelled FI document.
    Notice that an unexpected FI document type can cause the error message
    F5 151.
    Example:
    F2 invoice 90000001 was released, creating an accounting document with
    document type 'RV'.
    This F2 invoice is reversed by the S1 billing document 70000001.
    In customizing of SD there is:
    Billing Type    Document Type
    F2              RV
    S1
    In customizing of FI there is:
    Document Type    Number range   Reverse Document Type
    RV               00             AB
    AB               01             AB
    The FI number ranges (object RF_BELEG) are:
    No  From number    To number   Ext
    00  0090000000     0099999999  X
    01  0100000000     0199999999
    Different situations can occur, due to these customizing settings of the
    FI document type, caused by the type of cancellation.
    If the new cancellation is used:
    The FI document type 'RV' has 'Reverse Document Type' = 'AB'.
    Document type 'AB' has number range '01' set as internal.
    So the FI document will have its own number included in
    100000000-199999999.
    There is no issue.
    If the old cancellation is used:
    The cancellation billing type S1 has no 'Document type' maintained, so
    the FI document will get document type 'RV'. It has number range '00',
    set as external number range.
    So the FI document should get the same number of S1 billing document.
    But the S1 billing document has number 70000001, not included in the
    interval of number range '01'.
    This will cause error F5 151.
    I hope this information helps you.

Maybe you are looking for

  • Impact of SAP ECC 6.0 in BI 7.0

    Hi all, can any one know what type of impact of SAP ECC 6.0 on BI 7.0. if ECC 6.0 as source system for BI? kindly provide more info on it thanks

  • Service order creation from sale order

    Hi Friends,    Could you please tell me where is the setting for the automatic creation of service order from sale order.     Iam using LEIS , TAD and CD as the sales documents and SM01 as service order document.     Am I missing something?     Pleas

  • Opening  an image problem - with PSE11

    Help...have been in chat room with various Adobe Tech guys...have tried all their suggestions and none have worked. CANNOT click on an image(any file type)  in My Pictures and have it open directly ..WIN32 application error appears. Must go File/Open

  • How to check MAxl is running properly or not

    Hi All, i am working on ASO cube which has to implement Automation for dimension building and data loading. I am unable to execute even a single sample systax with out error. Is there any specific method to use Maxl in ASO cube or any precautions to

  • What is the latest software for 9800 ?

    may i know, what is the latest os for 9800? can i get 7.1 for it ?