Search Results change_serial




Overview
Explore in AI Chat

Overview

WIP_SERIAL_ASSOC_VALIDATIONS is an Oracle Applications (APPS) PL/SQL package that belongs to the Work in Process (WIP) module of Oracle E-Business Suite. The package is compiled with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking schema rather than the defining schema. Its header revision (115.1, dated 2002/11/26) indicates that the package is a long-standing, stable component of the WIP serial number infrastructure.

The business function of this package is to validate serial number associations against work in process entities. In discrete manufacturing, serial-controlled assemblies and components must be associated with, substituted on, or removed from a work order in a controlled manner. The procedures in this package encapsulate the validation logic that governs these operations before the underlying serial records are created, modified, or removed. In the ETRM classification scheme the package is registered under the generic API category "OTHER", reflecting that it is an internal validation utility rather than a published business API.

Key Procedures and Functions

The package exposes three documented procedures, all of which share an identical parameter signature: a group identifier, a WIP entity identifier, an organization identifier, and a substitution type indicator. The consistent signature allows callers to invoke any of the three operations in a uniform fashion, typically after the group of serial numbers has been staged in the interface tables.

  • CHANGE_SERIAL — Validates a request to change an existing serial number association for a WIP entity. This supports serial substitution scenarios in which one serialized unit replaces another on the same work order, and the substitution type distinguishes the nature of the replacement.
  • ADD_SERIAL — Validates a request to add a serial number association to a WIP entity. This is invoked when serialized components or assemblies are being attached to a discrete job, and the validation ensures the serial is eligible for association given the organization and job context.
  • DELETE_SERIAL — Validates a request to remove a serial number association from a WIP entity. This is the procedure most closely associated with the "delete_serial" search term; it confirms that the referenced serial may legally be disassociated from the specified WIP entity before the deletion proceeds.

No parameter lists are reproduced here because the documented signatures are positional and internal; parameter names should be confirmed against the package specification in the target instance.

Tables Accessed

Although the package header itself contains no table references, the ETRM metadata records the following tables as being accessed through APPS synonyms:

  • MTL_SERIAL_NUMBERS — The master serial number table; the procedures read serial attribute and status information to determine whether the requested change, addition, or deletion is permissible.
  • WIP_ENTITIES — Provides the WIP entity (job or schedule) definition against which the serial association is being validated.
  • WIP_DISCRETE_JOBS — Supplies discrete job attributes used to qualify the validation for discrete manufacturing environments.
  • WIP_JOB_DTLS_INTERFACE and WIP_JOB_SCHEDULE_INTERFACE — Interface tables through which job and schedule detail changes, including serial substitutions, are staged before processing.

Usage Notes

WIP_SERIAL_ASSOC_VALIDATIONS is an internal validation package. It is referenced by one other package within the EBS code base, and it is not intended for direct invocation by end users. In practice it is called from the WIP serial number entry and maintenance forms, from concurrent programs that process the WIP job detail and job schedule interfaces, and from other WIP packages that orchestrate serial substitution processing.

Custom code should not call these procedures directly unless the caller fully replicates the preconditions expected by the internal caller, including the population and locking of the group identifier. Because the package compiles with AUTHID CURRENT_USER, custom invocations may also require that the executing schema hold the necessary object privileges on the referenced MTL and WIP tables. For any release-specific behavior, the package body in the 12.1.1 or 12.2.2 instance should be reviewed, as only the specification and table-level metadata are documented here.