Search Results add_requirement

Overview

APPS.WIP_JOB_DTLS_SUBSTITUTIONS is a server-side PL/SQL package within the Oracle E-Business Suite Work in Process (WIP) module. It provides the programmatic interface for applying substitutions to the resource, requirement, and operation details of discrete jobs and repetitive schedules. Substitutions allow planners and shop-floor supervisors to replace or augment the standard resource and material structure of a job without altering the underlying routing or bill of material, and this package encapsulates the validation and data manipulation logic required to record those deviations against the job detail interface structures.

The package is classified as OTHER in the ETRM registry, meaning it is not a fully published open interface but is nevertheless invoked by other application components. It is referenced by two other packages, which confirms its role as a shared utility layer supporting broader WIP detail maintenance workflows. Every documented procedure in the package exposes the p_wip_entity_id parameter, the primary key of the WIP entity (job or schedule) being modified, which reflects its narrow scope: all operations are scoped to a single WIP entity within a single organization.

Key Procedures and Functions

The package exposes twenty-seven documented procedures and functions, organised into logical groups by the type of job detail element being substituted.

• Resource substitution procedures: DELETE_RESOURCE, ADD_RESOURCE, CHANGE_RESOURCE, DELETE_RESOURCE_INSTANCE, ADD_RESOURCE_INSTANCE, CHANGE_RESOURCE_INSTANCE, DELETE_SUB_RESOURCE, ADD_SUB_RESOURCE, and CHANGE_SUB_RESOURCE. These manage the addition, modification, and removal of resources, resource instances, and sub-resources assigned to a job operation.
• Requirement substitution procedures: DELETE_REQUIREMENT, ADD_REQUIREMENT, and CHANGE_REQUIREMENT. These maintain component and requirement substitutions tied to the job's operation sequence.
• Operation procedures: ADD_OPERATION, CHANGE_OPERATION, and VERIFY_OPERATION. These support inserting, updating, and validating operations on the job detail structure.
• Usage and helper routines: DELETE_RESOURCE_USAGE, SUBSTITUTION_RES_USAGES, SUB_USAGE, ADD_DEFAULT_USAGE, and NUM_OF_USAGE. These handle resource usage records, substitution usage derivation, default usage assignment, and counting of usage entries.

All substitution procedures share a common signature pattern comprising a group identifier (p_group_id), the WIP entity identifier (p_wip_entity_id), the organization identifier (p_organization_id), and two output parameters (p_err_code and p_err_msg) used to return status and error text to the caller.

Tables Accessed

The package reads and writes against tables accessed through APPS synonyms. Core WIP tables include WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_OPERATIONS, WIP_OPERATION_NETWORKS, WIP_OPERATION_RESOURCES, WIP_OPERATION_RESOURCE_USAGE, WIP_OP_RESOURCE_INSTANCES, WIP_REQUIREMENT_OPERATIONS, and WIP_SUB_OPERATION_RESOURCES, which store the job structure and substitution detail records. Interface staging tables WIP_JOB_DTLS_INTERFACE and WIP_JOB_SCHEDULE_INTERFACE support the loading and validation of job details prior to commit.

Setup and validation tables include MTL_PARAMETERS, MTL_SERIAL_NUMBERS, WIP_PARAMETERS, and DUAL, used for organization validation, serial number checks, parameter defaults, and single-row queries.

Usage Notes

WIP_JOB_DTLS_SUBSTITUTIONS is typically invoked from WIP maintenance forms, substitution entry screens, and concurrent programs that process job detail interface records, as well as from custom PL/SQL extensions requiring programmatic substitution of resources or requirements. Callers must supply a valid p_wip_entity_id and p_organization_id, and should always inspect p_err_code and p_err_msg before committing, since the package performs its own validation and will report failures through these output parameters rather than by raising exceptions.