Create accounting fails validate accounting def. completes normal

12.1.3
11gr2
windows 2003 32 bit
Validate accounting report
Subledger Accounting Application Report Date:
Application Accounting Definition Validation Report Page: 1
Application Application Accounting Definition Owner Event Class Status
Assets Assets Standard Accounting Oracle Additions Validating
Assets Assets Standard Accounting Oracle Adjustments Validating
Assets Assets Standard Accounting Oracle CIP Additions Validating
Assets Assets Standard Accounting Oracle CIP Adjustments Validating
Assets Assets Standard Accounting Oracle CIP Category Reclass Validating
Assets Assets Standard Accounting Oracle CIP Retirements Validating
Assets Assets Standard Accounting Oracle CIP Revaluation Validating
Assets Assets Standard Accounting Oracle CIP Source Line Validating
Transfers
Assets Assets Standard Accounting Oracle CIP Transfers Validating
Assets Assets Standard Accounting Oracle CIP Unit Adjustments Validating
Assets Assets Standard Accounting Oracle Capitalization Validating
Assets Assets Standard Accounting Oracle Category Reclass Validating
Assets Assets Standard Accounting Oracle Deferred Depreciation Validating
Assets Assets Standard Accounting Oracle Depreciation Validating
Assets Assets Standard Accounting Oracle Depreciation Validating
Adjustments
Assets Assets Standard Accounting Oracle Impairment Validating
Assets Assets Standard Accounting Oracle Reserve Transfers Validating
Assets Assets Standard Accounting Oracle Retirement Validating
Adjustments
Assets Assets Standard Accounting Oracle Retirements Validating
Assets Assets Standard Accounting Oracle Revaluation Validating
Assets Assets Standard Accounting Oracle Source Line Transfers Validating
Assets Assets Standard Accounting Oracle Terminal Gain and Validating
Loss
Assets Assets Standard Accounting Oracle Transfers Validating
Assets Assets Standard Accounting Oracle Unit Adjustments Validating
Assets Assets Standard Accounting Oracle Unplanned Validating
Depreciation
and create accounting ends in error like
Problem Description: after upgrade to 12.1.3 Create Account in Assets End with Error
"An internal error has occurred in the program xla_accounting_engine_pkg.RunPAD. ORA-04067: not executed, package body "APPS.XLA_00140_AAD_
An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_engine_pkg.RunPAD. ORA-04067: not executed, package body "APPS.XLA_00140_AAD_

I followed them before posting the issue none of them help ;)
It doesn't work for fixed assest I have fixed it for payables bu running import application definition for payables
i ran it for Fixed assest too
Subledger Accounting: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XLAALIMP module: Import Application Accounting Definitions
Current system time is 27-MAY-2012 12:45:47
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
P_APPLICATION_ID='140'
P_AMB_CONTEXT_CODE='DEFAULT'
P_SOURCE_PATH=my path of fixed assest\fa\12.0.0\patch\115\import\US\FAXLAAAD.ldt'
P_MERGE_ANALYSIS_ONLY_FLAG='N'
P_DEPENDENCY_CHECK1='Y'
P_IMPORT_OPTION='MERGE'
P_COMPILE_FLAG='Y'
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.AR8MSWIN1256
LOG :
Report: my xla path l\xla\12.0.0\reports\US\XLAALIMP.rdf
Logged onto server:
Username:
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
Output file size:
2725
------------- 1) PRINT   -------------
Printing output file.
Request ID : 740072
Number of copies : 0
Printer : noprint
Finished executing request completion options.
Concurrent request completed successfully
Current system time is 27-MAY-2012 12:46:30
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
Output file size:
2725
------------- 1) PRINT   -------------
Printing output file.
Request ID : 740072
Number of copies : 0
Printer : noprint
Finished executing request completion options.
Concurrent request completed successfully
Current system time is 27-MAY-2012 12:46:30
---------------------------------------------------------------------------

Similar Messages

Create Accounting when completed in warning the output is coming in XML

Hello to all,
I am having APPS version 12.1.3 OS version OEL 5.5
my problem is that when i am running Create Accounting concurrent request if it completes in warning the output (view output) is coming in XML in browser where as if its completing normal then the output appears correctly as expected, the output type for create accounting concurrent program is XML.
Please advise / guide me
thanks

Please find below log file details
==============================================================================================
Start of log messages from FND_FILE
06-OCT-2011 10:36:08 - Beginning of the Report
06-OCT-2011 10:36:08 - Starting of the Parent Thread
Starting main program for the source application = 200
06-OCT-2011 10:36:08 - Dynamic conditions built
06-OCT-2011 10:36:08 - Event Applications Determined
06-OCT-2011 10:36:08 - Security Context Set
06-OCT-2011 10:36:08 - Session Identifier Set
06-OCT-2011 10:36:08 - Setup for the ledger and Event applications Read
06-OCT-2011 10:36:08 - executing preaccounting hook
event key = 10-426334
06-OCT-2011 10:36:08 - preaccounting hook executed successfully
06-OCT-2011 10:36:08 - Pre-Accounting steps performed
06-OCT-2011 10:36:08 - Queue Created = XLA.XLA_426334_DOC_Q
06-OCT-2011 10:36:08 - Queue Created = XLA.XLA_426334_COMP_Q
06-OCT-2011 10:36:08 - Queue Started = XLA.XLA_426334_DOC_Q
06-OCT-2011 10:36:08 - Queue Started = XLA.XLA_426334_COMP_Q
06-OCT-2011 10:36:08 - Global Context Initialized
06-OCT-2011 10:36:08 - Calling sequencing batch_init
06-OCT-2011 10:36:08 - Returned from sequencing batch_init
06-OCT-2011 10:36:08 - Begin enqueue
06-OCT-2011 10:36:08 - Ready to Enqueue documents in the queue
06-OCT-2011 10:36:08 - Spawning unit processors
06-OCT-2011 10:36:08 - Unit processors spawned
06-OCT-2011 10:36:36 - Ready to Enqueue documents in the queue
06-OCT-2011 10:36:36 - Ready to Enqueue documents in the queue
06-OCT-2011 10:36:36 - Ready to Enqueue documents in the queue
06-OCT-2011 10:36:36 - Ready to Enqueue documents in the queue
06-OCT-2011 10:36:36 - Enqueueing completed
06-OCT-2011 10:36:36 - Waiting for Unit Processor requests to complete
06-OCT-2011 10:37:06 - Child Threads completed
06-OCT-2011 10:37:06 - Global Context cleared
06-OCT-2011 10:37:06 - Queue stopped = XLA.XLA_426334_DOC_Q
06-OCT-2011 10:37:06 - Queue stopped = XLA.XLA_426334_COMP_Q
06-OCT-2011 10:37:06 - Queue dropped = XLA.XLA_426334_DOC_Q
06-OCT-2011 10:37:06 - Queue dropped = XLA.XLA_426334_COMP_Q
06-OCT-2011 10:37:06 - Calling sequencing batch_exit
06-OCT-2011 10:37:06 - Returned from sequencing batch_exit
06-OCT-2011 10:37:06 - Executed post-accounting routine
06-OCT-2011 10:37:06 - Accounting Program completed successfully
06-OCT-2011 10:37:06 - executing postaccounting hook
event key = 10-426334
06-OCT-2011 10:37:06 - postaccounting hook executed successfully
- Accounting Time = 58.73 secs
- Transfer Time = 0 secs
06-OCT-2011 10:37:06 - End of the Report
End of log messages from FND_FILE
Executing request completion options...
Output file size:
1920
------------- 1) PUBLISH -------------
Beginning post-processing of request 426334 on node M at 06-OCT-2011 10:37:06.
Post-processing of request 426334 failed at 06-OCT-2011 10:39:06 with the error message:
The Output Post-processor is running but has not picked up this request.
No further attempts will be made to post-process this request, and the request will be marked
with Warning status.
Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary.
------------- 2) PRINT -------------
Not printing the output of this request because post-processing failed.
Finished executing request completion options.
Concurrent request completed
Current system time is 06-OCT-2011 10:39:06
Edited by: hassanksa on Oct 8, 2011 8:15 AM
Edited by: hassanksa on Oct 8, 2011 8:16 AM

One AR invoice failed to create accounting

Hi, all
We are using the Version 12.1.3
I have one AR invoice which fail to create accounting. I get the error number 95261 The account code combination 8F..ZZZZZZZZZ.000.000000.000000 is invalid. Please inform your system administrator or support representative that:
Values have not been entered for one or more required segments
When I run the report "Subledger Period Close Exception". It shows the event class status is Invalid. But I can create accounting for the other invoices which share the same information as this one.
Seek for help,thanks
Shirley

8F..ZZZZZZZZZ.000.000000.000000Looking like the second segment is empty.
Please crosscheck the SLA setup for the Account Derivation Rules (ADR) attached to the Journal Line Type, for which the CCID is in error.
There is no point in running the report "Subledger Period Close Exception", as anyway your Create Accounting says the event is in error.
By
Vamsi

Create accounting error :APP-SQLAP-100000, ora-00000

afer validate the AP credit memo. create accounting occured the error as below
the first form 'NOTE :create accounting successfully'
the secone form 'ERROR APP-SQLAP-10000:.........(x_rowid=AAAAHTUAAXAABIDYAA,X_invoice_id= 34345 ,ap_in:normal, successful completion : after callling AP_ETAK_SERVERICE_PKG,sysnchronize_for_doc_sep ()))'

Please see these docs.
Invoice Apparoval Throws Error App-Sqlap-10000 Ap_etax_services_pkg.Synchronize_for_doc_seq [ID 1158523.1]
When Cancelling An Invoice User Receives Error APPSQLAP-10000 ORA-00000 normal, successful completion occured in AP_INVOICES_PKG.UPDATE_ROW [ID 886316.1]
Error When Canceling Invoices APP-SQLAP-10000 AP_ETAX_SERVICES_PKG [ID 974712.1]
Thanks,
Hussein

Error when i create accounting

frist of all sorry if i put this message in wrong subject or wrong thread.this is my frist time in forum
dear all,
i use ebs r12 12.1.2 os Linux x86-64
when i create accounting i meet error this log :
Application Object Library: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
FNDWFBG module: Workflow Background Process
Current system time is 15-APR-2011 01:39:37
**Starts**15-APR-2011 01:39:37
**Ends**15-APR-2011 01:39:37
Start of log messages from FND_FILE
End of log messages from FND_FILE
Successfully resubmitted concurrent program FNDWFBG with request ID 450126 to start at 15-APR-2011 01:53:18 (ROUTINE=AFPSRS)
Executing request completion options...
Output is not being printed because:
The print option has been disabled for this report.
------------- 1) PRINT   -------------
Finished executing request completion options.
Concurrent request completed successfully
Current system time is 15-APR-2011 01:39:37
Subledger Accounting: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XLAACCPB module: Create Accounting
Current system time is 16-JAN-2012 12:43:15
XDO Data Engine Version No: 5.6.3
Resp: 20639
Org ID : 81
Request ID: 450125
All Parameters: P_APPLICATION_ID=200:P_SOURCE_APPLICATION_ID=200:P_DUMMY=Y:P_LEDGER_ID=2023:P_PROCESS_CATEGORY_CODE=PAYMENTS:P_END_DATE="2012/01/10 00:00:00":P_CREATE_ACCOUNTING_FLAG=Y:P_DUMMY_PARAM_1=Y:P_ACCOUNTING_MODE=D:P_DUMMY_PARAM_2=:P_ERRORS_ONLY_FLAG=N:P_REPORT_STYLE=D:P_TRANSFER_TO_GL_FLAG=:P_DUMMY_PARAM_3=:P_POST_IN_GL_FLAG=:P_GL_BATCH_NAME=test11:P_MIN_PRECISION=:P_INCLUDE_ZERO_AMOUNT_LINES=N:P_REQUEST_ID=:P_ENTITY_ID=:P_SOURCE_APPLICATION_NAME=Payables:P_APPLICATION_NAME=Payables:P_LEDGER_NAME=SMI_PL:P_PROCESS_CATEGORY_NAME=Payments:P_CREATE_ACCOUNTING=Yes:P_ACCOUNTING_MODE_NAME=Draft:P_ERRORS_ONLY=No:P_ACCOUNTING_REPORT_LEVEL=Detail:P_TRANSFER_TO_GL=:P_POST_IN_GL=:P_INCLUDE_ZERO_AMT_LINES=No: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=N:P_INCLUDE_USER_TRX_IDENTIFIERS=No:DebugFlag=Y:P_USER_ID=1110
Data Template Code: XLAACCPB
Data Template Application Short Name: XLA
Debug Flag: Y
{P_ACCOUNTING_REPORT_LEVEL=Detail, P_DUMMY=Y, P_ACCOUNTING_MODE_NAME=Draft, P_ERRORS_ONLY_FLAG=N, P_REPORT_STYLE=D, P_GL_BATCH_NAME=test11, P_END_DATE=2012/01/10 00:00:00, 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=, P_INCLUDE_USER_TRX_IDENTIFIERS=No, P_USER_ID=1110, P_PROCESS_CATEGORY_NAME=Payments, P_ERRORS_ONLY=No, P_DUMMY_PARAM_3=, P_SECURITY_CHAR_3=, P_DUMMY_PARAM_2=, P_SECURITY_CHAR_2=, P_DUMMY_PARAM_1=Y, P_SECURITY_CHAR_1=, P_ENTITY_ID=, P_PROCESS_CATEGORY_CODE=PAYMENTS, P_INCLUDE_ZERO_AMT_LINES=No, P_LEDGER_ID=2023, P_POST_IN_GL_FLAG=, P_APPLICATION_ID=200, P_INCLUDE_USER_TRX_ID_FLAG=N, P_APPLICATION_NAME=Payables, P_REQUEST_ID=, P_CONC_REQUEST_ID=, P_LEDGER_NAME=SMI_PL, P_SOURCE_APPLICATION_ID=200, P_CREATE_ACCOUNTING=Yes, P_CREATE_ACCOUNTING_FLAG=Y, P_MIN_PRECISION=, P_SOURCE_APPLICATION_NAME=Payables, P_INCLUDE_ZERO_AMOUNT_LINES=N, P_ACCOUNTING_MODE=D}
Calling XDO Data Engine...
[011612_124319140][][STATEMENT] oracle.jdbc.driver.OracleBlobInputStream@179f36b
[011612_124319242][][STATEMENT] Logger.init(): *** DEBUG MODE IS OFF. ***
[011612_124319244][][STATEMENT] DataTemplate.getTmpDir(): system-temp-dir property value from DATABASE: /usr/temp
[011612_124319246][][STATEMENT] Template parsing started...
[011612_124319389][][STATEMENT] Data Template ......
[011612_124319389][][STATEMENT] oracle.xml.parser.v2.XMLDocument@19fdbcb
[011612_124319525][][STATEMENT] Inside properties Parser...
[011612_124319525][][STATEMENT] db_fetch_size=20
[011612_124319526][][STATEMENT] Inside parameterParser...
[011612_124319527][][STATEMENT] Parameter:P_REQUEST_ID Default value:
[011612_124319527][][STATEMENT] Parameter:P_ENTITY_ID Default value:
[011612_124319527][][STATEMENT] Parameter:P_SOURCE_APPLICATION_ID Default value:
[011612_124319527][][STATEMENT] Parameter:P_SOURCE_APPLICATION_NAME Default value:
[011612_124319527][][STATEMENT] Parameter:P_APPLICATION_ID Default value:
[011612_124319527][][STATEMENT] Parameter:P_APPLICATION_NAME Default value:
[011612_124319527][][STATEMENT] Parameter:P_DUMMY Default value:
[011612_124319527][][STATEMENT] Parameter:P_LEDGER_ID Default value:
[011612_124319527][][STATEMENT] Parameter:P_LEDGER_NAME Default value:
[011612_124319527][][STATEMENT] Parameter:P_PROCESS_CATEGORY_CODE Default value:
[011612_124319528][][STATEMENT] Parameter:P_PROCESS_CATEGORY_NAME Default value:
[011612_124319528][][STATEMENT] Parameter:P_END_DATE Default value:
[011612_124319528][][STATEMENT] Parameter:P_CREATE_ACCOUNTING_FLAG Default value:
[011612_124319528][][STATEMENT] Parameter:P_CREATE_ACCOUNTING Default value:
[011612_124319528][][STATEMENT] Parameter:P_DUMMY_PARAM_1 Default value:
[011612_124319528][][STATEMENT] Parameter:P_ACCOUNTING_MODE Default value:
[011612_124319528][][STATEMENT] Parameter:P_DUMMY_PARAM_2 Default value:
[011612_124319528][][STATEMENT] Parameter:P_ERRORS_ONLY_FLAG Default value:
[011612_124319528][][STATEMENT] Parameter:P_REPORT_STYLE Default value:
[011612_124319528][][STATEMENT] Parameter:P_ACCOUNTING_MODE_NAME Default value:
[011612_124319528][][STATEMENT] Parameter:P_ERRORS_ONLY Default value:
[011612_124319528][][STATEMENT] Parameter:P_ACCOUNTING_REPORT_LEVEL Default value:
[011612_124319529][][STATEMENT] Parameter:P_TRANSFER_TO_GL_FLAG Default value:
[011612_124319529][][STATEMENT] Parameter:P_TRANSFER_TO_GL Default value:
[011612_124319529][][STATEMENT] Parameter:P_DUMMY_PARAM_3 Default value:
[011612_124319529][][STATEMENT] Parameter:P_POST_IN_GL_FLAG Default value:
[011612_124319529][][STATEMENT] Parameter:P_POST_IN_GL Default value:
[011612_124319529][][STATEMENT] Parameter:P_GL_BATCH_NAME Default value:
[011612_124319529][][STATEMENT] Parameter:P_MIN_PRECISION Default value:
[011612_124319529][][STATEMENT] Parameter:P_INCLUDE_ZERO_AMOUNT_LINES Default value:
[011612_124319529][][STATEMENT] Parameter:P_INCLUDE_ZERO_AMT_LINES Default value:
[011612_124319530][][STATEMENT] Parameter:P_VALUATION_METHOD_CODE Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_INT_1 Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_INT_2 Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_INT_3 Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_CHAR_1 Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_CHAR_2 Default value:
[011612_124319530][][STATEMENT] Parameter:P_SECURITY_CHAR_3 Default value:
[011612_124319530][][STATEMENT] Parameter:P_CONC_REQUEST_ID Default value:
[011612_124319531][][STATEMENT] Parameter:P_INCLUDE_USER_TRX_ID_FLAG Default value:
[011612_124319531][][STATEMENT] Parameter:P_INCLUDE_USER_TRX_IDENTIFIERS Default value:
[011612_124319531][][STATEMENT] Parameter:P_USER_ID Default value:
[011612_124319531][][STATEMENT] Inside dataQueryParser...
[011612_124319535][][STATEMENT] Inside dataStructureParser...
[011612_124319540][][STATEMENT] Group ...report
[011612_124319541][][STATEMENT] Group ...APPLICATION
[011612_124319542][][STATEMENT] Group ...APPLICATION_FLAG
[011612_124319543][][STATEMENT] Group ...NO_ACTION_EVT
[011612_124319544][][STATEMENT] Group ...ACCT_PROG_ERRORS
[011612_124319545][][STATEMENT] Group ...EVENT_CLASS_S
[011612_124319545][][STATEMENT] Group ...LEDGER_S
[011612_124319546][][STATEMENT] Group ...BALANCE_TYPE_S
[011612_124319547][][STATEMENT] Group ...EVENT
[011612_124319548][][STATEMENT] Group ...AE_HEADERS
[011612_124319550][][STATEMENT] Group ...AE_LINES
[011612_124319551][][STATEMENT] Group ...AE_ERRORS
[011612_124319552][][STATEMENT] Group ...NO_ENTRY_EVENTS
[011612_124319553][][STATEMENT] Template parsing completed...
[011612_124319553][][STATEMENT] Setting Data Template
[011612_124319553][][STATEMENT] Setting JDBC Connection
[011612_124319576][][STATEMENT] Paramter :P_REQUEST_ID Value :
[011612_124319642][][STATEMENT] Paramter :P_ENTITY_ID Value :
[011612_124319642][][STATEMENT] Paramter :P_SOURCE_APPLICATION_ID Value :200
[011612_124319642][][STATEMENT] Paramter :P_SOURCE_APPLICATION_NAME Value :Payables
[011612_124319642][][STATEMENT] Paramter :P_APPLICATION_ID Value :200
[011612_124319642][][STATEMENT] Paramter :P_APPLICATION_NAME Value :Payables
[011612_124319642][][STATEMENT] Paramter :P_DUMMY Value :Y
[011612_124319642][][STATEMENT] Paramter :P_LEDGER_ID Value :2023
[011612_124319642][][STATEMENT] Paramter :P_LEDGER_NAME Value :SMI_PL
[011612_124319643][][STATEMENT] Paramter :P_PROCESS_CATEGORY_CODE Value :PAYMENTS
[011612_124319643][][STATEMENT] Paramter :P_PROCESS_CATEGORY_NAME Value :Payments
[011612_124319658][][STATEMENT] Paramter :P_END_DATE Value :2012/01/10 00:00:00
[011612_124319658][][STATEMENT] Paramter :P_CREATE_ACCOUNTING_FLAG Value :Y
[011612_124319658][][STATEMENT] Paramter :P_CREATE_ACCOUNTING Value :Yes
[011612_124319658][][STATEMENT] Paramter :P_DUMMY_PARAM_1 Value :Y
[011612_124319658][][STATEMENT] Paramter :P_ACCOUNTING_MODE Value :D
[011612_124319658][][STATEMENT] Paramter :P_DUMMY_PARAM_2 Value :
[011612_124319658][][STATEMENT] Paramter :P_ERRORS_ONLY_FLAG Value :N
[011612_124319658][][STATEMENT] Paramter :P_REPORT_STYLE Value :D
[011612_124319658][][STATEMENT] Paramter :P_ACCOUNTING_MODE_NAME Value :Draft
[011612_124319658][][STATEMENT] Paramter :P_ERRORS_ONLY Value :No
[011612_124319658][][STATEMENT] Paramter :P_ACCOUNTING_REPORT_LEVEL Value :Detail
[011612_124319658][][STATEMENT] Paramter :P_TRANSFER_TO_GL_FLAG Value :
[011612_124319658][][STATEMENT] Paramter :P_TRANSFER_TO_GL Value :
[011612_124319659][][STATEMENT] Paramter :P_DUMMY_PARAM_3 Value :
[011612_124319659][][STATEMENT] Paramter :P_POST_IN_GL_FLAG Value :
[011612_124319659][][STATEMENT] Paramter :P_POST_IN_GL Value :
[011612_124319659][][STATEMENT] Paramter :P_GL_BATCH_NAME Value :test11
[011612_124319750][][STATEMENT] Paramter :P_MIN_PRECISION Value :
[011612_124319751][][STATEMENT] Paramter :P_INCLUDE_ZERO_AMOUNT_LINES Value :N
[011612_124319751][][STATEMENT] Paramter :P_INCLUDE_ZERO_AMT_LINES Value :No
[011612_124319751][][STATEMENT] Paramter :P_VALUATION_METHOD_CODE Value :
[011612_124319772][][STATEMENT] Paramter :P_SECURITY_INT_1 Value :
[011612_124319837][][STATEMENT] Paramter :P_SECURITY_INT_2 Value :
[011612_124319891][][STATEMENT] Paramter :P_SECURITY_INT_3 Value :
[011612_124319891][][STATEMENT] Paramter :P_SECURITY_CHAR_1 Value :
[011612_124319891][][STATEMENT] Paramter :P_SECURITY_CHAR_2 Value :
[011612_124319892][][STATEMENT] Paramter :P_SECURITY_CHAR_3 Value :
[011612_124319958][][STATEMENT] Paramter :P_CONC_REQUEST_ID Value :
[011612_124319958][][STATEMENT] Paramter :P_INCLUDE_USER_TRX_ID_FLAG Value :N
[011612_124319958][][STATEMENT] Paramter :P_INCLUDE_USER_TRX_IDENTIFIERS Value :No
[011612_124319958][][STATEMENT] Paramter :P_USER_ID Value :1110
[011612_124319958][][STATEMENT] Setting Parameters
[011612_124319958][][STATEMENT] Setting Parameters
[011612_124319960][][STATEMENT] Start process Data
[011612_124319960][][STATEMENT] Process Data ...
[011612_124319966][][STATEMENT] Executing data triggers...
[011612_124319966][][STATEMENT] BEGIN
XLA_CREATE_ACCT_RPT_PVT.P_REQUEST_ID := :P_REQUEST_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_ENTITY_ID := :P_ENTITY_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_SOURCE_APPLICATION_ID := :P_SOURCE_APPLICATION_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_SOURCE_APPLICATION_NAME := :P_SOURCE_APPLICATION_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_APPLICATION_ID := :P_APPLICATION_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_APPLICATION_NAME := :P_APPLICATION_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_DUMMY := :P_DUMMY ;
XLA_CREATE_ACCT_RPT_PVT.P_LEDGER_ID := :P_LEDGER_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_LEDGER_NAME := :P_LEDGER_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_PROCESS_CATEGORY_CODE := :P_PROCESS_CATEGORY_CODE ;
XLA_CREATE_ACCT_RPT_PVT.P_PROCESS_CATEGORY_NAME := :P_PROCESS_CATEGORY_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_END_DATE := :P_END_DATE ;
XLA_CREATE_ACCT_RPT_PVT.P_CREATE_ACCOUNTING_FLAG := :P_CREATE_ACCOUNTING_FLAG ;
XLA_CREATE_ACCT_RPT_PVT.P_CREATE_ACCOUNTING := :P_CREATE_ACCOUNTING ;
XLA_CREATE_ACCT_RPT_PVT.P_DUMMY_PARAM_1 := :P_DUMMY_PARAM_1 ;
XLA_CREATE_ACCT_RPT_PVT.P_ACCOUNTING_MODE := :P_ACCOUNTING_MODE ;
XLA_CREATE_ACCT_RPT_PVT.P_DUMMY_PARAM_2 := :P_DUMMY_PARAM_2 ;
XLA_CREATE_ACCT_RPT_PVT.P_ERRORS_ONLY_FLAG := :P_ERRORS_ONLY_FLAG ;
XLA_CREATE_ACCT_RPT_PVT.P_REPORT_STYLE := :P_REPORT_STYLE ;
XLA_CREATE_ACCT_RPT_PVT.P_ACCOUNTING_MODE_NAME := :P_ACCOUNTING_MODE_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_ERRORS_ONLY := :P_ERRORS_ONLY ;
XLA_CREATE_ACCT_RPT_PVT.P_ACCOUNTING_REPORT_LEVEL := :P_ACCOUNTING_REPORT_LEVEL ;
XLA_CREATE_ACCT_RPT_PVT.P_TRANSFER_TO_GL_FLAG := :P_TRANSFER_TO_GL_FLAG ;
XLA_CREATE_ACCT_RPT_PVT.P_TRANSFER_TO_GL := :P_TRANSFER_TO_GL ;
XLA_CREATE_ACCT_RPT_PVT.P_DUMMY_PARAM_3 := :P_DUMMY_PARAM_3 ;
XLA_CREATE_ACCT_RPT_PVT.P_POST_IN_GL_FLAG := :P_POST_IN_GL_FLAG ;
XLA_CREATE_ACCT_RPT_PVT.P_POST_IN_GL := :P_POST_IN_GL ;
XLA_CREATE_ACCT_RPT_PVT.P_GL_BATCH_NAME := :P_GL_BATCH_NAME ;
XLA_CREATE_ACCT_RPT_PVT.P_MIN_PRECISION := :P_MIN_PRECISION ;
XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_ZERO_AMOUNT_LINES := :P_INCLUDE_ZERO_AMOUNT_LINES ;
XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_ZERO_AMT_LINES := :P_INCLUDE_ZERO_AMT_LINES ;
XLA_CREATE_ACCT_RPT_PVT.P_VALUATION_METHOD_CODE := :P_VALUATION_METHOD_CODE ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_INT_1 := :P_SECURITY_INT_1 ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_INT_2 := :P_SECURITY_INT_2 ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_INT_3 := :P_SECURITY_INT_3 ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_CHAR_1 := :P_SECURITY_CHAR_1 ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_CHAR_2 := :P_SECURITY_CHAR_2 ;
XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_CHAR_3 := :P_SECURITY_CHAR_3 ;
XLA_CREATE_ACCT_RPT_PVT.P_CONC_REQUEST_ID := :P_CONC_REQUEST_ID ;
XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_USER_TRX_ID_FLAG := :P_INCLUDE_USER_TRX_ID_FLAG ;
XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_USER_TRX_IDENTIFIERS := :P_INCLUDE_USER_TRX_IDENTIFIERS ;
XLA_CREATE_ACCT_RPT_PVT.P_USER_ID := :P_USER_ID ;
:XDO_OUT_PARAMETER := 1;
END;
[011612_124319966][][STATEMENT] 1:null :
[011612_124319966][][STATEMENT] 2:null :
[011612_124319967][][STATEMENT] 3:200 :
[011612_124319967][][STATEMENT] 4:Payables :
[011612_124319967][][STATEMENT] 5:200 :
[011612_124319967][][STATEMENT] 6:Payables :
[011612_124319967][][STATEMENT] 7:Y :
[011612_124319967][][STATEMENT] 8:2023 :
[011612_124319967][][STATEMENT] 9:SMI_PL :
[011612_124319967][][STATEMENT] 10:PAYMENTS :
[011612_124319967][][STATEMENT] 11:Payments :
[011612_124319968][][STATEMENT] 12:2012-01-10 00:00:00.0 :
[011612_124319968][][STATEMENT] 13:Y :
[011612_124319968][][STATEMENT] 14:Yes :
[011612_124319968][][STATEMENT] 15:Y :
[011612_124319968][][STATEMENT] 16:D :
[011612_124319968][][STATEMENT] 17: :
[011612_124319968][][STATEMENT] 18:N :
[011612_124319968][][STATEMENT] 19:D :
[011612_124319968][][STATEMENT] 20:Draft :
[011612_124319968][][STATEMENT] 21:No :
[011612_124319968][][STATEMENT] 22:Detail :
[011612_124319968][][STATEMENT] 23: :
[011612_124319968][][STATEMENT] 24: :
[011612_124319968][][STATEMENT] 25: :
[011612_124319968][][STATEMENT] 26: :
[011612_124319968][][STATEMENT] 27: :
[011612_124319968][][STATEMENT] 28:test11 :
[011612_124319969][][STATEMENT] 29:null :
[011612_124319969][][STATEMENT] 30:N :
[011612_124319969][][STATEMENT] 31:No :
[011612_124319969][][STATEMENT] 32: :
[011612_124319969][][STATEMENT] 33:null :
[011612_124319969][][STATEMENT] 34:null :
[011612_124319969][][STATEMENT] 35:null :
[011612_124319969][][STATEMENT] 36: :
[011612_124319969][][STATEMENT] 37: :
[011612_124319969][][STATEMENT] 38: :
[011612_124319969][][STATEMENT] 39:null :
[011612_124319969][][STATEMENT] 40:N :
[011612_124319969][][STATEMENT] 41:No :
[011612_124319969][][STATEMENT] 42:1110 :
[011612_124319971][][STATEMENT] Executing data triggers...
[011612_124319971][][STATEMENT] Declare
l_flag Boolean;
BEGIN
l_flag := XLA_CREATE_ACCT_RPT_PVT.BeforeReport ;
if (l_flag) then
:XDO_OUT_PARAMETER := 1;
end if;
end;
[011612_124319994][][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.
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 275
ORA-06512: at line 4
     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
     at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:191)
     at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:950)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1225)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3488)
     at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:3857)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
     at oracle.apps.xdo.dataengine.XMLPGEN.executeTriggers(XMLPGEN.java:650)
     at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:263)
     at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:215)
     at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:254)
     at oracle.apps.xdo.dataengine.DataProcessor.processDataStructre(DataProcessor.java:390)
     at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:355)
     at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:334)
     at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:294)
     at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Oracle error 20100: java.sql.SQLException: ORA-20100: Error: FND_FILE failure. Unable to create file, o0010400.tmp in the directory, /usr/tmp.
You will find more information in the request log.
ORA-06512: at "APPS.FND_FILE", line 417
ORA-06512: at "APPS.FND_FILE", line 526
ORA-06512: at "APPS.FND_CONCURRENT", line 1328
ORA-06512: at line 1
has been detected in FND_CONCURRENT.SET_INTERIM_STATUS.+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PUBLISH -------------
Beginning post-processing of request 450125 on node ORAAPPS at 16-JAN-2012 12:43:20.
Post-processing of request 450125 failed at 16-JAN-2012 12:43:21 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
Finished executing request completion options.
Concurrent request completed
Current system time is 16-JAN-2012 12:43:21
anyone have same problem and already solving ??
Thanks,
Mahardika

[011612_124319994][][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.
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 275
ORA-06512: at line 4Please make sure you have no invalid objects.
Please also see these docs.
R12: Ap Invoice Online Accounting with Final Post Ends With Errors ORA-20001 XLA-95103 [ID 853424.1]
FAACCPB Create Accounting Internal Error xla_create_acct_rpt_pvt.BeforeReport [ID 783493.1]
CSTCRACC Create Accounting Err ORA-20001 Xla-95103 Internal Error Occurred ORA-01400 [ID 1309124.1]
CSTCRACC - Create Accounting - Cost Management Completes With Errors: java.sql.SQLException, ORA-20001, XLA-95103 [ID 1252703.1]
Create Accounting Concurrent Program Errors - ORA-20001 XLA-95103 [ID 1392267.1]
Create Accounting Error Due To Invalid Package Apps.Ap_payment_extract_details_v [ID 1366269.1]
------------- 1) PUBLISH -------------
Beginning post-processing of request 450125 on node ORAAPPS at 16-JAN-2012 12:43:20.
Post-processing of request 450125 failed at 16-JAN-2012 12:43:21 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
Also check OPP log file ($APPLCSF/$APPLLOG/FNDOPP* file).
Thanks,
Hussein

Create Accounting error for receipt reversal

Hi
Hope every one is well and upbeat over here. I am facing an issue in the receivables module and some expert's kind assistance is required.
A client entered a Miscellaneous receipt, the customer made the payment through credit card. The receipt was later reversed, When the client runs the create accounting report, it gives the following error
Line Error Number Error Message
0 The accounted amount and entered amount for the subledger jounral entry line have different sign. Please inform your system administrator or support representative that:
The sources assigned to the accounting attributes Accounted Amount and Entered Amount have different sign for extract line number 738414. Please make sure the sources assigned to the two accounting attributes have same sign, or assign different sources to these accounting attributes.
there is another error message which is:
The subledger journal entry does not balance in the entered currency. Please verify the entered amounts on the journal entry lines.
Please provide me with a solution to this problem.
Regards
Salman Tariq

Please see these docs.
Invoice Apparoval Throws Error App-Sqlap-10000 Ap_etax_services_pkg.Synchronize_for_doc_seq [ID 1158523.1]
When Cancelling An Invoice User Receives Error APPSQLAP-10000 ORA-00000 normal, successful completion occured in AP_INVOICES_PKG.UPDATE_ROW [ID 886316.1]
Error When Canceling Invoices APP-SQLAP-10000 AP_ETAX_SERVICES_PKG [ID 974712.1]
Thanks,
Hussein

Good Issue Using BAPI WS_DELIVERY_UPDATE but didn't create accounting doc

Hi Gurus,
i have some problem using BAPI WS_DELIVERY_UPDATE.
in our company. once finance unblock delivery block at sales order then that sales order should be automatic DO/GI.
to accomodate this request i use BAPI BAPI_OUTB_DELIVERY_CREATE_SLS to create DO and BAPI WS_DELIVERY_UPDATE to create GI from DO in one function module. this method was succesfull. +but the problem is when i am only execute BAPI WSDELIVERY_UPDATE to create GI (GI creation failed because : stock deficit,material already lock by another process). the GI document did not create accounting document.+
can any one help me.
thanks in advance
Best Regard,
Akbar.

Dear Mr Akbar,
Could we kindly verify for a possible update termination?
The terminated transaction may be re-executed to complete the transaction!!
Regards,
K Gopidas.

Error creating accounting document for a credit note

Hi All,
I am facing an issue while creating an accounting document for the credit note created.
The scenario is as follows:
Created a credit memo --> created credit note --> create accounting document
While creating accounting document, i'm getting an error message as 'The G/L account XXXXXXXX requires an assignement to CO object'.
Please let me know why i'm getting this error and how to overcome this issue.
Thanks,
Anil Kumar

While creating accounting document,
i'm getting an error message
First of all, I am not clear on your above statement as in normal circumstances, once you generate a credit memo, in bacground an accounting document will also be generated.
In your case, I believe while saving the credit memo, system throws the error to maintain CO object in which case, do the following:-
Go to TCode KA02 enter the controlling area, give the G/L acoount No and click on Master data tab. There select "Default Acc Assgmnt" tab and enter Cost centr and save.
Next Go to FS00, input the G/L Account and click on Edit Cost Element on top. There click on Basic Data and for the field CElem category, maintain the required numeric value. Now select the tab Default Acct Assgnmt and there maintain the required cost center and save.
thanks
G. Lakshmipathi

Field to create accounting in AP-Payment

Actually I have EBS r12 on win2003, sysdate is today 1/15/2012 Oracle apps year still in 2009 which the same year of installation, I will close the prior year and open the current year as a physical year, but before that i want to insert the opening balance for 2009 to particular vendors, I have started to create invoices and post final to GL it was successfully but the problem when I tried to create a Payments for the invoices which created showing error message "Online accounting could not be created for this transaction. Please submit the Create accounting Concurrent program with the report parameter set to Detail to determine the problem" note that the date for the invoices and payments was on Sept-2009 which opened Period in GL and in AP
I run the "Create Accounting" it's complete but with warning and the output is XML
the log :
Start of log messages from FND_FILE
09-Sep-2009 10:36:08 - Beginning of the Report
09-Sep-2009 10:36:08 - Starting of the Parent Thread
Starting main program for the source application = 200
09-Sep-2009 10:36:08 - Dynamic conditions built
09-Sep-2009 10:36:08 - Event Applications Determined
09-Sep-2009 10:36:08 - Security Context Set
09-Sep-2009 10:36:08 - Session Identifier Set
. . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . .., etc.
So could you please help me what I have to do
Best Regard,
Ebrahim Alturk

Try Submitting Create Accounting again with the Report Mode as Summary.
Still XML, then try to check the data in xla_accounting_errors.
If that is huge.
Query for a Payment, which is giving error in online accounting.
Use the following sqls to find out the error.SELECT entity_id
FROM xla.xla_transaction_entities
WHERE application_id = 200
AND ledger_id = &ledger_id
AND entity_code = 'AP_PAYMENTS'
AND NVL(source_id_int_1) = &check_id; -- get it from Help -> Diagnostics -> Examine
SELECT event_id, event_status_code, process_status_code
FROM xla_events
WHERE application_id = 200
AND entity_id = &entity_id; -- get it from above sql
SELECT *
FROM xla_accounting_errors
WHERE application_id = 200
AND event_id in (&event_id); -- place the event_ids from above sql,
--which are not having process_status_code as PBy
Vamsi

Create Accounting could not be done after voiding some payment.

Hi,
I am facing a unique problem. We have some payments which have been accounted properly and transferred to GL. But for some business issue we have to cancel those payments. But when we have voided those payments and tried to create account it it showed message "App-SQLAP-10710: Online Accounting could not be created please submit payables accounting process istead to create accounting entries for this transaction." But when I ran the Payables Accounting Process the problem remains. Now we are facing problem because we are having Period Close Exceptions Report.
Please help me.
Rubayat Newaz Khan

Hi Rubayat;
I am facing a unique problem. We have some payments which have been accounted properly and transferred to GL. But for some business issue we have to cancel those payments. But when we have voided those payments and tried to create account it it showed message "App-SQLAP-10710: Online Accounting could not be created please submit payables accounting process istead to create accounting entries for this transaction." But when I ran the Payables Accounting Process the problem remains. Now we are facing problem because we are having Period Close Exceptions Report. What is your EBS version and OS?
Please follow below and see its helpful:
APACCENG APP-SQLAP-10710 Create Accounting does not process for Cancelled Invoice and for Voided Payment [ID 124469.1]
Accounting For Voided Payment Fails with APP-SQLAP-10710 [ID 229910.1]
Online Accounting Could Not Be Created For Standard Invoice [ID 401709.1]11.5 AP APXPAWKB:Cannot Run Create Accounting For A Reconciled Payment. [ID 233823.1]
APACCENG - Cannot Account For a Prepayment [ID 200693.1]
Regard
Helios

Create Accounting in invoice and Create accounting in payment terms?

hi,
I want to know the difference between create accounting in invoice and create accounting in payment terms and is it compulsory to validate and create accounting in invoice before making payments ?
Regards
Sudharshan

If the accounting method is accrual, then invoice accounting will be Item Expense/Charge -> Liability.
And payment accounting will be Liability -> Cash (it is different if you have reconciliation also)
An invoice has to be validated to get accounted or to get paid.
Payment just need a validated invoice, not an accounted invoice.
But Payment accounting can be done only after the invoice is accounted.
By
Vamsi

R12 AP create account process success while no journal entries produced

Hi,
Enviroment:12.0.4
in AP, the invoice validate and create account all done successfully. while to query journal entries, there isn't any produced journal entries.
During the create account process, there is no error message, therefore i cann't find what is the problem.
can anyone give me a guide to how to find the problem is?or what the problem is ?
any help will be appreaciated.
Regards,
Chelsea

just to give a background of this process in R12
As we know there are two methods to create Payables Accounting in R12,
1.Online Accounting method
The Online Accounting method can be called from either the Invoice or Payment workbench and has the following modes:
Draft - The accounting is only created in the XLA Subledger tables and is not transferred to the General Ledger. Draft accounting can be recreated based on changes to the transaction data or accounting rules.
Final - The accounting is created in the XLA Subledger tables and is not transferred to the General Ledger. Accounting created in final mode can not be recreated/altered. Run the Transfer Journal Entries to GL program to transfer these entries from the XLA subledger tables to the General Ledger tables.
Final Post - The accounting is created in the XLA Subledger tables and is also transferred and posted to the General Ledger tables.
2)Create Accounting process.
The Create Accounting process has similar options, you can create accounting in Final or Draft mode and if Final mode is selected, the Transfer to GL parameter can be used to automatically transfer the accounting created by the corresponding run. When the Create Accounting process transfers the journal entries to GL it only transfers the accounting created by the process that calls it. If there is accounting created by the online option = Final or a previous Create Accounting program that was not transferred, that accounting will not be transferred. The Transfer Journal Entries to GL program needs to be ran separately to transfer any accounting created online or created by a previous Create Accounting process that did not transfer the entries.
Based on the above cases, the following are possible causes of journal entries not transferred in R12:
1. The accounting is created in Draft mode and can not be transferred.
2. The accounting is created in error and can not be transferred.
3. The accounting was created by Online Accounting with Final Mode.
4. The accounting was created by the Create Accounting process with Transfer to General Ledger = No
Hope this makes a clear understanding and you know the root cause.

How to create account group in mass

Hi, is there anybody who knows a BAPI to create account group, this process is normally made from KDH1, but I want to create a thousound of groups and i think that the best way is an ABAP program.
Regards.

Yes you can create cost elements in a batch session automatically.
Please use tcode OKB2 for default settings.
Define batch input session - OKb3
Execute batch session : SM35
Regards

Get message "Error creating account: Incoming server already exists."

trying to set up new IMAP account and get message "Error creating account: Incoming server already exists." Changed settings manually, but same error message.

''ScottNH [[#question-1040338|said]]''
<blockquote>
trying to set up new IMAP account and get message "Error creating account: Incoming server already exists." Changed settings manually, but same error message.
</blockquote>
I have been getting this too (for the last two days - on at least a dozen tries).
I am Running Win7 and already have three POP accounts.
All definitely have the incoming server pop.googlemail.com
I wanted to add a new IMAP account, so in T'Bird
Tools.... Account Settings
Account Actions ..... Add Mail Account
Filled in
my name,
the email address ([email protected] - and in gmail this mail account
was created as IMAP),
password (with a tick to remember this)
... continue
and it then detected the mail setup as IMAP,
Incoming : IMAP, imap.googlemail.com , SSL
Outgoing : SMTP, smtp.googlemail.com , SSL
Username: [email protected]
but when I then clicked on Done
it said Error Creating Account - Incoming server already exists.
And if I then clicked on OK followed by Manual Config, it then showed
in the Mail Account Setup
Incoming: IMAP imap.googlemail.com 993 SSL/TLS Normal Password
and again if I then clicked Done it gave the same error message as before.
(and I have screenshots to support all of this).
But I do not know if someone has been working on a fix to T'Bird or googlemail, because just now when I did it yet again in order to make a final check that what I have been writing here is correct , this time I did NOT get the error message and the new account has been setup!!!!!
So do others find this has now been cleared too?

AR Transaction Create Accounting Error APP-AR-96282

HI Everyone,
I need some urgent help.
I can't create online accounting of AR transaction because of Error: APP-AR-96282.
Autoaccounting has generated distributions for invoice properly & invoice is complete. Online Create accounting & even Accounting process is not able to generate accounting.
I couldn't find any related material on metalink as well. Can anyone provide help ?
Regards,
Fahd
Edited by: Fahd Khan on Aug 17, 2010 5:06 AM

also doesn't produce any output or list any error.Check http://www.orafaq.com/node/2245
Even it doesn't pick the transactions for accounting. Just receipts are getting accounted by Create Accounting program.Have you passed 'Receipts' for the Process Category parameter? If yes, leave it blank.
Get AR Diagnostics Test Collection for that transaction and check whether the xla_transaction_entities / xla_events are proper.
What is the event_status_code and process_status_code for event in xla_events?
By
Vamsi

Create accounting fails validate accounting def. completes normal

Similar Messages

Maybe you are looking for