Results for “fnd_privacy_attribute_children”

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

Overview

FND_PRIVACY_ATTRIBUTE_CHILDREN is a metadata repository table owned by the APPLSYS schema in Oracle E-Business Suite Application Object Library (FND). It stores the hierarchical relationships between privacy attributes, defining parent-child associations used by the EBS privacy and security framework to determine how attribute-level data protections cascade or inherit across related objects. The table functions as a configuration registry for privacy attribute dependency chains, allowing administrators and the privacy engine to resolve which attributes are subordinate to a given parent attribute when enforcing data access rules.

In ETRM 12.2.2 the table is documented with nine physical columns and is flagged VALID. The heuristic Data Vault classification mined from its foreign key structure is standalone. In modeling terms, this suggests the table behaves primarily as a descriptive reference or relationship structure rather than a fully normalized link or satellite; it may still be treated as a link-style association when cataloguing parent-to-child attribute dependencies.

Key Information Stored

The most significant columns in FND_PRIVACY_ATTRIBUTE_CHILDREN are:

• PARENT_ATTRIBUTE_CODE — the identifier of the governing parent privacy attribute. This column forms the leading component of the unique business key.
• ATTRIBUTE_CODE — the identifier of the child attribute subordinate to the parent. Together with PARENT_ATTRIBUTE_CODE it constitutes the unique business key.
• SECURITY_GROUP_ID — the security group scoping the attribute relationship; the sole documented foreign key references FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit who-columns recording creation and modification of each relationship row.

The documented unique index FND_PRIVACY_ATTR_CHILDREN_U1 (PARENT_ATTRIBUTE_CODE, ATTRIBUTE_CODE) is the business-key candidate; no dedicated surrogate primary key column is documented in the ETRM extract, so the composite business key should be treated as the logical identifier.

Common Use Cases and Queries

Typical reporting and administrative scenarios include resolving the full descendant hierarchy of a privacy attribute, auditing which child attributes are governed by a given parent, and validating configuration completeness before enabling privacy enforcement.

• List all children of a specific parent attribute:

SELECT attribute_code FROM fnd_privacy_attribute_children WHERE parent_attribute_code = :parent;

• Join to the security group definition to report the scoping of each relationship:

SELECT c.parent_attribute_code, c.attribute_code, g.security_group_name FROM fnd_privacy_attribute_children c, fnd_security_groups g WHERE c.security_group_id = g.security_group_id;

• Audit recently modified relationship rows using LAST_UPDATE_DATE to troubleshoot unexpected privacy behavior after configuration changes.

Related Objects

The documented foreign key establishes FND_SECURITY_GROUPS as the principal related table, joined on SECURITY_GROUP_ID. In practice the table is also consumed alongside the parent privacy attribute definitions in the FND privacy schema, and its audit columns align with the standard EBS WHO column conventions shared by most APPLSYS configuration tables. The following are the most significant related objects:

• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; scopes each parent-child attribute relationship.
• FND_PRIVACY_ATTRIBUTES — the parent attribute registry that defines PARENT_ATTRIBUTE_CODE and ATTRIBUTE_CODE values referenced here.
• FND_PRIVACY_ATTRIBUTE_RELATIONS — companion relationship metadata evaluated by the privacy engine.
• FND_OBJECTS and FND_OBJECT_INSTANCES — the object registry against which privacy attributes are ultimately enforced.
• FND_FORM_FUNCTIONS — function-level security definitions frequently co-configured with privacy attributes.
• Standard WHO-column audit infrastructure and the EBS privacy engine PL/SQL APIs that read this table during attribute resolution.