Results for “ctt_class”

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

Overview

The RA_CUSTOMER_TRX_V view in the APPS schema is a denormalized, reporting-oriented projection of Oracle Receivables transaction header data. It belongs to the AR (Receivables) product family and is documented as valid from Release 115 onward, remaining present in Oracle E-Business Suite 12.1.1 and 12.2.2. The view consolidates the transactional header record held in RA_CUSTOMER_TRX with human-readable descriptive attributes drawn from the Trading Community Architecture (TCA) model—customer names, account numbers, and formatted addresses—as well as derived values such as the first real due date. Because it presents a single flat row per transaction with bill-to and ship-to context already resolved, it is widely used as a reporting and integration surface where the raw normalized joins would otherwise be repetitive and expensive to reproduce. Rather than re-implementing address formatting and party resolution logic in every report, developers and integration teams query this view to obtain consistent, pre-joined results.

Underlying Base Objects

The view text is anchored on RA_CUSTOMER_TRX (aliased CT), which supplies the transaction identifier, transaction number, transaction date, term, completion and status flags, bill-to and ship-to identifiers, currency, purchase order, and the full ATTRIBUTE1 through ATTRIBUTE15 and INTERFACE_HEADER_ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns. List of Values behavior is supported by RA_CUST_TRX_TYPES and RA_BATCH_SOURCES. Party and site context is resolved through the TCA objects HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_ROLES, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_RELATIONSHIPS, with territory short names taken from FND_TERRITORIES_VL. Distribution data is joined from RA_CUST_TRX_LINE_GL_DIST, and freight context from ORG_FREIGHT. Two packages are essential to the view's behavior: ARPT_SQL_FUNC_UTIL.GET_FIRST_REAL_DUE_DATE, which derives the earliest genuine due date from the transaction, term, and date, and ARH_ADDR_PKG.FORMAT_LAST_ADDRESS_LINE, which assembles a localized last address line using the location's address style.

Key Columns

• CUSTOMER_TRX_ID / TRX_NUMBER / TRX_DATE — primary transaction identifier, user-facing number, and transaction date.
• GET_FIRST_REAL_DUE_DATE(...) — derived due date computed from the transaction's terms rather than a stored column.
• COMPLETE_FLAG / STATUS_TRX — completion and status indicators used to filter posted versus incomplete transactions.
• BILL_TO_CUSTOMER_ID / BILL_TO_SITE_USE_ID / SHIP_TO_CUSTOMER_ID / SHIP_TO_SITE_USE_ID — party and site-use references driving the address resolution.
• INVOICE_CURRENCY_CODE / PURCHASE_ORDER / SHIP_DATE_ACTUAL / WAYBILL_NUMBER / DOC_SEQUENCE_VALUE — commercial and shipping attributes.
• PARTY_NAME / ACCOUNT_NUMBER / LOCATION / ADDRESS1 / ADDRESS2 and the formatted last address line — resolved bill-to and ship-to party, account, and address text.
• Sequence number columns — CT_COMMIT.TRX_NUMBER, CT_PREV.TRX_NUMBER, BS_PREV.NAME, and CT_REL.TRX_NUMBER expose commitment, prior, and related transaction references.
• ATTRIBUTE1–15 / INTERFACE_HEADER_ATTRIBUTE1–15 — descriptive flexfield and interface context columns carried through unchanged.

Common Use Cases and Queries

The view supports receivables aging, customer statement, and integration extracts. A typical reporting query filters by transaction date and status to list open invoices with resolved bill-to detail:

• SELECT TRX_NUMBER, TRX_DATE, PARTY_NAME, ACCOUNT_NUMBER, BILL_TO_ADDRESS1, GET_FIRST_REAL_DUE_DATE FROM ... WHERE STATUS_TRX='OP'
• Ad hoc queries joining flexfield attributes (ATTRIBUTE1–15) to report on custom transaction classifications.
• Extracts that consume resolved party/site names for downstream systems without replicating TCA joins.
• Reconciliation of DOC_SEQUENCE_VALUE against document sequencing requirements.

Because it performs extensive function calls and joins, performance is best served by filtering on indexed header columns such as TRX_DATE and CUSTOMER_TRX_ID.