Results for “data_point_sub_category”

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

Overview

The AR_CMGT_DATA_POINTS_B table is a core configuration table within Oracle Credit Management, a sub-module of Oracle Receivables (AR). It stores the definition of each data point used by the Credit Management scoring and checklist framework. A data point represents an individual measurable attribute — for example, a customer's average days beyond terms, credit limit utilization, or a user-defined risk indicator — that the Credit Management engine evaluates when scoring customer accounts or building credit review checklists. Each row in AR_CMGT_DATA_POINTS_B describes how a single data point is identified, categorized, whether it is scorable or displayed on a checklist, and the PL/SQL package and function invoked to return its value at runtime.

Because the table holds descriptive attribute data that is keyed by a surrogate identifier rather than by transactional facts, the mined Data Vault classification is satellite-leaning. This classification is a heuristic modeling suggestion derived from the foreign-key topology: the table carries descriptive columns subordinate to an application reference, with no downstream hub or link relationships of its own. The table is owned by the AR schema and is present as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table contains 21 documented columns in the ETRM 12.2.2 physical schema, with a small number of attributes carrying the substantive business meaning.

• DATA_POINT_ID — the surrogate primary key, defined by AR_CMGT_DATA_POINTS_B_PK. It is also the leading column of the unique index AR_CMGT_DATA_POINTS_B_U1 (DATA_POINT_ID, ZD_EDITION_NAME), which serves as a business-key candidate and supports edition-based redefinition.
• APPLICATION_ID — foreign key to FND_APPLICATION, identifying the Oracle application that owns the data point definition.
• DATA_POINT_CODE and DATA_POINT_CATEGORY / DATA_POINT_SUB_CATEGORY — the business identifier and the categorization used to group and filter data points on scoring models and checklists.
• PACKAGE_NAME and FUNCTION_NAME — the stored program unit invoked to return the data point value.
• FUNCTION_TYPE and RETURN_DATA_TYPE with RETURN_DATE_FORMAT — describe how the function is executed and what data type and date format it returns.
• SCORABLE_FLAG, DISPLAY_ON_CHECKLIST_FLAG, USER_DEFINED_FLAG, and ENABLED_FLAG — control flags governing whether the data point participates in scoring, appears on checklists, was user-created, and is currently active.
• PARENT_DATA_POINT_ID — self-referencing hierarchy column allowing data points to be nested.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting and administration scenarios include listing all enabled, scorable data points for a given scoring model, verifying which data points render on a credit checklist, and auditing the package and function backing each data point.

• Retrieve scorable data points: SELECT DATA_POINT_ID, DATA_POINT_CODE, DATA_POINT_CATEGORY FROM AR_CMGT_DATA_POINTS_B WHERE SCORABLE_FLAG = 'Y' AND ENABLED_FLAG = 'Y';
• List checklist data points with their backing function: SELECT DATA_POINT_CODE, PACKAGE_NAME, FUNCTION_NAME FROM AR_CMGT_DATA_POINTS_B WHERE DISPLAY_ON_CHECKLIST_FLAG = 'Y';
• Find user-defined data points by category: SELECT DATA_POINT_CODE, DATA_POINT_CATEGORY FROM AR_CMGT_DATA_POINTS_B WHERE USER_DEFINED_FLAG = 'Y';

Related Objects

• FND_APPLICATION — referenced via AR_CMGT_DATA_POINTS_B.APPLICATION_ID; the authoritative source of application names and short names.
• OKL_LEASEAPP_DATAPOINTS — references this table through OKL_LEASEAPP_DATAPOINTS.DATA_POINT_ID → AR_CMGT_DATA_POINTS_B, linking leasing application data points to Credit Management definitions.
• AR_CMGT_DATA_POINTS_B_PK — the primary key constraint on DATA_POINT_ID.
• AR_CMGT_DATA_POINTS_B_U1 — the unique index on (DATA_POINT_ID, ZD_EDITION_NAME).
• Credit Management concurrent programs and scoring APIs — the PL/SQL packages named in PACKAGE_NAME and FUNCTION_NAME are executed by the Credit Management engine, making this table a runtime dependency for score and checklist generation.