Search Results wip_interface_s




Overview
Explore in AI Chat

Overview

WIP_SCHEDULING is a PL/SQL package body owned by the APPS schema that supports Oracle Work in Process (WIP) scheduling operations within Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to load scheduling information from the WIP scheduling interface into the discrete job tables, validate that scheduling data against the current state of production records, and propagate scheduling date changes across jobs, operations, and resource requirements. The package mediates between the open scheduling interface tables (WIP_SCHEDULING_INTERFACE and WIP_JOB_SCHEDULE_INTERFACE) and the core WIP execution tables, ensuring that scheduling inputs are validated before they affect live shop-floor data.

The package is classified as an OTHER API, indicating it is not a public, supported extension API but rather an internal utility invoked by WIP concurrent processes, forms, and dependent package logic. It is not referenced by any other database object, confirming its role as a top-level driver rather than a shared library. The object is VALID under ETRM documentation and depends on FND_GLOBAL, WIP_CONSTANTS, WIP_MASS_LOAD_UTILITIES, and WIP_SCHEDULING_INTERFACE in addition to the WIP base tables.

Key Procedures and Functions

The package exposes eleven documented procedures and functions that cover loading, validation, and date propagation:

  • LOAD_INTERFACE — Loads scheduling records from the interface tables for processing prior to validation and application.
  • LOAD_WIP — Loads the validated interface data into the WIP discrete job and related scheduling structures.
  • LOAD_WIP_CONCURRENT — Concurrent-program entry point that orchestrates the load cycle when invoked from the WIP scheduling manager.
  • VALIDATE_JOBS — Validates that discrete jobs referenced in the interface are eligible for scheduling updates.
  • VALIDATE_SCHEDULING_LEVEL — Checks the scheduling level attribute on input records for correctness.
  • VALIDATE_DATES — Verifies date fields on scheduling records for validity and consistency.
  • VALIDATE_USAGE_RATE — Validates usage rate values associated with operations and resources.
  • VALIDATE_OPS_RES_MATCH — Ensures that operation and resource combinations in the interface correspond to valid production definitions.
  • ERROR_ALL_IF_ANY — Implements group-level error handling, marking all rows in a logical batch as failed if any row is invalid.
  • UPDATE_REQ_DATES — Updates requirement (component) dates to align with revised job scheduling dates.
  • UPDATE_JOB_DATES — Applies revised scheduling dates to the discrete job and its operations.

Tables Accessed

WIP_SCHEDULING reads from and writes to the following tables via APPS synonyms:

  • WIP_INTERFACE_S — Holds discrete job interface rows that feed scheduling operations.
  • WIP_JOB_SCHEDULE_INTERFACE and WIP_SCHEDULING_INTERFACE — Staging tables for incoming scheduling data.
  • WIP_DISCRETE_JOBS — The target table for validated scheduling updates to jobs.
  • WIP_OPERATIONS — Updated when job dates shift so operation sequences remain aligned.
  • WIP_OPERATION_RESOURCES — Receives usage rate and resource-related validation and updates.
  • WIP_REQUIREMENT_OPERATIONS — Sources and receives requirement date updates through UPDATE_REQ_DATES.

Usage Notes

WIP_SCHEDULING is typically invoked through the WIP scheduling concurrent program (via LOAD_WIP_CONCURRENT), which loads, validates, and applies interface rows in a controlled batch. It may also be called from WIP forms when scheduling attributes are changed interactively, and from custom code that submits scheduling interface records programmatically. Because the package is not a supported extension API, customizations should call the documented WIP public APIs where available, or invoke the concurrent program rather than calling internal procedures directly. Error rows are flagged in the interface and reported by the standard concurrent program output.