Search Results g_warning

Overview

APPS.EAM_WO_PROCESSOR is a PL/SQL package within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. Its documented purpose is to process work order scheduling activity for EAM work orders, which in the EBS data model are represented as discrete jobs in Work in Process (WIP). The package exposes a single documented entry point, the schedule procedure, which drives the scheduling of an EAM work order for a given WIP entity and organization.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the calling user rather than the package owner. This is consistent with many EBS public APIs, where the invoking session is expected to hold the appropriate APPS-level grants or responsibility context. The header revision note ($Header: EAMWOPRS.pls 115.4 2002/11/20) indicates the package has been stable since the 11i era and is carried forward into 12.1.1 and 12.2.2 without structural change. Three named constants — G_SUCCESS (0), G_WARNING (1), and G_ERROR (2) — define the standard return-code convention used by the routine.

Key Procedures and Functions

ETRM documents one procedure for this package:

• SCHEDULE — Schedules an EAM work order. It accepts the standard concurrent-program return parameters (errbuf and retcode) plus identifying context for the work order: the WIP entity identifier, the status type, a group identifier, and the operating unit or organization identifier. The parameters are conventionally passed by name. On completion, retcode carries one of the package constants: G_SUCCESS, G_WARNING, or G_ERROR, with any diagnostic text returned through errbuf. No functions are documented, and no other procedures are exposed in the package specification.

Tables Accessed

The package operates across three documented tables, accessed through APPS synonyms:

• WIP_DISCRETE_JOBS — the base table holding the discrete job record that represents the EAM work order. The package reads and updates scheduling attributes on this row, including the status and scheduling dates that result from the schedule action.
• WIP_JOB_SCHEDULE_INTERFACE — the WIP scheduling interface table. Rows written here are consumed by the standard WIP scheduling concurrent process, which performs the actual date computation and resource scheduling for the job. The EAM package uses this interface rather than scheduling the job directly, ensuring that EAM work orders follow the same scheduling logic as manufacturing discrete jobs.
• PLITBLM — a generic PL/SQL index-by table used by EBS for bulk operations and multi-row processing. Its presence indicates the package uses array-based (bulk) DML in at least part of its internal logic.

Usage Notes

EAM_WO_PROCESSOR is an internal processing package rather than a fully public, documented API. It is typically invoked in one of three ways: from EAM work order forms when a user initiates a scheduling action; from a concurrent program that wraps the schedule procedure, using errbuf and retcode in the standard fashion; or from custom PL/SQL that requires programmatic scheduling of an EAM work order. Because the package is not referenced by any other documented package, callers must be explicitly coded against it.

Several cautions apply. The AUTHID CURRENT_USER declaration means the caller must have the necessary object privileges; failures can manifest as privilege errors rather than package errors. The procedure commits no explicit transaction control of its own in the documented interface, so the calling program should manage commit scope. Scheduling is asynchronous in effect: the interface rows written to WIP_JOB_SCHEDULE_INTERFACE must be processed by the WIP scheduling program before WIP_DISCRETE_JOBS reflects the final dates. Finally, the package has not changed materially since 2002, so behavior is identical across 12.1.1 and 12.2.2.