Results for “wip_parameters_v”

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

Overview

WIP_PARAMETERS_V is an APPS-owned database view in the Work in Process (WIP) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It is documented as providing foreign-key (denormalized) data for the WIP_PARAMETERS table, exposing the organization-level WIP defaulting and control settings alongside the descriptive values that reside in referenced lookup and parameter tables. Its primary design purpose is to spare report, form, and integration developers from having to repeatedly join WIP_PARAMETERS to MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, MFG_LOOKUPS, and related objects in order to present human-readable meanings.

For a user searching on the term subinv_locator_type, this view is directly relevant: SUBINV_LOCATOR_TYPE is exposed as a column here, derived from MTL_SECONDARY_INVENTORIES.LOCATOR_TYPE for the supply subinventory defined in WIP_PARAMETERS. It therefore answers the common question of whether the default pull supply subinventory is locator-controlled, and if so, under which control regime.

Underlying Base Objects

The documented referenced base objects for the view are:

• WIP_PARAMETERS (synonym) — the driving table; one row per WIP organization.
• MTL_PARAMETERS (synonym) — organization-level inventory parameters.
• MTL_SECONDARY_INVENTORIES (synonym) — source of the subinventory-level locator control information.
• MFG_LOOKUPS (view) — supplies meanings for lookup-coded columns such as completion cost source and system options.
• CST_COST_TYPES (synonym) — provides the cost type name referenced by COST_TYPE_ID.
• MTL_ATP_RULES (synonym), PER_ALL_PEOPLE_F (synonym), WIP_VALID_INTRAOPERATION_STEPS (synonym) and WSH_PICK_GROUPING_RULES (synonym) — supporting reference objects for ATP, person, intraoperation step, and pick grouping attributes.

The view is defined with a SELECT over WIP_PARAMETERS aliased WP, outer-joined to these references, and includes several DECODE-based derived columns. It is, in effect, a presentation layer over the WIP setup tables rather than a table storing independent data.

Key Columns

• ORGANIZATION_ID — WIP organization identifier; the join key to inventory organizations.
• DEFAULT_PULL_SUPPLY_SUBINV — default supply subinventory for pull sequences.
• SUBINV_LOCATOR_TYPE — locator type of the default supply subinventory, sourced from MTL_SECONDARY_INVENTORIES.LOCATOR_TYPE. Values distinguish "no locator control," "prespecified locator," and "dynamic entry" behaviors.
• STOCK_LOCATOR_CONTROL_CODE — locator control code from MTL_PARAMETERS, indicating organization-level locator policy.
• DEFAULT_PULL_SUPPLY_LOCATOR_ID — the default locator used with the supply subinventory.
• LOT_NUMBER_DEFAULT_TYPE, BACKFLUSH_LOT_ENTRY_TYPE — lot defaulting and backflush entry behavior.
• LOT_SELECTION_METHOD, LOT_VERIFICATION — derived columns decoded from BACKFLUSH_LOT_ENTRY_TYPE.
• QUEUE_ENABLED_FLAG, RUN_ENABLED_FLAG, TO_MOVE_ENABLED_FLAG, REJECT_ENABLED_FLAG, SCRAP_ENABLED_FLAG — derived status flags computed from WIP_VALID_INTRAOPERATION_STEPS step counts (0/1/2 semantics).
• COMPLETION_COST_SOURCE, COMPLETION_COST_SOURCE_MEANING — cost source code and its MFG_LOOKUPS meaning.
• COST_TYPE_ID, COST_TYPE — costing type reference and name.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1..ATTRIBUTE15 — descriptive flexfield columns.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include validating WIP setup during implementation, auditing locator/lot control configuration, and feeding integration extracts. A query to inspect locator control for a supply subinventory would be:

• SELECT organization_id, default_pull_supply_subinv, subinv_locator_type, stock_locator_control_code, default_pull_supply_locator_id FROM apps.wip_parameters_v WHERE organization_id = :org_id;
• SELECT organization_id, completion_cost_source_meaning, cost_type FROM apps.wip_parameters_v ORDER BY organization_id;
• SELECT organization_id, queue_enabled_flag, run_enabled_flag, to_move_enabled_flag FROM apps.wip_parameters_v WHERE organization_id = :org_id;

Because the view is a simple projection, it can be queried without join predicates beyond the organization filter; report writers should still restrict by ORGANIZATION_ID to avoid cross-organization ambiguity.