Results for “cst_wip_txn_type_view”

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

Overview

CST_WIP_TXN_TYPE_VIEW is a single-organization (SINGLE-ORG) reporting view owned by the APPS schema in Oracle E-Business Suite. It belongs to the BOM (Bills of Material) product family and presents the set of valid Work in Process (WIP) transaction types available in the system. Its purpose is to consolidate two disparate sources of WIP transaction type definitions into a single, uniformly structured result set, allowing reports, interfaces, and integrations to enumerate WIP transaction types without needing to know whether a given type originated from discrete manufacturing transactions or from the manufacturing lookup dictionary.

Because the view normalizes both sources to a common three-column layout, it functions as a lightweight reference or seed query. Typical consumers include custom reports on WIP activity, validation routines that check a transaction type before posting, migration and conversion scripts that map legacy transaction type codes, and integration layers that require a canonical list of WIP transaction types. Its SINGLE-ORG designation indicates it is scoped to the current operating organization context and does not aggregate across multiple organizations, distinguishing it from any multi-org counterpart.

Underlying Base Objects

The view text is defined as a UNION of two SELECT statements, drawing on two referenced base objects documented in the ETRM metadata:

• MTL_TRANSACTION_TYPES (referenced as a SYNONYM) — the first branch selects from this object, filtering on TRANSACTION_SOURCE_TYPE_ID = 5. This source type corresponds to WIP transactions, so the branch contributes the WIP-relevant transaction types maintained in the transaction type table.
• MFG_LOOKUPS (referenced as a VIEW) — the second branch selects lookup rows where LOOKUP_TYPE = 'WIP_TRANSACTION_TYPE', returning the lookup code and its meaning as the transaction type identifier and name.

The UNION combines these two streams, effectively merging the transaction-type-table representation of WIP transactions with the lookup-dictionary representation. The literal first column distinguishes the origin of each row, tagging records from MTL_TRANSACTION_TYPES as 'INV' and records from MFG_LOOKUPS as 'WIP'.

Key Columns

The view exposes three columns:

• PRODUCT_SHORT_NAME — A literal discriminator indicating the source of the transaction type row. Values are 'INV' (derived from MTL_TRANSACTION_TYPES) and 'WIP' (derived from MFG_LOOKUPS). This allows consumers to trace each row back to its originating subsystem and to filter by source when required.
• TRANSACTION_TYPE_ID — The identifier of the transaction type. For rows sourced from MTL_TRANSACTION_TYPES this is the numeric TRANSACTION_TYPE_ID; for rows sourced from MFG_LOOKUPS it is the LOOKUP_CODE. Because the two sources differ in native data type and format, consumers should treat this column as a textual or loosely typed identifier rather than assuming a strictly numeric key.
• TRANSACTION_TYPE_NAME — The descriptive name of the transaction type. It maps to TRANSACTION_TYPE_NAME from MTL_TRANSACTION_TYPES and to MEANING from MFG_LOOKUPS, providing a human-readable label suitable for display on reports and for populating value lists.

Common Use Cases and Queries

The view is most often used to populate selection lists, validate transaction type values, and drive WIP reporting. A straightforward enumeration of all transaction types follows:

• SELECT product_short_name, transaction_type_id, transaction_type_name FROM apps.cst_wip_txn_type_view ORDER BY product_short_name, transaction_type_name;

To restrict the output to transaction types originating from the transaction type table only:

• SELECT transaction_type_id, transaction_type_name FROM apps.cst_wip_txn_type_view WHERE product_short_name = 'INV';

To resolve a specific type by name or code — for example, when validating input in a conversion script — a parameterized query such as the following is typical:

• SELECT product_short_name, transaction_type_name FROM apps.cst_wip_txn_type_view WHERE transaction_type_id = :p_txn_type;

Because the view resolves its base objects through SYNONYM and VIEW references owned by APPS, queries should be executed with the APPS schema or an appropriate synonym in scope. As a read-only reference view it carries no update semantics; all maintenance of transaction types is performed against the underlying base tables, and the view reflects those changes automatically.