Results for “mtl_trx_types_view”

46 results




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

Overview

MTL_TRX_TYPES_VIEW is an APPS-owned database view within the INV (Inventory) product module of Oracle E-Business Suite. It is documented as "Retrofitted," indicating that the object was reconstructed or migrated as part of the ETRM delivery rather than authored originally as a new database object. The view exposes a consolidated, de-normalized projection of transaction type definitions by joining the core transaction type table with the transaction source type table. Its principal role is to provide a single, query-friendly source of transaction type metadata for reports, concurrent programs, forms, and integration interfaces that must resolve a transaction type identifier to its descriptive attributes. Because the view filters out disabled records, consumers automatically see only currently enabled transaction types and transaction source types.

The object is relevant to the search term "location_required_flag," since that column is one of the attributes surfaced directly by the view. This flag indicates whether a given transaction type requires a valid location to be supplied when the transaction is executed, making the view valuable for validation logic and for reporting on transaction configuration.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through public synonyms:

  • MTL_TRANSACTION_TYPES (SYNONYM) — the primary transaction type definition table, aliased TP in the view text. It supplies transaction type name and identifier, source type and action identifiers, description, type class, and the location_required_flag.
  • MTL_TXN_SOURCE_TYPES (SYNONYM) — the transaction source type table, aliased SRC. It supplies the descriptive flexfield context code and the transaction source type name.

The join is performed on TRANSACTION_SOURCE_TYPE_ID, establishing a one-to-many relationship from source type to transaction type. The defining SQL applies two filters: NVL(TP.DISABLE_DATE, SYSDATE+1) > SYSDATE and NVL(SRC.DISABLE_DATE, SYSDATE+1) > SYSDATE. Consequently, any transaction type or source type whose disable date is on or before the current system date is excluded from the result set. Records with a null disable date are treated as perpetually enabled.

Key Columns

  • TRANSACTION_TYPE_NAME — the descriptive name of the transaction type, such as a specific issue, receipt, or transfer type.
  • TRANSACTION_TYPE_ID — the unique surrogate key for the transaction type; the standard foreign key used throughout Inventory transaction tables.
  • TRANSACTION_SOURCE_TYPE_ID — identifies the source type to which the transaction type belongs and is the join key between the two base tables.
  • TRANSACTION_ACTION_ID — the action associated with the transaction type, used in transaction processing logic.
  • DESCRIPTION — free-text description of the transaction type.
  • DESCRIPTIVE_FLEX_CONTEXT_CODE — the DFF context code from the source type, enabling consumers to determine which descriptive flexfield structure applies.
  • TRANSACTION_SOURCE_TYPE_NAME — the descriptive name of the transaction source type.
  • TYPE_CLASS — the classification of the transaction type, used to group and drive behavior.
  • LOCATION_REQUIRED_FLAG — indicates whether a location must be specified for transactions of this type; central to the user's search.

Common Use Cases and Queries

The view is frequently used to present transaction type configuration in reporting and to feed validation routines that must know whether a location is mandatory. A typical validation query retrieves the flag for a specific transaction type:

SELECT transaction_type_id, transaction_type_name, location_required_flag
FROM apps.mtl_trx_types_view
WHERE transaction_type_id = :p_trx_type_id;

A configuration report listing all enabled transaction types and their source types can be produced as follows:

SELECT transaction_source_type_name, transaction_type_name, type_class, location_required_flag
FROM apps.mtl_trx_types_view
ORDER BY transaction_source_type_name, transaction_type_name;

Because the view already excludes disabled records, these queries require no additional disable-date predicates, simplifying downstream SQL and ensuring that integrations do not present obsolete transaction types. Organizations should note that the view is read-only and should not be used as a target for DML; configuration changes must be made against the underlying base tables.