Results for “ar_idep_commitment_usage”

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

Overview

The AR_IDEP_COMMITMENT_USAGE view is a reporting object owned by the APPS schema in Oracle E-Business Suite, belonging to the Receivables (AR) product family. It presents the association between parties (customers and related contacts) and customer transactions that function as commitments or deposits. Specifically, the view exposes the relationship records linking an HZ_PARTIES record to a RA_CUSTOMER_TRX_ALL transaction where the relationship object type is 'DEPOSIT'. This design supports the identification of parties who own or use a deposit-type commitment, making the view relevant for deposit tracking, commitment usage analysis, and customer relationship reporting.

The view returns relationship-level detail alongside core party attributes such as party name and email address, enabling downstream reporting and integration consumers to resolve the parties connected to a given transaction without directly navigating the underlying relationship model.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, AR_IDEP_COMMITMENT_USAGE is defined over the following referenced base objects, all resolved through APPS-owned synonyms:

• HZ_PARTIES — the trading community party master, aliased as PARTY.
• RA_CUSTOMER_TRX_ALL — the Receivables transaction table, aliased as TRX, supplying CUSTOMER_TRX_ID.
• HZ_RELATIONSHIPS — the relationship model that binds a subject party to an object (here, the deposit transaction), aliased as REL.
• ARPT_SQL_FUNC_UTIL — a package supplying the function GET_LOOKUP_MEANING, invoked to translate the relationship type code into a user-facing meaning.

The view joins these objects with filters constraining the relationship to SUBJECT_TYPE IN ('PERSON','ORGANIZATION') and SUBJECT_TABLE_NAME = 'HZ_PARTIES', and to OBJECT_TYPE = 'DEPOSIT' with OBJECT_TABLE_NAME = 'RA_CUSTOMER_TRX_ALL'. Only relationships typed as DOCUMENT_OWNER or DOCUMENT_USER are included, restricting output to parties holding an ownership or usage interest in the deposit transaction.

Key Columns

• ROW_ID — the row identifier carried from the HZ_PARTIES row referenced by the relationship subject.
• CUSTOMER_TRX_ID — the Receivables transaction identifier representing the deposit commitment.
• PARTY_ID — the unique identifier of the related party.
• EMAIL_ADDRESS — the party's electronic mail address.
• PARTY_NAME — the display name of the party.
• RELATIONSHIP_TYPE — the raw relationship classification code, either DOCUMENT_OWNER or DOCUMENT_USER.
• RELATIONSHIP_MEANING — the decoded meaning of RELATIONSHIP_TYPE, obtained via ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING using the lookup type 'PARTY_RELATIONS_TYPE'. This is the column referenced by users searching for "relationship_meaning".
• START_DATE / END_DATE — the effective dating of the relationship record.

Common Use Cases and Queries

Typical applications include identifying all parties attached to a deposit transaction, reporting ownership versus usage of deposit commitments, and resolving party contact details for notification or reconciliation processes. Effective dating via START_DATE and END_DATE supports point-in-time analysis of who held an interest in a commitment.

A representative query filtering by transaction and describing the relationship meaning:

• SELECT customer_trx_id, party_id, party_name, email_address, relationship_type, relationship_meaning FROM apps.ar_idep_commitment_usage WHERE customer_trx_id = :p_trx_id;

To isolate owners of deposit commitments:

• SELECT customer_trx_id, party_name, relationship_meaning FROM apps.ar_idep_commitment_usage WHERE relationship_type = 'DOCUMENT_OWNER';

Because RELATIONSHIP_MEANING is derived at query time from the lookup, reports should reference that column rather than hard-coding descriptions, ensuring alignment with configured lookup values.