Search Results schedule_description

Overview

The WIPFV_REPETITIVE_SCHEDULES view is a descriptive (flexfield-enabled) reporting view owned by the APPS schema within the Work in Process (WIP) module of Oracle E-Business Suite. It exposes repetitive schedule data — the manufacturing model in which a discrete quantity of an assembly is produced repeatedly over a defined window rather than through a single discrete job. In ETRM 12.2.2 the object carries a status of VALID and is classified as a VIEW, meaning applications and reports query it directly rather than through a base table.

The view's primary role is to present repetitive schedule records in a user-friendly, denormalized form. It joins scheduling attributes to descriptive flexfield references (denoted by the _DF:WIP:WIP_REPETITIVE_SCHEDULES:RE string) and to key flexfield references for the inventory item (_KF:INV:MSTK:SY1–SY3) and the accounting flexfield (_KF:SQLGL:GL#:CO1–CO9). These pseudo-column tokens are resolved by the Oracle Forms and OA Framework layers to render flexfield segments, which is why the view is often used in WIP forms, concurrent programs, and custom reports that need to display schedule information exactly as the application does.

Underlying Base Objects

The view draws on a documented set of base objects, principally WIP_REPETITIVE_SCHEDULES, WIP_REPETITIVE_ITEMS, and WIP_ENTITIES, with supporting joins to WIP_LINES for production line information. The schedule's item and organization context is provided through MTL_SYSTEM_ITEMS (aliased SY1, SY2, SY3) and MTL_PARAMETERS, while BOM_BILL_OF_MATERIALS and BOM_OPERATIONAL_ROUTINGS supply BOM and routing revision context. Nine joins to GL_CODE_COMBINATIONS (CO1–CO9) resolve the various WIP accounting class accounts, and HR_ALL_ORGANIZATION_UNITS supplies the organization name. The FND_GLOBAL package is referenced for session context such as the current organization (ORG_ID), which drives multi-org security filtering. The visible SELECT list confirms these relationships: schedule columns from RE (WIP_REPETITIVE_SCHEDULES), item/entity names from EN, organization code from PA, line code from LI, and account identifiers from the CO1–CO9 joins.

Key Columns

• REPETITIVE_SCHEDULE_ID — primary key uniquely identifying the repetitive schedule.
• WIP_ENTITY_ID — links the schedule to its WIP entity; ORGANIZATION_ID and LINE_ID establish the plant and production line.
• WIP_ENTITY_NAME — the schedule's entity name as displayed to users.
• DAILY_PRODUCTION_RATE and PROCESSING_WORK_DAYS — the rate and cadence driving production.
• FIRST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, LAST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE, DATE_RELEASED, DATE_CLOSED — the schedule lifecycle dates.
• STATUS_TYPE (lookup WIP_JOB_STATUS) and FIRM_PLANNED_FLAG (lookup SYS_YES_NO) — decoded status and firming indicators.
• QUANTITY_COMPLETED — cumulative completed quantity.
• COMPLETION_SUBINVENTORY and related material account columns — destination and accounting context.
• ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR, BOM_REVISION_DATE, ROUTING_REVISION_DATE — BOM/routing selection and revision detail.
• ORGANIZATION_CODE, LINE_CODE, DESCRIPTION — descriptive attributes surfaced from joined tables.

Common Use Cases and Queries

The view is typically queried for repetitive schedule reporting, line loading analysis, and integration extracts. A basic query retrieving active schedules follows:

SELECT repetitive_schedule_id,
       wip_entity_name,
       status_type,
       daily_production_rate,
       first_unit_start_date,
       last_unit_completion_date,
       quantity_completed
FROM   apps.wipfv_repetitive_schedules
WHERE  organization_id = :p_org_id
ORDER  BY first_unit_start_date;

Because the view resolves flexfield references, it is preferred over the base table when the output must match the application's displayed values. Common scenarios include feeding schedules into shop-floor or MES interfaces, reconciling daily rates against actual completions, and reporting line utilization by joining to WIP_LINES. Note the standard multi-org caveat: filter by ORG_ID derived from FND_GLOBAL to respect operating unit security.