Search Results fv_operating_units_all

Overview

RA_CUST_TRX_TYPES_ALL is the Receivables (AR) transaction type definition table in Oracle E-Business Suite, owned by the AR schema. It stores the setup records that classify and control every customer transaction an organization creates in Receivables, including invoices, credit memos, debit memos, commitments, chargebacks, and deposit transactions. Because each transaction must reference a transaction type, this table functions as a foundational reference object for the entire AR subledger rather than a transactional or high-volume table.

The table is multi-organization enabled; the ORG_ID column and the unique index RA_CUST_TRX_TYPES_U1 (CUST_TRX_TYPE_ID, ORG_ID, ZD_EDITION_NAME) reflect the partitioning of transaction type definitions by operating unit and, where applicable, by edition. The primary key constraint RA_CUST_TRX_TYPES_PK is defined on CUST_TRX_TYPE_ID.

From a dimensional modeling perspective, the mined relationship structure classifies this object heuristically as a hub: it carries a single surrogate business key (CUST_TRX_TYPE_ID), is referenced by a large number of dependent tables, and holds descriptive attributes that would conventionally be separated into satellites. This classification is a modeling suggestion only, derived from the foreign key topology, and does not imply an enforced Data Vault design in the delivered application.

Key Information Stored

The table contains 83 documented columns. The most significant are summarized below.

• CUST_TRX_TYPE_ID — surrogate primary key (RA_CUST_TRX_TYPES_PK); the value carried by every referencing transaction, payment schedule, and interface record.
• NAME and DESCRIPTION — the user-facing transaction type name and its explanation; NAME is the value most commonly displayed in forms, LOVs, and reports.
• TYPE — the functional classification that determines the accounting and processing behavior of the transaction (invoice, credit memo, debit memo, chargeback, deposit, and related categories).
• STATUS, START_DATE, and END_DATE — activation and effective-dating controls that govern whether the type is available for new transactions.
• POST_TO_GL and ACCOUNTING_AFFECT_FLAG — determine whether transactions of this type are transferred to the General Ledger and whether they create accounting entries.
• CREDIT_MEMO_TYPE_ID and SUBSEQUENT_TRX_TYPE_ID — self-referencing keys that link a type to its associated credit memo type and to the type used by subsequent transactions.
• DEFAULT_TERM — the default payment term, referencing RA_TERMS_B, applied when a transaction of this type is entered without an explicit term.
• GL_ID_REV, GL_ID_REC, GL_ID_FREIGHT, GL_ID_TAX, GL_ID_CLEARING, GL_ID_UNBILLED, GL_ID_UNEARNED, GL_ID_UNPAID_REC, GL_ID_REMITTANCE, and GL_ID_FACTOR — account derivation references to GL_CODE_COMBINATIONS for revenue, receivables, freight, tax, clearing, unbilled, unearned, and related accounting.
• SET_OF_BOOKS_ID — references GL_SETS_OF_BOOKS_11I and ties the definition to the ledger under which it operates.
• LEGAL_ENTITY_ID — references FV_LEGAL_ENTITIES, aligning the transaction type with a legal entity in the Subledger Accounting model.
• ALLOW_FREIGHT_FLAG, ALLOW_OVERAPPLICATION_FLAG, TAX_CALCULATION_FLAG, NATURAL_APPLICATION_ONLY_FLAG, EXCLUDE_FROM_LATE_CHARGES, and ADJ_POST_TO_GL — behavioral flags that drive freight handling, overapplication tolerance, tax calculation, application restrictions, and late charge and adjustment accounting.

Common Use Cases and Queries

Typical usage patterns include resolving a transaction type identifier to its descriptive name, identifying transaction types by category or ledger, and validating that a type is active for a given period before loading interface data.

SELECT cust_trx_type_id, name, type, status, post_to_gl
FROM   ra_cust_trx_types_all
WHERE  org_id = :p_org_id
AND    TRUNC(SYSDATE) BETWEEN NVL(start_date, TRUNC(SYSDATE))
                          AND NVL(end_date, TRUNC(SYSDATE))
ORDER BY name;

Joining to the transaction header table is standard when reporting on invoice populations by type:

SELECT ctt.name, ctt.type, COUNT(*) trx_count, SUM(cth.creation_date) dummy
FROM   ra_customer_trx_all   cth,
       ra_cust_trx_types_all ctt
WHERE  cth.cust_trx_type_id = ctt.cust_trx_type_id
AND    cth.org_id           = ctt.org_id
GROUP BY ctt.name, ctt.type;

Other frequent scenarios include confirming the default accounting accounts assigned to a type (joining the GL_ID_* columns to GL_CODE_COMBINATIONS), checking which credit memo type is mapped to a given invoice type via CREDIT_MEMO_TYPE_ID, and reconciling the default inventory transaction type recorded on RA_BATCH_SOURCES_ALL.

Related Objects

The following are the most significant dependents and references within the AR and adjacent modules.

• RA_CUSTOMER_TRX_ALL — joins on CUST_TRX_TYPE_ID; the primary transactional consumer of this reference data.
• RA_PAYMENT_SCHEDULES_ALL — joins on CUST_TRX_TYPE_ID; inherits the type from the originating transaction.
• RA_BATCH_SOURCES_ALL — joins on DEFAULT_INV_TRX_TYPE, defining the transaction type defaulted by a batch source.
• RA_INTERFACE_LINES_ALL — joins on CUST_TRX_TYPE_ID; the AutoInvoice interface requires a valid transaction type for imported lines.
• RA_TERMS_B — referenced through DEFAULT_TERM to supply default payment terms.
• GL_CODE_COMBINATIONS — referenced by the GL_ID_REV, GL_ID_REC, GL_ID_FREIGHT, GL_ID_TAX, and other GL_ID_* columns for account derivation.
• GL_SETS_OF_BOOKS_11I and FV_LEGAL_ENTITIES — referenced by SET_OF_BOOKS_ID and LEGAL_ENTITY_ID respectively.
• AR_SYSTEM_PARAMETERS_ALL — references this table through LATE_CHARGE_INV_TYPE_ID and LATE_CHARGE_DM_TYPE_ID to define default late charge transaction types.
• OE_TRANSACTION_TYPES_ALL and MTL_INTERCOMPANY_PARAMETERS — join on CUST_TRX_TYPE_ID, linking order and intercompany flows to their Receivables transaction types.
• AR_INV_API_HEADERS_GT — the public invoice API staging structure, joining on CUST_TRX_TYPE_ID for programmatic transaction creation.