Results for “connect_id”

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

Overview

FND_PURPOSE_ATTRIBUTE_LIST_V is an APPS-owned database view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents a consolidated, comma-delimited list of privacy attributes associated with each purpose code defined in the EBS privacy framework. It is a reporting and integration aid rather than an operational object; it does not store data of its own but derives its output from the intersection of purpose-attribute assignments and the multilingual privacy attribute definitions.

The view is significant because the underlying relationship between purposes and privacy attributes is fundamentally one-to-many. Consumer-facing integrations, audit extracts, security reviews, and self-service reporting frequently require that set of attributes to be flattened into a single readable string. FND_PURPOSE_ATTRIBUTE_LIST_V performs that flattening using hierarchical string aggregation, exposing one row per purpose code with the aggregated attribute names in a single column. Because the aggregation relies on hierarchical query mechanics, the view is also a useful reference example of pre-12c string aggregation techniques within EBS.

Underlying Base Objects

The view is defined over two documented base objects:

• FND_PURPOSE_ATTRIBUTES (referenced as a synonym) — the intersection table that maps purpose codes to privacy attribute codes, one row per assigned attribute.
• FND_PRIVACY_ATTRIBUTES_VL (a view) — the multilingual privacy attribute definition source, supplying the translatable PRIVACY_ATTRIBUTE_NAME value used in the output list.

The two are joined on PRIVACY_ATTRIBUTE_CODE. The inner inline view computes ROWNUM (RNUM) and uses the LAG analytic function to derive CONNECT_ID, which represents the previous row's ROWNUM within the same purpose code partition. The hierarchical CONNECT BY PRIOR RNUM = CONNECT_ID clause, combined with START WITH CONNECT_ID IS NULL, chains the rows of each purpose together. SYS_CONNECT_BY_PATH then builds the delimited path, and SUBSTR strips the leading delimiter. The outer query applies MAX(ATTR_NAME) and GROUP BY PURPOSE_CODE to collapse the resulting hierarchy to a single row per purpose.

Key Columns

• PURPOSE_CODE — The identifier of the purpose, originating from FND_PURPOSE_ATTRIBUTES.PURPOSE_CODE. It is the grouping key and the primary lookup column for the view.
• ATTR_LIST — The aggregated, comma-and-space delimited string of privacy attribute names assigned to the purpose. It is produced by SYS_CONNECT_BY_PATH over PRIVACY_ATTRIBUTE_NAME and selected through the MAX aggregation. The column alias ATTR_LIST is assigned in the outer query.

The internal columns RNUM, CONNECT_ID, and LEVEL are not projected by the outer query and are not visible to consumers of the view. PRIVACY_ATTRIBUTE_NAME is likewise consumed inside the subquery only.

Common Use Cases and Queries

Typical uses include audit documentation of which personal data attributes are collected under each purpose, validation that no purpose has an empty attribute list, and feeding extracts that require a flattened attribute representation.

Retrieve the attribute list for one purpose:

• SELECT purpose_code, attr_list FROM apps.fnd_purpose_attribute_list_v WHERE purpose_code = 'TELE_SALES';

List all purposes with their attributes, ordered alphabetically:

• SELECT purpose_code, attr_list FROM apps.fnd_purpose_attribute_list_v ORDER BY purpose_code;

Identify purposes with no assigned attributes:

• SELECT purpose_code, attr_list FROM apps.fnd_purpose_attribute_list_v WHERE attr_list IS NULL;

Note that the view returns one row per purpose code regardless of row count in FND_PURPOSE_ATTRIBUTES, and that purposes with no attributes may be absent or return a null ATTR_LIST depending on the join result. Access should be granted through the APPS schema, and queries should be run with the standard EBS responsibility and MOAC considerations in mind.