R12 : Disable "Create accounting" action in AR Transactions

Hi,
I would like to disable the Create accounting" action in AR Transactions for a responsibility.
Could somebody help me please?
Thank you
Tiana

Hi Tiana;
What is your EBS version. Please check below:
http://oraclefinancial.wordpress.com/2010/11/02/how-to-disable-create-online-accounting-in-payables/
http://oracle.ittoolbox.com/groups/technical-functional/oracle-apps-l/disable-create-accounting-check-box-3340367 << u may need form costumizaiton
Regard
Helios

Similar Messages

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.

Disable Multi Accounts Action

Hello,
I would like to disable the “disable”/”enable” action for multiple accounts at the same time on the Accounts->Find Users tab. I know how to do this for List Accounts tab (customizing User List Library form). But I don’t know how to disable these actions for multiple accounts from the Find Users tab.
Thanks for all your suggestions in advance.

No, I want to disable "disable/enable" actions for multi user accounts from Find Users tab. For example, I can do it for Accounts List tab and if I select several users and do Disable action from User Actions list menu, I retrieve error message like "Multiple selections are not allowed for the 'Disable' action." (customize <argument name='selectionMode' value='single'/> for field <Field name='disableUserAction'> in "User List Library"). How do I implement this functionality on Find Users tab?

Can't able to create accounting-Version - 11i, AP

Hi Friends,
I had month end issue while reviewing the unaccounted transaction report we identified some unaccounted payments during May-11, tried to do accounting manually (Actionscreate accounting) but its throws APP-SQLAP-10710 (Online accounting could not be created. Please submit the payables accounting process instead to create accounting entries for this transaction.) but tried running Paybles accounting process program also but still its not creating accounting.
Please advice on the same its urgent. Thanks…
Note: I have 10 payments vouchers for same invoice among them 5 is accounted other 5 I cant able to create accouting.
Thanks,
Sri

Hi Pillair,
Sorry for late reply...
Ya using CM, yes one of the payment was voided in this batch.
Thanks,
Sri

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

SQ01 - Disable create/change button

We are currently on Basis release 4.6 C, I am trying to disable Create/Change button in SQ01 transaction, following one of the SCN posts I Unmaintained S_QUERY Authorization object. This solution worked as expected in one of the sandboxes we have, however it failed to suppress create/change button in our development system. I was wondering if there is any additional step that I would need to take in the dev box to make this change effective?

transaction variant / screen variant might help you.
On the other hand it is nut fully clear for me, what difference does it make, if you remove the Change from one transaction, but remains in the other. If the objective is disallow the change for some users, than it has to be done through proper authorizations (i. e. only display auth for those users)

Disable user accounts on Unix, Linux resorces

Hi Everyone
I try to understand disable user account action on Unix, Linux systems
In Resource reference doc. I see the next:
Linux does not natively support Waveset enable and disable actions.
Waveset simulates enabling and disabling accounts by changing the
user password. The changed password is exposed on enable actions,
but it is not exposed on disable actions.
As a result, enable and disable actions are processed as update actions.
Any before or after actions that have been configured to operate on
updates will execute.
So what kind of commands waveset using for this action:
passwd -l <Username>
or just change password?
Thanks

Hi,
The out of the box adapter changes the user's Linux password on disable action.
To Implement locking of account by running "passwd -l username", you need to write a resource action and call it explicitly. Hope it helps
Regards
Arjun

Query for Transaction number in Create Accounting = Draft Mode

Hi al!!
I run the Create Accounting program concurrent in my R12 instance in DRAFT MODE, and when the concurrent program finish i want to obtain the TRANSACTION number of the transactions in the XLA_AE_LINES table, how can i do that ???... it's for AP_INVOICES, AP_PAYMENTS, RECEIPT and CE Tables...
Thanks in advance..
Pablo.-

1 row in ap_invoice_distributions_all ------> 1 row in xla_ae_lines.xla_ae_lines will have more than one row. dr and cr has to be there for each journal entry.
I want to do a query that get lines from XLA_AE_LINES and then obtain the transaction number (AP_INVOICES_ALL.INVOICE_NUM) that was generated this line in the table.Check the link http://www.orafaq.com/node/2242
I know that this is possible to do using the XLA_ENTITY_TRANSACTIONS table... but when the concurrent is run in DRAFT mode no line are created in this table.The rows in xla_transaction_entities table will get created when the invoice is created. NOT after running accounting, which is much earlier.
Check the link http://www.orafaq.com/node/2243
Also some more details on draft, final accounting are available at http://www.orafaq.com/node/2240
By
Vamsi

Create Accounting-R12

Hi Friends,
In R12, while running the create accounting, in the report parameters we have to select Include User Transaction Identifiers as Yes or No. What is the purpose of this one?
What is the exactly meant by user Transaction Identifiers?
regards,
VAS

If you say transaction identifiers as 'Yes' then the report output of the 'Create accounting" will show the details of the transaction which created the events and accounting.
thanks
Anup

Changing the catalog profile when creating a QN FROM ACTION BOX in transaction QM02

Hi All,
When I create a quality notification from the action box in transaction QM02, the catalog profile is fetched from the material master. I want this changed so that the catalog profile is
always copied from the QN being preocessed in QM02. (current QN)
I am not able to locate the code where the catalog profile for the new QN(QN being created) is fetched from the material master.
If I change the catalog profile in the material master, it works, but that is not a solution for me.
Need the exact point where I can pass in a different catalog code.
Also, I do not see the new QN number anywhere while debugging.
PS: The QN is being created from the action box in transaction QM02 and not from transaction QM01.
Thanks.

Hi All,
When I create a quality notification from the action box in transaction QM02, the catalog profile is fetched from the material master. I want this changed so that the catalog profile is
always copied from the QN being preocessed in QM02. (current QN)
I am not able to locate the code where the catalog profile for the new QN(QN being created) is fetched from the material master.
If I change the catalog profile in the material master, it works, but that is not a solution for me.
Need the exact point where I can pass in a different catalog code.
Also, I do not see the new QN number anywhere while debugging.
PS: The QN is being created from the action box in transaction QM02 and not from transaction QM01.
Thanks.

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

R12 Difference between 'Submit Accounting' and 'Create Accounting' program

Please can anyone clarify the difference between 'Submit Accounting' and 'Create Accounting' program in AR in Oracle Applications Release 12?

Balu,
All concurrent programs are explained in the module user's manual.
Oracle Receivables User Guide (zipped)
http://download.oracle.com/docs/cd/B40089_09/current/acrobat/120arug.zip
Oracle Subledger Accounting Implementation Guide
http://download.oracle.com/docs/cd/B40089_09/current/acrobat/120xlaig.pdf

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

Change GL account in OBYC for transaction keys GBB and BSV

Dear Logistics Colleagues
I would like to have your opinion on the following topic:
I have an request to change an GL account in account determination (OBYC) for transactions:
- GBB > Offsetting entry for inventory posting
-BSV > Change in stock account
What cutover should I consider or which actions should be executed before implementing the change?
Many thanks in advance for your help?
Regards,
Mohamed

Hi,
Just check all the orders whose GR is done, there LIV also done, for the scenario where this key will be utilized,
BSV - change in stock account, this will hit in subcontracting process. When you do GR against 101 mvt type this BSV will get credit, BSV is the balancing account to BSX for Finished goods, this amount goes to P&L accounts
GBB - Most of the time this will be 0, because it is for offsetting entries, check there is no balance in this GL,
If you want create OBYC for this 2 for some new valuation class then i do not think you need to look at cutover

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

R12 : Disable "Create accounting" action in AR Transactions

Similar Messages

Maybe you are looking for