Results for “transaction_source_category”

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

Overview

MTL_TXN_SOURCE_TYPES_ALL_V is an Oracle E-Business Suite Inventory (INV) view owned by the APPS schema. It presents a filtered or projected set of transaction source type definitions used throughout the Oracle Inventory and Order Management transaction processing framework. In the ETRM metadata for both 12.1.1 and 12.2.2, the view is documented with the note "10SC ONLY," indicating it is intended for specific sourcing/operational contexts rather than general-purpose reporting. Its status is VALID, and it exposes a comprehensive column set that mirrors the structure of the underlying transaction source type entity, including descriptive flexfield segments and standard WHO columns.

The view plays a supporting role in reporting and integration: it provides a stable, APPS-owned interface through which transaction source categories and validation flags can be queried without referencing the base table directly. This is significant in EBS environments where custom code, concurrent programs, or external integrations need to identify valid transaction source types for material transactions, move orders, and related inventory activities.

Underlying Base Objects

According to the documented view text, MTL_TXN_SOURCE_TYPES_ALL_V is defined as a direct SELECT over MTL_TXN_SOURCE_TYPES, referenced in the metadata as a SYNONYM. The view projects every listed column from that base object, including TRANSACTION_SOURCE_TYPE_ID, the descriptive flexfield context and attribute columns, the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY), and the concurrent program request columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

The relationship is therefore one-to-one at the row level: each row in the view corresponds to a transaction source type record in the base table. The "_ALL" suffix in EBS naming conventions typically denotes a view that has been consolidated across operating units or organizations, though the documented view text shows no organizational filter. Practitioners should nonetheless validate whether a corresponding organizational or security predicate exists in their specific instance before assuming unrestricted visibility.

Key Columns

The column most relevant to the user's search term, VALIDATED_FLAG, is exposed directly by this view. It indicates whether a given transaction source type has been validated for use in transaction processing, and it is commonly used to restrict queries to active, validated source types. Other significant columns include:

• TRANSACTION_SOURCE_TYPE_ID – Primary key and unique identifier for the source type.
• TRANSACTION_SOURCE_TYPE_NAME and DESCRIPTION – Business-facing name and description of the source type.
• TRANSACTION_SOURCE_CATEGORY and TRANSACTION_SOURCE – Classification values that determine the operational context in which the source type applies.
• DISABLE_DATE – Effective end date for the source type; a null value typically indicates it remains active.
• USER_DEFINED_FLAG – Distinguishes seeded Oracle source types from those created by users.
• DESCRIPTIVE_FLEX_CONTEXT_CODE and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield context and segment values for extensible attributes.
• WHO and concurrent program columns – Audit and request tracking metadata.

Common Use Cases and Queries

Typical uses include validating source types prior to material transaction entry, populating list-of-values queries, and reconciliation reporting. A representative query filtering on the validated flag is:

• SELECT transaction_source_type_id, transaction_source_type_name, transaction_source_category, validated_flag, disable_date FROM mtl_txn_source_types_all_v WHERE validated_flag = 'Y' AND disable_date IS NULL ORDER BY transaction_source_type_name;

Additional scenarios include auditing user-defined source types (WHERE user_defined_flag = 'Y'), joining the view to transaction tables such as MTL_MATERIAL_TRANSACTIONS to attribute transactions to their source type, and extracting descriptive flexfield attributes for downstream integration. Because the view is documented as "10SC ONLY," it should be treated as a context-specific interface, and any dependency should be reviewed against the target EBS release's data model before promotion.