Results for “ct_commit”

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

Overview

APPS.RA_CUSTOMER_TRX_CR_TRX_V is a receivables reporting view that presents transactional header information from Oracle Receivables (AR) alongside denormalized customer, party, address, and tax registration attributes. Its name reflects its primary design intent: to support reporting and integration scenarios involving customer transactions together with the related "credit transaction" reference (CT_COMMIT.TRX_NUMBER) and the fiscal registration data held at the party level through JGZZ_FISCAL_CODE. The view is particularly significant for users who search on party_ship, because it exposes the ship-to party registration number (PARTY_SHIP.JGZZ_FISCAL_CODE) directly on the transaction row, avoiding the need to join to HZ_PARTIES manually.

In both Oracle EBS 12.1.1 and 12.2.2, the object is owned by the APPS schema and is intended for read-only reporting. It is not an interface table and should not be used for DML. Its role is to flatten the RA_CUSTOMER_TRX header with its party and location context so that reports, extracts, and outbound interfaces can retrieve billing, shipping, and tax registration attributes in a single query.

Underlying Base Objects

The view is defined over the core AR transaction header, RA_CUSTOMER_TRX (with RA_CUSTOMER_TRX_ALL as the documented multi-org base), aliased as CT. Bill-to and ship-to context is resolved through HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_PARTIES. Lookup and reference data is supplied by AR_LOOKUPS, RA_CUST_TRX_TYPES_ALL, RA_TERMS, RA_BATCHES_ALL, RA_BATCH_SOURCES_ALL, RA_SALESREPS (view), RA_CUST_TRX_LINE_GL_DIST_ALL, SO_AGREEMENTS, and GL_DAILY_CONVERSION_TYPES. The view also references the ARPT_SQL_FUNC_UTIL and FND_ATTACHMENT_UTIL_PKG packages, indicating extended attribute and attachment handling logic embedded in its definition.

Key Columns

• CUSTOMER_TRX_ID, TRX_NUMBER, TRX_DATE, TERM_DUE_DATE — core transaction identity and dates.
• SHIP_TO_CUSTOMER_ID, SHIP_TO_SITE_USE_ID, AS_SHIP.CUST_ACCT_SITE_ID — ship-to customer and site use context; the "ship" component to which party_ship references point.
• PARTY_SHIP.JGZZ_FISCAL_CODE — ship-to party fiscal/registration code, the attribute most associated with the party_ship search.
• BILL_TO_CUSTOMER_ID, BILL_TO_SITE_USE_ID, PARTY_BILL.JGZZ_FISCAL_CODE — analogous bill-to attributes.
• Attribute1 through Attribute15 and INTERFACE_HEADER_ATTRIBUTE1 through 15 — descriptive flexfield and interface flexfield columns carried through for reporting.
• DEFAULT_USSGL_TRANSACTION_CODE and DEFAULT_USSGL_TRX_CODE_CONTEXT — transaction code reporting values.
• CUST_BILL.ACCOUNT_NUMBER, SU_BILL.LOCATION, LOC_BILL.ADDRESS1-3 — formatted bill-to address components.

Common Use Cases and Queries

This view is typically used to produce customer transaction extracts that require party fiscal identifiers for both ship-to and bill-to roles, and to reconcile transaction headers against their credit/reference transactions. A representative query filtering on the party_ship fiscal code is shown below.

SELECT trx_number,
       trx_date,
       ship_to_customer_id,
       jgzz_fiscal_code
FROM   apps.ra_customer_trx_cr_trx_v
WHERE  jgzz_fiscal_code IS NOT NULL;

Because the view already joins the HZ party hierarchy, it eliminates the need for manual joins to HZ_PARTIES and HZ_PARTY_SITES when reporting registration codes. For performance, queries should be restricted by TRX_DATE or SET_OF_BOOKS_ID where possible, and the ORG_ID context should be set correctly in multi-org environments. The view is read-only and must not be used for inserts or updates.