Error posting TAx to Accounting

Hi
I have 2 tax condition types in the billing document.
1 is statistical and the other is to be posted to Accounting.
While doing so I am getting the error
"Tax statement item missing for tax code C1
Message no. FF805
Diagnosis
No tax item exists for tax code C1 in a G/L account item. A possible cause is an incorrect transfer of parameters by the application to the Accounting interface.
Procedure
Enter an OSS message."
Can anyone let me know what could be the problem
I have checked the condition type, tax codes, the tax settings . Nothing seems to work.
Even taken help from ABAp, but cannot identify the exact error
Looking forward to hear from you
Thanks & regards,
Sheetal

Hello,
                                                                                Please consider note 112609 regarding this issue and check the
following:
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.
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.
In your pricing procedute you have customized the tax conditions with-
out reference steps.
Addionally please have a look at the note 872449. Often the error
occurs due to an wrong customizing.
I hope that the information are helpful.
regards
Claudia

Similar Messages

Error in VF02 (Posting keys for account determination for transaction JTS)

Hi,
I have created new account key JTS and also assigned G/L account in VKOA, But at the time of releasing the billing document to accounting, I am getting the below error;
Posting keys for account determination for transaction JTS do not exist
Message no. F5598

Hi Amanulla,
once we create the Account key in revenue determination we have to assign that account key to respective procedure and condition types.
check that.
please award points.
ravikanth

Posting keys for account determination for transaction EXD do not exist

hi
i am doing Sales order for 1 month,no error i have got
but now i am getting error
Posting keys for account determination for transaction EXD do not exist
HELP

Hello,
I have following suggestion to overcome this issue.
1. In the t-code "FTXP", check for assignment of the G/L account for the posting key.
2. Check out the SAP Note:200348.
3. In t-code "OBCN",for the account key EXD, make sure that the value of posting indicator is 2.
4. In t-code OBYZ, for the tax calculation procedures, change the key to EXD. The account keys in tax pricing procedures and SD pricing procedures Should be same.
Regards,
Sarthak

Posting keys for account determination for transaction EXC do not exist

hi
i am doing Sales order for 1 month,no error i have got
but now i am getting error
Posting keys for account determination for transaction EXD do not exist
HELP

There will not be any such postings called FI side / SD Side.
Positng always done in Financial perspective only into Certain G/L accounts depends on configuration we did.
As we know,
To post Invoice Conditions in G/L accounts , we configure Account Determination . These tables will be communicated through Account keys maintained in Pricing procedure & in Account determination tables.
To account the stock in Inventory, will configure the same in OBYC - FI/MM Account Determination.- this will be triggered through Movement type - Transaction key / General modifier / Valuation calss / Valution group code n other factors.
In your issue,
Which Postings you are referring to?
In SO creation, Controlling documents will be created ( Ref: COPA - Controlling & Profitablity Analysis Customization)
After PGI in Delivery: Inventory will accounted through OBYC settings
After releasing invoice to Accounting, G/L accounts posted through VKOA settings.
Hope ,now you provide exact information related to your query

Posting keys for account determination

Hi all
I'll try to post an sales ticket from Retail modul to SD module.
I have this message error : Posting keys for account determination for transaction ZST do not exist
Message no. F5598
Diagnosis
The posting keys necessary for account determination for transaction Z
    have not been set.
System Response
Because the posting key is missing, the system cannot generate any
    automatic postings.
Procedure
Maintain the posting keys necessary for transaction ZST.
In VKOA transaction, I check and for me the account determination has been set.
So I was wondering what's goes wrong with this.
Appreciate your expert advise..

HI,
Please check wther In the pricing procedure ZXXX some conditions have account key ZXX.
But in table T030B there is not any record with KTOSL = ZXX.
Check note 1273471,1128659
Regards
Ravinagh Boni

Entries appearing in Service Tax Control Account due to Error in System

Hello Experts,
     I am facing a problem in one particular GL i.e.Service Tax Control a/c
error-Entries appearing in Service Tax Control Account due to Error in System
entries are- Service tax control   a/c   -
Dr. 21,621.86
                        To Service Tax Control a/c     Cr.      21,621.86
My question is when i am making entry as Service tax Dr-21,621.86,Service Tax Cr.21,621.86,so it will adjust,and in FBL3N amt will show 0 but it was showing 21,621.86
Plz Guide me asap,very urgent issue
Thanks in Advance

Dear,
What was the balance before you posted the below entry?
Also run FBl3N with correct date parameters..
br,Vivek

Error FF753 Tax code 01 not appear in any G/L account item with FM Active

Hi
We have fund management configured for one of the company code, while creating billing document through VF01/VF02 we are getting the Error FF753 Tax code 01 not appear in any G/L account item.
This error however does not appear when posting directly from FI with the same tax code.
I have tried to change the message control in which case i am getting a dump pointing to PSM-FM.
Please advise.
Regards
Sandeep

Hi:
          If you could please refer to the contents of OSS Note 112609 - How are tax codes transferred to conditions ?
"Symptom
If a billing document is transferred to accounting the system displays error messages. Transferring tax codes from tax conditions into the pricing conditions and discounts does not function as expected.
Other terms
FF805, FF747, FF753, MWSKZ, MWSK1, tax code
Reason and Prerequisites
The tax condition in the SD pricing procedure contains incorrect reference steps, there are several tax conditions in the pricing procedure of which the tax codes overwrite each other or a program error exists.
Solution
In the accounting document for a billing document, the different G/L account line items are provided with a tax code. The tax code of the G/L accounts is transferred from the tax condition(s) of the billing document. How are the tax codes of the tax conditions transferred into the other conditions of a billing document ?
Basically:
The conditions of a billing document are read from top to bottom. As soon as an active tax (inactive = ' ') is read, the system transfers the tax code of this tax into the non-tax conditions as follows:
    1. The reference steps (From-step, To-step) are read (the reference steps are defined in the pricing procedure).
    2. The tax code is transferred into all conditions, for which
    the step number of the condition lies in the pricing procedure between "From-step" and "To-step",
    the condition is not inactive (exactly: the inactive flag is not equal to A (Condition exclusion), M (Inactive due to manual entry), or X (Incorrect)),
    the condition is not statistical (if it is no invoice list condition),
    the condition is no tax condition.
After the transfer of the tax code the system searches for the next active tax. If further taxes are found, their tax code is again transferred according to the above procedure. If the reference steps of different taxes overlap, tax codes that have already been transferred are overwritten. To all non-tax conditions which in the pricing procedure stand after the last tax condition the tax code of the last active tax condition is transferred if they are not statistical.
Special features:
    1. If the "From-step" of a tax condition refers to a subtotal of the pricing procedure, the tax code of the tax is not only transferred into the conditions with step number between From-step and To-step but into all non-tax conditions for which
    the step number of the condition in the pricing procedure is lower than the "To-step" of the tax condition.
    the condition is not statistical (if it is no invoice list condition).
    the condition is not a tax condition.
    2. If the "To-step" of the tax condition is smaller than the "From-step", then the system sets "To-step = From-step".
Notes:
    1. As of Release 4.0 the tax code is no longer transferred in pricing but only when the billing document is released to accounting.
    2. If you use several taxes and tax codes and Customizing is incorrect for the release of billing documents to accounting, among others the system may display error message FF747.
    3. If there are several taxes in the pricing procedure refer to Notes 72173 and 82091 for Releases 3.0D - 3.1G. For Release 3.1H, only note 82091 is relevant.
    4. For conditions which are transferred into accounting (thus not statistical, not inactive conditions) and do not contain a tax code, the system searches for a default tax code which in Accounting Customizing can be set depending on the company code (tax code for non-taxable transactions). This applies to releases up to and including Release 4.5B. For Release 4.6, refer to Note 385127."
Regards

Getting Error while posting billing into accounting.

Hi All,
Could any one help on this error,i am getting this while posting billing into accounting.
Tax statement item missing for tax code O0
Message no. FF805
Diagnosis
No tax item exists for tax code O0 in a G/L account item. A possible cause is an incorrect transfer of parameters by the application to the Accounting interface.
Procedure
Enter an OSS message.

Hi Raja,
We have many FF805 errors reported by customers and the same solution
has resolved the problem. Please note that the SD-FI interface changed
from earlier releases.
In the vast majority of cases, error FF805 occurs because of an error
in your pricing procedure. The previously attached note 112609 explains
in detail how tax codes are transfered to conditions.
The note 400766 explains the checks performed by the system on the Tax
codes:
1. system checks whether there is a revenue line for each tax line.
2. in the reverse case, for each revenue line containing a certain
   tax indicator there must be a tax line with this indicator.
If the tax condition has condition value zero and condition base
value zero, then it is not transferred to FI.
If you have revenue lines containing a tax indicator XX, but no
tax line with tax indicator XX, then the error FF805 issues, and
it is justified. => Please check these informations. I have attached
notes for further information.
-> EXAMPLE
   If tax condition MWST has base amount zero and value zero; for this
   reason it is not passed to accounting. But, according to the
   criteria reported by note 112609, its tax indicator EG: A7
   has been assigned to the condition EG: ZBR1.
   So in accounting there would be a revenue line with tax indicator A7,
   but there isn't any tax line with indicator A7 (because MWST doesn't
   pass to FI). The note 400766 states situation is unallowed, and error
   FF805 is justified.
Thanks and best regards,
Smile

Error in :Posting keys for account determination

Hi, Gurus,
      please suggest the solution for the following problem.
            we are selling two types of materials, one is the product material and the second one is the scrap material.Different type pricing procedures, sale order,delivery and billing types were configured for the same. For CST and VAT   same condition type :"ZCST - for CST " and ZVAT - for VAT" were used in both pricing procedure and the standard account keys : MW1 for ZCST and MWS for ZVAT and same G/L accounts configured .
.                                                   key combination for the condition types as mentioned below:
.                                                        ZCST: Country/PlntRegion/Region/TaxCl2Cust/TaxCl.2Mat
                                                         ZVAT: Country/PlntRegion/Region/TaxCl1Cust/TaxCl.Mat
     Now we want to capture CST and VAT seperately for both the materails.For that two new account keys created and incorporated the same in scrap pricing procedure and and new G/Ls created and assigned .Now the system is throwing following error while while releasing the billing document to accounting document.
Posting keys for account determination for transaction Z48 do not exist
Message no. F5598
here Z48 is the new accounting key created for the CST tax.We tried all the possibilities, but system is throwing the same error.
with regards
sam

Thank u for ur response.Now it is solved when OB40 and OBCN maintained.Here I am facing a new problem.pl. provide the solution.we configured twoseperate pricing procedures for our product and scrap material.We have configured same condition types for VAT(ie.condition type:ZVAT) and CST(cond type:ZCST), in both pricing procedures. Now We want to maintain seperate condition types for VAT and CST for pricing procedure for Product material and Scrap material. I have created two new condition types for scrap sales ZSCT- cst for scrap and ZSVT-vat for scrap by copying the same from existing conditions ZCST & ZVAT, and the same is included in the scrap pricing procedure. And also maintained OB40,OBCN,OVK1,OVK3,OVK4, FTXP,FV11 and VK11.
now I am facing the following problems.
1. while creating the Material master & customer master, in tax category sub screen all conditions i.e. conditions defined for product material( ZCST,ZVAT) and defined for scrap material (ZSCT, ZSVT) displaying and these are compulsory fields.
2. While creating the sale order for scrap material, system is considering the TAX classes from ZVAT/ ZCST (defined for product material) and taking the condition value from the condition type ZSVT/ ZSCT with the TAX class values of ZVAT/ZCST.
Now I would like to know is there any procedure to assign the Material type and Customer group to Tax category.
Thanks & Regards
sam

Error in determining posting key T030B account key JP7

Hi
While I am running MIRO, following error comes.
Error in determining posting key T030B account key JP7
Message no. FF701
Diagnosis
No posting keys could be found for the account key defined in the tax calculation procedure.
Procedure
Check the following settings in taxes on sales/purchases Customizing.
To do this, choose Maintain entries (F5):
1. Check or correct the calculation procedure.
2. Check whether you have specified a valid transaction key in the tax type used.
If it is a new transaction key, you must first define the posting rules. Enter the transaction keys in the calculation procedure
Can u please advise me where I have to make changes in my config.
Rakesh

Hi ,
this error is coming because transaction key JP7 is not maintained with respect to posting keys .
In SE16 open table T030B and maintain transaction Key JP7 with posting keys then hopfully ur error with get removed.
thanks
deepa

Error when creating Final Accounting Post to GL in AR

Hello,
I currently getting an error while creating Final Accounting Post to GL
I have changed the Profile Option SLA: Enable Trace to <null> as mentioned in the solution on metalink. But still I'm getting this error.
If anyone has encountered the error(LOG) below; please reply me as soon as possible
thanks
mevin
THE LOG
Subledger Accounting: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XLAACCPB module: Create Accounting
Current system time is 14-AUG-2009 09:36:54
XDO Data Engine Version No: 5.6.3
Resp: 50832
Org ID : 102
Request ID: 499751
All Parameters: P_APPLICATION_ID=222:P_SOURCE_APPLICATION_ID=:P_DUMMY=:P_LEDGER_ID=2089:P_PROCESS_CATEGORY_CODE=:P_END_DATE=:P_CREATE_ACCOUNTING_FLAG=N:P_DUMMY_PARAM_1=:P_ACCOUNTING_MODE=:P_DUMMY_PARAM_2=:P_ERRORS_ONLY_FLAG=N:P_REPORT_STYLE=D:P_TRANSFER_TO_GL_FLAG=Y:P_DUMMY_PARAM_3=:P_POST_IN_GL_FLAG=Y:P_GL_BATCH_NAME=:P_MIN_PRECISION=2:P_INCLUDE_ZERO_AMOUNT_LINES=:P_REQUEST_ID=:P_ENTITY_ID=118514:P_SOURCE_APPLICATION_NAME=:P_APPLICATION_NAME=:P_LEDGER_NAME=:P_PROCESS_CATEGORY_NAME=:P_CREATE_ACCOUNTING=:P_ACCOUNTING_MODE_NAME=:P_ERRORS_ONLY=:P_ACCOUNTING_REPORT_LEVEL=:P_TRANSFER_TO_GL=:P_POST_IN_GL=:P_INCLUDE_ZERO_AMT_LINES=:P_VALUATION_METHOD_CODE=:P_SECURITY_INT_1=:P_SECURITY_INT_2=:P_SECURITY_INT_3=:P_SECURITY_CHAR_1=:P_SECURITY_CHAR_2=:P_SECURITY_CHAR_3=:P_CONC_REQUEST_ID=:P_INCLUDE_USER_TRX_ID_FLAG=:P_INCLUDE_USER_TRX_IDENTIFIERS=:P_USER_ID=:DebugFlag=
Data Template Code: XLAACCPB
Data Template Application Short Name: XLA
Debug Flag:
{P_ACCOUNTING_REPORT_LEVEL=, P_DUMMY=, P_ACCOUNTING_MODE_NAME=, P_ERRORS_ONLY_FLAG=N, P_REPORT_STYLE=D, P_GL_BATCH_NAME=, P_END_DATE=, P_SECURITY_INT_3=, P_SECURITY_INT_2=, P_SECURITY_INT_1=, P_VALUATION_METHOD_CODE=, P_POST_IN_GL=, P_TRANSFER_TO_GL=, P_TRANSFER_TO_GL_FLAG=Y, P_INCLUDE_USER_TRX_IDENTIFIERS=, P_USER_ID=, P_PROCESS_CATEGORY_NAME=, P_ERRORS_ONLY=, P_DUMMY_PARAM_3=, P_SECURITY_CHAR_3=, P_DUMMY_PARAM_2=, P_SECURITY_CHAR_2=, P_DUMMY_PARAM_1=, P_SECURITY_CHAR_1=, P_ENTITY_ID=118514, P_PROCESS_CATEGORY_CODE=, P_INCLUDE_ZERO_AMT_LINES=, P_LEDGER_ID=2089, P_POST_IN_GL_FLAG=Y, P_APPLICATION_ID=222, P_INCLUDE_USER_TRX_ID_FLAG=, P_APPLICATION_NAME=, P_REQUEST_ID=, P_CONC_REQUEST_ID=, P_LEDGER_NAME=, P_SOURCE_APPLICATION_ID=, P_CREATE_ACCOUNTING=, P_CREATE_ACCOUNTING_FLAG=N, P_MIN_PRECISION=2, P_SOURCE_APPLICATION_NAME=, P_INCLUDE_ZERO_AMOUNT_LINES=, P_ACCOUNTING_MODE=}
Calling XDO Data Engine...
[081409_093744202][][EXCEPTION] SQLException encounter while executing data trigger....
java.sql.SQLException: ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_pkg.accounting_program_document. ORA-01086: savepoint 'SP_EVENTS' never established
ORA-20001: -: XLA-95103: An internal
ORA-06512: at "APPS.APP_EXCEPTION", line 72
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 262
ORA-06512: at line 4
     at java.lang.Throwable.<init>(Throwable.java:57)
     at java.lang.Throwable.<init>(Throwable.java:68)
     at java.sql.SQLException.<init>(SQLException.java:55)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
     at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:215)
     at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:965)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3445)
     at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4394)
     at oracle.apps.xdo.dataengine.XMLPGEN.executeTriggers(XMLPGEN.java:699)
     at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:255)
     at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:205)
     at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:237)
     at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:364)
     at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:236)
     at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:293)
     at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Start of log messages from FND_FILE
14-AUG-2009 09:37:19 - Beginning of the Report
GL Inerface tablename = GL_INTERFACE
GL Inerface tablename = GL_INTERFACE
tablename = GL_INTERFACE
14-AUG-2009 09:37:19- Submitting the Journal Import
GL Inerface tablename = GL_INTERFACE
GL Inerface tablename = GL_INTERFACE
tablename = GL_INTERFACE
14-AUG-2009 09:37:19- Submitting the Journal Import
14-AUG-2009 09:37:44- Journal Import completed
ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_pkg.accounting_program_document. ORA-01086: savepoint 'SP_EVENTS' never established
ORA-20001: -: XLA-95103: An internal
ORA-06512: at "APPS.APP_EXCEPTION", line 72
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 262
ORA-06512: at line 4
End of log messages from FND_FILE
Executing request completion options...
Finished executing request completion options.
Concurrent request completed
Current system time is 14-AUG-2009 09:37:45
---------------------------------------------------------------------------

select * from gl_je_sources_tl;
main columns to look at are:
IMPORT_USING_KEY_FLAG
je_source_name
je_source_key
user_je_source_name
select * from gl_je_categories;
main columns to look at are:
je_category_key
user_je_category_name
If import_using_key_flag is Y for your je_source (Receivables), for the application (222) you are running Create Accounting in Final Post Mode, then apply the patch 8568620
By
Vamsi

Error message when trying to post GR for account assignment category A

Hello gurus,
when I create a PO item with account assignment category A, PO creation works fine. But when I try to post the GR for that item, I get an error message similar to
"Account determination for entry <our chart of accounts> ANL <our company code> not possible".
Any idea what the problem might be?
I have had similar error messages in the past, when the automatic postings where not configured completely. So "ANL" should be some transaction like BSX or something. But I cannot find a transaction ANL.
Thanks in advance
Alicia

Thanks for your help, everything seems to be ok as described.
This seems to be a SAP error, see SAP note 1249431.
Greetz
Alicia

General Ledger Posting Error (GLT2 051) No accounting transaction variant

Hello SAP Gurus-
When testing lockbox in FLB2, I received the following error message:
General Ledger Posting Error (GLT2 051) No accounting transaction variant assigned to FB01/ /LB
We are on ECC 6.0
I created a new Document Type LB
I created a new G/L account for Lockbox clearing and AR
How do I fix this?
Thank you!

Hi,
Assign a transaction variant for the document type you created in Transaction code GSP_VZ3. Also, make sure that the GL accounts affected are assigned with item categories in GSP_LZ2.
Thanks
Aravind

Two Account key to post taxes in pricing procedure

Dear Experts,
My requirement is like this in pricing procedure additional tax tax conditon is there & for posting the same FI requirement is to post in VAT or CST acc key only.
means if CST is applicable this additional tax should post in MWS1 account key & if VAT is applicable this additional tax should go to J1F key.
As I have assigned J1F key, can we assign two account keys to post or can we create routine?
FI people don't want to create any new Acc Key for additional tax.
Pl. guide.
Thanks
Trupti Nadgouda

Thank you sir for the reply, but how can system determine automatically posting key as per VAT or CST applicable.
since in pricing procedure i have assigned as per below given
condition Type                         Acc Key
ZIN1 - CST                                   MW1
ZIN2 -VAT                                   J1F
ZATX - Additional Tax -                MW1 in case of CST is applicable
                                                     J1f in case of VAT
Pl. guide me how can i assign two account key for ZATX condition.
Thanks
Trupti Nadgouda

Error in determining posting key T030B account account key JP5

Dear all,
at the time of MIRO posting error msg comes
error in determining posting key T030B account account key JP5
Pls guide me
Thanls
amin

Hi
Give the Debit as 40 and Credit as 50
To find the GL code, go to FS00 and give ur company code and get the GL code and assign the same OB40
Regards
Prasanna R
Edited by: Prasanna Raju on Jun 25, 2009 12:35 PM
Edited by: Prasanna Raju on Jun 25, 2009 12:36 PM
Edited by: Prasanna Raju on Jun 25, 2009 12:36 PM

Error posting TAx to Accounting

Similar Messages

Maybe you are looking for