Results for “fnd_purpose_attributes_u1”

12 results




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

Overview

APPLSYS.FND_PURPOSE_ATTRIBUTES is a VALID Oracle E-Business Suite table owned by the APPLSYS schema. Its FND design data object is registered as FND.FND_PURPOSE_ATTRIBUTES, and it is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. The table forms part of the Oracle EBS foundation (FND) layer that governs how purposes and privacy attributes are mapped and defaulted across applications such as Oracle iRecruitment, Oracle Learning Management, and Oracle Advanced Benefits.

From a Data Vault modeling perspective, the mined relationship metadata classifies this object as standalone, which suggests interpreting FND_PURPOSE_ATTRIBUTES as a hub-like reference entity rather than a link or satellite. It does not itself act as a transaction link between two hubs, but it does carry a single documented foreign key from SECURITY_GROUP_ID to FND_SECURITY_GROUPS, so it may also be modeled as a hub with a dependent satellite for the remaining descriptive columns. The table exposes a "#" variant, FND_PURPOSE_ATTRIBUTES#, which indicates that it participates in Oracle's journal/audit shadow-table mechanism (the postfix "#" table stores the audit trail used by the FND audit infrastructure).

Key Information Stored

The table contains 11 documented columns. The most important include:

The U1 index on PURPOSE_ATTRIBUTE_ID is the technical surrogate key, while the U2 composite index on (PURPOSE_CODE, PRIVACY_ATTRIBUTE_CODE) is the meaningful business-key candidate. Practitioners should treat the two-column U2 combination as the natural identifier when reconciling data across the 12.1.1 and 12.2.2 releases, since the schema is identical in both.

Common Use Cases and Queries

Typical uses include retrieving the default attribute values for a given purpose, validating privacy configuration, and reporting on which privacy attributes are attached to each purpose. The standard query pattern mirrors the documented Query Text:

  • SELECT PURPOSE_ATTRIBUTE_ID, PURPOSE_CODE, PRIVACY_ATTRIBUTE_CODE, ATTRIBUTE_DEFAULT_CODE FROM APPLSYS.FND_PURPOSE_ATTRIBUTES WHERE PURPOSE_CODE = :purpose_code;
  • SELECT a.PURPOSE_CODE, a.PRIVACY_ATTRIBUTE_CODE, a.ATTRIBUTE_DEFAULT_CODE FROM APPLSYS.FND_PURPOSE_ATTRIBUTES a WHERE a.PURPOSE_CODE = :purpose_code AND a.PRIVACY_ATTRIBUTE_CODE = :attribute_code; — a direct lookup by the U2 business key.
  • SELECT a.* FROM APPLSYS.FND_PURPOSE_ATTRIBUTES a JOIN APPLSYS.FND_SECURITY_GROUPS g ON a.SECURITY_GROUP_ID = g.SECURITY_GROUP_ID; — join to resolve security group context.

Because the U2 index is unique, any query filtering on the purpose/attribute pair returns at most one row, making it well suited to lookup validation and to seed-data extraction for concurrent programs.

Related Objects

  • APPLSYS.FND_PURPOSE_ATTRIBUTES# — the audit shadow table maintained alongside the base table by the FND audit framework.
  • APPLSYS.FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; joins on the SECURITY_GROUP_ID column.
  • FND_PURPOSE_ATTRIBUTES_U1 / FND_PURPOSE_ATTRIBUTES_U2 — the two unique indexes on APPS_TS_TX_IDX; U2 on (PURPOSE_CODE, PRIVACY_ATTRIBUTE_CODE) is the key lookup access path.
  • APPLSYS.FND_PURPOSE / FND_PURPOSES — the parent purpose definitions joined by PURPOSE_CODE.
  • APPLSYS.FND_PRIVACY_ATTRIBUTES — the privacy attribute definitions joined by PRIVACY_ATTRIBUTE_CODE.

Because the documented metadata shows no outbound references other than SECURITY_GROUP_ID, most functional relationships are enforced at the application level via the PURPOSE_CODE and PRIVACY_ATTRIBUTE_CODE columns rather than by database foreign keys. Any integration or ETL that loads this table should therefore validate those code values against their respective FND reference tables.