Results for “component_yield_factor”

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

Overview

The APPS.WIP_REQUIREMENT_OPERATIONS_V view is a denormalized reporting and integration construct within the Oracle E-Business Suite Work in Process (WIP) module. It exposes the foreign-key descriptor data associated with the WIP_REQUIREMENT_OPERATIONS base table, which stores the material requirements that a discrete or repetitive job or schedule places on a given operation. The base table holds numeric foreign keys and coded lookup values; the view resolves those keys into human-readable descriptions such as item concatenated segments, department codes, and lookup meanings. Because the view is owned by APPS and carries a VALID status, it is intended for direct querying by reports, concurrent programs, and third-party integrations without requiring callers to re-implement the joins themselves. In the context of a search for "basis_type_meaning," the view is particularly relevant because it is one of the few accessible objects that surfaces BASIS_TYPE_MEANING, the decoded meaning of the BASIS_TYPE column, alongside NVL(BASIS_TYPE, 1) so that rows with no stored value are presented consistently as basis type 1.

Underlying Base Objects

According to the documented 12.2.2 metadata, the view is defined over six referenced base objects:

• WIP_REQUIREMENT_OPERATIONS (SYNONYM) — the driving table, aliased WRO, supplying requirement quantities, dates, supply type, basis type, and key columns.
• MTL_SYSTEM_ITEMS_VL (VIEW) — aliased MSIK, supplying CONCATENATED_SEGMENTS, ITEM_DESCRIPTION, PRIMARY_UOM_CODE, and inventory attribute flags.
• MFG_LOOKUPS (VIEW) — aliased ML1 and ML2, joined twice to resolve WIP_SUPPLY_TYPE into WIP_SUPPLY_MEANING and BASIS_TYPE into BASIS_TYPE_MEANING.
• BOM_DEPARTMENTS (SYNONYM) — aliased BD, supplying DEPARTMENT_CODE.
• WIP_OPERATIONS (SYNONYM) — aliased WOP, supplying routing existence and first/last unit dates.
• WIP_REPETITIVE_SCHEDULES (SYNONYM) — aliased WRS, supplying LINE_ID for repetitive schedules.

The view therefore concentrates the descriptive attributes of five related entities around a single requirement row.

Key Columns

The view carries the primary key ROW_ID derived from WRO.ROWID, followed by INVENTORY_ITEM_ID and its descriptive counterparts CONCATENATED_SEGMENTS and ITEM_DESCRIPTION. Job context is provided by ORGANIZATION_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, and REPETITIVE_SCHEDULE_ID. Scheduling information includes DEPARTMENT_ID with DEPARTMENT_CODE, DATE_REQUIRED, REQUIRED_QUANTITY, QUANTITY_PER_ASSEMBLY, COMPONENT_YIELD_FACTOR, and COMPONENT_YIELD_FACTOR-derived quantities. Quantity issued and open quantities are computed with DECODE and SIGN logic so that zero values and sign mismatches are suppressed rather than reported. Supply information is represented by WIP_SUPPLY_TYPE and WIP_SUPPLY_MEANING, plus SUPPLY_SUBINVENTORY and SUPPLY_LOCATOR_ID. The BASIS_TYPE column is wrapped in NVL(BASIS_TYPE, 1), and the corresponding BASIS_TYPE_MEANING is the decoded lookup value — this is the column referenced by the user's search term. ROUTING_EXISTS_FLAG is derived from WIP_OPERATIONS. Standard WHO columns and the ATTRIBUTE1 through ATTRIBUTE14 flexfield columns are also exposed, with LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE supporting audit and concurrent program traceability.

Common Use Cases and Queries

Typical usage covers component requirement reporting, shortage analysis, and integration extracts. A query to list requirements with their basis type description might read:

SELECT WIP_ENTITY_ID, OPERATION_SEQ_NUM, CONCATENATED_SEGMENTS, REQUIRED_QUANTITY, BASIS_TYPE, BASIS_TYPE_MEANING FROM APPS.WIP_REQUIREMENT_OPERATIONS_V WHERE ORGANIZATION_ID = :org_id AND BASIS_TYPE_MEANING = 'Per Assembly';

Because BASIS_TYPE_MEANING is already decoded, callers need not join MFG_LOOKUPS. Combined with ROUTING_EXISTS_FLAG and the OPERATION_SEQ_NUM column, the view also supports open-shop-floor queries that distinguish operation-level requirements from non-routing requirements, and it can be joined to WIP_ENTITIES or WIP_DISCRETE_JOBS for job-level reporting.