Error when Posting to Accounting

dear SAP Gurus,
I have one inquiry about the posting.
I have created the posting run to Accounting using the Tcode PRFI or PRRW (create posting run), which is successful. But when I tried to post it to Accounting using Tcode PRRW, I encountered error as follow:
A RW609 Error in document: TRAVL 0000000215 ECDCLNT110
A F5152 Document number 3100 100000004 2009 was already assigned
Posting run 0000000227 could not be posted
in the posting run management, it shows the message "Document transfer has failed".
It is strange that previously I didn't encounter any problem, and it works fine in other clients. The problem exists in sandbox, which was no problem before, and I don't think that I change some customizing for travel expense.
Does it have anything to do with change in FI customizing? Would you please show me where can I locate the problem and solve it?
Many thanks before for the kind answer
cheers
salomon

hi,
see the condition record of mwst thru vk11.
see tha customer master and material master what y have mentioned as output tax. it should be as 1 = liable for tax.
see whether u have maintained the mwst in the pricing procedure.
see whether u have maintained the mws account keys in account determination as 175000.
suppose if you would have created the new tax procedure, check the details once again carefully. I am sending you the tax procedure in easy steps. follow it, u r problem will resolved.
Define Tax determination Procedure
SPRO—Financial accounting-Financial accounting global settings—Tax on sales / purchases—Basic settings-Check calculation procedures---Define procedures
Select TAXD copy as TAXIN and save
Back
Select Assign Country to calculation procedure
IN   TAXIN
Save
Back
Select calculation
Select Tax codes for sales & purchases
Country=IN
Continue
Country key=IN
Tax code=ZQ
Continue
Tax code= ZQ  - India tax
TAX type= A
Check=Yes
Continue
Output tax MWS=10
Save
IMG—SD—Basic functions—TAXES
Define tax determination rules
New entries
Tax country   SEQ   Tax cat
IN   1   MWST
Save
VK11
Condition Type= MWST
Select Domestic
Country=IN
Taxcl1cu=1
Taxcl1mat=1
Tax code=ZQ
Enter
Automatically rate=10%
Save
reward points if it is useful.
regards
KR

Similar Messages

  • Error when posting to profitabilty segments

    Dear All
    I get the following error when posting poriftabilty segment data in the accounting doument, if i try to enter the same characteristic value even to diffrent G/L Accounts.
    Data record already exists
    Message no. KE581
    Diagnosis
    This error should not occur.
    Procedure
    Contact your system administrator or SAP directly (component CO-PA-ACT).
    Has anyone come across this issue... ? Pls let me know how to resolve this?
    Thanks
    Gayani

    Hi,
    Please implement the latest version of the note 1321225 into your system in order to solve this problem!
    Afterwards please execute the function module RKE_GENERATE_INTERFACE_ACT in transaction SE37 for the operating concern you use - as described in note 1321225 under 'Solution'!
    Please enter function module RKE_GENERATE_INTERFACE_ACT in transaction SE37, press F8, enter your operating concern and press F8 again.
    Afterwards the described problem with error message KE581 should be solved.
    regards
    Waman

  • Error In Posting to accounts - PF  calculated wrong

    Hi,
    I am getting error in Posting to accounts- error - Posting balance is not cleared (Period -
    Following Wage types are calculated wrong  -
    Expense
    MF90 PF adm chrgs * 1,00,000 = 715,000.000
    MF70 EDLI contri * 1,00,000 =6,500.000
    Balance sheet
    MF90 PF adm chrgs * 1,00,000 = 715,000.000-
    MF70 EDLI contri * 1,00,000 = 325,000.000-
    MF80 EDLI adm chrgs * 1,00,000 =6,500.000-
    /3P2 Professional Tax Basis = 8,387.096-
    Symbolic accounts assigned are as standard - no changes made
    Please help me solve this.
    Thanks in advance.
    Monica

    Hi Monica,
    We have solved this issue in our company.
    For this you have to create another wage types & make a "PCR" as it divide the 100000 amount from the technical wage types, & then instead of posting the technical wage types post the new wage types u have created.
    Don't worry about statutory reports as in there SAP is using some factor which will give the correct value.
    Regards,
    Gaurav

  • Error when posting a SOAP request

    Hi all,
    Facing error when posting the SOAP request and after entering the Server Username and password giving error that http not found and url
    The URL i follow is http://<hostname>:<port>/XISOAPAdapter/MessageServlet?version=7.0&channel=:BusinessSystem:PI_SOAP_CC
    can any one of you tell me in place of XISOAPAdapter what should i place?
    Please help me to post the SOAP request to PI server.
    Thanks in advance ,
    Manohar.

    Hi ,
    copy the same URL  (Endpoint that you had given while generating wsdl file) to the browser and chek the status. ( http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel)
    See the below URL for the same i.e. SOAP adapter...http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
    You should get response something like this '
    Message Servlet is in Status OK
    Status information:
    Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#15 $) bound to /MessageServlet
    Classname ModuleProcessor: null
    Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
    Lookupname for remoteModuleProcessorLookupName: null
    ModuleProcessorClass not instantiated
    ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0
    ModuleProcessorRemote not instantiated
    This  is make sure that webservice endpoint is given correctly. Don't forget to give username and password for connecting to XI server. user should xiappluser .
    Ranjeet Singh.

  • Error when posting goods issue

    hi gurus,
    can anyone please help me with this error when posting goods issue to a free issue sales order " line item text is mandatory for vendor invoices".
    thanks in advance

    Dear Ysabella
    It seems the item texts is not maintained in the order which is made as mandatory.
    Go to sale order VA02, select that line item and click on "GotoItemTexts".  There maintain the relevant text and retry.
    thanks
    G. Lakshmipathi

  • Error when posting IDoc *** in system ERP100

    Hi Experts!
    Can you pls help me with a goods receipt issue?
    When user tries to make a good receipt on a PO, we have the msg "Error when posting IDoc *** in system ERP100" in SRM front-end application monitor.
    The same msg is getting displayed in RZ20.
    On the idoc itself in tcode WE02 however, I can't see any problem and unfortunately I have no access to the same t-code in R/3. Anyway, I don't see the GR on the PO.
    What can be the reason for this problem please?
    What is in general the way to analyse and solve this kind of issue?
    Thanks a lot !!
    imre

    Hi,
    First find out the PO number from the idoc in tx WE02 in SRM system. Then in ERP , transaction BD87 , specify the details like message type and the system information .... and find out the PO that was errored out for GR. From this we can find the cause of the error. First try to rectify the error and then run the report to clear the contents of  BBP_DOCUMENT_TAB.
    Hope this helps.
    Regards,
    Kalyan

  • Error when posting the goods receipt

    Hi we have recently successfuly updated 4.6 B to ECC 6.0.But when i am doing captive consumption by 949 Mvt. through process message system gives an error that
    Error when posting the goods receipt
    Message no. CB345
    Diagnosis
    With the selected process message, a goods receipt for the order was reported to the warehouse (destination ZPI1).  However, an error occurred when the goods receipt was posted.
    Please do needful.
    Regards,
    PP

    Hi Daniel,
    This is the first time i am coming across an issue like this.
    neverthless from a logical front,
    1. Remove Cost center as a valid receiver in Settlement Profile.
    2. Your OKB9 setting are pretty much good. No need to worry about it.  Becasue, OKB9 only will work if the system doesn't identify any other cost object. In this case Production Order is an automatic cost object which system should have taken.
    3. Check the Settlement rule when you have created Production Order. It should have been MAT.
    4. I hope you are creating Production Order with Material (using CO01 and not CO07)
    5. Make sure in OPL8, the default rule in controlling tab is PP1.
    Once all these are fine, i do not see any reason why you will get your probelm.
    Please check and revert back to me if the problem still persists.
    Best Regards
    Surya

  • Invalid Account Code error when posting AP Credit Note

    Dear Experts,
    I hit this error message when posting an AP Credit Note based entirely on an existing AP Invoice (nothing was changed in the credit note).
    Invalid Account Code [Message 173-9]
    I have found 2 notes, but I dont think they're relevant
    [Note 1311905|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0001311905]
    [Note 1286288|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0001286288]
    Please help!
    Warmest Regards,
    Chinho

    Dear All,
    I found the solution!
    In my AP Invoice, there was a Rounding amount, but when I copied over to AP Credit Note, the system unusually set the Rounding amount as $0.00 and copies the Rounding amount to the Discount field instead.
    **The "Invalid Account Code" error happened because I did not set GL account determination for discounts scenario.
    So what I did was I cleared the Discount field in the Credit Note, and enter the rounding figure into the Rounding field again. Then, the AP Credit Note was able to go in Successfully!
    Thanks guys.
    Warmest Regards,
    Chinho

  • 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 when posting debit balances to expense accounts

    dear experts.
    A screen dump is produced when saving or posting debit balances to expense accounts for only certain periods and for a certain fiscal year in this case year 2006. credit balances are being posted without any problem to the same accounts, same periods and fiscal year. what might be the problem. can the problem be solved form the ABAP side or FI side?
    its urgent

    Hi Willard,
    Karthik is right, we need more input to resolve this issue. ST22 can give it to you.
    This issue as far as I understand has nothing to do with ABAP. It has to be resolved by functional / basis people.
    Is there any internal order / cost center assignment when posting to these expense a/c's?
    Regards,
    Siva

  • Error while Posting to Accounting

    Hello Experts,
    When I execute PC00_M99_CIPE for Posting to Accounting an error occured "Document Type is not permitted".
    Payroll Status is EXIT Payroll in Control Record.
    Please guide.
    Regards,
    Rajesh

    Hi mohan, Thanks for your reply.
    As you suggested we are maintaining Document Type "AB" which has worked fine for previous all payroll postings.
    And FI module has also maintained the same.Do I need to change it to PY even then?
    As you said to execute the Program RPCIPE01 instead, I did the same but again the system is throwing an error : "Country grouping  from posting variant SAP is not permitted". Where to fix this problem in the system.
    Please guide.
    Rajesh
    Edited by: Rajesh Sinha on Jul 22, 2010 8:58 AM

  • Error when posting - Call up of feature PPMOD was not successful

    Good Afternoon,
    We recently completed an upgrade to ECC6.0 and this week we have seen two cases of receiving an error when trying to post payroll to FI using RPCIPE00.
    The error we are receiving is:  Call up of feature PPMOD was not successful, Message no. 3G100
    The diagnosis on the error message is:  Feature PPMOD has been called to set the employee grouping for account determination. This call was unsuccessful and suggests that we check the decision tree for PPMOD.
    While there have been some somewhat recent changes to PPMOD, I have stepped through the feature for both individuals who had this error and can find no problem with the logic in the decision tree. I've also regenerated the feature successfully. After searching OSS I found note 1243065, which is the exact error that we are receiving. The problem is that this note was included in HR support pack 44, and we're already on HR support pack 48. We also found a post that suggested we use RPCIPE00_OLD, but gave us the same error.
    My next step was to post a customer message, but thought it would be worthwile to post something here and see if anyone has any suggestions first.
    Thanks in advance,
    -Nick
    Edited by: Nicholas Petters on Apr 15, 2010 5:32 PM

    The issue may not be related to the note you indicated as this note should already be included in your system with SP 48. Please check what personnnel areas the errors ees are in, and see if they're in the decision tree of 'PPMOD' .
    If this looks OK, run payroll simulation for the error ee, put break-point in form 'CALL_549B' of program '/1PAPA/FEAT310PPMOD' and see what value STRUC-WERKS  (pers. area) is when it fails.

  • 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

  • Error when posting invoice for Asset purchase order

    Hi,
    we are getting the errore message account determination for asset posting with keys not defined in chart of accounts,when posting an invoice for asset purchase order.
    Can any one see why this error is coming and what will be the solution.
    Nagesh

    Hi Prabhakar,
    Here is the reply,
    we have 10 line items,in which 3 items are freight related and other 7 items are related to goods reciept.
    i am trying to enter invoice for 3 line items at a time with two relevant to goods reciept and other related to non goods receipt(freight related).
    accounting entries generated after the GR are as follows,
    asset under construction account,and GR/IR account.
    Let me know the details is sufficient or not.

  • Error when posting inventory differences

    We receive an error when trying to post an inventory difference with MI07.  The error message is "Account xxxxxx requires an assignment to a CO object" (SAP message KI235).  I've looked at the account, which is a cost element, using KA02 and there is a default cost center entered on the default account assignment tab.  Our issue is that we have multiple plants with inventory.  The default cost center is for plant 1 but we are trying to post an inventory difference for plant 2.  We shouldn't have to change the default cost center in KA02 everytime we post an inventory difference to plant 2.  What configuration change do I need to make so I can post inventory differences to both plants without having to change the default cost center for the cost element?  Both plants reside in the same controlling area but the cost centers are different.

    Hi,
    Maintain default Cost Center for Cost Element based on Valuation Area (Plant) in OKB9.
    Here maintain the Co. Code, Cost Element, and select Acct Assignment detail indicator as '1' i.e. Valuation area is mandatory. Now select the entry and double click on "Detail per business area/valuation area" in dialog structure and click New Entries and then specify the Valuation Area (Plant) and Default Cost Center for the Plant.

Maybe you are looking for

  • IPhone 4 switch off

    I am having iPhone4 with updated ios 5.0.1. I charged my battery to 100% but after using it for 30 min or less it got switched off automatically. I pressed the sleep button for 10 sec after that it shows me the apple symbol but it goes off in 10-15 s

  • RE1000 works, but it freezes my router!

    Hello guys! Just made my RE1000 setup yesterday and the first impression was it worked fine, as It repeated the signal and even it had 50ms of ping instead of my normal 4-10ms, a speed test shown 6Mb/s of download speed (which is fine). I was navigat

  • Migratable Servers & Services

    Hey everyone...           For the purposes of this discussion, assume I've created two managed servers: "managedServerOne" and "managedServerTwo".           I've been working with JMS on WLS and am struggling a bit with the semantics of migration. Wh

  • APDU error 6a80

    Hi there, i'm new to javacard technology and i'm trying to run the wallet.java example usingEclipse. I get an error message of 6a80 when i try to debug the app. Does anyone have any ideas of what the problem could be? I havent changed any of the code

  • What have I done differently here?

    Here is my landing page for my site ifamg.com. The "yellowish" section, bottom right half of the page, has 2 links: the book graphic and the "click here" text.  The book link (when I'm viewing this in Firefox) opens up a new window to show my Store (