Search Results event_effectivity_date

Overview

APPS.WIP_FLOW_ASSEMBLY_EVENTS_V is a documented Oracle E-Business Suite view belonging to the Work in Process (WIP) module. It exposes a flattened, denormalized representation of assembly-level routing events, combining data from bill of material (BOM) routing definitions, standard operations, departments, and inventory item master records. The view carries an Oracle Internal Use Only designation in the ETRM metadata, meaning that Oracle Corporation does not support direct customer access to this object except through standard Oracle Applications programs. Its status is VALID, and its FND Design Data reference is WIP.WIP_FLOW_ASSEMBLY_EVENTS_V. The view type is documented as Internal. Despite the restricted support posture, the object is frequently encountered in reporting and diagnostic contexts, particularly where flow manufacturing routing events and operation effectivity windows are analyzed. The column EVENT_EFFECTIVITY_DATE, which surfaces in the underlying metadata alongside EFFECTIVITY_DATE and DISABLE_DATE, is central to queries seeking to determine when a routing event becomes active on a flow assembly, and it is the column most commonly associated with the "event_effectivity_date" search term.

Underlying Base Objects

The view is defined over six documented base objects within the APPS schema. BOM_DEPARTMENTS supplies department identifiers and department codes. BOM_OPERATIONAL_ROUTINGS provides the routing header context, including routing revision and alternate designator information. BOM_OPERATION_SEQUENCES contributes operation sequence details such as sequence identifiers, operation sequence numbers, and lead time percentages. BOM_STANDARD_OPERATIONS provides standard operation definitions and codes. MTL_ROUTING_REV_HIGHDATE_V, itself a view, resolves the high date or revision effectivity boundary for routings. MTL_SYSTEM_ITEMS_KFV supplies the concatenated item description key flexfield values used for the ASSEMBLY_NAME column. The ETRM metadata records all of these as SYNONYM references except MTL_ROUTING_REV_HIGHDATE_V, which is listed as a VIEW. Notably, the view is not referenced by any other database object, confirming it functions as a terminal reporting or internal retrieval layer rather than a shared dependency.

Key Columns

The view exposes twenty columns. LINE_ID, NODE_LABEL, ORGANIZATION_ID, and INVENTORY_ITEM_ID identify the assembly line and item context. ALTERNATE_ROUTING_DESIGNATOR and PROCESS_REVISION describe which routing variant and revision applies. EFFECTIVITY_DATE records the routing effectivity date, while EVENT_EFFECTIVITY_DATE records the effectivity date of the specific assembly event, and DISABLE_DATE records the date the event is disabled. LINE_OPERATION_SEQUENCE_ID, OPERATION_SEQUENCE_ID, OPERATION_SEQ_NUM, OPERATION_CODE, and OPERATION_DESCRIPTION identify the operation within the routing. OPERATION_LEAD_TIME_PERCENT and DEPARTMENT_ID relate to scheduling and departmental assignment. STANDARD_OPERATION_ID and DEPARTMENT_CODE complete the operation and department identification. ASSEMBLY_NAME carries the concatenated item name, and NODE_TYPE indicates the node classification within the flow structure.

Common Use Cases and Queries

Typical uses include auditing flow assembly routing effectivity windows, validating that operation events are active for a given date, and reconciling assembly names against the item master. A representative query filtering on the event effectivity date is shown below.

• SELECT LINE_ID, NODE_LABEL, ORGANIZATION_ID, INVENTORY_ITEM_ID, ASSEMBLY_NAME, OPERATION_SEQ_NUM, EVENT_EFFECTIVITY_DATE, DISABLE_DATE FROM APPS.WIP_FLOW_ASSEMBLY_EVENTS_V WHERE EVENT_EFFECTIVITY_DATE >= SYSDATE AND (DISABLE_DATE IS NULL OR DISABLE_DATE > SYSDATE);
• SELECT ASSEMBLY_NAME, PROCESS_REVISION, ALTERNATE_ROUTING_DESIGNATOR, EVENT_EFFECTIVITY_DATE FROM APPS.WIP_FLOW_ASSEMBLY_EVENTS_V WHERE ORGANIZATION_ID = :org_id AND INVENTORY_ITEM_ID = :item_id ORDER BY EVENT_EFFECTIVITY_DATE;
• SELECT ORGANIZATION_ID, DEPARTMENT_CODE, OPERATION_CODE, COUNT(*) FROM APPS.WIP_FLOW_ASSEMBLY_EVENTS_V WHERE EVENT_EFFECTIVITY_DATE BETWEEN :start_date AND :end_date GROUP BY ORGANIZATION_ID, DEPARTMENT_CODE, OPERATION_CODE;

Because Oracle classifies the view as internal and unsupported for direct external access, any custom reporting built against it should be validated against the supported WIP and BOM public APIs where possible.