--- title: "Extracting Oracle Custom Code" slug: "how-to-extract-upload-your-custom-code-using-the-code-box" updated: 2023-06-12T09:14:00Z published: 2023-06-12T09:14:00Z canonical: "success.panaya.com/how-to-extract-upload-your-custom-code-using-the-code-box" --- > ## 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 Panaya solution requires running JavaScript on your Oracle Apps Server. This script extracts custom-developed code and retrieves custom objects usage in Oracle Apps.This article is for extracting custom code for upgrade projects.[Click here for extracting code for ongoing changes](/v1/docs/how-to-upload-your-custom-code-for-ongoing-changes-risk-analysis).  [For a list of objects extracted by Panaya, click here](/v1/docs/what-objects-does-panaya-extract) **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-1639921732956.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-1639921745623.png) --- ## ## **Extracting the Code and Usage** **Important!** For complete 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) **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 -prompt [] [-customJavaTop=]  **Note** If you wish to expedite the extraction process when upgrading to Oracle EBS version 12.2 and above, [click here](/v1/docs/how-to-expedite-the-extraction-process-when-upgrading-to-oracle-ebs-target-version-122-and-above). --- ## **Parameters** [] - What data to extract during the ETL [-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. [-prompt] - this will open a dialog box for the user to enter the APPS and SYSTEM password. This will mask the password for cases where other users attempt to sign in to the system and execute the command ps -ef. **Note** The prompt will request the APPS password for the Oracle EBS target version up to 12.1.3 (including). The prompt will request both APPS and SYSTEM passwords for Oracle EBS target version above 12.2 (including). 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 ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1639921764260.png) During the extraction process, an output directory will automatically will be created for you. The name of the directory will be output__