Results for “queue_mandatory_flag”

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

Overview

WSM_OPERATION_DETAILS_V is a database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the WSM (Shop Floor Management) product family and exists to present operation-level shop floor configuration alongside descriptive attributes of the associated standard operation. In ETRM and related technical documentation the object carries a status of VALID, indicating that the compiled view definition is consistent with its referenced objects at the time of documentation.

The view is read-only by construction and is typically consumed by reports, concurrent program validations, and integration extracts that need to resolve whether a given routing operation requires operator confirmation at the queue, run, or to-move stages. Because it joins two underlying entities, it spares callers from repeating the join between operation detail records and the standard operation master.

Underlying Base Objects

The ETRM 12.2.2 metadata documents two referenced base objects, both accessed through APPS synonyms: BOM_STANDARD_OPERATIONS and WSM_OPERATION_DETAILS. The view text confirms this relationship explicitly:

• WSM_OPERATION_DETAILS WOD supplies the organization-scoped detail row, including the mandatory flags, secondary inventory, and inventory location.
• BOM_STANDARD_OPERATIONS BSO supplies the descriptive attributes OPERATION_CODE and OPERATION_DESCRIPTION.
• The two are joined on STANDARD_OPERATION_ID, an equi-join on the standard operation identifier.

Consequently the view returns one row per WSM_OPERATION_DETAILS record that has a matching standard operation. The row identity is exposed through WOD.ROWID as ROW_ID, and all standard audit columns from the detail row are carried through unchanged.

Key Columns

The view exposes fifteen columns. The following are the most significant for functional and troubleshooting purposes:

• ROW_ID — the ROWID of the underlying WSM_OPERATION_DETAILS row, useful for direct DML targeting or diagnostics.
• STANDARD_OPERATION_ID — the join key linking detail configuration to the standard operation master.
• OPERATION_CODE and OPERATION_DESCRIPTION — human-readable identification of the operation, sourced from BOM_STANDARD_OPERATIONS.
• ORGANIZATION_ID — the inventory organization to which the detail configuration applies.
• SECONDARY_INVENTORY_NAME and INVENTORY_LOCATION_ID — the default staging inventory and locator for the operation.
• QUEUE_MANDATORY_FLAG, RUN_MANDATORY_FLAG, and TO_MOVE_MANDATORY_FLAG — indicators controlling whether the operator must record queue, run, and to-move transactions respectively. These are the columns most often queried when validating shop floor transaction behavior.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from the detail row.

Common Use Cases and Queries

Typical uses include auditing which operations enforce mandatory move or run confirmation, extracting organization-specific operation defaults, and joining to routing or work order tables to determine expected operator prompts. The following query lists mandatory run operations for a given organization:

SELECT operation_code,
       operation_description,
       organization_id,
       run_mandatory_flag
FROM   apps.wsm_operation_details_v
WHERE  organization_id = :org_id
AND    run_mandatory_flag = 'Y';

To audit all three mandatory flags together:

SELECT operation_code,
       queue_mandatory_flag,
       run_mandatory_flag,
       to_move_mandatory_flag
FROM   apps.wsm_operation_details_v
WHERE  standard_operation_id = :std_op_id;

Because the view performs an inner join, any WSM_OPERATION_DETAILS row lacking a valid parent standard operation will not appear. When results appear incomplete, the underlying tables should be queried directly to confirm data integrity between the two base objects.