3/18/2020 Document 1338511.

1
Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

What Diagnostic Tests Are Available For Fusion Financials (Doc ID 1338511.1)

In this Document

Main Content
Purpose
Troubleshooting Steps
Diagnostic Tests For Fusion General Ledger
1. General Ledger Closing Validations
2. General Ledger Misclassified Accounts Validations
3. General Ledger - Chart of Accounts diagnostic report
4. General Ledger - Ledger setup report
5. General Ledger Accounting Calendar Data
6. General Ledger Tree version data
7. General Ledger Value set values data
Diagnostic Test For Fusion Payments
1. IBY PPR Data Collector Report
2. Payment Schedule Corruption
Diagnostic Tests For Fusion Receivables
1. Transaction Data
2. Receipt Data
3.AutoInvoice Interface Data
Diagnostic Tests For Fusion Assets
1. Validations for Fixed Assets Setup
2. Generate Asset Trace: Basic Information and Generate Asset Trace: Accounting Information
3. Generate Mass Addition Trace
Diagnostic Tests ForFusion Intercompany System
1. Intercompany and Intracompany Rules Data Collector Report
Diagnostic Tests For Fusion Payables
1. Payables List
Diagnostic Tests For Cash Management
1. Receipt Diagnostics

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 1/19
3/18/2020 Document 1338511.1

2. Payment Diagnostics
3. Bank Statement Auto Reconciliation Diagnostic
4. Bank Statement Processing Diagnostics
Diagnostic Test For Fusion Subledger Accounting
1. GL Transfer
References

APPLIES TO:

Oracle Fusion Payments - Version 11.1.5.0.0 and later

Oracle Fusion General Ledger - Version 11.1.1.5.1 and later
Oracle Fusion Cash Management - Version 11.1.5.0.0 and later
Oracle Fusion Receivables - Version 11.1.1.5.1 and later
Oracle Fusion Payables - Version 11.1.1.5.1 and later
Information in this document applies to any platform.

MAIN CONTENT

Purpose
Checked for relevance on 01-19-2017

This document provides guidance on using the Diagnostic Tests available to support the Oracle Fusion Financials products.

For more information on using Diagnostic Tests please see the Fusion Applications Administrators Guide, as well as Note 1314486.1 - How To Get The Most From
Diagnostic Test Framework (DTF).

Troubleshooting Steps

Diagnostic Tests For Fusion General Ledger

1. General Ledger Closing Validations

Use-Cases:

This diagnostic test checks different criteria to help determine whether a period is ready to be closed in General Ledger.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 2/19
3/18/2020 Document 1338511.1

This should be run at the beginning of the period close activities to assess what actions are outstanding before closing the period.

Input Parameters (required):

Ledger ID: List of values to select the appropriate ledger.

Period Name: List of values to select the appropriate period for the ledger.

Output Details:

Retained Earnings account information

Accounting Calendar information
Subledger Period Status information
Journal Entry status information
Period Balances details

Things to Look for: In this test, warnings and fix information is provided in red text after each section if necessary as listed below.

Whether the period of interest is still open in the subledgers

Journals that have not been imported from the interface table
Journals that have not been posted
Possible mismatch between beginning balances debit and credit, period net balances debit and credit and ending balances debit and credit.

Output Example Section:

View Sample Output

2. General Ledger Misclassified Accounts Validations

Use-Cases:

This diagnostic test identifies the code combinations those are misclassified. An account is misclassified if the account type of the segment value is different from
the account type on a code combination that uses that value.
Run this test when experiencing issues with General Ledger Code Combinations, like the balance of balance sheet accounts not rolling forward into the new year
or unexpected balances in the Retained Earnings account.

Input Parameters (required):

Ledger ID: List of values to select the appropriate ledger.

Period Name: List of values to select the Last Period Name for Earlier Year.

Output Details:

Ledger Details
Chart of Accounts
Accounting Calendar
Journaling
Average Balance
Budgetary Control

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 3/19
3/18/2020 Document 1338511.1

Chart Of Accounts Details

Misclassified Accounts
References

Things to Look for: In this test, warnings and fix information is provided in red text after each section if necessary as listed below.

Know the Value Set name of the Segment Name 'Account'

Misclassified Detail Accounts
Misclassified Summary Accounts
All Ledgers Using Value Set of the Segment Name 'Account'

Output Example Section:

3. General Ledger - Chart of Accounts diagnostic report

Use-Cases:

This diagnostic test checks different criteria to list information about the chart of accounts (COA) structure and Trees associated with the segments.

Input Parameters (required):

Chart Of Accounts: list of values to select the appropriate COA.

Output Details:

COA segment information

Flex qualifier information
Tree information for COA segments
Information on whether Maintain Value Sets and Maintain Chart of Accounts Hierarchies needs to be re-run
Discrepancy between Balancing Segment in Ledger Definition and COA definition
Value Set Secured with incorrect data security object name
Value Set Secured with no security grants
Tree Version Audit Violations

Things to Look for: In this test, error information is displayed as *** ERROR *** in the appropriate section.

Output Example Section:

View Sample Output

4. General Ledger - Ledger setup report

Use-Cases:

This diagnostic test lists setup information for a ledger.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 4/19
3/18/2020 Document 1338511.1

Input Parameters (required):

Ledger Name: list of values to select the ledger.

Output Details:

Ledger standard information

COA segment information
Flex qualifier information
List of secondary ledgers
List of reporting currencies
List of legal entities
Ledger and Legal Entity BSV Assignments
List of journal sources
List of journal categories

Things to Look for: In this test, additional information to the tables for each section is displayed as *** Note *** under the appropriate section.

Output Example Section:

View Sample Output

5. General Ledger Accounting Calendar Data

Use-Cases:

This diagnostic test lists calendar information.

Input Parameters (required):

Calendar Name: list of values to select the calendar.

Optional Parameter:

Period Year: no LOV.

Output Details:

Calendar details
Period set details
Period type details
Calendar validation information
Period details
Period map details
Period status details
List of ledgers that use calendar

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 5/19
3/18/2020 Document 1338511.1

Output Example Section:

View Sample Output

6. General Ledger Tree version data

Use-Cases:

This diagnostic test lists the hierarchy definition for a tree and tree version.

Input Parameters (required):

Tree Code: list of values to select the hierarchy.

Tree Version: list of values to select the hierarchy version.

Output Details:

Information of parent level values and description.

Things to Look for: In this test, the child values are not being displayed although the description of the values is.

Output Example Section:

View Sample Output

7. General Ledger Value set values data

Use-Cases:

This diagnostic test lists the values that are part of a value set.

Input Parameters (required):

Value Set Name: list of values to select the value set.

Output Details:

Information of values that are in a value set. It includes the description, enabled flag, summary flag and others.

Output Example Section:

View Sample Output

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 6/19
3/18/2020 Document 1338511.1

Diagnostic Test For Fusion Payments

1. IBY PPR Data Collector Report

Use-Cases:

This diagnostic collects data from the main tables involved in the Payment Process Requests (PPR).
This should be run when information on a specific PPR is needed.

Input Parameters (required):

Maximum Rows to Display: maximum number of rows to display for each query ran by this test. Default is 500.
Payment Service Request ID: List of values to select the ID of the PPR process of interest.

Output Details:

Information from relevant Payables, Cash Management and Payments tables involved in the payment process.

Things to Look for:

The report includes information on key columns under the section 'PPR Data Collector - Summary Report', as well as all columns from the different relevant
tables under the section 'PPR Data Collector - Detail Report'.

Output Example Section:

View Sample Output

Please see Note 1377744.1 Fusion: Generate IBY PPR Diagnostic Report for more details.

2. Payment Schedule Corruption

Use-Cases:

This diagnostic test lists corruptions found in the payment schedule for Payables invoices
This should be run when user complains of one or more of the following scenarios:
The invoice is over paid or the proposed payment for the invoice is incorrect
Invoice incorrectly picked up in a PPR
Invoice paid twice
Partially paid invoice cannot be paid
Paid invoice does not show as paid
Invoice paid for the wrong amount

Input Parameters (required):

Start Date: Start date compared against the invoice date of the invoices
End Date: End date compared against the invoice date of the invoices

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 7/19
3/18/2020 Document 1338511.1

Output Details:

The output shows invoices having the following issues:

Payment Schedules with Corrupt Amounts
Overpaid Payment Schedules

Things to Look for: In this test:

Look for invoices listed under 'Payment Schedules with Corrupt Amounts' or 'Overpaid Payment Schedules'.
Get the APLISTH for the invoice and review the same
Based on the corruption, look for functional fix and/or datafix.

Output Example Section:

View Sample Output

Diagnostic Tests For Fusion Receivables

1. Transaction Data

Use-Cases:

This diagnostic provides information regarding a specific transaction across various Receivables, E-Business tax and General Ledger tables
This should be run when you encounter issues regarding a transaction that prevents it from posting.

Input Parameters:

Transaction ID (Required): List of values to select a particular transaction.

Show GL Tables (Optional): Indicates whether you want to see data in the General Ledger tables, default value = Y (Yes).

Output Details:

Data is retrieved from various tables to display information pertaining to the Transaction Id provided. The select statements are also printed to assist you in
understanding how the data was retrieved.

Ledger Information (Primary and Secondary)

Receivables Calendar Information
Transactions Header, Line, Distributions Data from RA_CUST* tables
Applications information
Adjustments information
Accounting information
General Ledger information

Things to Look for:

In this test, warnings and fix information is provided in red text after each section if appropriate.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 8/19
3/18/2020 Document 1338511.1

Output Example Section:

View Sample Output

2. Receipt Data

Use-Cases:

This diagnostic provides information regarding a specific receipt across various Receivables and General Ledger tables
This should be run when you encounter issues regarding a receipt that prevents it from getting applied or posted to the General Ledger.

Input Parameters:

Cash Receipt ID (Required): List of values to select a particular receipt.

Show GL Tables (Optional): Indicates whether you want to see data in the General Ledger tables, default value = Y (Yes).

Output Details:

Data is retrieved from various tables to display information pertaining to the Cash Receipt Id provided. The select statements are also printed to assist you in
understanding how the data was retrieved.

Ledger Information (Primary and Secondary)

Receivables Calendar Information
Receipt Header, Line data
Applications information
Distributions information
Cash Management information
Accounting information
General Ledger information

Things to Look for:

In this test, warnings and fix information is provided in red text after each section if appropriate.

Output Example Section:

View Sample Output

3.AutoInvoice Interface Data

Use-Cases:

This diagnostic collects data from AutoInvoice Interface tables for a given column name and value including cross-references to AR, HZ and GL tables. It also lists
file versions of Pro*C code, invalid data objects and disabled database triggers.
This should be run to investigate issues regarding transactions that were imported via Autoinvoice.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 9/19
3/18/2020 Document 1338511.1

Input Parameters:

Column Name (Required): Determines which column will be used to select transaction data.
Column Value (Required): Determines which transaction(s) will be included in the output.

Output Details:

Data particular to a specific transaction that either was imported, or, will be imported is collected and shown in the output. If the transaction has been imported, related
data in AR, HZ, and GL tables will also be included. The select statements are also printed to assist you in understanding how the data was retrieved.

RA_INTERFACE_LINES_ALL
RA_INTERFACE_DISTRIBUTIONS
RA_INTERFACE_SALESCREDITS_ALL
RA_INTERFACE_ERRORS_ALL
RA_CUST_TRX_TYPES_ALL
RA_TERMS_B
RA_BATCH_SOURCES
FND_CURRENCIES
MTL_SYSTEM_ITEMS_B
GL_CODE_COMBINATIONS Sales Account (Items)
HZ_CUST_ACCOUNTS Bill To
HZ_CUST_ACCOUNTS Ship To
HZ_CUST_ACCOUNTS Sold To
HZ_PARTY_SITES Bill To
HZ_PARTY_SITES Ship To
HZ_LOCATIONS Bill To
HZ_LOCATIONS Ship To
JTF_RS_SALESREPS
GL_CODE_COMBINATIONS Revenue Account (Salesreps)
GL_CODE_COMBINATIONS Freight Account (Salesreps)
GL_CODE_COMBINATIONS Receivables Account (Salesreps)
Invalid Objects
Disabled Triggers
References

Things to Look for:

No validation will be done on the data collected, therefore no error or warning messages will be provided.

Output Example Section:

View sample output here.

Diagnostic Tests For Fusion Assets

1. Validations for Fixed Assets Setup

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 10/19
3/18/2020 Document 1338511.1

Use-Cases:

These diagnostic tests validate the setup of Fusion Assets as outlined in the System Setup chapter of the corresponding User Guide.
They should be run to verify that the setup is correct and complete when implementing or upgrading Fusion Assets.
There are eight different tests that validate different asset setup features like bonus rules, book controls, calendars, categories, etc.

Input Parameters :

None

Output Details:

Information from relevant Assets and Foundation tables involved in the Fusion Assets Setup is retrieved, if a validation finds problematic data.

Things to Look for:

Each setup validation test will display a 'Critical Issues Found' Diagnostic Status when issues are found with the setup.
In these tests, warnings and fix information is provided in red text for each section for which an issue is found.

Output Example Section:

Please see Note 1338395.1 Diagnostics: Validations for Fixed Assets Setup for further details.

2. Generate Asset Trace: Basic Information and Generate Asset Trace: Accounting Information

Use-Cases:

These diagnostic tests provide the descriptive, financial, historical, and accounting details of an asset in a specific book.
They should be run to help Support diagnose problems with your current Fusion Assets issue.

Input Parameters:

Asset Number (Required): List of values to select a particular Asset.

Depreciation Book (Required): List of values to select the Depreciation Book for the particular Asset.

Output Details:

Data is retrieved from various Assets and Subledger Accounting tables to display information pertaining to the Asset Number provided in the Depreciation Book
provided. The select statements are also printed to assist you in understanding how the data was retrieved.

Assets information
Accounting information
Subledger Accounting information

Things to Look for:

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 11/19
3/18/2020 Document 1338511.1

In these tests, all data for the selected asset in the selected book are returned in order to be able to analyze an issue in Fusion Assets.

Output Example Section:

View Sample Output of Asset Trace Basic Information View Sample Output of Asset Trace Accounting Information

Please see Note 1338411.1 - Diagnostics: Generate Asset Trace for further details.

3. Generate Mass Addition Trace

Use-Cases:

This diagnostic test provides the complete details of a source line in the Mass Additions interface.
It should be run to help Support diagnose problems with your current Fusion Assets addition issue.

Input Parameters:

mass_addition_id (Required): List of values to select a particular mass addition ID.

Output Details:

Data is retrieved from the Mass Additions Interface and Assets tables to display information pertaining to the Mass Addition ID provided. The select statements are also
printed to assist you in understanding how the data was retrieved.

Mass Addition information

Assets information

Things to Look for:

In these tests, all data for the selected Mass Addition ID are returned in order to be able to analyze an issue in with an addition to Fusion Assets.

Output Example Section:

View Sample Output of Mass Addition Trace

Please see Note 1382286.1 - Diagnostics: Generate Mass Addition Trace for further details.

Diagnostic Tests ForFusion Intercompany System

1. Intercompany and Intracompany Rules Data Collector Report

Use-Cases:

This diagnostic collects data from the main tables for Intercompany and Intracompany Rules.
This should be run to verify Intercompany and Intracompany Rules.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 12/19
3/18/2020 Document 1338511.1

Input Parameters:
Maximum Rows to Display: maximum number of rows to display for each query ran by this test. Default is 500.
Ledger ID : List of values to select a particular ledger.

Output Details:

Data is retrieved from various tables to display information pertaining to the Ledger ID provided. The select statements are also printed to assist you in understanding
how the data was retrieved.Ledger Information

Intercompany Rule - Chart of Accounts

Intercompany Rule - Ledger
Intercompany Rule - Legal Entity
Intercompany Rule - Balancing Segment Values
Intracompany Rules
GL Code Combinations.

Things to Look for:

In this test, warnings and fix information is provided in red text after each section if appropriate.
Output Example Section:
View Sample Output

Diagnostic Tests For Fusion Payables

1. Payables List

This diagnostic provides information regarding a specific invoice across various Payables, E-Business tax and General Ledger tables.
This should be run when you encounter issues regarding an Invoice .

Input Parameters (required):

INCLUDE_GL_TABLES If yes, data from GL tables is included in the display.

INCLUDE_RELATED_DATA If yes, data for related invoices is included in the display.
INVOICE_ID Transaction ID (Invoice_ID) of the invoice.
MAX_ROWNUM Option restricts the maximum number of records displayed per table.

Output Details:

Ledger Definition
Secondary Ledgers
Setup - This Section Displays the details of the Setup Data for the Transaction
Summary - This Section Displays Summary Data for the Transaction
Invoices - This Section Displays the details of the Invoice Data for the Transaction
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 13/19
3/18/2020 Document 1338511.1

Payments - This Section Displays the details of the Payment Data for the Transaction
Withholding Tax - This Section Displays the details of the Withholding Data for the Transaction
Accounting - This Section Displays the details of the Accounting Data for the Transaction
General Ledger - This Section Displays the details of the GL Data for the Transaction
Payment Document and Bank - This Section Displays the details of the Bank and Payment Document Data for the Transaction
Suppliers - This Section Displays the details of the Supplier Data for the Transaction
Purchasing - This Section Displays the details of the Purchasing Data for the Transaction
Prepayment - This Section Displays the details of the Prepayment Application Data for the Transaction
Cash Management - This Section Displays the details of the Cash Management Data for the Transaction
Projects - This Section Displays the details of the Projects Data for the Transaction
Assets - This Section Displays the details of the Assets Data for the Transaction
Currency - This Section Displays the details of the Currency Data for the Transaction

Things to Look for:

In this test, warnings are provided in red text after each section if necessary as listed below.
In this test all data for the selected invoice_id are returned in order to be able to analyze an issue in Fusion Payables.

Output Example Section:

View Sample Output

Diagnostic Tests For Cash Management

1. Receipt Diagnostics

Use-Cases:

This diagnostic shows the receipt in the Receivables tables. Then if this receipt has ever been reconciled it shows the corresponding Cash Managment tables for
the bank,statement header and lines tables.
The diagnostic should be run if there is a problem with a specific receipt when reconciling a bank statement to the General Ledger or a receipt to a bank
statement.

Input Parameters (required):

Receipt_id : List of values show available receipt_ids along with their corresponding receipt number. Note there is an enhancement (11873224) which will enable
to user to search on receipt number. Currently it's only possible to search on receipt_id.

Output Details:

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 14/19
3/18/2020 Document 1338511.1

Receivables receipt information

Bank Account Details
Bank Account Statement Details
Cash Management Reconciliation and Transactional Details

Things to Look for: In this test:

Current_Record_Flag for the Cash_Receipt_History_id is correctly showing the matched or unmatched record to the corresponding statement line.
Check there is no orphan data in ce_recon_history that cannot be tied back to ar_cash_receipt_history_all for the specific receipt.
Check receipt has been accounted.
Check if the receipt is still showing as available to reconcile.

Output Example Section:

Receipt Diagnostics

2. Payment Diagnostics

Use-Cases:

* This diagnostic shows the payment in the Payables tables. Then if this payment has ever been reconciled it shows the corresponding Cash Managment tables for the
bank,statement header and lines tables.
* The diagnostic should be run if there is a problem with a specific payment when reconciling a bank statement to the General Ledger or a payment to a bank
statement.

Input Parameters (required):

Check_id : List of values show available check_ids.

Note there is an enhancement (11882641) which will enable to user to search on check number. Currently it's only possible to search on check_id.

Output Details:

* Payables payment information

* Bank Account Details
* Bank Account Statement Details
* Cash Management Reconciliation and Transactional Details

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 15/19
3/18/2020 Document 1338511.1

Things to Look for: In this test:

* Check ce_recon_history shows the correct record corresponding to ap_payment_history_all table.

* Check there is no orphan data in ce_recon_history that cannot be tied back to ap_payment_history_all for the specific payment.
* Check payment has been accounted.
* Check if the payment is still showing as available to reconcile.

Output Example Section:

Payment Diagnostics

3. Bank Statement Auto Reconciliation Diagnostic

Use-Cases:

This diagnostic shows legal entity level bank account information along with additional details of the bank statement reconciliation process like reconciliation
rule sets, reconciliation matching rules, bank statements, system transactions, reconciled bank statements and reconciliation exceptions.
The diagnostic should be run if there are issues running auto reconciliation process.

Input Parameters (required):

Bank Account: List of values to select the bank account used during Auto Reconciliation process
End Date: End date compared against the end date or time for which the account statement was issued.
Start Date: Start date compared against the start date or time for which the account statement was issued

Output Details:

Level bank account information

Reconciliation rule sets
Reconciliation matching rules
Bank Statements fall into the selected date range
System transactions fall into the selected date range
Reconciled Bank Statements
Reconciliation exceptions

Things to Look for:

Check if the system transactions are correctly listed under the selected date range
Check is a bank statement exists for the selected date range
Check for any reconciliation exceptions

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 16/19
3/18/2020 Document 1338511.1

Output Example Section:

View Sample Output

4. Bank Statement Processing Diagnostics

Use-Cases:

This diagnostic provides information about Automatic Bank Statement File Import.
The diagnostic should be run when facing issues loading bank statement files into Cash Management.

Input Parameters (required):

Inbound File ID: Enter the Inbound File ID. Default value is Null.
Request ID: Enter the Request ID for the Electronic Bank Statement Request.

Output Details:

Inbound File Details

Inbound File Content
Associated Format Details
Associated Code Map Details
Header Interface Details
Statement Balance Interface Details
Statement Balance Availability Details
Statement Line Availability Interface Details
Statement Header Totals Interface Details
Statement Headers Totals Availability Interface Details
Statement Lines Batches Interface Details
Statement Line Charges Interface Details
Statement Line Interface Details
Parse Rules Details
Import Error Details
Statement Header Data
Statement Lines Data
Statement Balances Details
Statement Balance Availability Details
Statement Line Availability Details
Statement Line Charges Interface Details
Internal Transaction Codes
Internal Balance Codes Details

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 17/19
3/18/2020 Document 1338511.1

Things to Look for:

Check for errors under Inbound File Details section

Check for errors under Import Error Details section

Output Example Section:

View Sample Output

Diagnostic Test For Fusion Subledger Accounting

1. GL Transfer

Use-Cases:

Find possible invalid data issues for subledger data transferred from SLA to GL
Use this diagnostic to find possible invalid data issues for subledger data transferred from SLA to GL.

Input Parameters (required):

Ledger Id (LOV) *
Application Id (LOV) *
Je Source Name (LOV) *
Start Date in YYYY-MM-DD (LOV) *
End Date in YYYY-MM-DD (LOV) *

Output Details:
Information relevant to the Application ID / Source Name entered at runtime.
Example - Payables

Negative LEDGER_ID in GL
Accounted in 11i but Transferred to GL in R12 with Null GL_SL_LINK_ID
Marked as Transferred in XLA but NOT in GL
Marked as transferred in XLA but Reversed in GL
Marked as transferred in XLA but Deleted in GL
Data Exists in GL but Its Corresponding Data Is Deleted in XLA
Data marked as transferred in XLA but Deleted in GL showing Reference Columns
Data marked as not transferred in XLA but transferred to GL
Data transferred multiple times in GL

Things to Look for:

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 18/19
3/18/2020 Document 1338511.1

* The Parameter Order is not as listed above.

Output Example Section:

View Sample Output

REFERENCES

NOTE:1374930.1 - How To Assign Access To The Fusion Applications Diagnostic Dashboard

NOTE:1338395.1 - Diagnostics: Validations for Fixed Assets Setup
NOTE:1377744.1 - Fusion: Generate IBY PPR Diagnostic Report
NOTE:1338411.1 - Diagnostics: Generate Asset Trace
NOTE:1314486.1 - How To Get The Most from Fusion Applications Diagnostic Test Framework (DTF)
NOTE:1382286.1 - Diagnostics: Generate Mass Addition Trace
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=39qkb0uq1_1191&id=1338511.1 19/19