Results for “wip_movproc_pub”

37 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WIP_MOVPROC_PUB is the public application programming interface (API) package body in the APPS schema responsible for processing move transactions within Oracle Work in Process. Move transactions represent the movement of assemblies and components between operations and departments on a discrete work order or repetitive schedule, and they drive the operational routing progress as well as the associated material and resource transaction accounting. As a published (PUB) API, WIP_MOVPROC_PUB exposes a supported entry point through which external callers—other Oracle E-Business Suite modules, bolt-on extensions, and third-party integrations—can submit and process move transaction data without directly manipulating the underlying interface and error tables.

The package functions as the outer orchestration layer for move processing. It sits above WIP_MOVPROC_PRIV, which contains the private implementation logic, and it relies on the FND_API framework for standard API return status handling, FND_MESSAGE for user-facing message retrieval, and FND_LOG together with WIP_LOGGER for instrumentation and diagnostics. This layered design is characteristic of Oracle's public/private API pattern, allowing the package to enforce validation, logging, and error capture while delegating core transaction logic to protected units. Its documented status is VALID in the APPS schema.

Key Procedures and Functions

The ETRM metadata documents a single public procedure for this package body:

  • PROCESSINTERFACE — The principal public entry point of the package. It processes move transaction records submitted through the move transaction interface, reading the staged rows, applying validation and business logic, and writing results or errors back to the interface and error tables. It is designed to be called programmatically rather than interactively, and it returns standard API status information to the caller.

Detailed parameter lists are not reproduced here. Callers should reference the package specification in the target release for the exact signature, as argument lists may differ between 12.1.1 and 12.2.2. The remaining move-processing routines are contained within WIP_MOVPROC_PUB's private counterpart, WIP_MOVPROC_PRIV, and are not part of the documented public surface.

Tables Accessed

Two tables are documented as being referenced through APPS synonyms:

  • WIP_MOVE_TXN_INTERFACE — The staging table holding move transaction records awaiting processing. PROCESSINTERFACE reads pending rows from this table and applies the transaction logic to them.
  • WIP_TXN_INTERFACE_ERRORS — The error repository where validation failures and processing exceptions are recorded, allowing users to review, correct, and resubmit rejected transactions through the standard interface error handling flow.

Additional internal access is delegated to WIP_MOVPROC_PRIV and the WIP_CONSTANTS package, which supplies the predefined constant values used throughout move processing.

Usage Notes

WIP_MOVPROC_PUB is typically invoked in batch or programmatic contexts rather than from a user-facing form. Common invocation paths include concurrent programs that process the move transaction interface, custom PL/SQL routines performing bulk shop floor moves or system-to-system integration loads, and other Oracle applications requiring move transactions to be applied on behalf of a work order or schedule. Because WIP_MOVPROC_PUB is documented as not being referenced by any other database object, it is intended to be called directly by external code rather than consumed internally by other packaged APIs.

Callers should invoke the API through its public specification, honor the FND_API return status, and check WIP_TXN_INTERFACE_ERRORS for diagnostic detail when processing reports failures. Given the version differences between 12.1.1 and 12.2.2, the package specification for the specific installed release should always be consulted before coding against this API.