Results for “subinventory_code”

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

Overview

WSM_INV_GENEALOGY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the WSM (Shop Floor Management) product family. It presents a consolidated, denormalized projection of inventory material transactions, joining each transactional record to its organization, transaction type, transaction action, and transaction source type. The view is intended for genealogy and shop-floor reporting: it allows implementers and report developers to query inventory movements without repeatedly reconstructing the multi-table join graph that underpins transaction inquiry. The view is documented as VALID under both Oracle EBS 12.1.1 and 12.2.2.

A defining characteristic of this view is its use of the MFG_LOOKUPS lookup type MTL_TRANSACTION_ACTION to translate the numeric action identifier into a user-facing meaning. This is directly relevant to the search term mtl_transaction_action, which corresponds to the lookup type that classifies inventory transaction actions (for example, issue, receipt, transfer, and related movement semantics) across Oracle Inventory and Shop Floor Management.

Underlying Base Objects

The documented view text joins six objects. The primary driving table is MTL_MATERIAL_TRANSACTIONS (referenced as a synonym), which stores individual inventory transaction records. It is joined to:

• MTL_PARAMETERS — provides the organization context and organization code.
• HR_ORGANIZATION_UNITS — supplies the organization name; the documented dependency list also references the HR_GENERAL and HR_SECURITY packages, which govern organization-level security in Human Resources.
• MTL_TRANSACTION_TYPES — supplies the descriptive transaction type.
• MFG_LOOKUPS — restricted to lookup type MTL_TRANSACTION_ACTION, supplying the action meaning.
• MTL_TXN_SOURCE_TYPES — provides the transaction source type description.

Because HR_ORGANIZATION_UNITS is secured through HR_SECURITY and HR_GENERAL, queries against this view inherit organization access restrictions, which is a material consideration for reporting design and performance.

Key Columns

The view exposes eleven columns. The join predicates in the view text do not include a filter on TRANSACTION_ACTION_ID being non-null, so rows where the action lookup does not resolve may be excluded by the inner join to MFG_LOOKUPS.

• TRANSACTION_ID — primary identifier of the material transaction.
• SUBINVENTORY_CODE — subinventory in which the transaction occurred.
• TRANSACTION_DATE — effective date of the movement.
• CREATED_BY — user who created the transaction record.
• ORGANIZATION_CODE / ORGANIZATION_NAME — organization identifiers sourced from MTL_PARAMETERS and HR_ORGANIZATION_UNITS respectively.
• TRANSACTION_TYPE — description from MTL_TRANSACTION_TYPES.
• TRANSACTION_ACTION — the MEANING value from MFG_LOOKUPS for lookup type MTL_TRANSACTION_ACTION.
• SOURCE_TYPE — description from MTL_TXN_SOURCE_TYPES.
• LOCATOR_ID — inventory locator associated with the transaction.
• ORGANIZATION_ID — numeric organization identifier.

Common Use Cases and Queries

Typical uses include genealogical traceability of material movements, shop-floor transaction audits, and reconciliation of inventory activity by action and source type. The following example retrieves recent transactions with their resolved action meaning.

• SELECT transaction_id, organization_code, transaction_date, transaction_type, transaction_action, source_type FROM apps.wsm_inv_genealogy_v WHERE transaction_date >= SYSDATE - 30;
• SELECT transaction_action, COUNT(*) FROM apps.wsm_inv_genealogy_v GROUP BY transaction_action;
• SELECT * FROM apps.wsm_inv_genealogy_v WHERE organization_id = :org_id AND subinventory_code = :sub;

Because the view performs inner joins across organization, type, action, and source lookups, rows lacking a matching lookup entry are omitted. Reports requiring complete transaction populations should query MTL_MATERIAL_TRANSACTIONS directly and apply outer joins to MFG_LOOKUPS where action classification is required.