Search Results ar_cmgt_bank_ref_data




Overview
Explore in AI Chat

Overview

The AR_CMGT_BANK_REF_DATA table is a Receivables module object within the Oracle E-Business Suite 12.1.1 / 12.2.2 database schema owned by AR. It stores reference information about the banks at which a company under credit review maintains active accounts. This object supports the Credit Management functionality in Oracle Receivables, where credit analysts gather financial and banking intelligence on customers before approving or adjusting credit terms and limits. Each row represents a single bank reference associated with a specific credit request and case folder, capturing both institutional and point-of-contact details.

The metadata assigns a heuristic Data Vault classification of standalone, meaning the table is not modeled as a classic hub, link, or satellite. Rather, it functions as a descriptive adjunct to the parent credit request record. In practice, this suggests treating it as a supporting table whose lifecycle is governed by its parent credit request rather than as an independent business entity.

Key Information Stored

The table contains 22 documented columns. Its surrogate primary key is defined by the AR_CMGT_BANK_REF_DATA_PK constraint on DATAPOINT_ID, and a unique index, AR_CMGT_BANK_REF_DATA_U1, also covers DATAPOINT_ID, confirming it as the sole documented business-key candidate. Foreign key relationships tie CREDIT_REQUEST_ID to AR_CMGT_CREDIT_REQUESTS and CASE_FOLDER_ID to AR_CMGT_CASE_FOLDERS, anchoring each bank record to its credit workflow context.

  • DATAPOINT_ID — surrogate primary key uniquely identifying each bank reference record.
  • CREDIT_REQUEST_ID — foreign key linking the bank reference to a specific credit request.
  • CASE_FOLDER_ID — foreign key linking the record to the credit case folder.
  • BANK_NAME — the name of the financial institution.
  • ADDRESS, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTRY — geographic details of the bank branch or headquarters.
  • CONTACT_NAME, PHONE, FAX, EMAIL — the bank officer or representative and their contact channels.
  • URL — the bank's website address.
  • BANK_ROUTING_NUMBER — the routing or transit identifier for the account.
  • NOTES — free-form analyst commentary on the banking relationship.

Standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) provide WHO-column traceability consistent with other EBS transactional tables.

Common Use Cases and Queries

Credit analysts and receivables reporting teams use this table to review the banking profile of customers under credit evaluation. A typical query joins bank references to their parent credit request to present a consolidated view:

  • Retrieving all banks for a given credit request: SELECT b.* FROM ar_cmgt_bank_ref_data b WHERE b.credit_request_id = :request_id;
  • Listing bank contacts for a specific case folder: SELECT bank_name, contact_name, phone FROM ar_cmgt_bank_ref_data WHERE case_folder_id = :folder_id;
  • Joining to the credit request header to combine bank details with customer credit terms for a credit review report.
  • Auditing recently modified bank records using LAST_UPDATE_DATE for data quality monitoring.

Because the table often holds only a few rows per credit request, it is well suited to inline reporting and descriptive dashboard panels within Credit Management.

Related Objects

The most significant related objects are those directly referenced by the documented foreign keys, plus the primary-key parent context:

  • AR_CMGT_CREDIT_REQUESTS — parent of CREDIT_REQUEST_ID; each bank reference belongs to one credit request.
  • AR_CMGT_CASE_FOLDERS — parent of CASE_FOLDER_ID; groups bank references within the credit case workflow.
  • AR_CMGT_BANK_REF_DATA_PK — primary key constraint on DATAPOINT_ID.
  • AR_CMGT_BANK_REF_DATA_U1 — unique index supporting the DATAPOINT_ID key.

These relationships confirm that AR_CMGT_BANK_REF_DATA operates strictly as a dependent reference table within the Receivables Credit Management sub-model rather than as a shared enterprise entity.