7/24/2019 Document 1483743.

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

R12: Diagnostic Script to help troubleshoot Purchasing Accounting or Encumbrance Issues

(Doc ID 1483743.1)

In this Document

Main Content
Purpose
When to use it?
How to use it?
Still Have Questions?
References

APPLIES TO:

Oracle Purchasing - Version 12.0.0 to 12.2.6 [Release 12 to 12.2]

Information in this document applies to any platform.

MAIN CONTENT

Please utilize Procurement Encumbrance Accounting Analyzer - Note 1970384.1 - to collect specific accounting data -
as well as troubleshooting information for Encumbrance based documents.

Purpose

The purpose of this document is to describe how to use the diagnostic script POAccountDiag.sql to collect
troubleshooting information and to validate common data issues for accounting errors within your Purchasing application.
This diagnostic will allow you to address some data integrity issues without requiring you to log a Service Request with
support and will provide consolidated information to Oracle Support when a Service Request is needed.

The script will produce an html output that contains information relevant to encumbrance issues for the document line
specified as part of the parameters, along with some data validation checks to identify common data corruption issues.

When to use it?

Most cases you need to run POAccountDiag.sql prior to logging a Service Request when you have errors
reserving/unreserving funds for a document or when approval fails due to a reservation failure. Use it as well for any
encumbrance issue

How to use it?

Important: Always be sure to download and run the latest version of POAccountDiag.sql from this note for the most
comprehensive diagnostic on your purchasing documents. The script will be kept up to date with new Generic Data
Fix (GDF) scripts and other Non-GDF data validation queries as they are released by development.

The current version of POAccountDiag.sql is 120.6.10

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1atz2rbv3q_125&id=1483743.1 1/4
7/24/2019 Document 1483743.1

This script will check the data for a document line (Purchase Order, Blanket Release or Requisition) you specify. It will also
scan for additional known issues. It will not fix the data but simply report on what corruption exists and point you to the
notes and/or patches that will allow you to fix the data.

NOTE: In the images below and/or the attached document, user details / company name / address / email / telephone
number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance). Any
similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Use the instructions below to run the script:

1. Download the file POAccountDiag.sql .

2. Run the SQL file as shown:

Note: Script POAccountDiag.sql is intended to be run using SQL*Plus. Do not use SQL developer as it will not recognize
some SQL commands.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1atz2rbv3q_125&id=1483743.1 2/4
7/24/2019 Document 1483743.1

This script will prompt for these parameters:

a. Applications username: Enter the name of the user used to log into the application to reproduce the issue

b. Responsibility ID: Enter the responsibility ID from which the issue reproduces. The responsibility names and IDs
are listed by the script above this parameter

c. Document Type: the options are PO, REQUISITION or RELEASE

d. Document Number: Enter the number of the document (PO, Requisition, or Release) you are having problems with

e. Release number: enter value only if the document type is a release, otherwise just hit enter key

f. Document Header ID: This is optional and can be used in case the document found by using the document number
(parameter d) is not the correct one.

h. For older version POAccountDiag.sql only: Line number: to prevent large volume of output data and potential
issues with the script, the script prints information for only a specific line in the document. Enter the line number you
want to troubleshoot. Default value is 1.

i. Validate Data?: In addition to gather troubleshooting information, this script includes a section where known data
corruption issues are validated against your document. Running validation can cause the script to take longer to
finish but it provides helpful information that can help resolve your issue. Enter Y to run validation of data. Default
value is Y

j. Generate Debug Messages?: Use it ONLY if your issue is approving a document or reserving funds. The diagnostic
will execute the main Check Funds procedure for the entire document to allow us gather runtime information like
FND Debug, trace file and runtime data from the global tables. This diagnostic will not modify any data in your
system. Enter Y if you want to gather this information. Default value is N

k. Generate trace? : Enter Y ONLY if the script has performance issues. This trace will be used internally to improve
the script. If you want to generate trace for the script, make sure to select Validate Data?: N. Default value for this
parameter is N

3. The diagnostic script will create an output file of the

format POAccounting_ DOCUMENT_NUMBER RELEASE_NUMBER
._R .html in the same directory from where you run the
diagnostic script. You will see this message when the script completes:

Click below to see a sample of the output and log files generated.

Sample Output File

4. If you entered "Y" in the parameter "Generate Debug Messages?", you might need to collect the FND debug information
and the trace output. The following screenshot is part of the diagnostic output and indicates what you need to perform to
collect this additional information.

5. Review the output file to determine if there is any message indicating possible cause of your issue.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1atz2rbv3q_125&id=1483743.1 3/4
7/24/2019 Document 1483743.1

Still Have Questions?

Join our growing Oracle Procurement Community and learn from your peers and Oracle on how to address your unique iss

1. Access the Community page directly at http://communities.oracle.com or via My Oracle Support with https://supporthtm
2. In ‘Select a sub-space to participate or start a discussion’ enter Procurement.
3. Double click on Procurement (MOSC) from the list.
4. Click on ‘Start a Discussion’ link under the Actions section and submit your question.

The information, software, products and services contained on this web site may be out of date or include omissions,
inaccuracies or other errors. The information, software products and services contained on this web site, including the
materials, are provided "as is" and without warranty. Oracle does not warrant that the information in the materials is
up to date or error free, nor does it provide any other warranties, whether expressed or implied in law, including the
implied warranties of merchantability or fitness for a particular purpose. The materials are not a program or
documentation under the terms of your license agreement(s) with Oracle. 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, this
web site or any other hyper-linked web site. Oracle reserves the right to make changes or updates to this web site or
the products or programs described in this web site at any time without notice.

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1atz2rbv3q_125&id=1483743.1 4/4