Search Results data_point_category




Overview
Explore in AI Chat

Overview

APPS.AR_CMGT_SCORABLE_DATA_POINTS_V is a reporting and integration view within the Oracle Receivables Credit Management (AR_CMGT) module. It presents the complete set of "scorable" data points available to the credit scoring engine in Oracle E-Business Suite 12.1.1 and 12.2.2. Credit scoring evaluates customers against a configurable set of attributes — payment history, exposure, aging, and externally sourced credit bureau data — and each attribute is represented here as a distinct data point. The view consolidates two logically distinct sources into a single uniform result set: internally defined Receivables data points and external Dun & Bradstreet (DNB) data elements. Because it exposes only rows where the scorable flag is set, consumers are shielded from the administrative and configuration rows that exist for display or maintenance purposes.

Underlying Base Objects

The view is defined by a UNION of two documented base views:

  • AR_CMGT_DATA_POINTS_VL — the internal credit management data points, filtered by scorable_flag = 'Y'. These rows represent Receivables-native attributes used by scoring models.
  • AR_CMGT_DNB_ELEMENTS_VL — the DNB data elements, likewise filtered by scorable_flag = 'Y'. These supply externally sourced credit attributes.

The two branches are aligned so that both return the same column list: identifier, name, category, application, return data type, and return date format. The internal branch additionally provides data_point_code and function_name; for DNB rows these two columns are returned as NULL, and data_point_category is hard-coded to the literal value 'DNB' to distinguish the external elements from internal categories. The UNION (rather than UNION ALL) also implies de-duplication across the combined result set.

Key Columns

  • DATA_POINT_ID — unique identifier for the data point or DNB element; sourced from data_point_id (internal) or data_element_id (DNB).
  • DATA_POINT_NAME — the displayed name of the data point or element.
  • DATA_POINT_CATEGORY — classification of the data point; carries the literal 'DNB' for external elements.
  • APPLICATION_ID — the application that owns the data point, supporting multi-application integration.
  • RETURN_DATA_TYPE — the data type of the value returned when the data point is evaluated (numeric, character, date, and so on).
  • RETURN_DATE_FORMAT — the date format applied when the return type is a date.
  • DATA_POINT_CODE — the internal code identifying the data point; NULL for DNB elements. This is the column most often referenced when searching for a specific scoring attribute.
  • FUNCTION_NAME — the PL/SQL function invoked to compute or retrieve the data point value; NULL for DNB elements.

Common Use Cases and Queries

This view is typically queried when building or troubleshooting credit scoring models, when mapping scoring inputs to application columns, or when reconciling which attributes are eligible for scoring. A common requirement is to locate a data point by its code:

SELECT data_point_id, data_point_name, data_point_category,
       application_id, data_point_code, function_name
FROM   apps.ar_cmgt_scorable_data_points_v
WHERE  data_point_code = :data_point_code;

To inventory all scorable points grouped by category:

SELECT data_point_category, COUNT(*) scorable_points
FROM   apps.ar_cmgt_scorable_data_points_v
GROUP  BY data_point_category
ORDER  BY data_point_category;

To isolate the internal versus DNB elements, filter on the presence of a data point code:

SELECT data_point_id, data_point_name, return_data_type
FROM   apps.ar_cmgt_scorable_data_points_v
WHERE  data_point_code IS NOT NULL;

Because the view is a read-only selection over configuration views, it is appropriate for reporting, scoring engine introspection, and integration extracts, but it is not intended for direct DML.