OracleApps Epicenter

Odyssey of an OracleApps Consultant

Get Updates! Subscribe to the OracleAppsHub to receive notifications when there are new posts:
Enter your email ad sign up

Categories 11i AOL API Integration Asset Basic Accounting Beginner Beyond Apps Blogroll Cash Management Centrestage Conversion Depot Repair EBS Suite EDI Emerging Technologies Finance

Functional Fusion Fusion Application General Interest HRMS Implementations Integration InterCompany JumpStart Methodology/Process Misc News OPM Oracle Application Oracle Diagnostics Oracle E-Business Tax Oracle General Ledger Oracle Legal Entity Configurator Oracle Manufacturing Oracle Order Management Oracle Payable Oracle Payment Module Oracle Pricing Oracle Product Oracle Purchasing Oracle Receivable Oracle TCA Oracle Treasury Personalizations R12 Release12 Report Manager SEPA Subledger Accounting Technical Tool Uncategorized Web ADI XBRL XML Publisher Archives May 2011 April 2011 March 2011

February 2011 January 2011 December 2010 November 2010 September 2010 August 2010 June 2010 May 2010 September 2009 May 2009 April 2009 March 2009 February 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008 July 2008 June 2008 May 2008 April 2008 March 2008 February 2008 January 2008 December 2007 November 2007 October 2007 September 2007 August 2007 July 2007 June 2007 May 2007 April 2007 March 2007 February 2007 January 2007 December 2006 October 2006 August 2006 Links Metalink Oracle

Oracle Integration Repository Disclaimer Disclaimer Meta: RSS Comments RSS Valid XHTML eMail Ad

Search
Search

Powered Search

Recent Posts User Management Reporting Integrate with Oracles iPhone App FA Tax Book Implementation Its all about GL Drilldown Identity Management for Oracle R12 E-Business Suite Blogroll David Haimes Floyd Teter Steven Chan Tim Dexter

Trioragroup Blog Total Page View User Onlines 37 Users

Sub Ledger Accounting Technical perspective

SLA(Sub Ledger Accounting) -Characteristics All SLA data is stored in SLA and is imported to GL from SLA. A protocol exists to ensure all subledgers are transferring data into SLA consistently Creates the final accounting for Subledger Journal Entries (JEs) and transfers the accounting to GL During reconciliation subledgers to GL, all reconciliation reports point to the SLA tables Concurrent program used to transfer data into SLA and import to GL. SLA Can Fill In Individual Segments or Entire AFF SLA Can Create Multiple Representations of Each Subledger Transactions Stores a complete and balanced Subledger JE in a common model for each business event that requires accounting Process & Program for Subleder Accounting: Transfer to GL Process Oracle EBS's accounting process is basically a 2 step process: 1. Step 1. Create Accounting 2. Step 2. Transfer Journal Entries to GL

Create Accounting :This is one step process for transferring accounting entries to GL from Sub ledgers like AR, AP,FA,CM... You need to submit this concurrent programs 1. Accounting Program. This creates Journals and generates output detailing the Transfer/Error details of events depending on input Parameters 2. Journal Import. This transfers Journals to GL. May also post depending on Input Parameters 3. Subledger Accounting Balances Update Transfer Journal Entries to GL :The Transfer Journal Entries to GL program enables you to transfer any eligible journal entries to General Ledger, including those from previous batch runs that have not yet been transferred to General Ledger. This one also picks up online final accounted Transactions not transferred to GL You need to submit this concurrent programs 1. Journal Import. This transfers Journals to GL. May also post depending on Input Parameters SLA Technical As discussed in earlier post, all subledger table is tighten with SLA specific table. Here is one of the example of AR.

New Functionality in Release 12 Sub ledger Accounting Inquiry : where you can view Detailed Transaction and Full Journal Entry ,which can be exported to Excel. The form will display data under these three tabs: 1. Subledger Journal Entries 2. Accounting Events 3. Supporting Reference Balances Accounting Modes In SLA Accounting created in two mode either Draft or Final mode, the difference between these two is ;

Draft: where you can Review Report and Correct errors Final: where you can directly transfer to GL and Post in GL There is one Profile Option which you need to set ...SLA: Disable Journal Import set to No by default. Important SLA Reports Subledger Accounting provides the following reports 1. Journal Entries Report o Seeded data extract provides over 100 columns of data 2. Account Analysis Report o Seeded come with data extract over 100 columns of data. o This is based out of XML Publisher. 3. Third Party Balances. 4. Multiperiod Accounting Reports 5. Open Account Balances (Trial Balance) :This report displays balances created by subledger transactions and detail transactions supporting the balance. A variety of seeded BI Publisher Templates are included to provide multiple representations/ summary levels of the data. o Open Balance Definitions are configurable. o Seeded data extracts provide over 90 columns of data. o Default templates are based out of Group by Account, Applied Transaction Detail o To Run an Open Account Balances Listing, check out old post . Create Open Account Balances Listing Definitions Run Request: Open Account Balances Data Manager (automatically run as part of GL Posting) Run Request: Open Account Balances Listing, select applicable parameters 6. Period Close Exceptions Report -Review the subledger period close exceptions report when closing the GL period.You can define roles and responsibilities for exceptions. Will listout some other reporting requirement for Month end reconciliation in another post. SLA Objects There are more than 2,100 objects have been added to the E-Business Suite database due to SLA. select object_type,count(*) from dba_objects where object_namelike '%XLA%' group by object_type; SLA Diagnostics SLA Diagnostics provides features to review the SLA journal entries created. This helps you to:

review the source values available in the transaction objects during implementation/testing. analyze issues related to the generation of subledgerjournal entries You can enable this features by: Setting Profile Option-SLA: Enable Diagnostics to Yes Enter Transactions Run Request: Create Accounting Run Request: Transaction Objects Diagnostics

Fig

iagnostic Framework Business Process flow

You can run Transaction Objects Diagnostics Request directly from Oracle as shown below:

Similar Post R12 SLA: Analyzing Subledger Accounting R12 SLA: Transaction Account Builder R12 SLA: From Product Accounting to Subledger Accounting R12 SLA: Accounting Methods Builder Posted in Subledger Accounting | 10 Comments Email This Post | Print This Post

Have you joined OracleappsHub CommunityNetwork Forums ? Don't wait. Do it today 10 Responses 1. Manish Says:
October 9th, 2008 at 6:37 am

Great post as always. A fundamental question thats faced by companies that venture into implementing Oracle Financials is how best to convert/migrate legacy GL data into Oracle GL and then all the other subledgers. Do you have any pointers to documentation and/or articles online which describe this process step by step? If you look at the GL Users guide (for example for R12), theres a chapter on using GL_INTERFACE, but thats from a technical point of view and does not really talk about

how to go about loading opening balances, whether to load by period, reconcile each period and close period before loading another period etc. 2. Gareth Roberts Says:
October 10th, 2008 at 1:53 am

Nice post! 3. Nenad Says:

Hi Sanjit, Maybe you can help. We are experiencing a major showstopper using 12.0.4 with the RUP5 for Financials and CPC March 2009 applied and Oracle Support cannot solve more then a month. Here is the part of the log file for the Create Accounting program. Sometimes it works and sometimes it does not. Crazy! XLAACCPB module: Create Accounting ++ Current system time is 24-APR-2009 14:46:55 ++ XDO Data Engine Version No: 5.6.3 Resp: 50637 Org ID : 864 Request ID: 1062547 All Parameters: P_APPLICATION_ID=200:P_SOURCE_APPLICATION_ID=:P_DUMMY=:P_LEDG ER_ID=2022:P_PROCESS_CATEGORY_CODE=:P_END_DATE=:P_CREATE_ACC OUNTING_FLAG=N:P_DUMMY_PARAM_1=:P_ACCOUNTING_MODE=:P_DUM MY_PARAM_2=:P_ERRORS_ONLY_FLAG=N:P_REPORT_STYLE=D:P_TRANSFE R_TO_GL_FLAG=Y:P_DUMMY_PARAM_3=:P_POST_IN_GL_FLAG=Y:P_GL_BA TCH_NAME=:P_MIN_PRECISION=:P_INCLUDE_ZERO_AMOUNT_LINES=:P_RE QUEST_ID=:P_ENTITY_ID=20023:P_SOURCE_APPLICATION_NAME=:P_APPLI CATION_NAME=:P_LEDGER_NAME=:P_PROCESS_CATEGORY_NAME=:P_CRE ATE_ACCOUNTING=:P_ACCOUNTING_MODE_NAME=:P_ERRORS_ONLY=:P_ ACCOUNTING_REPORT_LEVEL=:P_TRANSFER_TO_GL=:P_POST_IN_GL=:P_IN CLUDE_ZERO_AMT_LINES=:P_VALUATION_METHOD_CODE=:P_SECURITY_I NT_1=:P_SECURITY_INT_2=:P_SECURITY_INT_3=:P_SECURITY_CHAR_1=:P_S ECURITY_CHAR_2=:P_SECURITY_CHAR_3=:P_CONC_REQUEST_ID=:P_INCLU DE_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=20023, P_PROCESS_CATEGORY_CODE=, P_INCLUDE_ZERO_AMT_LINES=, P_LEDGER_ID=2022, P_POST_IN_GL_FLAG=Y, P_APPLICATION_ID=200, 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=, P_SOURCE_APPLICATION_NAME=, P_INCLUDE_ZERO_AMOUNT_LINES=, P_ACCOUNTING_MODE=} Calling XDO Data Engine [042409_024657272][][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-95293:.. 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 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:9

65) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.jav a: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) 4. Sanjit Anand Says:
May 25th, 2009 at 5:45 pm

the catch here is ORA-20001: -: XLA-95103: If I am not wrong, this is known issue in Oracle which is caused by Profile Option SLA: Enable Trace. Try this way: Change the setup for the Profile Option SLA: Enable Trace and be set it to NULL at all levels: Site, Application, Responsibility, User. If still getting error, I would advice raise an SR. 5. Mustafa Says:
June 8th, 2009 at 5:36 pm

Hi Sanjit, thank you for your wonderful blog it is very useful to me. can you please clarify how to disable Final Posting from subledgers. In many places only GL users are authorized for posting. I need to disable final posting from subledgers and also disable it in the create accounting program. Thanks 6. Vanitha Says:
June 9th, 2009 at 4:13 am

Any idea on this warning message in Create Accounting Program ? ORA-20002: 3207: User XXX does not have access to notification 51827. ORA-06512: at APPS.WF_ADVANCED_WORKLIST, line 82 ORA-06512: at line 1 Subledger Accounting: Version : 12.0.0 Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved. XLAACCPB module: Create Accounting + -+ Current system time is 05-JUN-2009 19:49:48 + -+ XDO Data Engine Version No: 5.6.3 Resp: 50543 Org ID : 102 Request ID: 1922153 All Parameters: P_SOURCE_APPLICATION_ID=200:P_APPLICATION_ID=200:P_DUMMY=Y:P_L EDGER_ID=2 033:P_PROCESS_CATEGORY_CODE=:P_END_DATE=2009/06/07 00:00:00:P_CREATE_ACCOUNTING_FLAG=Y:P_DUMMY_PARAM_1=Y:P_ACC OUNTING_MODE =F:P_DUMMY_PARAM_2=Y:P_ERRORS_ONLY_FLAG=N:P_REPORT_STYLE=D: P_TRANSFER_TO _GL_FLAG=Y:P_DUMMY_PARAM_3=Y:P_POST_IN_GL_FLAG=Y:P_GL_BATCH _NAME=:P_MIN_ PRECISION=:P_INCLUDE_ZERO_AMOUNT_LINES=N:P_REQUEST_ID=:P_ENTI TY_ID=:P_SO URCE_APPLICATION_NAME=Payables:P_APPLICATION_NAME=Payables:P_LE DGER_NAME =ZEBRA UK GBP:P_PROCESS_CATEGORY_NAME=:P_CREATE_ACCOUNTING=Yes:P_ACC OUNTING_MODE_N AME=Final:P_ERRORS_ONLY=No:P_ACCOUNTING_REPORT_LEVEL=Detail:P_ TRANSFER_T O_GL=Yes:P_POST_IN_GL=Yes:P_INCLUDE_ZERO_AMT_LINES=No:P_VALUA TION_METHOD _CODE=:P_SECURITY_INT_1=:P_SECURITY_INT_2=:P_SECURITY_INT_3=:P_S

ECURITY_ CHAR_1=:P_SECURITY_CHAR_2=:P_SECURITY_CHAR_3=:P_CONC_REQUEST _ID=:P_INCLU DE_USER_TRX_ID_FLAG=N:P_INCLUDE_USER_TRX_IDENTIFIERS=No:P_USE R_ID=0:Debu gFlag=N Data Template Code: XLAACCPB Data Template Application Short Name: XLA Debug Flag: N {P_ACCOUNTING_REPORT_LEVEL=Detail, P_DUMMY=Y, P_ACCOUNTING_MODE_NAME=Final, P_ERRORS_ONLY_FLAG=N, P_REPORT_STYLE=D, P_GL_BATCH_NAME=, P_END_DATE=2009/06/07 00:00:00, P_SECURITY_INT_3=, P_SECURITY_INT_2=, P_SECURITY_INT_1=, P_VALUATION_METHOD_CODE=, P_POST_IN_GL=Yes, P_TRANSFER_TO_GL=Yes, P_TRANSFER_TO_GL_FLAG=Y, P_INCLUDE_USER_TRX_IDENTIFIERS=No, P_USER_ID=0, P_PROCESS_CATEGORY_NAME=, P_ERRORS_ONLY=No, P_DUMMY_PARAM_3=Y, P_SECURITY_CHAR_3=, P_DUMMY_PARAM_2=Y, P_SECURITY_CHAR_2=, P_DUMMY_PARAM_1=Y, P_SECURITY_CHAR_1=, P_ENTITY_ID=, P_PROCESS_CATEGORY_CODE=, P_INCLUDE_ZERO_AMT_LINES=No, P_LEDGER_ID=2033, P_POST_IN_GL_FLAG=Y, 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=ZEBRA UK GBP, 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=F} Calling XDO Data Engine + -+ Start of log messages from FND_FILE + -+ 05-JUN-2009 19:50:02 Beginning of the Report 05-JUN-2009 19:50:02 Starting of the Parent Thread Starting main program for the source application = 200 05-JUN-2009 19:50:02 Dynamic conditions built 05-JUN-2009 19:50:02 Event Applications Determined 05-JUN-2009 19:50:02 Security Context Set 05-JUN-2009 19:50:02 Session Identifier Set 05-JUN-2009 19:50:02 Setup for the ledger and Event applications Read 05-JUN-2009 19:50:02 executing preaccounting hook event key = 4144-1922153 05-JUN-2009 19:50:02 preaccounting hook executed successfully 05-JUN-2009 19:50:02 Pre-Accounting steps performed 05-JUN-2009 19:50:02 Queue Created = XLA.XLA_1922153_DOC_Q

05-JUN-2009 19:50:02 Queue Created = XLA.XLA_1922153_COMP_Q 05-JUN-2009 19:50:02 Queue Started = XLA.XLA_1922153_DOC_Q 05-JUN-2009 19:50:02 Queue Started = XLA.XLA_1922153_COMP_Q 05-JUN-2009 19:50:02 Global Context Initialized 05-JUN-2009 19:50:02 Calling sequencing batch_init 05-JUN-2009 19:50:02 Returned from sequencing batch_init 05-JUN-2009 19:50:02 Begin enqueue 05-JUN-2009 19:50:02 Ready to Enqueue documents in the queue 05-JUN-2009 19:50:02 Spawning unit processors 05-JUN-2009 19:50:02 Unit processors spawned 05-JUN-2009 19:50:09 Ready to Enqueue documents in the queue 05-JUN-2009 19:50:46 Ready to Enqueue documents in the queue 05-JUN-2009 19:50:46 Ready to Enqueue documents in the queue 05-JUN-2009 19:50:51 Ready to Enqueue documents in the queue 05-JUN-2009 19:50:51 Enqueueing completed 05-JUN-2009 19:50:51 Waiting for Unit Processor requests to complete 05-JUN-2009 19:51:51 Child Threads completed 05-JUN-2009 19:51:51 Global Context cleared 05-JUN-2009 19:51:51 Queue stopped = XLA.XLA_1922153_DOC_Q 05-JUN-2009 19:51:51 Queue stopped = XLA.XLA_1922153_COMP_Q 05-JUN-2009 19:51:51 Queue dropped = XLA.XLA_1922153_DOC_Q 05-JUN-2009 19:51:51 Queue dropped = XLA.XLA_1922153_COMP_Q 05-JUN-2009 19:51:51 Calling sequencing batch_exit 05-JUN-2009 19:51:51 Returned from sequencing batch_exit 05-JUN-2009 19:51:51 Executed post-accounting routine 05-JUN-2009 19:51:51 request for balance calulation submitted 05-JUN-2009 19:51:51 Accounting Program completed successfully 05-JUN-2009 19:51:51 executing postaccounting hook event key = 4144-1922153 05-JUN-2009 19:51:51 postaccounting hook executed successfully - Accounting Time = 108.25 secs - Transfer Time = 0 secs 05-JUN-2009 19:51:51 End of the Report + 7. Roland Docking Says:
July 14th, 2010 at 2:27 am

Hi maybe You can help me, im getting the following creating accounting XDO Data Engine Version No: 5.6.3 Resp: 50562 Org ID : 82 Request ID: 4915573 All Parameters: P_APPLICATION_ID=222:P_SOURCE_APPLICATION_ID=:P_DUMMY=:P_LEDG ER_ID=2021:P_PROCESS_CATEGORY_CODE=:P_END_DATE=:P_CREATE_ACC

OUNTING_FLAG=N:P_DUMMY_PARAM_1=:P_ACCOUNTING_MODE=:P_DUM MY_PARAM_2=:P_ERRORS_ONLY_FLAG=N:P_REPORT_STYLE=D:P_TRANSFE R_TO_GL_FLAG=Y:P_DUMMY_PARAM_3=:P_POST_IN_GL_FLAG=Y:P_GL_BA TCH_NAME=:P_MIN_PRECISION=2:P_INCLUDE_ZERO_AMOUNT_LINES=:P_R EQUEST_ID=:P_ENTITY_ID=698930:P_SOURCE_APPLICATION_NAME=:P_APP LICATION_NAME=:P_LEDGER_NAME=:P_PROCESS_CATEGORY_NAME=:P_C REATE_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_SECURIT Y_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_IN CLUDE_USER_TRX_ID_FLAG=:P_INCLUDE_USER_TRX_IDENTIFIERS=:P_USE R_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=698930, P_PROCESS_CATEGORY_CODE=, P_INCLUDE_ZERO_AMT_LINES=, P_LEDGER_ID=2021, 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 [071410_101331390][][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_CREATE_ACCT_RPT_PVT.print_logfile. ORA-20100: Error: FND_FILE failure.

Unable to create file, o0219474.tmp in the directory, /usr/tm 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.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:9 65) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.jav a:3339) at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3445) at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4395) 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:348) at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:293 ) 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, o0219474.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 1326 ORA-06512: at line 1 has been detected in FND_CONCURRENT.SET_INTERIM_STATUS.+

+ Start of log messages from FND_FILE 8. Naveen Says:

Hi Sanjit, Nice post as always.I would like to know what is the interface program for Sub ledger. Like the one we have for GL e.g .GL INTERFACE. DO you where i can find the documnet related to that. We need to change the interface from third party to Sub ledger for R12 which is going to GL in 11i. Thanks, Naveen 9. SivaSankar C Says:
September 13th, 2010 at 10:54 am

Dear, Create Accounting ran with Transfer to GL and Post in Final Mode, Could you please reply, how do we revers the accounting entries created but not transfered to GL due to table space problem Thanks in Advance 10. Vamsi Kasina Says:
January 11th, 2011 at 1:34 pm

GL Transfer Datafixes 883557.1 Leave a Comment

Mail (will not be published)

Website

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.
Submit Comment

All content present on this website is property of OracleappsHub.com and subject to international copyright laws. 2006-2011 Copyright OracleApps Epicenter.All Rights reserved.