Search Results po_requisition_lines_s




Overview
Explore in AI Chat

Overview

APPS.PO_REQUISITION_LINES_PKG2 is a valid PL/SQL package body in the Oracle E-Business Suite APPS schema. It belongs to the Oracle Purchasing (PO) module and supports the processing of requisition line records, which represent the individual items, services, and charges requested internally before they are sourced, approved, and converted into purchase orders or other downstream documents. The package is designated with an API classification of OTHER, indicating that it is a supporting or internal utility package rather than a published, fully documented public interface such as the requisition import APIs.

The package operates across Oracle EBS release 12.1.1 and 12.2.2. Its object name parallels the PO_REQUISITION_LINES table and the PO_REQUISITION_LINES_S sequence, and the metadata confirms it is not referenced by any other database object, reflecting its role as a top-level implementation unit invoked by forms, workflows, or dependent logic rather than as a reusable library consumed by other packages.

Key Procedures and Functions

ETRM documents a single procedure within this package body: INSERT_ROW. Consistent with the package's name and dependency footprint, INSERT_ROW is intended to create a new requisition line record within the Purchasing data model. Its responsibility is to accept the attribute values for a requisition line, perform any necessary defaulting or validation, and persist the row through the base requisition line tables and supporting constructs such as the attribute value tables and the primary key sequence.

No function signatures or parameter lists are enumerated in the available metadata; consequently, no parameter-level detail is asserted here. Any customization or extension should derive the exact call signature directly from the deployed package specification in the target environment rather than from documentation.

Tables Accessed

The dependency listing identifies the following objects referenced by the package:

  • PO_REQUISITION_LINES_ALL — the core requisition line base table, holding the primary line attributes for insert operations in a multi-organization environment.
  • PO_REQUISITION_LINES — the dependent requisition line table / operational view commonly used within Purchasing processing logic.
  • PO_REQUISITION_HEADERS_ALL — the requisition header base table, providing parent header context and validation for line creation.
  • PO_REQUISITION_LINES_S — the sequence supplying the primary key for new requisition line rows.
  • PO_ATTRIBUTE_VALUES, PO_ATTRIBUTE_VALUES_TLP, and PO_ATTRIBUTE_VALUES_PVT — the flexible attribute value structures used to store descriptive flexfield and additional attribute data associated with requisition lines.
  • APPS.PO_MESSAGE_S — the message sequence, and APPS.PO_REQ_LINES_SV — the requisition lines validation view, both referenced for messaging and validation purposes.
  • SYS.DUAL and SYS.STANDARD — standard Oracle constructs used for scalar evaluation and sequence retrieval.

This combination confirms that INSERT_ROW writes requisition line data to the base tables while also capturing associated attribute values and enforcing line-level validation.

Usage Notes

Because the package is not referenced by any other database object, it is not part of a broader internal dependency chain. It is most plausibly invoked from the Oracle Purchasing requisition forms, from workflow or OA Framework processing that creates requisition lines, or from custom PL/SQL extensions that need to insert a requisition line programmatically. The presence of PO_ATTRIBUTE_VALUES_PVT and PO_REQ_LINES_SV suggests the procedure coordinates attribute parsing and validation before the row is committed.

When used in custom code on 12.1.1 or 12.2.2, INSERT_ROW should be treated as a low-level helper rather than a supported public API. Oracle's documented public interfaces for requisition creation remain the Requisition Import and related open interfaces; direct calls to this package risk dependence on undocumented behavior. Developers should rely on the deployed package specification for exact parameters, ensure the requisition header and line sequence values are correctly derived, and validate that attribute value rows are populated consistently with the base line record in accordance with the standard eTRM metadata.