Search Results ar_cmgt_cf_anl_notes




Overview

The AR_CMGT_CF_ANL_NOTES table is a Receivables (AR) module object within the Oracle E-Business Suite, validated and present in both 12.1.1 and 12.2.2 environments. It stores topical notes authored by a credit analyst and persisted in the case folder during a credit review cycle. The table is part of the Credit Management (CMGT) subcomponent of Receivables, which supports the review, assessment, and documentation of customer creditworthiness. Each row represents a discrete note associated with a specific credit case folder, capturing the analyst's observations, remarks, or findings on a particular subject matter.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is classified as standalone. This classification is a modeling suggestion rather than a definitive architectural directive; it reflects the observation that the table has no child tables referencing it and depends only on a single parent, functioning in practice as a descriptive satellite of the case folder entity. Its structural role is to supply narrative context to the structured credit review data held in the case folder, providing qualifiable human judgment alongside quantified credit metrics.

Key Information Stored

The table comprises twelve documented columns. The surrogate primary key, enforced through AR_CMGT_CF_ANL_NOTES_PK and reinforced by unique index AR_CMGT_CF_ANL_NOTES_U1, is ANALYSIS_NOTES_ID. This column uniquely identifies each note and serves as the single documented business-key candidate, meaning no alternate unique index exists to distinguish rows independently of the surrogate identifier.

The most significant columns include:

  • ANALYSIS_NOTES_ID — Surrogate primary key uniquely identifying each analyst note record.
  • CASE_FOLDER_ID — Foreign key to AR_CMGT_CASE_FOLDERS, tying the note to its parent credit review case folder.
  • TOPIC — Subject heading or category of the note, providing a topical index for retrieval.
  • NOTES — The free-text body containing the analyst's narrative content.
  • IMPORTANCE — Relative significance or priority assigned to the note, useful for ranking and filtering.
  • DISPLAY — Flag governing whether the note is presented in the case folder user interface.
  • DATE_OPENED — Date on which the note was opened or initiated.
  • CREATED_BY, CREATION_DATE — Standard audit columns recording author and creation timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit trail columns capturing the most recent modification.

This audit column set follows the conventional Oracle EBS WHO-column pattern, supporting traceability and change history at the application layer.

Common Use Cases and Queries

The primary reporting scenario is retrieving all notes for a given case folder during credit review, typically filtered by importance or ordered chronologically. A representative query joins the notes to their parent folder:

  • SELECT n.TOPIC, n.NOTES, n.IMPORTANCE, n.DATE_OPENED FROM AR.AR_CMGT_CF_ANL_NOTES n WHERE n.CASE_FOLDER_ID = :folder_id AND n.DISPLAY = 'Y' ORDER BY n.DATE_OPENED DESC;

Analysts may also audit note activity by author for a period, counting contributions per analyst:

  • SELECT CREATED_BY, COUNT(*) FROM AR.AR_CMGT_CF_ANL_NOTES WHERE CREATION_DATE BETWEEN :start AND :end GROUP BY CREATED_BY;

Additional patterns include identifying high-importance notes across open cases, searching note text for keywords, and extracting notes for inclusion in credit review documentation or external correspondence. Because the table is standalone, queries rarely require multi-level joins beyond the case folder parent.

Related Objects

The most significant related object is the parent table referenced by the documented foreign key:

  • AR_CMGT_CASE_FOLDERS — joined via AR_CMGT_CF_ANL_NOTES.CASE_FOLDER_ID = AR_CMGT_CASE_FOLDERS.CASE_FOLDER_ID; the controlling entity for all credit review notes.

Broader dependencies within the Credit Management framework include the case folder's associated credit analysis, customer, and review records, which provide the context in which notes are created. The AJF (Application Object Library) layer also indirectly references this table, as CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN map to FND_USER, enabling user-level reporting. Integration surfaces generally occur through the case folder APIs and Receivables credit management web pages rather than direct DML against this table.