Copyright (c) 2002 Oracle Corporation Redwood Shores, California, USA
Oracle Support Services. All rights reserved. ================================================================================ ================================================================================ Abstract Oracle Receivables - Transaction Data Collection ================================================================================ PRODUCT: Accounts Receivable (AR) SUBCOMPONENT: TRNSACTION PRODUCT VERSIONS: Release 11.5 DATABASE VERSIONS: 8.1.6 or higher PLATFORM: Generic DATE CREATED: 20-DEC-2002 PARAMETERS: Username Responsibility Id Column Output ( Limited/All columns ) Trx Number Customer Trx Id Include GL Tables ( Y/N ) ================================================================================ Instructions ================================================================================ Included Files: CoreApiHtml.sql ARTransactionInfo115.sql ARTransactionInfo115_readme.htm ARTransactionInfo115_readme.txt ARTransactionInfo115_Sample_Output.htm Execution Environment: SQL*Plus Access Privileges: Requires APPS user access Usage: sqlplus <apps user>/<apps pw> @ARTransactionInfo115 Instructions: The files ARTransactionInfo115.sql and CoreApiHtml.sql should be unzipped to a common directory. From this directory, start SQLPLUS in the APPS schema, and run the file ARTransactionInfo115.sql When prompted, enter the applications user name. This will return a list of vali d responsibilities assigned to the user just entered. Enter the responsibility id of the responsibility used when the problem occurs. Next, you will be prompted for the column output. Possible Values : L(imited) or A(ll) A(ll) is the default and will select all the columns of each table in the same o rder as the columns have been defined in the table ( Select * ). L(imited) will only select the most relevant columns of each table logically gro uped together. Next, you can optionally enter the transaction number of the transaction to be a nalyzed. Enter the transaction number only when the corresponding customer trx id is unkn own. A list of matching transactions will be returned on the screen. As transaction numbers are not unique it could be more than one transaction is found. Next, you will be prompted for the customer trx id. Reporting will occur for the id entered here. The last parameter allows to exclude the GL tables from the generated output. Including GL data can have a very negative impact on the performance of this tes t. Set this parameter to 'N' to speed up execution when it is not relevant to diagn ose the transaction's posting status in GL. If GL data can not be excluded, follow t he instructions in Note 269874.1 to improve the performance
The test will produce an output file named
ARTransactionInfo115_[customer_trx_id]_diag.htm This file can be viewed in a browser or uploaded for support analysis. ================================================================================ Description ================================================================================ This test will list for a given customer trx id the data stored in the following AR and GL tables/views : RA_CUSTOMER_TRX RA_CUSTOMER_TRX_ALL RA_CUST_TRX_TYPES RA_BATCH_SOURCES RA_CUSTOMER_TRX_LINES_ALL RA_CUST_TRX_LINE_SALESREPS_ALL AR_CREDIT_MEMO_AMOUNTS RA_CUST_TRX_LINE_GL_DIST_ALL AR_REVENUE_ADJUSTMENTS_ALL AR_TRANSACTION_HISTORY_ALL AR_RECEIVABLE_APPLICATIONS_ALL AR_DISTRIBUTIONS_ALL AR_PAYMENT_SCHEDULES_ALL AR_ADJUSTMENTS_ALL RA_RULES RA_RULE_SCHEDULES GL_INTERFACE GL_JE_LINES GL_IMPORT_REFERENCES If Mrc is enabled and reporting set of books have been defined, then in addition data in the following AR MRC tables will be listed : RA_MC_CUSTOMER_TRX RA_MC_TRX_LINE_GL_DIST AR_MC_TRANSACTION_HISTORY AR_MC_RECEIVABLE_APPS AR_MC_PAYMENT_SCHEDULES AR_MC_DISTRIBUTIONS_ALL AR_MC_ADJUSTMENTS Depending on the class of the transaction some of the above tables will not be included. Reporting is slightly different for Invoices, Creditmemo's and Bill Receivable Transactions. When Global Accounting Engine Subledgers have been defined for Receivables, then also data in the following AX tables will be listed : AX_EVENTS AX_DOCUMENT_STATUSES AX_SLE_HEADERS AX_SLE_LINES AX_BALANCES The outcome of this test is very useful for support and development when there is an issue with a transaction. ================================================================================ References ================================================================================ Note 269874.1 : How to improve performance of Receipt, Transaction, Adjustment Data Collection Diagnostic Tests ================================================================================ Disclaimer ================================================================================ Except where expressly provided otherwise, the information, software, provided on an "AS IS" and "AS AVAILABLE" basis. Oracle expressly disclaims all warranties of any kind, whether express or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose and non-infringement. Oracle makes no warranty that: (A) the results that may be obtained from the use of the software will be accurate or reliable; or (B) the information, or other material obtained will meet your expectations. Any content, materials, information or software downloaded or otherwise obtained is done at your own discretion and risk. Oracle shall have no responsibility for any damage to your computer system or loss of data that results from the download of any content, materials, information or software. Oracle reserves the right to make changes or updates to the software at any time without notice. ================================================================================ Limitation of Liability ================================================================================ In no event shall Oracle be liable for any direct, indirect, incidental, special or consequential damages, or damages for loss of profits, revenue, data or use, incurred by you or any third party, whether in an action in contract or tort, arising from your access to, or use of, the software. Some jurisdictions do not allow the limitation or exclusion of liability. Accordingly, some of the above limitations may not apply to you.