OracleFree worksheetPDF, Excel, Word exportOracle E-Business Suite

Oracle EBS Profile Option Change Log Worksheet

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.

Download:
Change dateProfile option (user name)LevelLevel valueOld valueNew valueInstanceChange ticketChanged byApproved byReason
Changes logged
4

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.

Compare EBS settings across instances

Optional walkthrough of querying configuration across DEV, TEST and PROD from one read-only interface.

Optional. The tool and every export work without this. No spam.

How to use the log

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

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.

  • 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

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.

Frequently Asked Questions

Where are Oracle EBS profile option values stored?

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?

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?

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?

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.

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.