Results for “purpose_code”

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

Overview

FND_PURPOSE_ATTRIBUTE_LIST_V is a reporting view owned by the APPS schema within the FND – Application Object Library product. It presents a denormalized, comma-separated listing of privacy attribute names associated with each purpose code registered in Oracle E-Business Suite. Purposes in EBS represent the declared reasons for collecting or processing personally identifiable information, and each purpose may be tied to one or more privacy attributes. The view consolidates that many-to-many relationship into a single row per purpose, exposing the aggregated attribute list as a delimited string.

The view is particularly relevant to users searching on purpose_code, the primary grouping key exposed by the view. It serves as a convenient read-only access point for administrators, auditors, and developers who need to inspect how purposes map to privacy attributes without writing recursive SQL against the underlying intersection table. Because the view is defined in the APPS schema and marked VALID, it is available for querying from any EBS session with suitable privileges.

Underlying Base Objects

The documented base objects referenced by this view are FND_PRIVACY_ATTRIBUTES_VL (a view) and FND_PURPOSE_ATTRIBUTES (a synonym). FND_PURPOSE_ATTRIBUTES is the intersection object that records the association between a purpose code and a privacy attribute code. FND_PRIVACY_ATTRIBUTES_VL is the multi-language view supplying translatable privacy attribute names.

The view text joins these two objects on PRIVACY_ATTRIBUTE_CODE and then applies a hierarchical query. A LAG analytic function generates a CONNECT_ID that links each row to its predecessor within the same purpose code, ordered by purpose code. The CONNECT BY PRIOR RNUM = CONNECT_ID clause walks this chain starting from rows where CONNECT_ID is null, and SYS_CONNECT_BY_PATH builds the delimited attribute name string. The outer query applies SUBSTR to strip the leading delimiter and MAX with GROUP BY PURPOSE_CODE to collapse the hierarchy into one row per purpose. A commented predicate (--AND D.PURPOSE_CODE = 'TELE_SALES') in the source indicates the pattern used for filtering a single purpose.

Key Columns

• PURPOSE_CODE — The unique code identifying a purpose. It is the grouping column of the view and the field most commonly used in WHERE clauses, joins to other purpose-related tables, and reporting filters.
• ATTR_LIST — The aggregated, comma-and-space delimited string of privacy attribute names associated with the purpose. It is produced by SYS_CONNECT_BY_PATH over PRIVACY_ATTRIBUTE_NAME and returned by the MAX aggregate. A null or empty value indicates the purpose has no associated privacy attributes.

Because the view exposes only these two columns, consumers relying on additional descriptive attributes of the purpose or individual attribute-level detail must join back to FND_PURPOSE_ATTRIBUTES or FND_PRIVACY_ATTRIBUTES_VL.

Common Use Cases and Queries

The principal use case is auditing and reporting on privacy attribute assignments per purpose. A typical query retrieves the full mapping:

• SELECT purpose_code, attr_list FROM fnd_purpose_attribute_list_v;
• SELECT purpose_code, attr_list FROM fnd_purpose_attribute_list_v WHERE purpose_code = 'TELE_SALES';
• SELECT purpose_code, attr_list FROM fnd_purpose_attribute_list_v WHERE attr_list LIKE '%EMAIL%';

The second query mirrors the commented predicate found in the view definition and is useful when investigating a single purpose. The third supports reverse lookups, identifying which purposes reference a given attribute by name. Additional scenarios include feeding comma-separated attribute lists into downstream integrations or extracts, and validating configuration after patches or upgrades. Because ATTR_LIST is a synthesized string, filtering on it uses pattern matching rather than equality against individual values. Where exact attribute-level rows are required, query FND_PURPOSE_ATTRIBUTES directly and join to FND_PRIVACY_ATTRIBUTES_VL for translated names.