How to upload your custom code for ongoing changes risk analysis?

This article is relevant for Release Dynamix ongoing changes risk and impact analysis
If you are working on a standalone Patches project or an upgrade project, follow these instructions instead
Panaya solution requires running a Java Script on your Oracle Apps Server.
This Script performs the following tasks:
  • Extraction of custom developed code
  • Identification of the usage of these custom objects within your Oracle Apps system

For a list of objects extracted by Panaya, click here

If you encounter issues while performing the following steps, these articles might help.

Before running the Extraction Process,
please make sure that you meet the requirements
Good to Know!
You can automate this process by implementing our API | Learn more
Download the Oracle Extraction Tool
  1. Click on the Settings button to open up the Settings panel, then select Code Box
  2. Before you continue, check that the relevant System appears on the top left corner of the screen
  3. Download the Oracle extraction tool (jar file)
    Always download the newest extraction code from Panaya's Code Box. It is not recommended to use older versions of the extraction.

Extracting the Custom Code and Usage Statistics

For full usage statistics define the following - 

  • Form Usage - Set the system profile option Sign-On: Audit Level to Form for the highest auditing level
  • Framework -  To activate tracking, set Page Access Tracking in Oracle Applications 11i [ID 278881.1] or Page Access Tracking in Oracle Applications Release 12 [ID 402116.1]

For more information click here


  1. Upload panaya-extractor.jar to your Oracle Application Server.
  2. Change your working directory to the location of the panaya-extractor.jar
  3. Using your Oracle Apps OS user, execute the following command:
    java -jar panaya-extractor.jar <apps password> [<ETL type>] [-customJavaTop=<Custom Java Top>]

    Parameters explanation
    <apps password> - The password of your apps schema in the DB
    [<ETL type>] - What data to extract during the ETL 

    F - Full ETL (Customizations & Usage data) Please use this for the first extraction
    C - Customizations only
    U - Usage only

    If no ETL type is specified, a Full ETL will be executed

    [-customJavaTop=<Custom Java Top>] - Path(s) to your framework projects other than $JAVA_TOP.
    If more than one path is defined in the classpath, use ':' as a delimiter - If -customJavaTop is not specified, will use only $JAVA_TOP.

    During the extraction process, an output directory will automatically will be created for you.
    The name of the directory will be output_<date>_<time>.
    At the end of the process, one ZIP File will be created in your output directory, which you will need to upload to Panaya Code Box.
    If you do not have access from your Application server to the Panaya web site, please copy the file from there.
If you run the Concurrent Manager on a different server than the Oracle Application server, a separate extraction must be done from each server.
If you have shared APPL_TOP with your Concurrent Manager server, you do not need to do a separate extraction.
Upload the Extract File
  1. Upload the ZIP file to Panaya Code Box
  2. Click on the Upload button 
  3. Users with the following permissions will be notified by email once the analysis is available (this usually takes 48 hours or less) - 
    - Code Box - Upload ETL and/or Upload PTL permissions
    - Users - Create and Edit permission
  4. Upon completion, you will recieve an email notification. Now is the time to analyze Patches and Customizations