--- title: "Extracting Oracle Custom Code for Ongoing Changes" slug: "how-to-upload-your-custom-code-for-ongoing-changes-risk-analysis" updated: 2022-02-14T08:38:39Z published: 2022-02-14T08:38:39Z canonical: "success.panaya.com/how-to-upload-your-custom-code-for-ongoing-changes-risk-analysis" --- > ## Documentation Index > Fetch the complete documentation index at: https://success.panaya.com/llms.txt > Use this file to discover all available pages before exploring further. # Extracting Oracle Custom Code for Ongoing Changes 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](/v1/docs/how-to-extract-upload-your-custom-code-using-the-code-box)Panaya solution requires running JavaScript on your Oracle Apps Server. This script extracts custom-developed code and retrieves custom objects usage in Oracle Apps. [For a list of objects extracted by Panaya, click here](/v1/docs/what-objects-and-file-types-are-covered-by-panaya-upgrade-project-impact-analysis) **Prerequisites** Verify that you meet the requirements [in this article](/v1/docs/what-are-the-prerequisites-for-running-the-oracle-code-extraction) **Good to Know!** You can automate this process by implementing our API. [Learn more](/v1/docs/how-to-implement-automatic-custom-code-upload-using-api) ## **Oracle Extraction Tool** 1. Click on the **Settings button**![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1639922349160.png) 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. ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1639922361977.png) --- ## **Extracting the Code and Usage** **Upload** panaya-extractor.jar to your **Oracle Application Server**. Then, **change** your working directory to the **location** of the panaya-extractor.jar. Using your Oracle Apps OS user, **execute the following command -** java -jar panaya-extractor.jar [] [-customJavaTop=] **Important!** 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](/v1/docs/what-usage-information-is-collected-by-panaya) --- ## **Parameters** - The password of your apps schema in the DB [] - 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=] - 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. ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1639922383640.png) During the extraction process, an output directory will automatically be created for you. The name of the directory will be output__