Search Results update_requirement_headers

Overview

CSP_REQUIREMENT_HEADERS_PUB is the public application programming interface for Oracle's Service Procurement (CSP) requirement headers in Oracle E-Business Suite 12.1.1 and 12.2.2. The package encapsulates the business logic required to create, maintain, and remove service requirement header records housed in the CSP_REQUIREMENT_HEADERS table. Requirement headers represent the top-level demand entities used in the procure-to-order and service procurement flows, capturing details such as task references, resource assignments, ship-to locations, need-by dates, and destination organizations.

The package declares its cursor with the AUTHID CURRENT_USER clause and includes a standard RQH_Rec_Type record definition that mirrors the columns of the underlying requirement header table. This record uses FND_API.G_MISS_* sentinel defaults so callers can supply sparse payloads that the API interprets as "no change" during updates or "derive from defaults" during inserts. A G_DEFAULT_NUM_REC_FETCH constant of 30 governs the rows fetched per call in any bulk retrieval logic.

Key Procedures and Functions

The documented public interface exposes three procedures:

• CREATE_REQUIREMENT_HEADERS — Inserts new requirement header records. This entry point accepts the header payload and creates the corresponding rows, populating the audit and descriptive attributes defined by RQH_Rec_Type.
• UPDATE_REQUIREMENT_HEADERS — Modifies existing requirement headers. Attributes left at their FND_API.G_MISS_* defaults are not written, allowing partial updates.
• DELETE_REQUIREMENT_HEADERS — Removes requirement headers. This is the procedure commonly referenced when users search for "delete_requirement_headers." It is the supported, API-driven mechanism for deleting requirement header rows, ensuring any dependent lines and object usages are handled consistently.

The procedures follow the standard Oracle public API pattern of taking a record or scalar identifier plus a return status, returning success or error via FND_API-style conventions so callers can inspect messages on failure.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• CSP_REQUIREMENT_LINES — Child lines associated with a requirement header; maintained in coordination with header operations, especially deletion.
• JTF_OBJECT_USAGES — Tracks object usage relationships tied to the requirement.
• JTF_RS_RESOURCE_EXTNS — Resource extension attributes used when resolving resource assignments.
• JTF_TASKS_B and JTF_TASK_ASSIGNMENTS — Task and task assignment records linked to requirement headers via TASK_ID and TASK_ASSIGNMENT_ID.
• MTL_PARAMETERS and MTL_SECONDARY_INVENTORIES — Inventory organization parameters and subinventory data used for destination and shipping validation.
• PLITBLM — Standard EBS PL/SQL table used for message and error handling.

Usage Notes

CSP_REQUIREMENT_HEADERS_PUB is invoked primarily from Oracle Service Procurement forms and related concurrent or PL/SQL callers that manage requirement headers, rather than being called directly by end users. The metadata indicates the package is referenced by one other package.

When called from custom code, developers should pass records initialized with FND_API.G_MISS_* values and always check the API return status. For deletion specifically, DELETE_REQUIREMENT_HEADERS should be used instead of direct DML on CSP_REQUIREMENT_HEADERS, because it enforces the business rules and cascading logic for associated lines, tasks, and object usage records.