Results for “ar_cmgt_check_list_dtls”

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

Overview

The AR_CMGT_CHECK_LIST_DTLS table is a core detail-level object within Oracle Credit Management, a sub-module of Oracle Receivables (AR). It stores the individual line items that constitute a credit checklist — the analytical steps, data points, and scoring criteria that a credit analyst must evaluate when reviewing a customer's creditworthiness. While the checklist header defines the overall template (for example, a "New Customer Credit Review" or "Annual Credit Re-evaluation"), this table defines each discrete data point that belongs to that checklist and the rules governing how it is used during the scoring process.

The object is owned by the AR schema and resides in the APPS-enabled database tier. It is classified as a VALID table in EBS 12.1.1 and 12.2.2, and the documented physical schema exposes nine columns. From a heuristic data-vault modeling perspective, this object is best characterized as a link table, since its primary key is a composite of two identifiers (CHECK_LIST_ID and DATA_POINT_ID) that together represent a many-to-many association between checklist templates and credit data points. It carries descriptive and control attributes, so it can also be viewed as a link with satellite behavior, but the association semantics dominate.

Key Information Stored

The primary key, AR_CMGT_CHECK_LIST_DTLS_PK, is a composite surrogate key composed of CHECK_LIST_ID and DATA_POINT_ID. The unique index AR_CMGT_CHECK_LIST_DTLS_U1 mirrors this same column pair, confirming that no data point may appear twice on the same checklist. The most consequential columns include:

• CHECK_LIST_ID — Foreign identifier linking each detail row to its parent checklist definition; this is the column most frequently used in user searches.
• DATA_POINT_ID — Identifies the specific credit data point (such as "Payment History Score" or "Credit Bureau Rating") that belongs to the checklist.
• REQUIRED_FLAG — Determines whether the data point is mandatory before a credit review can be submitted for approval.
• NUMBER_OF_REFERENCES — Indicates how many references or occurrences of the data point are expected, useful in weighted scoring logic.

The remaining audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — follow standard Oracle EBS WHO-column conventions and support change tracking and concurrent-program diagnostics.

Common Use Cases and Queries

Credit administrators typically query this table to audit which data points are attached to a checklist, to enforce required-field validations, or to report on checklist composition for compliance reviews. A representative query to list all data points for a given checklist is:

SELECT CHECK_LIST_ID, DATA_POINT_ID, REQUIRED_FLAG, NUMBER_OF_REFERENCES
FROM AR.AR_CMGT_CHECK_LIST_DTLS
WHERE CHECK_LIST_ID = :p_check_list_id
ORDER BY DATA_POINT_ID;

Reporting scenarios include identifying checklists with mandatory data points, measuring checklist complexity by counting detail rows, and joining to the data point definition table to produce analyst-facing worksheets. Because the table is standalone in the FK heuristic, joins to parent or data-point masters are performed on the shared business identifiers rather than enforced foreign keys, so query authors should confirm referential consistency when building custom reports.

Related Objects

The following objects are most significant in relation to AR_CMGT_CHECK_LIST_DTLS:

• AR_CMGT_CHECK_LISTS — The checklist header table, joined on CHECK_LIST_ID.
• AR_CMGT_DATA_POINTS — The master definition of credit data points, joined on DATA_POINT_ID.
• AR_CMGT_CHECK_LIST_VALUES — Stores captured values against checklist data points.
• AR_CMGT_CHECKLIST_V — A reporting view exposing checklist metadata for inquiry.
• AR_CMGT_DATA_POINT_USAGES — Tracks how data points are consumed across checklists and scoring models.
• Credit Management APIs — The public PL/SQL packages used to create and maintain checklist detail rows programmatically.

Together these objects form the structural backbone of the Oracle Credit Management scoring and review framework.