Oracle Technical : How to find Files Versions and Locations

1) To find the patch set level of an application (module):

1. Get the application ID

select application_id , application_name from fnd_application_tl where application_name like <application_name>

for eg. if Application Name is ‘Oracle Quoting’
select * from fnd_application_tl where application_name like ‘%Oracle Quoting%’

2. Get the Patch Set Level for the application (field: PATCH_LEVEL).

Select * from fnd_product_installations where application_id = <application_id>

For e.g. Application_id of Oracle Quoting is 880

Select * from fnd_product_installations where application_id = 880

2) Finding all installed applications

The query to be used for obtaining this information is as follows:

SELECT application_name, application_short_name, decode (status, ‘I’, ‘Installed’, ‘S’, ‘Shared’, ‘Not Installed’) status, a.application_id
FROM fnd_application_all_view a, fnd_product_installations i
WHERE a.application_id = i.application_id
order by 1;

3) To find the location of a file

If we know that a file beginning with hello and ending with a .c extension is located in one of the subdirectories of the current working directory, we can type:

find . -name “hello*.c” –print
find . -name “*pg.xml” –print

4) To find file version

In order to obtain the file version, the command to be run is as follows:

adident Header ‘filename’

5) Location of the .odf file

In order to check for the location of the .odf file, we need to check the following directory after patch application,


This file also exists in $PO_TOP/admin

6) To get the file version of concurrent programs

For UNIX, the command is as follows:

$strings -a $PO_TOP/bin/POXCON | grep ‘$Header’

7) To find the file versions associated with .exe file

The relevant command is as follows:

cd $PO_TOP/bin
strings -a RVCTP | grep -i ‘$Header’

8) Location of .pls files

The relevant command is as follows:


9) To find .lct file

The relevant command is as follows:

strings -a ‘afsload.lct’| grep ‘Header’
10) To find .lpc file

.lpc are generally part of .exe files eg. rvtbm.lpc. The relevant command is as follows:

strings -a RVCTP | grep ‘Header’ | grep ‘rvtbm’

This gives the version of rvtbm.lpc

11) To find .pld file

These are stored as .pll files in AU_TOP/resource. The relevant command is as follows:

strings -a RCVCOTRX.pll | grep ‘Header’
strings -a RCVRCERL.pll | grep ‘Header’
find . -name poemp.odf

12) To find .ppc file

.ppc are generally part of .exe files eg. inltpu.ppc. The relevant command is as follows:

cd $INV_TOP/bin
strings -a INVLIBR | grep -i inltpu

This will give the version of inltpu.ppc. Here INVLIBR is the exe file which has this .ppc file Therefore it is important to know which .exe holds this file also.

14) To find JAVA Files version

Find where the JAVA_TOP is
{How to find : env | grep ‘JAVA_TOP’}
This command will give you the path to JAVA_TOP
e.g. JAVA_TOP=/amer/oracle/vis51/vis51comn/java
Go to that path (directory)
i.e. cd /amer/oracle/vis51/vis51comn/java
Find available files
ls -al
You’ll find a file called
Here you have two options to get the version of
A). string | grep ‘’
B). adident Header | grep ‘ReassignmentRule’
(Note : with adident, do not give the file extension .java)
You will get the file version e.g.

Oracle R12 : Receivables : How to Enable Debugging for Statement Generation Program ( ARXSGP )

“Customer Statement Generation” Program has its own pros and cons. Some client implement it and other ignored it but it is one of good features to use. Many time we get performance or data issues and need to troubleshoot, here are some step to identify any problems :

Enable “Debug Flag” at program level

Responsibility: System Administrator
Navigation: Concurrent > Program > Define
Query shortname = ARXSGP
Click Parameters
Scroll to parameter debug_flag

This might be the last parameter, seeded value for default = select meaning from  fnd_lookups where lookup_type = ‘YES_NO’ and lookup_code = ‘N’

Change this to : select meaning from fnd_lookups where lookup_type = YES_NO’ and lookup_code = ‘Y’  and Save

Set Profile Option ( AR: Enable Debug Message Output ) as Yes

Responsibility: System Administrator
Navigation: Profile > System

Query for Application = Receivables
user = <your user name>
Profile Option = AR: Enable Debug Message Output – Ensure it is set to Yes.

Normally, the statement generation process creates data in the AR_STATEMENT* tables which are used for statement printing. After the statements process completes, it deletes data in these temporary tables. When you need to debug the behavior of statements, it is sometimes necessary to see the data that was populated into these tables. You can disable the deletion of records in the tables by doing the following.

Responsibility: Receivables Manager
Navigation: Print Documents > Statements

Invoke the Menu: Help > Diagnostic > Examine  –Enter the following values:

Value = Y
Click OK and Submit the program

Verfiy Log file :  Review the log file generated by the Concurrent Process: Statement Generation Program. If debug was enabled correctly, you should see text like the following in the log file.

  • arxsgp: Argument 38 Y
  • arxsgp: DEBUG_FLAG is Y, records in interim tables will NOT be deleted

The Statements program use the following 2 interim tables to generate the statement:
The AR_STATEMENT_HEADERS and AR_STATEMENT_LINE_CLUSTERS are interim tables populated by the Statement Generation program. The code creates rows in these tables that are then picked up by the Print Statements program. You can  check the data in following tables:
Picture of AR - Statement Printing (3:45)