Results for “acquisition_date”

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

Overview

The AR_CMGT_GUARANTOR_DATA table is a Receivables (AR) module object that stores information about an entity legally responsible for fulfilling a credit obligation if the primary party — the company under credit review — fails to pay its debt. It is part of the Oracle Credit Management (AR_CMGT) schema component within Oracle E-Business Suite 12.1.1 and 12.2.2. The object resides in the AR schema, carries VALID status, and exposes 44 documented columns in the 12.2.2 physical schema.

The table functions as a guarantor registration and credit-assessment ledger. Each row links a credit request to an external party (the guarantor), captures the guaranteed amount and funding availability window, and optionally holds collateral-style valuation details such as asset class, appraised value, and valuation method. This dual purpose — guarantor tracking plus collateral valuation — supports both the credit review workflow and the risk assessment that underlies credit limit decisions.

From a modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is link. This suggests the table acts primarily as a relationship record connecting a credit request, a guarantor party, and a contact party. Analysts designing a Data Vault or dimensional model may therefore treat it as a link table with descriptive satellite content attached to the same physical object.

Key Information Stored

The surrogate primary key is DATAPOINT_ID, enforced by the AR_CMGT_GUARANTOR_DATA_PK constraint. A unique index, AR_CMGT_GUARANTOR_DATA_U1, is defined on DATAPOINT_ID as well, making it a business-key candidate. The most significant columns include:

• CREDIT_REQUEST_ID and GUARANTOR_CREDIT_REQUEST_ID — foreign keys to AR_CMGT_CREDIT_REQUESTS, tying the guarantor record to the credit review in progress.
• PARTY_ID and CONTACT_PARTY_ID — foreign keys to HZ_PARTIES, identifying the guarantor entity and the contact person at that entity.
• CASE_FOLDER_ID — foreign key to AR_CMGT_CASE_FOLDERS, linking the record to the credit case file.
• GUARANTEED_AMOUNT and CURRENCY — the monetary value and denomination of the guarantee.
• FUNDING_AVAILABLE_FROM and FUNDING_AVAILABLE_TO — the effective window during which funds are available.
• TAX_NUMBER, REFERENCE_NAME, CONTACT_NAME, ADDRESS, CITY, STATE, POSTAL_CODE, PHONE_NUMBER, EMAIL — guarantor identification and contact detail.
• ASSET_CLASS_CODE, ASSET_TYPE_CODE, ASSET_IDENTIFIER, VALUATION, VALUATION_METHOD_CODE, VALUATION_DATE, APPRAISER — collateral attributes used when the guarantee is secured against an asset.
• CREDIT_CLASSIFICATION and REVIEW_TYPE — categorization flags for credit assessment reporting.
• NOTES and DESCRIPTION — free-form supporting commentary.

Common Use Cases and Queries

Credit analysts and AR reporting teams query this table to review guarantor coverage for companies under credit review, to validate concentration of guarantees by assigned amount, and to reconcile collateral valuations against approved credit limits. A typical join retrieves the credit request, guarantor party, and guarantee amount:

SELECT g.DATAPOINT_ID, g.CREDIT_REQUEST_ID, g.PARTY_ID, hp.PARTY_NAME, g.GUARANTEED_AMOUNT, g.CURRENCY, g.FUNDING_AVAILABLE_FROM, g.FUNDING_AVAILABLE_TO, g.CREDIT_CLASSIFICATION FROM AR.AR_CMGT_GUARANTOR_DATA g, HZ_PARTIES hp WHERE g.PARTY_ID = hp.PARTY_ID AND g.CREDIT_REQUEST_ID = :request_id;

Collateral reporting follows a similar pattern, filtering on VALUATION_DATE or ASSET_CLASS_CODE. Case-folder-driven reports join to AR_CMGT_CASE_FOLDERS on CASE_FOLDER_ID to align guarantee data with the overall credit case. Audit-style queries frequently filter on LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY to track data provenance.

Related Objects

The most significant related objects, based on the documented foreign-key relationships, are:

• AR_CMGT_CREDIT_REQUESTS — referenced via GUARANTOR_CREDIT_REQUEST_ID and CREDIT_REQUEST_ID; the parent credit review record.
• HZ_PARTIES — referenced via PARTY_ID (guarantor entity) and CONTACT_PARTY_ID (guarantor contact).
• AR_CMGT_CASE_FOLDERS — referenced via CASE_FOLDER_ID; the credit case container.
• AR_CMGT_GUARANTOR_DATA_PK / AR_CMGT_GUARANTOR_DATA_U1 — the primary-key constraint and unique index on DATAPOINT_ID.
• AR Credit Management concurrent programs and the Credit Management HTML pages, which read and write rows through the AR_CMGT APIs.
• AR reporting views and OBIEE/EBS repository extracts that surface guarantor and collateral data for credit-limit decisioning.

The table’s central role in the AR_CMGT link structure means any change to AR_CMGT_CREDIT_REQUESTS, HZ_PARTIES, or AR_CMGT_CASE_FOLDERS can affect guarantor records, so referential integrity must be considered in all integration and purge activities.