Results for “fnd_privacy_attributes_vl”

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

Overview

FND_PRIVACY_ATTRIBUTES_VL is a PL/SQL view owned by the APPS schema in the Oracle E-Business Suite Application Object Library (FND). In EBS 12.1.1 and 12.2.2, it exposes the privacy attribute definitions that drive the E-Business Suite's data privacy and personally identifiable information (PII) framework, which is part of Oracle's Advanced Security / data-masking infrastructure. The "VL" suffix denotes a "view of lists" that joins a _B (base) table to a _TL (translated) table and filters the translated side by the session's language, thereby returning one row per privacy attribute carrying language-appropriate descriptive text.

Because the view is a read-only projection rather than a transactional table, it is used primarily for reporting, inquiry, and integration. Administrators and developers query it to determine which attributes are flagged as sensitive or PII, their sensitivity classification, and the data-scrambling configuration. It also serves as the metadata source for tools that render privacy attribute definitions in the user's native language.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

• FND_PRIVACY_ATTRIBUTES_B — the base table holding the non-translatable, language-independent attribute data. It supplies all columns prefixed with the B alias in the view text, including the code, type, sensitivity, PII flag, descriptive flexfield (DFF) columns ATTRIBUTE1–ATTRIBUTE15, and the OCScrambling columns DSCRAM_LEVEL and DSCRAM_ALGO_ID.
• FND_PRIVACY_ATTRIBUTES_TL — the translated table holding language-specific descriptive text supplied under the aliases T.PRIVACY_ATTRIBUTE_NAME, T.DESCRIPTION, and T.DESCRIPTION_INT.

The join is performed on PRIVACY_ATTRIBUTE_CODE (B equals T), with the translated side additionally constrained by T.LANGUAGE = USERENV('LANG'). This guarantees that only the row matching the session language is returned, so each privacy attribute appears exactly once. The B.ROWID is surfaced as ROW_ID to support RowID-based addressing.

Key Columns

• PRIVACY_ATTRIBUTE_CODE — unique business key identifying each privacy attribute; the join column between the base and translated tables.
• PRIVACY_ATTRIBUTE_NAME, DESCRIPTION, DESCRIPTION_INT — language-specific name and descriptions sourced from the _TL table.
• PRIVACY_ATTRIBUTE_TYPE — classification of the attribute type within the privacy framework.
• SENSITIVITY — the sensitivity rating assigned to the attribute, used for policy and masking decisions.
• PII_FLAG — indicates whether the attribute is considered personally identifiable information.
• LOCKED_FLAG — indicates whether the attribute definition is locked against modification.
• DSCRAM_LEVEL, DSCRAM_ALGO_ID — the data-scrambling level and algorithm reference applied to the attribute.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment values.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, plus ROW_ID (the base row's ROWID).

Common Use Cases and Queries

The view is typically queried to audit which attributes are marked as PII or carry elevated sensitivity, and to verify scrambling configuration before enabling masking. A representative query listing all PII attributes in the current session language is shown below.

SELECT privacy_attribute_code, privacy_attribute_name, privacy_attribute_type, sensitivity, pii_flag, dscram_level, dscram_algo_id FROM apps.fnd_privacy_attributes_vl WHERE pii_flag = 'Y' ORDER BY privacy_attribute_code;

To inspect attributes assigned a specific sensitivity rating or those that are locked, add predicates on the corresponding columns, for example WHERE sensitivity = 'HIGH' or WHERE locked_flag = 'Y'. Because the translated name and description are already resolved by the view, no explicit join is required. Note that results reflect only the language defined by USERENV('LANG'); querying with a different session language is required to obtain alternate-language descriptions.