Results for “ar_receipt_trx_type_view”

18 results




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

Overview

The AR_RECEIPT_TRX_TYPE_VIEW is a documented Oracle E-Business Suite Receivables (AR) database view owned by the APPS schema. Its formal description in the ETRM metadata states that it is "a union of AR_RECEIPT_METHODS and RA_CUST_TRX_TYPES." As the definition implies, the view consolidates two otherwise unrelated Receivables reference entities—receipt methods and customer transaction types—into a single, uniformly shaped result set that exposes a common set of five columns: NAME, DESCRIPTION, TYPE, CUST_TRX_TYPE_ID, and RECEIPT_METHOD_ID. Its role is therefore not to model a business relationship per se, but to provide a generic lookup surface over two Receivables configuration lists, allowing reports and integrations that need a combined name-list to resolve both entity categories through one object. The view is designated VALID in the ETRM documentation and is present in both Oracle EBS 12.1.1 and 12.2.2 releases, where it resides in the APPS schema rather than any product-specific schema. Because it draws on two of the most frequently referenced Receivables setup tables—the very objects that users commonly search for under the term "ra_cust_trx_types"—it also serves as a convenient bridging point for developers who query Receivables transaction type metadata alongside receipt method metadata.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through public synonyms in the APPS schema:

  • AR_RECEIPT_METHODS (SYNONYM) — supplies the NAME and RECEIPT_METHOD_ID values contributed by the first branch of the UNION.
  • RA_CUST_TRX_TYPES (SYNONYM) — supplies the NAME, DESCRIPTION, TYPE, and CUST_TRX_TYPE_ID values contributed by the second branch of the UNION.

The documented view text confirms the structure: the first SELECT projects NAME, NAME, NULL, TO_NUMBER(NULL), and RECEIPT_METHOD_ID from AR_RECEIPT_METHODS; the second projects NAME, DESCRIPTION, TYPE, CUST_TRX_TYPE_ID, and TO_NUMBER(NULL) from RA_CUST_TRX_TYPES. The NULL and TO_NUMBER(NULL) placeholders preserve column-count and datatype alignment across the UNION. Consequently, rows originating from receipt methods carry a populated RECEIPT_METHOD_ID and nulls in the transaction-type columns, whereas rows originating from RA_CUST_TRX_TYPES carry populated transaction-type attributes and a null RECEIPT_METHOD_ID. There is no join condition between the two tables; the view is a pure set union.

Key Columns

  • NAME — the receipt method name when sourced from AR_RECEIPT_METHODS, or the customer transaction type name when sourced from RA_CUST_TRX_TYPES. This is the common display attribute across both branches.
  • DESCRIPTION — populated only for rows sourced from RA_CUST_TRX_TYPES, where it carries the transaction type description. It is NULL for receipt method rows, whose first branch projects NAME twice rather than a description.
  • TYPE — populated only for RA_CUST_TRX_TYPES rows; corresponds to the transaction type classification, such as invoice, credit memo, debit memo, chargeback, or deposit.
  • CUST_TRX_TYPE_ID — the primary key of the source row in RA_CUST_TRX_TYPES; NULL for receipt method rows.
  • RECEIPT_METHOD_ID — the primary key of the source row in AR_RECEIPT_METHODS; NULL for transaction type rows.

The mutual exclusivity of CUST_TRX_TYPE_ID and RECEIPT_METHOD_ID is the practical discriminator: a non-null CUST_TRX_TYPE_ID identifies a transaction type row, while a non-null RECEIPT_METHOD_ID identifies a receipt method row. Because NAME is non-null in both branches, it is the natural label column for combined lists.

Common Use Cases and Queries

Typical usage centers on populating combined selection lists, validating setup values in concurrent programs or forms, and driving integration extracts that must enumerate both receipt methods and transaction types in a single pass. A query to list all transaction type rows is:

  • SELECT name, description, type, cust_trx_type_id FROM apps.ar_receipt_trx_type_view WHERE cust_trx_type_id IS NOT NULL; — retrieves only RA_CUST_TRX_TYPES-sourced rows.
  • SELECT name, receipt_method_id FROM apps.ar_receipt_trx_type_view WHERE receipt_method_id IS NOT NULL; — retrieves only AR_RECEIPT_METHODS-sourced rows.
  • SELECT name, cust_trx_type_id, receipt_method_id FROM apps.ar_receipt_trx_type_view ORDER BY name; — produces the full combined name list across both entities.

Because the view performs a UNION with no filtering and no join, it should be treated strictly as a reference/lookup utility. For transactional reporting that requires actual relationships, such as linking a receipt to its transaction type, developers should query the base tables directly rather than relying on this view, which intentionally does not correlate the two sources. Users searching for "ra_cust_trx_types" will find that this view exposes that table's key attributes—NAME, DESCRIPTION, TYPE, and CUST_TRX_TYPE_ID—while additionally surfacing receipt method identifiers from AR_RECEIPT_METHODS.