Search Results ozf_x_get_trx_types

Overview

The APPS.OZF_X_GET_TRX_TYPES view is a Trade Management (OZF) reporting and integration construct that exposes customer transaction type definitions to Oracle E-Business Suite modules and custom extensions. It is a valid database object owned by the APPS schema and is delivered as part of the OZF – Trade Management product family in Oracle EBS 12.1.1 and 12.2.2. Functionally, the view provides a filtered, operationally scoped projection of the Receivables transaction type repository, presenting the attributes that Trade Management and downstream consumers require when resolving how customer transactions—such as invoices, credit memos, and debit memos—are classified and posted to the General Ledger.

The view is particularly relevant to implementers and developers who reference the GL_ID_TAX column and related accounting identifiers, since it exposes the full set of GL account reference columns used by Receivables posting logic. Because it is layered over an AR synonym rather than a bespoke OZF table, it delivers Receivables master data through a Trade Management access point, enabling consistent lookups across modules without duplicating transaction type definitions.

Underlying Base Objects

Per the documented metadata, OZF_X_GET_TRX_TYPES is defined solely over the base object RA_CUST_TRX_TYPES_ALL, referenced through a SYNONYM. The view definition selects the complete set of transaction type columns from AR.RA_CUST_TRX_TYPES_ALL and applies an organizational security filter based on the session's USERENV('CLIENT_INFO') value. Specifically, the WHERE clause compares the record's ORG_ID against the organization identifier parsed from CLIENT_INFO, normalizing both sides and defaulting to -99 when no value is available. This construct effectively enforces multi-org (Operating Unit) access rules at the view level, returning only the transaction types that belong to the current organization context.

Because RA_CUST_TRX_TYPES_ALL is the single source of truth for Receivables transaction types, the view inherits all its referential relationships—including the GL account references used during posting—while adding the OZF-facing presentation layer.

Key Columns

• CUST_TRX_TYPE_ID — Primary key identifying the customer transaction type; the join key used by invoices, credit memos, and Trade Management accruals.
• NAME — User-defined transaction type name presented in lookups and LOVs.
• TYPE — Classifies the transaction type (for example, invoice, credit memo, debit memo, chargeback, or deposit).
• POST_TO_GL — Indicates whether transactions of this type post to the General Ledger.
• ACCOUNTING_AFFECT_FLAG — Determines whether the transaction type affects accounting balances.
• GL_ID_REV, GL_ID_FREIGHT, GL_ID_CLEARING, GL_ID_TAX, GL_ID_UNBILLED, GL_ID_UNEARNED — The General Ledger account identifiers applied to revenue, freight, clearing, tax, unbilled, and unearned amounts respectively. GL_ID_TAX is the account reference relevant to tax posting and is a frequent target of troubleshooting and reporting queries.
• TAX_CALCULATION_FLAG — Controls whether tax is calculated for transactions of this type.
• SET_OF_BOOKS_ID — The ledger or set of books to which the transaction type is associated.
• NATURAL_APPLICATION_ONLY_FLAG and the ATTRIBUTE1–ATTRIBUTE15 descriptive flexfield columns — Support application-specific restrictions and extensible attribute reporting.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY) — Provide auditability.

Common Use Cases and Queries

Typical scenarios include resolving the tax, revenue, and clearing accounts assigned to a transaction type, validating posting configuration before period close, and populating custom reports or interfaces in Trade Management. A representative query retrieving transaction types with their tax and revenue accounts is shown below.

• Account resolution: SELECT cust_trx_type_id, name, gl_id_tax, gl_id_rev, gl_id_clearing FROM ozf_x_get_trx_types WHERE post_to_gl = 'Y';
• Tax configuration audit: SELECT name, type, gl_id_tax, tax_calculation_flag FROM ozf_x_get_trx_types WHERE gl_id_tax IS NULL AND tax_calculation_flag = 'Y';
• Type lookup by class: SELECT cust_trx_type_id, name FROM ozf_x_get_trx_types WHERE type = 'INV' ORDER BY name;
• Organization-scoped listing, relying on the view's built-in ORG_ID filter: SELECT cust_trx_type_id, name, set_of_books_id, gl_id_tax FROM ozf_x_get_trx_types;

Because OZF_X_GET_TRX_TYPES enforces Operating Unit security through USERENV('CLIENT_INFO'), callers should ensure the correct organization context is initialized before querying; otherwise the filter may resolve to the -99 default and return no rows. Reporting logic that requires cross-organization visibility must reference RA_CUST_TRX_TYPES_ALL directly rather than the view. In all cases, GL_ID_TAX and its sibling GL account columns should be joined to GL_CODE_COMBINATIONS to translate raw identifiers into concatenated account strings for presentation.