Billing Document is not released to Account -Error

Hi,
I am getting the below error while releasing the billing document into accounting.kindly help me
Error Log
             0900000165 000000 Document 0900000165 saved (no accounting document generated
             0900000165 000000 Enter a true account assignment object with revenues
            Long txt
                Detail
                 Diagnosis
                     You made an account assignment for 420100, a revenue
                     element, in controlling area 9000 to a cost center or
                     profit center.
                 System response
                     Cost centers and profit centers can carry revenues in the
                     R/3 System as statistics only. To ensure reconciliation
                     between FI and CO for revenue element 420100, a CO account
                     assignment object must record the revenues as a real value.
                     This object type is used for updating to the reconciliation
                     ledger.
                     In principle, it's possible for the R/3 System to
                     automatically derive this CO account assignment object, the
                     reconciliation object. However, all postings made in CO for
                     costing-based Profitability Analysis are logged in the
                     reconciliation ledger under "reconciliation object". In
                     this manner, the reconcilation ledger identifies the exact
                     values flowing into the operating profit. If you post
                     reconciliation objects during revenue postings to cost
                     centers or profit centers, you must do so while keeping the
                     interpretation of the reconciliation ledger reports in
                     mind. The sums of revenue postings to profitability
                     segments, cost centers, and profit centers cannot be broken
                     down further.
Procedure
    o   To avoid posting to reconciliation objects, make
        account assignments to a real CO account assignment
        object.
    o   If you want to post to reconciliation objects, you can
        change this message to a caution or a note for future
        users, or deactivate the message entirely. Use the
        Implementation Guide under "Controlling: General" and
        choose Change message control. Enter area KI and
        message number 166. If you do not enter an individual
        user here, the change is valid for all users.
Technical data
    Tech. data details
     Client
     Group Number
     Sales Document Number                  0900000165
     Item Number of the SD Document         000000
     Schedule Line Number                   0166
     Counter in Control Tables              00
     Message Identification                 KI
     System Message Number                  166
     Output Type                            E
     Message Variable 01                    420100
     Message Variable 02                    9000
     Message Variable 03
     Message Variable 04
Please help me
Thanks
Supriya

Hi Supriya,
The following step is missing in your configuration: So please check the following step:
Financial Accounting (New) - Financial Accounting Basic Settings (New) - Ledgers - Real-Time Integration of Controlling with Financial Accounting - Account Determination for Real-Time Integration - Define Account Determination for Real-Time Integration
The above step is used for:
You define account determination for the real-time integration of Controlling (CO) with Financial Accounting (FI).
You have two options for the definition of account determination:
Account determination without substitution (standard account determination)
The level of differentiation with which you want to trace the postings to Financial Accounting determines how many accounts you create and whether you assign transactions or object classes. You can assign the accounts as follows:
You specify an account for all reconciliation postings.
You assign an account to each business transaction.
You assign an account to each object class.
You assign an account to each transaction and to each object class.
Account determination with substitution
In addition to account determination without substitution, you can determine the reconciliation account using substitution. For this, you have to define account determination at least for the specification of the posting key. Furthermore, you can use substitution to refine account determination.
In contrast to when the reconciliation ledger is used, additional fields are available when real-time integration is used:
RCL_ICCF-BEKNZ
RCL_ICCF-RSEGMENT
RCL_ICCF-SSEGMENT
These fields are only filled by the system when real-time integration is used.
Caution
If you deploy the following functions, you may not use the additional fields in account determination:
You still use reconciliation posting instead of real-time integration.
You use real-time integration but you still have the reconciliation ledger activated so that you can use the reconciliation reports from Cost Element Accounting, such as CO/FI Reconciliation in Company Code Currency.
These functions use the reconciliation ledger data, which does not contain the additional fields.
For more information about defining account determination, see Define Adjustment Accounts for Reconciliation Posting.
Please let me know if you need more clarification
Thanks & Regards,
Venkataraju Khottari

Similar Messages

  • Output to be blocked for Billing documents, if not released to Accounting

    Hi SAP Gurus,
    We have a requirement, where the Billing documents should not be issued output, if they are not released to accounting.
    The system should not allow the user to issue output for billing documents, if not released to accounting.
    Regards,
    sree.

    Standard routine 62 should be able to suffice your requirement.
    Provided output determination in billing doc should happen from output condition record (VV31).
    If you manaully assign assign output type in billing doc, then system will overlook the requirement.
    In addition to that if your output type is assigned with requiremrnt routine 62 in your output procedure.
    Then till your release tke billing doc to accounting, you will not be able see output type determine in billing doc.
    If you have doubt, whether the output type is getting determined properly or not.
    Then output(header/item) screen in your billing doc(VF02), in menubar select Goto - then choose  Determin. Analysis.
    It will show message that due requirement 62, output determination didn't too place.
    Regards
    JP

  • Reg: Billing document not released to Accounting -Error

    Hi Gurus,
    I am facing a problem in Billing.I am creating a billing document and while saving the document it shows up the error " Credit Control area 1200 not assigned to Company Code 1000".
    I have checked the enterprise structure and everything regarding Credit Control Area exists in the system.
    I am able to create the billing document and release to accounting for the same company code for different payers.
    But this error occurs unique to a particular Customer's Billing Document alone.
    Please do provide me a solution to this error.
    Regards,
    Sarosh

    Hi Ravi
    Check in the enterprise structure wheather you have assigned correct credit control area to the (sales orgn+ dist channel + division) to your sales area . or not
    Secondly check in VD02 wheather you have assigned any wrong credit control area or not
    Regards
    Srinath

  • Why Documents are not releasing to Accounting Automatically?any reason?

    Hi,
    Is there is any reason that these documents are not automatically being passed to accounting.Please help me to fix this issue.
    Thanks
    Supriya

    Hello,
    This is not just FICO consultant issue.
    If you do not have sufficient configuration in VKOA, it cannot be generated.
    If you have closed the period in FI, obviously the entries will not be posted.
    If the user is not having authorization, obvisouly it fails to generate accounting documents.
    There is no special configuration, but this is system behaviour. If something is not available, then it cannot generate the entry.
    Hope you have gone through the points mentioned by me.
    Regards,
    Ravi

  • Billing documents should not be created when it is not released to accounti

    Hi SD gurus,
    In some situation, billing documents are generated but it is not released to accounting which results in mismatch between FI value and SD value. We go to VFX3 and see the list of billing documents and take corrective action.
    Our requirement is that the billing document should not be generated when system is not releasing this billing document to accounting.
    Please suggest a solution for this.
    Regards,
    Senthil.

    Thanks giri.
    For the following reasons, the billing documents are not released to accounting.
    1. If the user wrongly chosen the billing type for the delivery.
    2. After creating condition type, it has to be assigned in COPA. If we forgot to do it, billing doc will not released.
    Our requirement is that if the billing document is not able create accounting document, the billing document itself should not be generated.
    Hope this will be suffice to understand my issue and suggest a suitable solution.
    Points will be rewarded.
    Regards,
    Kumar.

  • Billing Document Not releasing to Accounting because of Condition Type

    Hi,
    We have used Sales Condition Type ZSCM(Which is a statistical condition type) in Billing Documents and they are already released to Accounting.Today we have created one more Billing Document with same Condition type ZSCM.But this billing document is not getting released to Accounting?
    What could be the reason? Why it was released to Accounting before with the same condition type ZSCM and why it is not getting released to Accounting this time.
    I am breaking my head to find the possible reasons...kindly help me out to find the problem.
    1.Billing document 90005889 - has value 64.48462- and It has only 2 Items and it was released to accounting
    2.Billing document 90005729 - has value 217.87960- and It has only 21 Items and it was not released to accounting and asking to activate +/- sing in KE4I transaction for the ZSCM condition type.
    Why billing document 90005889 is  released for accounting and why 90005729 was not released to accounting?
    Thanks
    Supriya

    Hi,
    There can be following possible reasons fo the samed :
    1. If the specific GL account is not getting any assignment to CO object.
    2. Also you need to check assignment with VKOA that whichever GL is assigned as per business process of Sales (the account which is going to be credited) and all relevant settings in VKOA.
    3. Pls check all substitutions and validations if any connected with that condition type and GL. Becuase sometimes it may happen that because of calling some other application (for ex. Set or substitution as generally transportation of this element happen with entire hierarchy if you add your substition in the node.) at he time of posting of billing document. This has already happen with our business scenario.
    4. Also check if this sales revenue GL is assinged to any set and if that set is called through any substitution ot validation.
    Pls check all these possibilities and revert.
    Thanks & Regards,
    Taral Patel

  • Billing Document not released to Accounting -Issue

    Hi,
    While releasing the billing document,it is not releasing to accounting and giving the below error log.
    Thanks
    Supriya

    Diagnosis
        When condition "ZSCM" (application "V") was transferred to the value field "VV139" in operating concern "AFCO" in Profitability Analysis, the following became apparent:
    u2022     The condition can take both positive and negative   values
    u2022     The flag "Transfer values with +/- signs" has not be set in Customizing for value field assignment.
        Inconsistencies in the data could occur as a consequence.
    System Response
        It is not possible to post the document in Profitability Analysis.
    Procedure
        Set the flag "Transfer values with +/- signs" for the condition "ZSCM".
        You should set the flag "Transfer values with +/- signs"  selectively for individual conditions if:
    1.  The conditions can take both negative and positive values (for example, in the case of conditions that describe a transfer price surcharge or a loss deduction).
    2.  The conditions appear several times in a billing document and thus cause a debit posting as well as a
        credit posting (this is the case, for example, when creating or cancelling reserves).
    By activating the flag "Transfer values with +/- signs", you balance the positive and negative values in a
    condition. You can thereby guarantee that the sum of the negative and positive condition values is displayed as the correct total value in the value field assigned to the condition.
    Caution when in the production system!
        If you have already used condition "ZSCM" to post data in the production system, then the sign in
        Profitability Analysis may differ from the previous sign as a result of the flag "Transfer values with +/-
        signs" having been activated. See the F1 Help documentation on the field "Transfer values with +/-
        signs" or the OSS note 52849. If deviating signs occur, it makes sense to move condition "ZSCM" to a new value field! Contact your system adviser or SAP.
        The +/- signs are handled as follows for the flag "Transfer values with +/- signs":
        Billing document (normal) "trans.with signs"  "trans.w/o signs"
         Debit posting                   negative     positive       (such as sales deductions)
         Credit posting                  positive      positive       (such as revenues)
        Credit memos/returns    "trans.with signs"  "trans.w/o signs"
         Debit posting                   negative     negative       (such as revenues)
         Credit posting                  positive       negative       (such as sales deductions)
        Maintain Condition Assignment to Value Fields u2013 SD Condition
        Maintain Condition Assignment to Value Fields u2013 MM condition
    Procedure for System Administration
    Thanks
    Supriya

  • Billing doc not released to accounting

    Hi !
    What can be the reasons that a billing document is not automatically released to accounting?
    I know one reason - that is when there is a posting block assigned to the billing document type .
    Plz correct me if I am wrong with the above reason,and plz provide if there can be other reasons as well.
    Thanks.
    Edited by: Shamik Sengupta on Feb 25, 2008 4:43 PM

    Go to FS00 (Edit G/L Account) and assign a cost element to it in Edit Cost Element tab. Based on the name given to this G/L account you could correctly determine which category under which you could create it as a cost element.
    Go to VF02, try clicking on the green flag and the system would throw an error.
    Anaylze the error and try out transactions OKB9, VKOA to find out whether you have correctly maintained your entries.
    Try running transaction FS00 and see whether the G/L accnt used for determination is valid in that particulat Company Code.
    Sometimes the error could also be because the G/L accnt might required to be created as a cost element.
    Let me know what is the error that you are getting. We can then propose a solution.
    Reward if helpful
    Regards
    Ravi

  • Excise Invoice creation error -Billing document does not exists

    Dear Experts,
    I have created supplementary sales order, billing with refernece through sales order by VF01.
    Now I want to create Excise Invoice but system gives error Billing Document does not exists
    I have checked billing document in VBRK table & it is showing in table.
    My item categroy is L2N -and set it to C
    I have assigned Billing type under Outgoing excise invoice ->Assign billing type to delivery type still my excise invoice is not generating.
    Pl. guide me.
    Thanks
    Trupti

    Resolved my problem.
    Actually in Billing item categroy if you put SD Doc. Catg. as M you can do excise invoice even if you have not created the
    outbound delivery.
    So cycle will be Supplementary Sales Order->VF01 with ref. to SO->J1IIN -Excise invoice creation.
    Thanks to all.
    Trupti.

  • Invoice Document not released to Accounting -Period was closed

    Hi,
    SD Invoices are not released to Accounting.Those documents are from previous period and also also those periods were already closed.
    Now what should i do? if i want to release the invoice documents which are created in previous periods.Kindly advice me.
    Thanks
    Supriya

    Hi Supriya,
    Please open previous period for posting. Please follow the given below path:-
    SPRO  Financial Accounting  Financial Accounting Global Settings  Document  Posting Periods  Open and Closed Posting Periods
    Here you need to enter Posting Period Variant name assigned to company code and other detail like account number.
    To know the Posting Period Variant follow this path:-
    SPRO  Financial Accounting  Financial Accounting Global Settings  Document  Posting Periods  Assign Variants to Company Code
    Or else you can take help of some FI guy.
    Regards,
    Anand

  • Insufficient Authorization old Invoices Will Not Release to Accounting

    I have some old invoices that will not release to accounting.  Instead of trying to secure a new credit card from the customer how can I remove the credit card information/or trick the order into thinking it doesn't need it so that I can get the open billing documents to the customers open account?
    Please any help will be appreciated.
    Again the error message is insufficient authorization, need to get these documents released to accounting.

    That is true...if it has been partially utilized in another Billing doc, then it wont let delete the lines...
    So when this hapenned to me, this is what i did....and maybe this is not the best practice.
    I first got a Manual authorization in the sales order. Now generally we get the auth. from a 3rd party application Delego. So when we did the manual auth, we just entered a fake Auth number. This way, we tricked the system to let us post the Invoice to accounts. But definitely it posted to the card receivable account insted of the customer account. Now the settlement of this item would fail because the Auth number is not valid but the settlement fails only after it does the additional G/l posting to post to the Clearing account. To clear off this clearing account posting, we created a credit memo for the same amount and again with a fake Auth so now when this credit is processed for settlement, it also fails but reverses the provious debit...so that all accounts are now all balanced out.
    So now remains the customer....so we finally did a Debit memo equal to the original invocie amout and now this posts to the customers account.
    I was unable to find any other solution and was skeptical of doing any enhancement or changes just for a single case. Pls also let me know if you come across any better ideas.

  • Billing document are not flowing into FI and COPA

    Hello SAP CO gurus,
    please help me out by giving possible reasons why Billing document are not flowing into FI and COPA.
    what are the settings need to check?
    is there any option to get release by manual?
    Initiatives rewards with points........
    Regards
    Chandra.

    Hello Chandra,
    Check whether any standard cost estimate is existing for that material for which your billing. If it is there then check whether costing key from COPA is able to access the cost estimate.
    I am also working on the same issue but not solved yet.
    regards
    Nivas

  • Billing Document fails on Transfer to Accounting

    Hi Gurus.
    I have created a Sales Order for a BP with Direct Billing.
    The Billling Document created is failing to Transfer, when I review the Billing Document I see it has an error on Middeware Connection Status: "C": "Error Constructing Tax Data for mBDoc"
    I do not specialize in Tax configuration. How do I correct this so that my Bdoc can get created.
    Many Thanks in advance
    Panduranga

    Hi
    Please can you tell us how did you resolve the error , we have around 50+docs stuck with same error
    Could you please share the answer with detailed screenshots
    regards
    devendra

  • 1728283 - Document is not released

    Hi Experts,
    Is there new sapnote in replacement of 1728283? I cannot view the details since error "Document is not released" will promt.
    I want to read this doc since I need to upgrade my kernel from 7.01 to 7.21 EXT.
    Regards,
    Chonalyn

    Dear Chona,
    Please use this link to view this note:
    Installation of kernel 721 (EXT)
    Thanks & Regards,
    V Srinivasan

  • Billing document does not exist in VF22

    Dear Experts,
       We are working on Invoice list it gives output with LR00.
    but we have created a new output type ZPGR and assigned in
        SD>Billing>Billing document>Invoice List>Maintain Output for Invoice list
         Prgram-RLB_INVOICE and smart form ZS_INVOICE_PACK_2_GRP
    and VF21 i was able club billing documents. but in VF22 while issuing output it give error 'Billing document does not exist'
    checked and found because VBTYP in VBRK for invoice list document(LR) it is 3. but RLB_INVOICE program checking values MNOPSU56.
    any idea how to deal with, is there any other program instead of RLB_INVOICE to assign smart form
    Please suggest
    Regards
    Siva

    Hi Sunkesula,
    below is the sample Z print program.
    i copy some of the code from RLB_INVOICE and change the sapscript calling method to smartform calling method.
    REPORT Z_TEST.
    INCLUDE XXXX. "you may define any include you want
    INCLUDE XXXX. ""you may define any include you want
    *       FORM ENTRY
    FORM entry USING return_code us_screen.
      DATA: lf_retcode TYPE sy-subrc.
      CLEAR retcode.
      xscreen = us_screen.
      PERFORM processing USING us_screen
                         CHANGING lf_retcode.
      IF lf_retcode NE 0.
        return_code = 1.
      ELSE.
        return_code = 0.
      ENDIF.
    ENDFORM.                    "ENTRY
    *       FORM PROCESSING                                               *
    FORM processing USING proc_screen
                    CHANGING cf_retcode.
      DATA: lf_formname           TYPE tdsfname,
                lf_fm_name            TYPE rs38l_fnam.
    * SmartForm from customizing table TNAPR
      lf_formname = tnapr-sform.
    * determine smartform function module for invoice
        CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
          EXPORTING
            formname           = lf_formname
    *       variant            = ' '
    *       direct_call        = ' '
          IMPORTING
            fm_name            = lf_fm_name
          EXCEPTIONS
            no_form            = 1
            no_function_module = 2
            OTHERS             = 3.
        IF sy-subrc <> 0.
    *   error handling
          cf_retcode = sy-subrc.
          PERFORM protocol_update.
        ENDIF.
      ENDIF.
    "call the fm of the smartform. You may pass in any data you would like to display here
    CALL FUNCTION lf_fm_name
    ENDFORM. " processing

Maybe you are looking for