Error in Account posting

Hi Gurus,
We have created billing for normal sales process while posting the document to accounting we are getting the below error.
"Doc. type D1 and category A only allow following characters " ABCEM"
Can you tell me the what is the cause for this error.
Babs

Hi Babs
double click on error message and post the same.

Similar Messages

Error 'Specify account number' while posting a parked document through FBV0

Hi,
I am getting an error 'Specify account number' while posting a parked document through transaction FBV0.
I am not able to figure it out as to what account number it is referring to. Since the document is parked I assume the GL account used has no problem. Please help.

Hi,
Try to change the Account number and then save or post the data. I think Once We Parking the Document it wont allow to post the data without changing.
Try same scenario in the development its be useful
Regards,

Error in Account determination for service vendor while posting miro

Error in Account determination:Table T030 Key 1000 KDT
Balance in Transaction currency
Vendor currency is of INR

Dear Badri,
Find this 2 posts maybe it will help you
http://www.sapfans.com/forums/viewtopic.php?f=6&t=343353
Error in Account determination: table t030 key xxxx KDT

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 in MIGO posting against PO with account assignment category K

Hi folks,
I have craeted a P.O. Account assignment category K, while creating GR, I am getting following error message
Account determination for entry SABB (chart of account) Z44 (Tra/event key) TE (act. grouping code) not possible
Message no. M8147
What could be the possibel cause.
I have already did the G.R with same account assignment in the past.
Regards

Dear
The system did not find an account for this transaction. This means that the account determination is not maintained in MM Customizing (Valuation). The key is made up of:
Chart of account
Transaction key (= Posting transaction)
Valuation grouping code
Account grouping code
Valuation class
System Response
The system cannot update a G/L account for this transaction. You cannot post the transaction.
Procedure
Contact your system administrator.
If you have the authorization, check the Account determination in Customizing forValuation.
Regards

Error in account determination while billing posting which includes rebate

Dear All,
Everytime I try to post my billing document which includes rebate, I get "error in account determination" message. Can anybody help me how do I rectify this error. I have checked all the following points:
1. Activated the Rebate at Customer Master Data
2. Activated the Rebate at Sales Organization Level (IMG)
3. Activated the Rebate at BillingLevel (IMG)
4. And finally have created a condition for rebate (VBO1)
Looking forward for your early response.
Best,
Vivek.

hi
if u r getting error by using rebate
pls go through this way
pls find the account key for rebate in pricing procedure and pls check in t.code vkoa whether they are assined gl account or not for that particular account key
eg: account keys erl -revenues etc....
Thanks & Regards
phaneendra

Account determination Error during material posting

hi
when i try to post the stock through MB1C, it shows an error that Account determination for omb1 (company Code)GBP_BSA not possible.
please help me out and where i exactly i missed the configuaration
thanks

Hi Friend,
Goto Transaction code OMS2 and click on the Qantity update for your plant and material combination.
This will help
regards,
santosh

Account Determination error during MIGO Posting

Dear All,
Kindly help resolve error duirng MIGO posting "ACCOUNT DETERMINATION FOR ENTRY GBB____ZOB TF01 not possible". This is Message no. M8 147.
The error happens once the transaction is being saved.
Hoping for your positive response.
Thanks and regards,
ching

Hi,
Goto OBYC Transaction.
Select the Procedure as ' GBB" and enter the Chart of Accounts ( for Your Company code)
Enter the Valuation modifier as assigned to others.
Enter the General modifier as ZOB
Enter the Valuation class ( with respect ROH/SFG others)
Enter the Debit/ Credit G/L account
save then proceed your transaction MIGO.
rgds
Chidanand

Posting to FI/CO error - error in accounting result import

Dear All,
We are facing the following error:
after we created a simulation of posting in PC00_M99_CIPE for one payroll area, we check the created documents and when we check accounts there in the documents there is a message "Error in accounting results import" and then follows the personnel number. And this personnel number is from another payroll area!!!
How can it be? How can a person from another payroll area be included into a posting run for simultaion payroll area??? Why does this error come? And why the posting run status is not "Documents with errors", but is okay - "Documents created".

Guys,
I run the simulation for 1 pers. number! And in the documents there are many pernr with wrong import results. And what is even more interestins id that each time I run the simulation, there are different pernr with wromg import results from different payroll areas. By the way, all of them have retroactive calculations. Maybe something wrong with some inner counters???

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

Error Message at F-02 "Enter Name & city for One-time account posting"

While create JV in one time customer ledger through F-02, following error message appeared & system not allow to crate JV.
"Enter Name & city for One-time account posting", Please help
Regards
BK GAIKWAD

Hi
Are you having separate account group for this One time vendor?
Via this account group, the vendor-specific fields, such as name, address, and bank address data should be changed from suppressed to display when you enter the vendor master record. You need to enter this data when you enter the document.
Check the fields status of Name, city etc in the below path
SPRO - Financial Accounting - Accounts receivable and accounts payable - Vendor accounts - MAster data - Preparations for creation of master data - Define account group with screen layout
Regards
Malathi

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 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 in determining posting key T030B account key GT0 Message no. FF701

While doing MIRO i am getting this error
Error in determining posting key T030B account key GT0
Message no. FF701
I dont know y..can u pls help me on this?

Hi
Try this
This error is coming because transaction key GT0 is not maintained with respect to posting keys .
In SE16 open table T030B and maintain transaction Key GT0 with posting keys then hopfully ur error with get removed.
Goto to SE11 put the table name T030B enter then click on change button select transaction type GT0 Maintain Debit 40 & Credit 50.
go to OB40
here find the GT0 key double click on it and then maintain the posting key

Error in BAPI for salary account posting

Dear Experts,
I am developing and report for salary account posting whrere i am using a bapi called BAPI_ACC_DOCUMENT_POSTING. Which require RFC destinetion of the target system where the document should post in its import parameters.But m not passing anything thr and its automatically taking an rfc destinatin.But while i try to run this report document is not posted and in its return table 2 error msgs comes
1. Error in document: BKPFF $ CLNTD11320
2. FI/COinterface: Line item entered several times
Pls provive me input if any one has come across this error.
Thanks

Line item passed to the vendor and gl tables of the bapi cannot be same.ie. if vendor table contains 3 entry with line item 1,2,3 gl should contain line item starting from 4.Line item field cannbe field manually using a count variable.

Error in Account posting

Similar Messages

Maybe you are looking for