Error in Accounting Interface

Dear All,
when creating billing document for cash sales Accounting Document is NOT Creating and in the cash invoice header in the field of posting status Error in Accounting Interface
as for the cash sales invoice all the G/L accounts are maintained (VKOA,OV77) and their is no posting block in the billing type.
Please give the soluation of this problem, its very urgent.
Thanks in advance.
Best Regards
salm

Check with FI Consultant if Profit Centre is required to be maintained in Customer Master Data.
The current solution will be to cancell Billing Document --> Cancel PGI --> Cancel Delivery --> foreclose Sales Order
Maintain Profit Centre in Customer Master Data
Recreate Sales Order --> Delivery --> PGI --> Billing Document
Alternatively,
With the help of Abaper force Profit Centre in Billing Document in Debug Mode. (Not recommended practise)
Regards,
Rajesh Banka

Similar Messages

Error in accounting interface -no accounting document generated

Hi All,
For a billing document the accounting document is not generated.
The posting status is hsown as "error in accounting interface".
Also the billing date(23rd May) is less than the created on date(2nd June).
I know when we go to the change mode of the billing doc and give the billing date as current date it will realease to accouting.
What I wnat to know is what could be the possible reasons for the billing date being less than created on date and the posting status being "error in accounting interface".
Please help.

hello, friend.
is your billing referenced to the sales order or delivery? in standard, if you do not specify the billing date on creation, the system will take the goods issue date for delivery-related billing.
for order-related billing, it will reference the service rendered date. if there is no entry, then it will try to reference the billing date in the sales order.
as to errors in the interface, there are at least a few i can think of:
1. the profit center per line item in the sales order was not entered/proposed, or that the entry itself was in error
2. the revenue posting based on the original billing date is for a period already closed (however, this opinion is mine and needs to be confirmed by FICO)
3. errors in account determination is also a possible reason, although you have to look at the error message if this is pointed out
hope this helped you.
regards.

Error in Account Interface

Hi Friends,
Credit Memo is not posted to FI. In posting status at header data of billing document I could see a message some thing like " Error in Account Interface"
Can any body give me some what could be the problem.
Thanks in advance
J M

Hello,
if the error message is FF805 then please have a look as follow:
This error can be occurs by the following causes:
1.
When the tax condition has a condition base value with '0' this
condition is deleted when releasing to accounting. This checking is
implemented with release 4.6. In release 3.1 this was not implemented.
As a result the error FF805 is triggered. So please check that the
tax base is not zero in the document.
2.
The error message FF 805 often is created due to errors in
customizing, especially in the pricing procedure. Please check
whether you have two active, non-statistical tax conditions in your
procedure with overlapping reference steps (transaction V/08).
This also can trigger this error.
Addionally please have a look at the note 872449. Often the error
occurs due to an wrong customizing.
You should use the condition base formula 16 for MWST.
Surely I could help you with this information and I wish you a nice
start in the week.
regards
Claudia

Error in accounting interface at the time of Invoice posting

Hi..
Im getting this error at the time of Invoice Posting .
"Error in accounting interface "
Plz guide me
regards
Deepa

Deepa,
Go to VF02, enter your invoice, click on the green flag (release to accounting), now the system will show the exact error.
Prase

VF01 : "Error in accounting interface" during first billing doc creation

Hi
i had done OB52, & OBH2 & VN01 (assigned new no. range to the sd billing documents).
Now i am able to do PGI & while creating the Billing document i am facing the error that
Error in accounting interface
Can any body suggest me , how to proceed.
Regards
Manvir

Hello,
go to transaction vf02 > environment .Account deternmniation analysis > revenue accout determination
this would help you to find the accoutn determination errors if any . you can correct accordingly using the transaction code VKOA.
also read the message for any other hints , you can post the message if the error is not reswolved
hope this helps
Thanks
akasha

Error in accounting interface: FI/CO interface: Balance in transaction cur

Hello Gurus-
We are on ECC 6.0 and we are having a problem with a few billing documents. Below is an example of the error we are receiving with several billing documents via VXF3:
Diagnosis
    The balances in transaction currency must be zero for
    logical transaction when transferring to the FI/CO
    interface. A balance of "                    1.75-" "U
    was determined for the logical transaction "".
System Response
    The FI/CO interface does not process any transactions
    have a balance in transaction currency other than zero
Procedure
    This is a system error of the calling application.
I have checked CMOD, account determination, OB09 and the G/L's FS00. The billing docs are in balance. I have someone checking out the interface to FICO in the meantime but I am hoping that someone can help me understand what the issue is? The billing document is in USD. This is not an inter or intra company billing document.
Thank you!!

Hello-
I am having this issue as well. Have you checked OSSNote 1459805?
Error F5702 Balance in Transaction Currency when releasing SD invoice to accounting
Symptom
u2022     Cannot release invoice to accounting.
u2022     Error message "Balance in Transaction Currency" occurs.
u2022     When releasing an invoice to accounting, the document does not release due to error F5 702: Balance in Transaction Currency
Environment
SAP Release Independent
Reproducing the Issue
1.     Go to transaction VF02.
2.     Enter your billing document number.
3.     Click on the green flag button to release the document to accounting.
4.     Error 'Balance in Transaction Currency' will occur.
Cause
1.     Withholding tax condition has not been flagged as statistical.
2.     Active enhancements SDVFX010, SDVFX011 wrongly implemented.
3.     Formula or userexit in pricing changing field KOMP-NETWR.
4.     Down payment request with credit card.
5.     Credit/debit memo created from credit/debit memo request with revenue recognition type RRREL = F; the credit/debit memo request has been created with reference to SD document not having revenue recognition type RRREL = A or B.
Resolution
Resolution to 1:
Check SAP note 662011
Resolution to 2:
Check SAP note 160211
Resolution to 3:
The gross value (net value + tax value) passed from SD to FI must correspond to the sum of active, not-statistical, pricing conditions. If field KOMP-NETWR is changed, the gross value is affected. This causes the error F5 702. It is not supported change KOMP-NETWR by custom modification.
Resolution to 4:
Functionality not supported. The combination of SD down payment functionality and credit card is not designed.
Resolution to 5:
Functionality not supported. Credit/debit memo request with revenue recognition type F can only be created with reference to SD documents with revenue recognition type A or B. Other use is not supported. See the Best practices guide attached to note 1172799 about supported revenue recognition processes.
Related SAP Notes:
48431
Unused user exit runs
160211
Using USER_EXIT creates data inconsistency
662011
VF02 Error Message: Balance in Transaction Currency
1172799
New version of Best Practices for revenue recognition

Billing Error in accounting interface

Dear Experts
As per our requirement both scenarios (with/without tax)
should work
for all countries including Australia & Newzland.
I have also tried changing AU & NZ pricing procedures as suggested in
note 122609 but it is not working as expected. It is
capturing base
amount in tax line .
functionJ_1BSA_COMPONENT_ACTIVE is relevant.
In general SAP unallows to post FI documents like one
created from SD
invoice ( G/L lines with a tax code, but not tax lines with
same tax code. It gives error FF805.)
For India (and other countries) the function
ID_TAX_RECALCULATION_CHECK sets SKIP_RECALCULATION = 'X'.
But for New Zeland and Australia FM is missing .
Client has a common legacy system that was designed based on
the same pricing procedure for all the countries. We had to make it work for Australia
and New Zealand also as per the requirement.
Please let us know what we need to do for the same.
Let me know if any other solution is available to achieve
this.
Regards,
Shachi

Hi,
Thanks for reply. I had tested by creating a new sale order and billing document after changing the tax classification of customer master.
Note 642469 - Additional countries/components with special processing is already implemented in the sysytem.
I raised an OSS message the revert is:
Thank you for the example. Now I could see that function
J_1BSA_COMPONENT_ACTIVE is relevant.
In general SAP unallows to post FI documents like one created from SD
invoice 9000000520: G/L lines with a tax code, but not tax lines with
same tax code. It gives error FF805.
For India (and other countries) the function
ID_TAX_RECALCULATION_CHECK sets SKIP_RECALCULATION = 'X'. I suppose
this is done to fulfill local legal requirement.
But for New Zeland there is not any known legal requirement to allow
FI documents with tax code and without tax line. So the general rule
(explained in note 400766) is valid.
But still im not getting how to resolve it.
As per our requirement both scenarios (with/without tax) should work
for all countries including Australia & Newzland.
I have also tried changing AU
& NZ pricing procedures as suggested in
note 122609 but it is not working
as expected. It is capturing base
amount in tax line
If there is any problem in pricing procedure, why is it allowing
for India & Other countries?
We have a common legacy system that was designed based on the same
pricing procedure for all the countries
If i change any settings its allowed for only one scenario but in existing system for India and other countries both scenario worked very well.
Kindly share your valuable inputs.
Regards,
Shachi

Error in account determination: table T030K key 1000 MW1 Message no. FF709

Dear Gurus
We have activate automatic release to account at VF01 level. For one billing doc system is giving us error
Error in account determination: table T030K key 1000 MW1Message no. FF709
At Environment -> Act determination analysis here the system is not giving any error. But accounting entries are not there and Excise accounting entries are generated and showing there.
When we check at header level Header tab Accounting data block Posting status system is showing Error in Accounting Interface.
We have assign MW1 accounting key for CST condition Type.
Assignment in VKOA is also done.
In OB40 tax code and the GL is also done.
Reetesh NIgam

hello, friend.
when you configure account determination, you assign not only account assignment groups (customer, material) to GL accounts, you also need to make assignments for taxes, represented in SAP default by the posting key MWS.
an example assignment in account determination, procedure 5 (General) would be as follow:
Applic/Ty/Chart of Accts/Sales Org/Act Asg Grp/Act Asg Grp/Account key/GL accounts
V   KOFI   INT   1000   01   01   ERL   xxxxxx
V   KOFI   INT   1000   01   01   ERS   xxxxxx
V   KOFI   INT   1000   01   01   ERF   xxxxxx
V   KOFI   INT   1000   01   01   MWS   xxxxxx
please check if your tax condition type/s are included in your pricing procedure and have been defined in FI.
regards.

Error in Acctg Interface in Invoice

hi all,
I cannot create an accounting doc for an invoice which has a posting status: " Error in Accounting Interface".
I read all the threads in the forums. I did not have issue with Acct Determination for Revenue. I do not use acct assignment group. The Account Anlysis in VF02 is fine.
Do we assign anything from an invoice to a cost center ??
When i try to release accounting doc, i got error msg:
Cost Center Control-Area/ 3150 does not exist on 7/7/2010
Issue is there is no cost center 3150 at all. Why is it saying cost center ? Any suggestions are welcome.
thanks
Joyce

Cost center is not available in the specific Controlling area. Reason could be any of the below :
- not available on particular date, that means the validity is not in the period in which you are posting.
- cost center itself is not available.
-wrongly selected cost center / wrongly entered cost center
Please check the valid from date and valid to date of the cost center in the cost center master data in KS02 and you can extend the valid to date if necessary.
OR
Is it a GUI transaction that you are trying to pass or some batch input/BAPI?
If the last is correct, put leading zeros in the cost centre field. If it's a normal transaction, check that the cost centre is assigned to the right company code (KS03).
Thanks & Regards
JP

Error in Financial Interface

Hi Friends,
In invoice posting we are getting posting status as " Error in Financial Interface" What is to be checked?
The background program runs once a day and sometimes we get this error for the document, But if the same Debit / Credit memo is released through VF02 then we have no error.
Any help in this issue would be great.
Venkat.

Hi JC,
Following reasons for error `Error in Accounting interface` when releasing SD Billing document to Accounting
1. Output tax code is not defined / assigned to the GL Account
2. Product Cost estimate calculated with wrong consting variant
3. Assignment of Costing element to value field T code KE4R
4. SD condition is not assigned to COPA
Please check and let us know the outcome.
Regards,
Santosh

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.

Accounting Interface error HKONT

A debit memo ******495 was created on 12/03/2009. The accounting document had output tax account ****4400.
This was cancelled. Cancellation invoice *****8865. The cancellation invoice is getting an error in accounting "error: HKONT not equal to ****4405" I checked output tax in OB40 and FTXP for account key MWS and tax code S4 (as per condition type JRC1). Account is *****4405. This was changed from ****4400 to ****4405 after the original debit memo was created.
Changing it back only for this invoice cacellation is not an option.
Can someone give a work around to cancell the original debit memo. OR I might be totally wrong about the root cause.

Hi Sandeep,
As you have already stated the tax account was changed between invoice
and cancellation.
Since we convert only the documents during the cancellation, the system
tries to post to the original account.
Since meanwhile, however, the tax account was changed in the FTXP,
the system runs into the FF 804 error during the check.
You have 2 possibilities:
1. Changing the tax account to the FTXP back to the original and
posting this one cancellation.
2. Working with the old cancellation procedure (SAP Note 339928) and
then putting the flag "rule_new_cancel" on A.
Please also review the SAP Notes 400766 and 400000.
I hope the information is helpful in resolving the issue.
Cheers,
Alex

Error in accounting document creation

Hello All,
While releasing the billing document, getting the following error:
<b>SYST: Tax jurisdiction code at lowest level not transferred
Message no. FF793
Diagnosis
The application has not transferred the tax jurisdiction code at the lowest level (TXJDP) to the Accounting interface.</b>
Can someone help me as to what the error is and how to rectify the same.
Thanks,
Gopal

Gopal,
check Tax Jurisdiction Code

Reg.Error in account determination: table T030K key NCCA EXD

Dear Friends
we are doing domestic sales for that I am doing pricing procedure, I create 5 condition types without access sequence,and I manualy enter all the mrp price,mrp discount,bed,eces,shec and cst in billing, during the billing release I am getting the error
" Error in account determination: table T030K key NCCA EXD" Diagnosis In the chart of accounts to be posted to, no accounts are defined for the tax code you used. " in VKOA I maintained the account key ERL,MWS and EXD,and also in OBCN and OB40 but I am getting the same error.
do I need to create separate procure for pricing ? or can I use the same procedure which in SD.
do I need to change the TAXINJ and put the EXD there ? I am unable to solve this problem. Please help me .
Thanks
Rajakumar.K

FYI, as per SD pricing for tax condition type is concern, it doesn't require tax procedures to be maintain.
Tax % with correspondingly tax codes are maintain & determine from Condition record in to the pricing of sales doc.
These kind of error occurs due to non determination or missing tax code in sales doc pricing.
In turn, raises error due to accounting interface.
So, as per best practices, tax condition type are determined through condition record in sales document.
Thus, you ought to have access sequence for tax condition type & should create condition record with respective TAX % & Tax code. By, manually processing tax values into pricing, you will be able to maintain tax %, but without TAX CODE.
I hope this can assist you.
Thanks & Regards
JP

Error FI/CO interface: Balance in transaction currency from BAPI BAPI_ACC_DOCUMENT_POST

Hi All,
We are facing error FI/CO interface: Balance in transaction currency from BAPI BAPI_ACC_DOCUMENT_POST.
This error we are getting only in case of passing tax data.
Can anyone help me on this.
Below is the code :
   *fill header
gd_documentheader-username   = sy-uname.
gd_documentheader-header_txt = 'Test'.
gd_documentheader-comp_code = p_ccode.   "SQ
gd_documentheader-doc_date   = sy-datum.
gd_documentheader-pstng_date = sy-datum.
gd_documentheader-doc_type   = 'KR'.
gd_documentheader-ref_doc_no = p_xblnr. "SQ
*gd_documentheader-bus_act = 'RMWE'.
city = p_city.
state = p_state.
zipcode = p_zip.
*get tax juridisction code
IF NOT ( city     IS INITIAL ) AND
   NOT ( state    IS INITIAL ) AND
   NOT ( zipcode IS INITIAL ).
SELECT SINGLE rfcdest INTO ttxd-rfcdest FROM ttxd
   WHERE kalsm = 'TAXUSX'.
CLEAR x_com_jur.
REFRESH t_com_jur.
x_com_jur-city     = city.
x_com_jur-state    = state.
IF zipcode+5(4) EQ space.
    zipcode+5(4) = '0000'.
ENDIF.
CONCATENATE zipcode+0(5) '-' zipcode+5(4)
         INTO x_com_jur-zipcode.
x_com_jur-country = 'US'.
CALL FUNCTION 'RFC_DETERMINE_JURISDICTION'
    DESTINATION ttxd-rfcdest
    EXPORTING
      location_data    = x_com_jur
    IMPORTING
      location_err     = x_com_err
    TABLES
      location_results = t_com_jur.
IF sy-subrc = 0.
    READ TABLE t_com_jur INTO x_com_jur INDEX 1.
    it_accountgl-taxjurcode = x_com_jur-txjcd.
ENDIF.
ENDIF.
*fill AP (line 1) - vendor related data
SELECT SINGLE zterm FROM lfb1 INTO p_zterm WHERE lifnr = p_lifnr.
it_accountpayable-itemno_acc = 1.
it_accountpayable-tax_code = p_txcd.
it_accountpayable-pmnttrms   = p_zterm. "SQ
it_accountpayable-vendor_no = p_lifnr. "SQ
*it_accountpayable-item_text = 'S2P Testing in UDR1'. - SQ
it_accountpayable-pymt_meth = p_pmet. "- SQ
APPEND it_accountpayable.
*fill GL (line 2)
it_accountgl-itemno_acc      = 2.
*item_text - sq
IF p_asset IS NOT INITIAL.
TABLES : anlz,
           anla.
SELECT SINGLE * FROM anlz WHERE anln1 = p_asset.
SELECT SINGLE * FROM anla WHERE anln1 = p_asset.
*concatenate '00' anla-KTOGR into it_accountgl-gl_account .
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = anla-ktogr
    IMPORTING
      output = it_accountgl-gl_account.
it_accountgl-asset_no = p_asset.
it_accountgl-sub_number = '0000'.
it_accountgl-cs_trans_t = '105'.
it_accountgl-acct_type = 'A'.
ELSE.
it_accountgl-gl_account      = p_gl.
it_accountgl-costcenter      = p_cc.
it_accountgl-wbs_element     = p_posid.
ENDIF.
it_accountgl-comp_code       = p_ccode.
it_accountgl-tax_code = p_txcd. "SQ
it_accountgl-pstng_date      = sy-datum.
it_accountgl-fisc_year       = sy-datum(4).
APPEND it_accountgl.
CLEAR it_currencyamount.
*fill currency ammounts for lines 1 & 2
it_currencyamount-currency    = p_waers. "SQ
it_currencyamount-itemno_acc = 1.
*it_currencyamount-amt_base = -1.
it_currencyamount-amt_doccur = - 116. "p_totamt.
it_currencyamount-CURRENCY_ISO = 'USD'.
it_currencyamount-tax_amt = - 16.
APPEND it_currencyamount.
CLEAR it_currencyamount.
it_currencyamount-itemno_acc = 2.
it_currencyamount-currency    = p_waers. "SQ
it_currencyamount-amt_doccur = 100.
it_currencyamount-CURRENCY_ISO = 'USD'.
*it_currencyamount-amt_base = 100.
*it_currencyamount-TAX_AMT = -10.
APPEND it_currencyamount.
*tax data
it_accounttax-itemno_acc = 3.
it_accounttax-tax_code = p_txcd.
it_accounttax-gl_account = '0023110000'.
*it_accounttax-gl_account = p_gl.
it_accounttax-TAXJURCODE = x_com_jur-txjcd.
it_accounttax-acct_key = 'NVV'.
it_accounttax-cond_key = 'XP2I'.
**it_accounttax-direct_tax = 'X'.
APPEND it_accounttax.
CLEAR it_currencyamount.
it_currencyamount-itemno_acc = 3.
it_currencyamount-currency    = p_waers. "SQ
it_currencyamount-amt_doccur = 16.
it_currencyamount-CURRENCY_ISO = 'USD'.
it_currencyamount-amt_base = 100.
it_currencyamount-TAX_AMT = - 16 .
APPEND it_currencyamount.
   CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
EXPORTING
    documentheader          = gd_documentheader
IMPORTING
   obj_key                 = wa_obj_key
TABLES
   accountgl               = it_accountgl
*   ACCOUNTRECEIVABLE       =
   accountpayable          = it_accountpayable
   accounttax              = it_accounttax
    currencyamount          = it_currencyamount
*   CRITERIA                =
*   VALUEFIELD              =
*   EXTENSION1              =
    return                  = it_return
COMMIT WORK.
Regards,
Priyaranjan

Hi,
Reason 1:
An revenue-recognition-relevant item has several active conditions whose values cancel themselves so that a net item value of 0 results. The conditions have both the same revenue account (SAKN1) and the same clearing account (SAKN2).
For these conditions, the system writes a line with value 0 into the temporary FI/CO interface (internal tables: CACCIT, CACCCR). If table VBREVK does not contain control lines for this line, no further processing occurs and the line remains in the temporary FI/CO interface. Then the system reads this line for the creation of the next billing item which conatins a net value and generates a posting line with value 0. As a result, there is a balance in the FI/CO interface, and the billing document cannot be transferred.
Reason 2:
The billing document contains at least one item with an item category for which there is a setting stipulating that the values of this item should not be transferred to the header total of the document.
That is, in the maintenance of the item categories, this item category has the characteristic 'X' or 'Y' in 'Statistical value' field.
Reason 3:
Case: Billing document contains items without pricing conditions.
Then, on release to accounting, error RW022 occurs.
regards,
Saju.S

*Error in Accounting Interface*

Similar Messages

Maybe you are looking for

Error in Accounting Interface