Search Results change_sub_resource

Overview

APPS.WIP_RESOURCE_VALIDATIONS is a server-side PL/SQL validation package within the Oracle E-Business Suite Work in Process (WIP) module. Its business function is to enforce data integrity and business rules whenever resources or resource substitutions are added to, changed on, or removed from a discrete work order (job) through the WIP job maintenance interfaces. The package centralizes the validation logic that precedes the physical insert, update, or delete of rows in the WIP operation resource tables, ensuring that operations and resources are consistent with the job's routing, that referenced resources exist for the department, and that no downstream transactional data (cost, outside processing purchase orders, or open interfaces) will be corrupted by the change.

For the queried term delete_sub_resource, the package exposes DELETE_SUB_RESOURCE as one of its documented procedures. It works in tandem with ADD_SUB_RESOURCE, CHECK_RES_SUBSTITUTION, and SUBSTITUTE_INFO to manage resource substitutions on a work order, validating that a substitute resource is legitimate and that the original resource may be removed safely.

Key Procedures and Functions

The 22 documented program units are grouped by the operation they support:

• DEL_RES_INFO_EXIST — Verifies that the resource information required to delete a resource (job, operation sequence, and old resource identifiers) is present and non-null before deletion proceeds.
• RES_JOB_MATCH — Confirms that the job, operation, resource sequence, and old resource identifier match and exist, invoked when deleting a resource.
• SAFE_DELETE — Checks WIP cost transaction interface and WIP transaction (WCTI/WT) records for the job/operation/resource combination to determine whether deletion is safe.
• SAFE_PO — Performs outside-processing validation by inspecting purchasing data before a resource is removed.
• DELETE_RESOURCE — The main driver procedure that orchestrates the four validation routines above for a resource deletion.
• ADD_RES_INFO_EXIST — Validates that the resource information supplied when adding a resource is present.
• VALID_RESOURCE — Verifies that the resource being added is valid for the job and organization.
• RESOURCE_SEQ_NUM — Validates the resource sequence number for the added resource.
• USAGE_RATE_OR_AMOUNT — Confirms that the usage rate or amount is supplied and valid.
• ASSIGNED_UNITS and VALIDATE_ASSIGNED_UNITS — Validate the assigned units against usage rate and quantity.
• ADD_RESOURCE — The main driver for adding a resource after all validations pass.
• CHANGE_RESOURCE and CHNG_RES_INFO_EXIST — Validate and apply changes to an existing operation resource.
• CHECK_RES_SUBSTITUTION — Determines whether a resource may be substituted on the job.
• IS_ERROR, INFO_MISSING — Utility routines reporting error state and missing mandatory information.
• SUBSTITUTE_INFO, ADD_SUB_RESOURCE, DELETE_SUB_RESOURCE — Manage substitution information, adding and deleting substitute resources on an operation.

Tables Accessed

The package reads and writes through APPS synonyms covering WIP, BOM, and Purchasing schemas. BOM_DEPARTMENT_RESOURCES and BOM_RESOURCES supply valid resource definitions for the department and organization. WIP_OPERATIONS, WIP_OPERATION_RESOURCES, and WIP_OP_RESOURCE_INSTANCES are the primary job detail and resource instance tables being validated against and modified. The WIP_COST_TXN_INTERFACE, WIP_JOB_DTLS_INTERFACE, and WIP_JOB_SCHEDULE_INTERFACE tables are inspected to detect pending interface activity that would make a change unsafe. Purchasing tables — PO_DISTRIBUTIONS_ALL, PO_HEADERS_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, PO_REQUISITIONS_INTERFACE_ALL, and PO_REQUISITION_LINES_ALL — support the SAFE_PO outside-processing check. WIP_PARAMETERS supplies module-level settings and defaults.

Usage Notes

WIP_RESOURCE_VALIDATIONS is not intended for direct end-user invocation. It is typically called by the WIP job/schedule maintenance forms and such concurrent or batch processes as the job schedule and detail interfaces, which rely on its error-flagging routines (IS_ERROR, INFO_MISSING) to surface validation failures. It is referenced by one other package, indicating a narrow, focused consumer profile. Custom code that programmatically adds, changes, or deletes operation resources on a work order should invoke the appropriate driver procedure (ADD_RESOURCE, CHANGE_RESOURCE, DELETE_RESOURCE, ADD_SUB_RESOURCE, DELETE_SUB_RESOURCE) rather than performing direct DML, so that the associated routing, substitution, cost-interface, and purchasing safeguards are applied. The package is defined with AUTHID CURRENT_USER, so privileges and synonym resolution follow the invoking schema.