Search Results update_requirement_header_pre

Overview

The APPS.CSP_REQUIREMENT_HEADERS_IUHK package body is an Internal Hook API (IUHK) belonging to the Oracle E-Business Suite ETRM (Enterprise Territory and Resource Management) / Service Parts module. Its sole architectural purpose is to expose vertical-industry customization points around the core DML operations performed on requirement headers. Rather than modifying Oracle-seeded logic, implementers register pre- and post-processing hooks that are executed automatically when the base package CSP_REQUIREMENT_HEADERS_PKG performs an Insert, Update, or Delete against a requirement header row.

The package is classified as OTHER in the ETRM 12.2.2 metadata and is owned by APPS. The embedded $Header comment (cspirqhb.pls 115.3 2002/11/26) confirms it is a legacy, stable wrapper whose structure has not materially changed across 12.1.1 and 12.2.2. Because the package contains no declarative tables of its own and simply delegates to the hook dispatcher, it is a thin, low-risk extension surface. It is referenced by one other package in the ETRM data model and is not intended for direct invocation by end users.

Key Procedures and Functions

Six documented procedures constitute the entire callable surface. Each accepts an OUT NOCOPY x_return_status parameter that propagates the hook's success or failure to the calling DML operation. None of the procedures declares business-data parameters; their role is purely to signal which lifecycle event is in progress.

• CREATE_REQUIREMENT_HEADER_PRE — Fires the "Before" hook for an insert against the requirement headers entity.
• CREATE_REQUIREMENT_HEADER_POST — Fires the "After" hook for an insert, allowing vertical logic to observe the newly created header.
• UPDATE_REQUIREMENT_HEADER_PRE — Fires the "Before" hook for an update, enabling validation or augmentation prior to the persisted change.
• UPDATE_REQUIREMENT_HEADER_POST — Fires the "After" hook for an update.
• DELETE_REQUIREMENT_HEADER_PRE — Fires the "Before" hook for a delete, supporting referential or business-rule checks.
• DELETE_REQUIREMENT_HEADER_POST — Fires the "After" hook for a delete.

Internally, every procedure calls csp_ship_to_address_pvt.call_internal_hook, passing the base package name (CSP_REQUIREMENT_HEADERS_PKG), the operation (INSERT_ROW, UPDATE_ROW, or DELETE_ROW), and a phase indicator of 'B' (before) or 'A' (after). This indirection means customization is not coded into the IUHK itself but into whatever procedure the dispatcher resolves; the IUHK merely standardizes the event vocabulary.

Tables Accessed

The provided ETRM metadata documents no direct table references for this package. Because it is a dispatcher-only hook wrapper, it does not issue SELECT, INSERT, UPDATE, or DELETE statements against any base table. All persistent access to the requirement header entity is performed by CSP_REQUIREMENT_HEADERS_PKG, which calls these hook points before and after its own DML. Any tables touched at runtime are therefore those referenced inside customer-supplied hook implementations, and they must be resolved through APPS synonyms.

Usage Notes

This package is never invoked manually by an end user. It is called indirectly by the core requirement header API whenever a row is created, changed, or removed, typically triggered from Service/Depot Repair forms, order-fulfillment flows, or concurrent programs that manipulate requirement headers.

• Customization should be registered through the supported internal-hook mechanism rather than by editing this package body; direct modification risks being overwritten by patching or AD utilities.
• Hook logic should be transactional and lightweight, since it executes synchronously within the caller's DML and a raised exception or a non-success x_return_status aborts the operation.
• Behavior is identical in 12.1.1 and 12.2.2; the file version indicates a long-stable interface.