Results for “type_class”

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

Overview

The CST_XLA_INV_TXN_TYPES_REF_V view is an APPS-owned database view that resides in the Oracle E-Business Suite (EBS) environment, documented across releases 12.1.1 and 12.2.2. It is catalogued under the BOM (Bills of Material) product family but serves a cross-functional role at the intersection of Inventory and Subledger Accounting (XLA). The view exposes inventory transaction type reference data in a form suitable for consumption by the XLA and Costing engines, which must map physical inventory movements to their corresponding accounting event types. In practice, this view acts as a thin, purpose-built projection over the inventory transaction type master, presenting a curated set of columns needed for subledger accounting lookups, reporting, and integration. Because it is a view rather than a table, it introduces no additional storage and simply re-presents base data with column aliases and a light transformation applied to one attribute. Users querying on the search term transaction_type_name will find that the view surfaces this attribute directly, allowing them to join transaction type names to accounting events, cost records, or reporting queries without referencing the base table implicitly.

Underlying Base Objects

The view is defined over a single documented base object: the synonym MTL_TRANSACTION_TYPES, which in the APPS schema resolves to the Inventory transaction types table. The relationship is one-to-one; the view performs no joins and no aggregation, so every row in the view corresponds to exactly one row in the underlying transaction type master. The view text selects five columns from the base table, applying aliasing and a single DECODE transformation. The synonym abstraction is significant: it allows the view to be compiled and validated independently of the physical table owner while still resolving through the APPS synonym layer. Because the view carries a VALID status in the ETRM metadata, its underlying dependency chain is intact and it can be queried reliably. The dependency on a single Inventory base object means the view inherits that table's security and data lifecycle, and any change to transaction type definitions is immediately reflected in the view.

Key Columns

• INV_TRANSACTION_TYPE_ID — The unique surrogate identifier for the inventory transaction type, aliased from TRANSACTION_TYPE_ID. This is the primary key used in joins to costing and accounting tables.
• TRANSACTION_TYPE_NAME — The user-facing name of the transaction type, aliased directly from TRANSACTION_TYPE_NAME. This is the column most commonly referenced by the search term and is the descriptive label used in reports and cross-references.
• TXN_TYPE_USER_DEFINED_FLAG — Indicates whether the transaction type is seeded by Oracle or user-defined, aliased from USER_DEFINED_FLAG. This distinction is important when filtering to standard versus custom transaction types.
• TYPE_CLASS — A derived flag produced by DECODE(TYPE_CLASS, 1, 'Y', 'N'). It converts the numeric class code into a Y/N indicator. Type class typically distinguishes transaction types relevant to costing and accounting processing.
• INV_TXN_TYPE_DESCRIPTION — The descriptive text of the transaction type, aliased from DESCRIPTION, providing additional context for reporting.

Common Use Cases and Queries

This view is typically joined to subledger accounting and costing tables to resolve transaction type names and descriptions for reporting. A common pattern is to enumerate all transaction types with their user-defined status:

SELECT INV_TRANSACTION_TYPE_ID, TRANSACTION_TYPE_NAME, TXN_TYPE_USER_DEFINED_FLAG, TYPE_CLASS FROM APPS.CST_XLA_INV_TXN_TYPES_REF_V WHERE TXN_TYPE_USER_DEFINED_FLAG = 'Y';

For costing reconciliation, analysts join the view to accounting event tables on INV_TRANSACTION_TYPE_ID to translate numeric identifiers into readable names. For example:

SELECT v.TRANSACTION_TYPE_NAME, v.INV_TXN_TYPE_DESCRIPTION FROM APPS.CST_XLA_INV_TXN_TYPES_REF_V v WHERE v.INV_TRANSACTION_TYPE_ID = :type_id;

Because the view is lightweight and carries no filtering predicate, it is well suited to lookup queries, LOV (List of Values) definitions, and integration extracts where the transaction type name must be presented alongside accounting metadata. Its single-table lineage also makes it predictable and inexpensive to query in both 12.1.1 and 12.2.2 environments.