Results for “delete_profile_option_values”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FND_PROFILE_OPTION_VALUES_PKG is a PL/SQL package owned by the APPS schema that provides the low-level data manipulation layer for Oracle EBS profile option values. Profile options are the standard configuration mechanism through which Oracle Applications behavior is controlled at the Site, Application, Responsibility, and User levels. This package encapsulates the insert, update, and delete operations against the FND_PROFILE_OPTION_VALUES table, allowing callers to persist profile option settings without issuing direct DML against the underlying tables. In the ETRM classification it is registered as an OTHER API rather than a public, supported interface, indicating that it is an internal utility package rather than a formally published extension point. The package is marked VALID in the APPS schema and depends only on SYS.STANDARD at the dependency level, reflecting that all table access is performed through APPS synonyms.
Key Procedures and Functions
The ETRM documentation records six documented procedures and functions within the package. The primary entry points are the standard table-handler triple:
- INSERT_ROW — Inserts a new row into FND_PROFILE_OPTION_VALUES, creating a profile option value assignment at a specific hierarchy level (Site, Application, Responsibility, or User) for a given profile option.
- UPDATE_ROW — Modifies an existing profile option value row, used when the value assigned to a level is changed rather than newly created.
- DELETE_ROW — Removes a single profile option value row identified by its level and context, reversing a specific assignment.
- DELETE_PROFILE_OPTION_VALUES — Performs a mass deletion of profile option values, typically scoped to a profile option or level, and is the mechanism used when an option is retired or its values are reset.
The remaining two documented entries correspond to the package specification and body declarations rather than distinct callable units. Parameter lists are not published in the ETRM record and should be obtained from the package specification in the database.
Tables Accessed
The package references two tables through APPS synonyms:
- FND_PROFILE_OPTIONS — The profile option definition table. It is consulted to validate that the option being set exists and to determine attributes governing valid values, such as the level hierarchy (hierarchy type) and whether the option is user-updatable.
- FND_PROFILE_OPTION_VALUES — The transaction table holding the actual assigned values. It carries the profile option identifier together with LEVEL_ID, LEVEL_VALUE, and LEVEL_VALUE_APPLICATION_ID, which together identify the specific context of the assignment. All insert, update, and delete activity performed by this package targets this table.
Access to both tables is indirect, resolved through synonyms owned by APPS, which is why the dependency report shows no direct table dependencies other than SYS.STANDARD.
Usage Notes
FND_PROFILE_OPTION_VALUES_PKG is referenced by two other packages — FND_PROFILE and FND_PROFILE_OPTIONS_PKG — and by itself. FND_PROFILE is the runtime profile caching and retrieval package, while FND_PROFILE_OPTIONS_PKG manages profile option definitions. This reference pattern confirms that the package sits beneath the public profile APIs as a private persistence layer. In practice, profile option values are changed through the System Administrator responsibility's Profile > System form, which drives the higher-level FND_PROFILE APIs; those in turn call this package to write the changes. Direct invocation from custom code is possible but is not recommended, because the package does not expose a documented, supported signature in the ETRM inventory and bypasses validation and caching logic performed by FND_PROFILE. Customizations requiring programmatic profile manipulation should prefer the documented FND_PROFILE.PUT and related public APIs, which handle cache invalidation and validation. Where the package is called directly, changes should be committed within the caller's transaction and followed by appropriate cache refresh, otherwise the running session may continue to read stale values.