Search Results substitution_res_usages

Overview

WIP_RES_USAGE_SUBSTITUTIONS is an Oracle Work in Process (WIP) PL/SQL package that supports resource usage substitution during shop floor execution. Its central purpose is to allow a resource assigned to a discrete job or work order to be replaced by an alternative resource, and to record the corresponding resource usage against the correct manufacturing entity and organization. This capability is essential when a planned resource becomes unavailable — for example, a machine is down or a qualified operator is absent — and production must proceed using a substitute resource without rebuilding the routing or re-planning the job.

The package is defined with AUTHID CURRENT_USER, meaning its procedures execute under the privileges of the calling session rather than the package owner. The package specification header (wiprusts.pls, version 115.6) dates from the 11i era and remains current through Oracle EBS 12.1.1 and 12.2.2. Its API classification in the ETRM is OTHER, indicating it is an internal, non-public API intended for controlled invocation rather than general customer extension.

Key Procedures and Functions

The ETRM documents two public procedures in the package specification:

• SUBSTITUTION_RES_USAGES — The primary driver procedure. It performs resource usage substitution for a group of resource usages associated with a given work order group. It coordinates the substitution logic across the affected usage records for a WIP entity within a specific organization.
• SUB_USAGE — The lower-level worker procedure that processes an individual resource usage substitution at the granularity of a single operation and resource sequence. It identifies the usage to substitute and applies the change for the specified operation sequence number and resource sequence number.

Both procedures communicate outcomes through standard EBS concurrent-style OUT parameters: an error code, an error message, and a return status. The return status follows the conventional WIP/FND success-indicator pattern, allowing callers to branch on success or error. The actual parameter signatures are not reproduced here; consumers must reference the package specification for the accepted argument list. No functions are documented; both entries are procedures.

Tables Accessed

Per the ETRM metadata, the package references the following tables through APPS synonyms:

• WIP_JOB_DTLS_INTERFACE — The WIP job detail interface table. It is used to store and stage job-level detail changes produced by the substitution, enabling the affected transaction to be processed further or interfaced into the WIP execution flow. Writing substitution results here supports downstream job detail maintenance and reporting.
• WIP_OPERATION_RESOURCE_USAGE — The operation resource usage table. This holds the actual resource usage rows recorded against operations and resources on a job. The package reads and updates these rows to reflect the substitution of one resource for another at the operation/resource sequence level.

Together these tables give the package access to both the interface layer and the live usage layer, which is consistent with its role of translating a substitution request into updated resource usage records.

Usage Notes

WIP_RES_USAGE_SUBSTITUTIONS is an internal API and is not referenced by any other documented package (0 dependents in the ETRM). It is typically invoked indirectly from Oracle Work in Process forms or shop floor flows during resource charge and resource substitution processing, rather than being called directly by customers. Custom code should not rely on the package signature, because the API classification is OTHER and the specification may change without the compatibility guarantees that Oracle attaches to published public APIs such as the WIP_MANAGEMENT or WIP_MOVE packages. When extending or troubleshooting substitution behavior, developers should prefer public WIP APIs and treat this package as implementation detail invoked through standard application flows. As with any call to an AUTHID CURRENT_USER package, the executing user must hold the appropriate WIP and inventory privileges, and callers must handle the x_err_code, x_err_msg, and x_return_status outputs to detect failure conditions reliably.