Results for “trx_reason_code”

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

Overview

AR_TRANSACTIONS_S_V is a shared extraction view owned by the APPS schema in Oracle E-Business Suite Receivables. Its documented description is "transaction shared extract," indicating that it is not a user-facing inquiry object but a staging and integration surface used to feed downstream processes — most notably Subledger Accounting (SLA/XLA) extract routines and external reporting engines. The view presents a flattened, denormalized projection of Accounts Receivable transaction headers combined with accounting extract attributes, allowing consumers to retrieve transaction context and accounting-relevant descriptors from a single object rather than joining across RA_CUSTOMER_TRX_ALL and AR_XLA_LINES_EXTRACT directly.

The presence of a hard-coded INDEX hint on AR_XLA_LINES_EXTRACT_N1 in the view text confirms that the view is designed primarily for high-volume extract operations driven by the XLA extract line index. This is characteristic of the Create Accounting and Subledger Accounting transfer processes in EBS 12.1.1 and 12.2.2, where transaction data is materialized into extraction tables prior to journal entry creation. The view remains VALID in the ETRM 12.2.2 metadata, indicating no structural break between the two releases.

Underlying Base Objects

The documented base objects underlying the view are:

• RA_CUSTOMER_TRX_ALL — the primary Receivables transaction header table, supplying transaction identity, global attributes, and descriptive flexfield context.
• AR_XLA_LINES_EXTRACT — the Subledger Accounting extract table holding accounting attributes associated with transaction lines; the view's INDEX hint targets this object's N1 index.
• RA_CUST_TRX_TYPES_ALL — transaction type definitions, referenced to resolve the document sequence category shown as TRX_DOC_SEQUENCE_CATEGORY.
• AR_RECEIPT_METHODS — receipt method definitions used for installment and rules-based credit method derivation.
• RA_RULES — revenue recognition and invoicing rules referenced by transaction records.
• RA_TERRITORIES — territory definitions associated with the transaction context.

All referenced objects are listed as synonyms in the APPS schema, meaning the view resolves through the standard APPS public synonyms rather than fully qualified table names. This is consistent with EBS coding standards and supports multi-org and patching flexibility.

Key Columns

The column list follows a consistent naming convention in which source columns are aliased with a TRX_ prefix to distinguish extracted transaction attributes from other view consumers.

• TRX_CUSTOMER_TRX_ID — the primary transaction identifier, joining back to RA_CUSTOMER_TRX_ALL.
• TRX_DOC_SEQUENCE_ID, TRX_DOC_SEQUENCE_VALUE, TRX_DOC_SEQUENCE_CATEGORY — document sequence information; the category is conditionally derived and returns NULL when no sequence value exists.
• TRX_ATTR_CAT and TRX_ATTR1–TRX_ATTR15 — the source descriptive flexfield context and segment values.
• TRX_GLOBAL_ATTR_CAT and TRX_GLOBAL_ATTR1–TRX_GLOBAL_ATTR20 — the global descriptive flexfield context and its twenty segments.
• TRX_CREDIT_METHOD_FOR_RULES and TRX_CREDIT_METHOD_FOR_INSTALLMENTS — credit method codes applicable to rule-based and installment transactions, resolved against AR_RECEIPT_METHODS.
• TRX_FOB_POINT — free-on-board terms carried from the transaction header.

Notably, the view does not appear to expose a column explicitly labeled TRX_TYPE_CLASS. Transaction type classification is instead obtained by joining to RA_CUST_TRX_TYPES_ALL on the transaction type identifier, where the TYPE_CLASS column distinguishes invoice, credit memo, debit memo, chargeback, deposit, and guarantee transaction classes.

Common Use Cases and Queries

The view is principally queried during SLA diagnostics, interface troubleshooting, and custom extract development. Because it exposes flexfield and global attribute data alongside transaction identifiers, it is commonly used to verify that extract attributes are populated correctly before accounting is generated.

A typical query retrieves transaction context for a given transaction and classifies it using the transaction type table:

• SELECT v.trx_customer_trx_id, t.name, t.type_class, v.trx_doc_sequence_value FROM ar_transactions_s_v v, ra_cust_trx_types_all t WHERE v.trx_customer_trx_id = :trx_id AND t.cust_trx_type_id = v.trx_cust_trx_type_id;
• SELECT trx_customer_trx_id, trx_attr_cat, trx_attr1, trx_global_attr_cat, trx_global_attr1 FROM ar_transactions_s_v WHERE trx_doc_sequence_value IS NOT NULL;
• SELECT COUNT(*), trx_credit_method_for_rules FROM ar_transactions_s_v GROUP BY trx_credit_method_for_rules;

Given the documented index hint, queries that constrain on extract line attributes or transaction identifiers will benefit from the underlying AR_XLA_LINES_EXTRACT_N1 index and should avoid leading wildcard predicates that would negate it.