Search Results parent_data_point_id

Overview

AR_CMGT_DATA_POINTS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and exposes the metadata that defines "data points" used by the Collections Management and credit management framework. In Oracle Advanced Collections, data points represent discrete, scored or checklist-displayed attributes drawn from a customer, transaction, or external source, and they drive scoring models, credit reviews, and collection strategies.

The view presents a translation-aware, user-facing layer over the underlying data point definitions, joining the base table, its translation table, and application information. Because Oracle EBS implements translated ("_TL") tables for objects whose descriptive text is localized, the _VL suffix indicates this view returns rows in the session's current language, resolved through USERENV('LANG'). This makes it suitable for reporting, integrations, and any functional reference where the data point name and description must appear in the logged-in user's language.

Underlying Base Objects

The documented metadata for this view identifies three referenced objects:

• AR_CMGT_DATA_POINTS_B (SYNONYM) — the base table storing language-independent attributes of each data point, including flags, application, package and function references, return data type, and parent relationships.
• AR_CMGT_DATA_POINTS_TL (SYNONYM) — the translation table providing the localized DATA_POINT_NAME and DESCRIPTION.
• FND_APPLICATION_VL (VIEW) — the Applications view supplying APPLICATION_NAME.

The view joins B to T on DATA_POINT_ID with T.LANGUAGE = USERENV('LANG'), and joins B to FND_APPLICATION_VL on APPLICATION_ID. The ROW_ID column is derived from B.ROWID, giving each row a stable identifier aligned to the base table.

Key Columns

• DATA_POINT_ID — Primary identifier of the data point; the join key across the base and translation tables.
• DATA_POINT_NAME and DESCRIPTION — Localized text sourced from AR_CMGT_DATA_POINTS_TL.
• DATA_POINT_CODE and DATA_POINT_CATEGORY / DATA_POINT_SUB_CATEGORY — Functional classification of the data point.
• USER_DEFINED_FLAG — Indicates whether the data point was user-created or seeded by Oracle.
• SCORABLE_FLAG and DISPLAY_ON_CHECKLIST_FLAG — Control whether the data point participates in scoring models or appears on collection checklists.
• APPLICATION_ID and APPLICATION_NAME — The owning application, linked through FND_APPLICATION_VL.
• PACKAGE_NAME, FUNCTION_NAME, and FUNCTION_TYPE — The PL/SQL implementation that resolves the data point value at runtime.
• RETURN_DATA_TYPE and RETURN_DATE_FORMAT — Define the expected value type and date formatting returned by the function.
• PARENT_DATA_POINT_ID — Supports hierarchical relationships between data points.
• ENABLED_FLAG — NVL-normalized to 'N' when null; governs active use.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include validating configuration for scoring models and checklists, auditing user-defined versus seeded data points, and driving integration extracts where localized names are required.

List enabled, scorable data points with localized names:

• SELECT data_point_id, data_point_name, data_point_code, data_point_category, application_name FROM ar_cmgt_data_points_vl WHERE scorable_flag = 'Y' AND enabled_flag = 'Y' ORDER BY data_point_name;

Identify user-defined data points and their implementing functions:

• SELECT data_point_name, package_name, function_name, function_type, return_data_type FROM ar_cmgt_data_points_vl WHERE user_defined_flag = 'Y';

Report data points by application and category for a configuration review:

• SELECT application_name, data_point_category, COUNT(*) FROM ar_cmgt_data_points_vl GROUP BY application_name, data_point_category ORDER BY 1, 2;

Because the view filters on USERENV('LANG'), callers should run queries in a session whose language corresponds to the desired translation; for example, setting NLS_LANG appropriately ensures DATA_POINT_NAME and DESCRIPTION are returned in the expected locale.