Search Results get_line_id

Overview

WIP_REPETITIVE_UTILITIES is an Oracle Work in Process (WIP) utility package owned by APPS and classified as OTHER in the ETRM repository for EBS 12.1.1 and 12.2.2. It provides the underlying programmatic machinery for managing repetitive manufacturing schedules: splitting a released schedule into two consecutive schedules, rolling a closed or completed schedule forward to the next defined schedule for a production line/assembly association, and resolving the identity of the first and last schedule associated with a production line. The package is declared with AUTHID CURRENT_USER, meaning its unqualified references resolve against the invoker's schema and privileges rather than the definer's, which is significant because the referenced tables are reached through APPS synonyms.

The header comment identifies the script as wipreuts.pls, version 115.8, last shipped 2002/11/29. The package therefore predates the 12.x multi-org and OAF changes and remains largely stable across the 12.1.1 and 12.2.2 releases. It exposes five documented procedures and functions: SPLIT_SCHEDULE, ROLL_FORWARD, ROLL_FORWARD_COVER, GET_FIRST_LAST_SCHED, and GET_LINE_ID. The package is referenced by two other packages, indicating it is a shared utility layer consumed by higher-level WIP logic rather than an end-user-facing API.

Key Procedures and Functions

• SPLIT_SCHEDULE — Splits a single repetitive schedule into two consecutive schedules. The caller supplies the schedule to be split and the organization, and receives the identifier of the newly created schedule as an IN OUT parameter. The header comment states the assumption that the schedule being split is already released, so callers must not invoke it against unreleased schedules.
• ROLL_FORWARD — Releases the next schedule defined for a production line/assembly association, if one exists. The caller passes the closing schedule, an IN OUT parameter for the rolled-forward schedule, the roll-forward type, the organization, and a Boolean controlling whether status is updated. When the update flag is TRUE, the closed schedule's status is set to Complete-No Charges if a successor schedule exists, or Complete-Charges if none is defined. The roll-forward type draws on WIP_CONSTANTS values including ROLL_COMPLETE, ROLL_CANCEL, and ROLL_EC_IMP.
• ROLL_FORWARD_COVER — A companion variant of the roll-forward operation that performs the cover-specific handling of the closed and rolled-forward schedules using the same schedule, roll-forward type, and organization inputs, without the status-update Boolean.
• GET_FIRST_LAST_SCHED — Resolves the first and last schedules associated with a production line, allowing callers to establish the chronological boundaries of a repetitive schedule chain.
• GET_LINE_ID — Returns the production line identifier. This is the function most commonly targeted by searches, since custom code, forms personalizations, and interfaces frequently need to translate between a line name or schedule and the internal line ID used by WIP_REPETITIVE_SCHEDULES.

Tables Accessed

The package reads and writes the core repetitive manufacturing tables through APPS synonyms. WIP_REPETITIVE_SCHEDULES and its _S sequence-backed counterpart hold the schedule rows that SPLIT_SCHEDULE, ROLL_FORWARD, ROLL_FORWARD_COVER, and GET_FIRST_LAST_SCHED operate against. WIP_REPETITIVE_ITEMS supplies the production line/assembly association that determines which schedule is eligible for roll forward. WIP_OPERATIONS, WIP_OPERATION_RESOURCES, and WIP_REQUIREMENT_OPERATIONS provide the routing, resource, and requirement detail that must be carried or validated when schedules are split and rolled. WIP_PARAMETERS and MTL_PARAMETERS supply organization-level WIP and inventory defaults. BOM_CALENDAR_DATES provides the manufacturing calendar used to date schedules. FND_ATTACHED_DOCUMENTS supports any document attachments associated with the schedule records. DUAL is used for singleton evaluations and sequence or date lookups.

Usage Notes

WIP_REPETITIVE_UTILITIES is not intended for direct end-user invocation. It is called by the standard WIP schedule maintenance forms and concurrent programs, and by the two dependent packages documented in the repository. Customizations and extensions that need to split or roll forward repetitive schedules, or that simply need to resolve a production line ID from a line or schedule, typically call these procedures directly from custom PL/SQL. Because the package is AUTHID CURRENT_USER, custom callers should be granted execute on the package and select privileges on the underlying WIP and INV tables, and they must supply a valid organization identifier on every call so that multi-org views resolve correctly. The ROLL_FORWARD status-update flag should be set carefully: passing TRUE changes the closed schedule's status to Complete-No Charges or Complete-Charges, which is a committed business action and should not be used in exploratory or read-only code paths. The package header is version 115.8, so line identifiers and schedule statuses should be validated against the current 12.2.2 WIP_CONSTANTS definitions before reuse in new development.