# Oracle EBS Profile Option Change Log Worksheet > Source: https://netray.co/tools/oracle-ebs-profile-option-change-log-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Track every profile option change with its level, old and new value, reason and approver, so clones, upgrades and audits stop being guesswork. ## Category oracle ## Erp Oracle E-Business Suite ## Audience - EBS DBA - EBS functional analyst - IT auditor ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Change date **Key:** date **Type:** date #### Profile option (user name) **Key:** profile **Type:** text #### Level **Key:** level **Type:** select **Options:** - Site - Application - Responsibility - User - Server - Org #### Level value **Key:** level_value **Type:** text #### Old value **Key:** old_val **Type:** text #### New value **Key:** new_val **Type:** text #### Instance **Key:** instance **Type:** select **Options:** - DEV - TEST - UAT - PROD #### Change ticket **Key:** ticket **Type:** text #### Changed by **Key:** by **Type:** text #### Approved by **Key:** approved **Type:** text #### Reason **Key:** reason **Type:** text **Rows:** **Date:** 2026-10-05 **Profile:** Concurrent: Report Access Level **Level:** Site **Level value:** Site **Old val:** User **New val:** Responsibility **Instance:** TEST **Ticket:** CHG-4812 **By:** R. Mehta **Approved:** S. Collins **Reason:** Align with security design **Date:** 2026-10-06 **Profile:** Printer **Level:** User **Level value:** JDOE **New val:** PRN_FIN_02 **Instance:** PROD **Ticket:** CHG-4820 **By:** R. Mehta **Approved:** S. Collins **Reason:** New finance printer **Date:** 2026-10-09 **Profile:** Sign-On: Audit Level **Level:** Site **Level value:** Site **Old val:** None **New val:** D **Instance:** UAT **Ticket:** CHG-4833 **By:** L. Okafor **Approved:** S. Collins **Reason:** Enable sign-on audit for review **Date:** 2026-10-12 **Profile:** Concurrent: Active Request Limit **Level:** User **Level value:** BATCHUSR **New val:** 5 **Instance:** PROD **Ticket:** CHG-4841 **By:** L. Okafor **Approved:** S. Collins **Reason:** Throttle batch user **Totals:** #### Changes logged **Key:** date **Agg:** count **Notes:** Profile values are stored in FND_PROFILE_OPTION_VALUES against FND_PROFILE_OPTIONS. Use this log together with the Profile Options report or a SQL extract from your own instance, and verify the profile option names against your release. ## Content **Intro:** Profile options quietly control how EBS behaves, and they are rarely tracked well. After a clone or an upgrade, someone always asks why a setting differs between TEST and PROD. This log gives you a simple, exportable record of who changed what, at which level and why. **Sections:** #### How to use the log **Body:** Add one row per change. Record the user-visible profile option name, the level where the value was set and the level value, such as a responsibility name or user name. Always capture the old value so a rollback is possible. Export to Excel or CSV for audits, or paste the rows into your change ticket. Keep the log per environment or use the instance column to filter. #### Why profile levels matter **Body:** A profile option can be set at several levels and the most specific wins at runtime. In the usual order, user overrides responsibility, which overrides application, which overrides site. Some options also support server or organization levels. A value that looks correct at site level may be overridden somewhere you did not check, so the level and level value columns are the most important fields in this log. **Bullets:** - Always log the level and the exact level value - Treat site level changes as high impact - Re-check profile values after every clone - Note seeded defaults you changed, so upgrades can be reviewed #### Using the log after a clone or upgrade **Body:** Cloning copies profile values from the source, and Oracle's clone tooling resets some, such as URLs and node related values. Compare your log with the target instance to see which environment specific values must be reapplied. Before an upgrade, the log also tells you which seeded options were customised, which is a short list worth reviewing in the release notes. **Cta:** If you want an easier way to answer configuration questions across several EBS instances, we can show a read-only, query-visible approach. No obligation. **Faq:** #### Where are Oracle EBS profile option values stored? **Answer:** Definitions sit in FND_PROFILE_OPTIONS and the values at each level sit in FND_PROFILE_OPTION_VALUES. The System Profile Values form shows them in the application. Table details can vary a little by version, so verify in your instance. #### Which profile level wins in Oracle EBS? **Answer:** The most specific level that has a value is used. In the usual hierarchy user is more specific than responsibility, then application, then site. Some profile options may also be set at server or organization level. #### Does EBS audit profile option changes automatically? **Answer:** The tables hold who last updated a value and when, but not a full history of old values. Many sites add database auditing or keep a manual log like this one to preserve the old value and the reason. #### Should profile options be changed directly in production? **Answer:** Prefer a controlled change: test in a lower instance, log the change, get approval, then apply it in production. Some profile values can be migrated with FNDLOAD, others are set by hand and need documentation. ## Search terms oracle ebs profile option change log, oracle apps profile options audit, ebs profile option values after clone, fnd_profile_option_values change tracking, oracle ebs profile option levels site responsibility user, oracle ebs configuration change log excel --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json