Results for “invbv_inventory_txn_types”

14 results




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

Overview

The INVBV_INVENTORY_TXN_TYPES view is a reporting and integration object owned by the APPS schema within the Oracle Inventory (INV) module. In Oracle E-Business Suite 12.1.1 and 12.2.2, it is classified as VALID and is described in ETRM documentation as "Retrofitted," indicating it was introduced or adapted to preserve backward compatibility for existing customizations and integrations during an upgrade or architectural change. Functionally, the view exposes a curated projection of the inventory transaction type definitions stored in the underlying MTL_TRANSACTION_TYPES table. Because it is defined WITH READ ONLY, it is intended strictly for query, validation, and reference purposes rather than for DML operations.

The view serves as a simplified access point for applications, concurrent programs, and external integrations that need to enumerate or validate inventory transaction types without directly binding to the base table. It is particularly relevant to users filtering on transaction classification, since it surfaces the TYPE_CLASS column prominently among its projected attributes.

Underlying Base Objects

The view is defined over a single documented base object: the synonym MTL_TRANSACTION_TYPES, aliased within the view text as MTT. The SELECT statement references this synonym with a WITH READ ONLY clause, and Oracle EBS metadata records the referenced base object as MTL_TRANSACTION_TYPES (SYNONYM). The view therefore relies on the standard INV transaction type setup data maintained through the Inventory transaction type definition forms. No joins to other tables are present in the documented view text; it is a direct, column-level projection of the base table's contents.

Key Columns

  • TRANSACTION_TYPE_ID — Primary identifier for each transaction type, referenced throughout INV transaction processing.
  • TRANSACTION_TYPE_NAME — The user-facing name of the transaction type (for example, "Sales Order Issue" or "Miscellaneous Receipt").
  • DESCRIPTION — Free-text description associated with the transaction type.
  • TRANSACTION_ACTION — Exposed via the literal expression '_LA:MTT.TRANSACTION_ACTION_ID:MFG_LOOKUPS:MTL_TRANSACTION_ACTION:MEANING', which is an Oracle Application Framework (OAF) descriptive-flexfield lookup reference resolving the action meaning from the MFG_LOOKUPS table using the MTL_TRANSACTION_ACTION lookup type.
  • TRANSACTION_SOURCE_TYPE_ID — Identifies the source type that may generate this transaction.
  • INACTIVE_DATE — The date on which the transaction type was disabled. Note that ETRM lists this column as INACTIVE_DATE, mapped from DISABLE_DATE in the base table.
  • USER_DEFINED_FLAG — Indicates whether the transaction type is seeded by Oracle (N) or user-defined (Y).
  • TYPE_CLASS — The classification column most relevant to the user's search; it distinguishes transaction type categories used in transaction processing and reporting logic.

Common Use Cases and Queries

This view is commonly queried to drive LOVs, validate transaction types during interface loads, and report on enabled versus disabled transaction definitions. Filtering by TYPE_CLASS is a frequent requirement when segregating transaction types for a specific business process.

  • List all active transaction types:
    SELECT transaction_type_id,
           transaction_type_name,
           type_class
    FROM   apps.invbv_inventory_txn_types
    WHERE  inactive_date IS NULL
    ORDER BY transaction_type_name;
  • Filter by classification:
    SELECT transaction_type_id,
           transaction_type_name,
           description,
           type_class
    FROM   apps.invbv_inventory_txn_types
    WHERE  type_class = :p_type_class;
  • Identify seeded versus user-defined types:
    SELECT transaction_type_name,
           user_defined_flag,
           type_class
    FROM   apps.invbv_inventory_txn_types
    WHERE  user_defined_flag = 'Y';

Because the view is read-only, any maintenance of transaction type definitions must be performed against the underlying MTL_TRANSACTION_TYPES table or through the standard Inventory setup forms.