Search Results add_resource_instance

Overview

WIP_RES_INST_VALIDATIONS is an APPS-owned PL/SQL package in Oracle E-Business Suite that supports the Work in Process (WIP) resource instance validation layer. Its role is to validate resource instance data — additions, changes, and deletions — associated with work orders, flows, and shop-floor transactions. Resource instances represent the actual resources (employees, equipment, or production resources) consumed or applied against an operation on a discrete job, repetitive schedule, or flow schedule. Because resource instance records must satisfy numerous integrity constraints before they are persisted, this package provides a centralized validation API rather than scattering checks across forms, interfaces, and concurrent programs.

The package header shown in the ETRM documentation carries a Header identifier of wiprivds.pls (120.0, dated 2005/05/25), indicating it is a long-standing component of the WIP module that persisted largely unchanged into the 12.1.1 and 12.2.2 releases. Consistent with the general pattern of validation-only packages in EBS, WIP_RES_INST_VALIDATIONS performs checks and returns diagnostic information; the actual DML is typically executed by the calling application or a paired DML package.

Key Procedures and Functions

• IS_ERROR — A function that determines whether errors have already been recorded during preceding validations for a given validation group. The documentation notes it does not pass additional resource parameters because the check is unique up to the resource sequence number. This is used to short-circuit subsequent validation logic when a prior step has already failed.
• INFO_MISSING — A function declared in the original header but commented out in the documented source. It was intended to detect cases where required data is NULL. Since it is not active in the shipped package, callers should not invoke it.
• ADD_RESOURCE_INSTANCE — A procedure that validates a request to add a new resource instance to a work order or schedule. It returns an error code and error message via OUT NOCOPY parameters when validation fails.
• CHANGE_RESOURCE_INSTANCE — A procedure that validates a modification to an existing resource instance, including substitution changes. As with the other procedures, results are returned through the error code and message outputs.
• DELETE_RESOURCE_INSTANCE — A procedure that validates the removal of a resource instance. This is the procedure surfaced by the user search term "delete_resource_instance". It does not itself delete the record; it verifies that deletion is permissible and reports any blocking conditions.

All three DML-validation procedures share a common signature shape: group ID, WIP entity ID, organization ID, and substitution type as inputs, with error code and error message as outputs. The shared inputs allow the package to identify the resource instance context consistently across add, change, and delete operations.

Tables Accessed

• BOM_DEP_RES_INSTANCES, BOM_DEPARTMENT_RESOURCES, BOM_RESOURCES — Department resource, resource, and resource instance definitions that provide the master data against which instance records are validated.
• BOM_RESOURCE_EMPLOYEES, BOM_RESOURCE_EQUIPMENTS — Employee and equipment resource type associations, ensuring the resource instance can be tied to a valid resource entity.
• WIP_OPERATION_RESOURCES, WIP_OP_RESOURCE_INSTANCES — Work-in-process operation resource and instance records that the validation procedures inspect for the target job or schedule.
• WIP_OPERATIONS — Operation definitions that anchor resource instances to a valid operation sequence.
• MTL_SYSTEM_ITEMS_KFV — The key flexfield view used to resolve and validate item references tied to the resource instance.
• WIP_JOB_DTLS_INTERFACE, WIP_JOB_SCHEDULE_INTERFACE — Open interface tables, suggesting the package also validates resource instance data arriving through job and schedule interface loads.

Usage Notes

WIP_RES_INST_VALIDATIONS is an internal validation package rather than a user-facing API. It is invoked by WIP forms and by one other package noted in the metadata. Typical callers include the Work Order and shop-floor resource forms during resource assignment or removal, and interface processing logic when job or schedule interface records are validated prior to import. Custom extensions that manipulate WIP resource instances directly should route their validations through these procedures before performing DML, using the returned error code and message to surface problems to the user or log them in a concurrent request. Because it is undocumented in the public API sense and classified as OTHER, it should be treated as a supporting validation utility and used with care across upgrades.