Search Results create_requirement_headers




Overview
Explore in AI Chat

Overview

CSP_CREATE_PARTS_REQ_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under ETRM as an "OTHER" API object. It belongs to the Service (CSP) product family and provides programmatic creation of spare-parts requirement records within the Oracle EBS service supply chain. Spare-parts requirements represent demand for service parts associated with field service tasks, depot repair orders, or other service-driven activities, and they flow downstream into replenishment, procurement, and order-management processes.

The package was last modified in the 12.2.x code line (header revision 120.0.12020000.5, dated 21-Mar-2013) and is declared with AUTHID CURRENT_USER, meaning executing procedures resolve unqualified object references under the privileges of the calling schema rather than the package owner. The package exposes two documented entry points — create_requirement_headers and create_requirement_lines — that together support the header-then-line creation pattern typical of Oracle EBS public APIs.

Key Procedures and Functions

  • CREATE_REQUIREMENT_HEADERS — The procedure the user searched for. This function creates a service parts requirement header record and returns a REF CURSOR (typed as reqmt_hdr_cur) to the caller. It accepts a broad set of header-level attributes covering requirement classification, ship-to location, task and task-assignment context, shipping method, need-by date, destination organization, descriptive flexfield attributes (attribute1 through attribute15 plus attribute_category), order type, address type, resource and resource type, timezone, destination subinventory, and standard audit columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login). Because it returns a cursor rather than an out parameter for the new identifier, callers typically fetch the generated requirement header ID from the returned result set before invoking the line-level API.
  • CREATE_REQUIREMENT_LINES — Creates the detail lines that belong to a requirement header. The parameter list confirms that each line carries its own requirement_line_id, a foreign-key reference (requirement_header_id) back to the header, inventory item and UOM information, required quantity, ship-complete flag, likelihood percentage, and revision. Audit columns are again passed explicitly rather than defaulted, which is consistent with Oracle's public API conventions and allows the caller to preserve source-system values. The parameter list also references a source organization, supporting the sourcing context of the requirement line.

Tables Accessed

The ETRM metadata documents only DUAL as a referenced table via APPS synonyms, which reflects that the package body performs its data manipulation through other public packages and synonyms not enumerated in the excerpt — most notably the requirement-lines public package referenced by the reqmt_lines_tbl variable declaration (csp_requirement_lines_pub.rql_tbl_type). In practice, the API persists data into the CSP requirement header and line tables that back the service requirements data model, while DUAL is used for single-row cursor constructs and lightweight validation queries. The absence of a large explicit table list in the metadata indicates that the package is a thin orchestration layer around the underlying service requirements public APIs rather than a direct DML package.

Usage Notes

CSP_CREATE_PARTS_REQ_PKG is typically invoked from custom PL/SQL or from service-related concurrent programs and forms that must generate spare-parts demand outside the standard Service user interface. The standard invocation sequence is to call create_requirement_headers first, obtain the requirement header ID from the returned REF CURSOR, and then call create_requirement_lines once per detail line, passing that header ID. Because the API classification is "OTHER" rather than a formally supported public API, and because ETRM reports zero packages referencing it, the package should be treated as internal to the Service application. Customizations should confirm compatibility across the target patch level — behavior can differ between 12.1.1 and 12.2.2 — and should avoid relying on undocumented internals of the package spec. All calls should be committed explicitly by the caller, and audit parameters should be populated consistently with the application's conventions to preserve data integrity.