Search Results add_req

Overview

WIP_REQUIREMENT_VALIDATIONS is an Oracle Work in Progress (WIP) validation package owned by the APPS schema. It provides the server-side validation engine that governs the addition, modification, and deletion of material requirements for discrete jobs and work orders. In Oracle EBS, a "requirement" represents an inventory item that must be consumed at a specific operation of a job. Because these requirements can be loaded or changed through multiple avenues — the WIP Material Transactions interface, the Job Details interface, the Job Schedule interface, and native WIP forms — the package centralizes the referential and business-rule checks needed before the data is committed.

Its API classification is OTHER, indicating that Oracle does not expose it as a formally published public API, though its procedures are callable and are referenced by one other package. The package is compiled with AUTHID CURRENT_USER, so privileges are evaluated against the calling user rather than the package owner.

Key Procedures and Functions

The thirteen documented units partition into three functional groups: deletion, addition, and change/miscellaneous.

• Delete path: DEL_REQ_INFO_EXIST verifies that required identifier information exists before a delete; REQ_JOB_MATCH confirms that the operation and resource combination matches an existing requirement. SAFE_DELETE is the guarded deletion routine that this metadata's "safe_delete" search term targets — it encapsulates the checks required to remove a requirement without orphaning dependent records. DELETE_REQ is the main delete driver that orchestrates the three preceding validations.
• Add path: ADD_REQ_INFO_EXIST checks that mandatory attributes are present for an add; REQ_JOB_NOT_EXIST ensures the operation/resource combination does not already exist, preventing duplicates; VALID_REQUIREMENT performs the add-specific validation; ADD_REQ executes the addition.
• Change and utility path: CHANGE_REQ handles requirement modification, CHNG_REQ_INFO_EXIST validates the data needed for change, POST_DEFAULT applies defaulted column values, and the helper functions IS_ERROR and INFO_MISSING report validation failures and missing information respectively.

Tables Accessed

The package reads and writes several core WIP and inventory tables through APPS synonyms. WIP_REQUIREMENT_OPERATIONS and WIP_OPERATIONS hold the requirement and operation rows under validation. WIP_DISCRETE_JOBS and WIP_ENTITIES identify the job context and its organization. WIP_JOB_DTLS_INTERFACE and WIP_JOB_SCHEDULE_INTERFACE are the inbound interface tables through which requirements arrive from external systems. On the inventory side, MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV supply item attributes, MTL_SECONDARY_INVENTORIES provides subinventory context, MTL_PARAMETERS holds organization-level settings, and BOM_SUBSTITUTE_COMPONENTS supports substitute-item logic. MTL_MATERIAL_TRANSACTIONS and MTL_MATERIAL_TRANSACTIONS_TEMP are consulted for transaction-level effects. PLITBLM is an Oracle Applications-supplied table used for storing PL/SQL error message text.

Usage Notes

This package is typically invoked indirectly from WIP forms (such as the Material Requirements window of the Discrete Jobs form) and from concurrent programs that process the WIP Job Details and Job Schedule interfaces. Custom code that inserts or deletes requirement rows should route through these procedures rather than manipulating WIP_REQUIREMENT_OPERATIONS directly, so that duplicate-prevention, substitute handling, and error reporting remain consistent. Because SAFE_DELETE is documented as "for delete only" and the add routines as "for add only," callers must select the correct entry point for the operation being performed. The presence of IS_ERROR and INFO_MISSING allows a calling program to interrogate the outcome of a validation before committing.