Results for “wsm_split_merge_transactions”

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

Overview

WSM_SPLIT_MERGE_TRANSACTIONS is the base header table for WIP lot transactions in Oracle Shop Floor Management (OSFM), a module within the WSM product family. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the WSM schema and records the header-level information for split and merge operations performed against work-in-process lots on the shop floor. Each row represents a discrete lot transaction—such as splitting a parent lot into multiple children or merging multiple lots into a single lot—and serves as the anchor point for the transaction lines and inventory consequences that follow.

From a Data Vault modeling perspective, the heuristic classification supplied in the ETRM metadata is link. This reflects the table's role as an associative construct that connects several business entities: the organization performing the transaction, the employee executing it, the transaction reason, and an accounting suspense account. The table's natural identity is the surrogate primary key TRANSACTION_ID, which is also enforced through the unique index WSM_SPLIT_MERGE_TXN_U1. WSM_SPLIT_MERGE_TRANSACTIONS holds 39 documented columns, many of which are standard EBS Who columns and a DFF attribute group (ATTRIBUTE_CATEGORY through ATTRIBUTE15).

Key Information Stored

The most operationally significant columns include:

• TRANSACTION_ID — the surrogate primary key (constraint WSM_SPLIT_MERGE_TRANSACTIO_PK) and unique-index business-key candidate; uniquely identifies each split or merge transaction.
• TRANSACTION_TYPE_ID — distinguishes the nature of the transaction (split versus merge, or variants thereof).
• TRANSACTION_DATE — the effective date of the lot transaction, used for period and cost reporting.
• ORGANIZATION_ID — the inventory organization in which the transaction occurred; foreign key to WSM_PARAMETERS.
• REASON_ID — the reason code assigned to the transaction; foreign key to MTL_TRANSACTION_REASONS.
• EMPLOYEE_ID — the operator or employee performing the transaction; foreign key to PSB_EMPLOYEES.
• TRANSACTION_REFERENCE — a free-text or user-defined reference that identifies the transaction for audit and traceability.
• STATUS — the processing state of the transaction record.
• COSTED — a cost-manager indicator showing whether the transaction has been picked up by costing.
• CONCURRENT_REQUEST_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrency and program-context columns recording the concurrent request that processed the row.
• GROUP_ID, INTERNAL_GROUP_ID — grouping identifiers used to tie related rows together during batch processing.
• ERROR_MESSAGE — diagnostic text populated when the transaction fails processing.
• ATTRIBUTE1 – ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the descriptive flexfield segment used for customer-specific extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit (Who) columns.

Common Use Cases and Queries

Typical reporting use cases include tracing the history of a lot's splits and merges, reconciling OSFM lot activity against inventory and cost records, and auditing failed transactions. A representative query retrieving recent transactions for an organization follows:

SELECT transaction_id, transaction_type_id, transaction_date,
       organization_id, reason_id, employee_id, status, costed
FROM   wsm.wsm_split_merge_transactions
WHERE  organization_id = :org_id
AND    transaction_date >= :start_date
ORDER  BY transaction_date;

For concurrency troubleshooting, querying by CONCURRENT_REQUEST_ID or filtering on a populated ERROR_MESSAGE isolates records that failed during batch processing. Filtering on COSTED = 'N' identifies transactions not yet processed by the cost manager, which is useful in period-close reconciliations.

Related Objects

The following objects are directly related through documented foreign keys or by structural dependency:

• MTL_TRANSACTION_REASONS — joined on REASON_ID to obtain the reason description for a transaction.
• WSM_PARAMETERS — joined on ORGANIZATION_ID to resolve organization-level OSFM parameters.
• PSB_EMPLOYEES — joined on EMPLOYEE_ID to identify the operator.
• WSM_SPLIT_MERGE_TXN_U1 — the unique index enforcing business-key uniqueness on TRANSACTION_ID.
• WSM_SPLIT_MERGE_TRANSACTIO_PK — the primary-key constraint on TRANSACTION_ID.
• Detail (line-level) WSM transaction tables, which carry the child rows keyed by TRANSACTION_ID to describe the individual lot movements resulting from the header transaction.