Results for “fnd_purpose_attributes”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_PURPOSE_ATTRIBUTES is an Application Object Library (FND) configuration table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the privacy attribute settings associated with purposes registered in the FND_PURPOSE repository, forming part of the Oracle EBS data-privacy and security framework. A "purpose" in EBS represents a declared business use for which data is collected, exposed, or processed; FND_PURPOSE_ATTRIBUTES records which privacy attributes apply to each purpose and the default value assigned to each attribute. The table is shipped with a status of VALID and is treated as an Oracle-proprietary data object, meaning direct DML is generally discouraged outside of supported patching and setup paths.

Under the heuristic Data Vault classification mined from the foreign-key structure, FND_PURPOSE_ATTRIBUTES is identified as a standalone object — that is, a self-contained table with no downstream dependents documented in the ETRM relationship graph. In Data Vault modeling terms this suggests it behaves more like a reference or configuration satellite anchored to its own surrogate key rather than a hub or link participating in a network of business transactions.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• PURPOSE_ATTRIBUTE_ID — the surrogate primary key, enforced by unique index FND_PURPOSE_ATTRIBUTES_U1. This is the internal identifier used for row-level referencing and is not meaningful to end users.
• PURPOSE_CODE and PRIVACY_ATTRIBUTE_CODE — the true business key, enforced by unique index FND_PURPOSE_ATTRIBUTES_U2. Together they assert that a given privacy attribute is defined at most once per purpose.
• ATTRIBUTE_DEFAULT_CODE — the default value applied to the privacy attribute when the purpose is invoked, driving runtime behavior in privacy-aware processing.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, controlling which security group the attribute definition belongs to and therefore which operating units or data partitions can see it.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS framework to detect concurrent updates through the Forms or OAF layer.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO columns auditing row provenance and change history, required for support diagnostics and conformance with EBS audit expectations.

Common Use Cases and Queries

Typical usage centers on auditing, troubleshooting, and setup verification. A recurring pattern is to enumerate all privacy attributes registered for a given purpose:

• SELECT PURPOSE_CODE, PRIVACY_ATTRIBUTE_CODE, ATTRIBUTE_DEFAULT_CODE FROM FND_PURPOSE_ATTRIBUTES WHERE PURPOSE_CODE = :purpose;
• Joining to FND_SECURITY_GROUPS to determine the security group context: SELECT a.*, s.SECURITY_GROUP_KEY FROM FND_PURPOSE_ATTRIBUTES a, FND_SECURITY_GROUPS s WHERE a.SECURITY_GROUP_ID = s.SECURITY_GROUP_ID;
• Audit and recent-change reporting by filtering on LAST_UPDATE_DATE or LAST_UPDATED_BY to identify configuration drift after patching.
• Validating that no orphaned or duplicate purpose/attribute pairs exist, which the U2 index should prevent but which can be checked after data fixes.

These queries are commonly embedded in custom reports or in pre-upgrade diagnostics that confirm privacy configuration remains intact across 12.1.1 to 12.2.2 migrations.

Related Objects

The documented foreign-key relationship links the table directly to a small set of core objects:

• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; defines the security partitioning applied to each attribute row.
• FND_PURPOSE_ATTRIBUTES_U1 / U2 — the unique indexes that enforce the surrogate and business keys, treated here as depended-on database objects.
• FND_PURPOSE — the parent purpose repository implied by PURPOSE_CODE, though no explicit FK is documented in the ETRM metadata.
• FND_PRIVACY_ATTRIBUTES or the corresponding privacy attribute registry — implied by PRIVACY_ATTRIBUTE_CODE, providing the attribute definition referenced by each row.

The limited FK footprint and its standalone Data Vault classification confirm that FND_PURPOSE_ATTRIBUTES functions primarily as a configuration reference table rather than a transactional or high-fan-out object within EBS.