Search Results itemsearch_buttons




Overview
Explore in AI Chat

Overview

ICX_REQ_SEARCH is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite release 12.1.1 and 12.2.2. It is classified under the ETRM API classification OTHER, reflecting that it is an internal, form-supporting package rather than a published, externally callable business API. Its functional domain is the iProcurement / Internet Procurement self-service requisitioning flow, where it implements the item search and selection experience used by requesters when building shopping carts.

In practical terms, the package generates the HTML-driven item search pages that allow a user to locate catalog items by attribute, review matching results, view item detail, and move selected items into the shopping cart for subsequent submission as a requisition. It is a presentation-layer package that combines dynamic SQL, Oracle Application Framework-style HTML generation (via HTP/HTF), and shopping cart persistence logic. Because it operates directly against requisition interface tables and cart tables, it sits between the user interface and the underlying procurement data model.

Key Procedures and Functions

The ETRM metadata documents five entry points:

  • ITEMSEARCH — The primary search routine. It accepts user-specified search criteria, resolves the relevant attribute definitions, and returns the set of matching catalog items. It is the core driver of the search results page.
  • ITEMSEARCH_DISPLAY — Renders the HTML presentation of item search results. It consumes the output of ITEMSEARCH and formats each row for display, including item description, attributes, and selection controls.
  • ITEMSEARCH_BUTTONS — Generates the action buttons and navigation controls associated with the item search page, such as search, reset, add-to-cart, and return actions.
  • DISPLAYITEM — Produces the item detail view for a single selected item, showing the full attribute set and related purchasing information before the user confirms selection.
  • SUBMIT_ITEMS — Persists the user's item selections into the shopping cart structures, creating or updating cart lines that will later be converted into requisition lines.

No parameter signatures are documented in the ETRM record; parameter lists should not be assumed and must be verified against the deployed package source in the target environment.

Tables Accessed

The package references the following tables through APPS synonyms:

  • AK_ATTRIBUTES, AK_OBJECT_ATTRIBUTES, AK_REGIONS — Oracle Application Framework / AK attribute metadata that drives the dynamic display of searchable item attributes.
  • AK_EXCLUDED_ITEMS — Identifies items excluded from the searchable catalog, used to filter results.
  • ICX_PARAMETERS — iProcurement system-level and session parameters controlling search behavior and display options.
  • ICX_SHOPPING_CARTS and ICX_SHOPPING_CART_LINES — The requisition shopping cart header and line tables, written by SUBMIT_ITEMS when the user adds items to the cart.
  • PO_REQUISITION_LINES_S — The requisition line base table referenced in the evolution of cart lines into requisition demand.
  • DUAL, PLITBLM — Utility references used for scalar selects and PL/SQL table/array handling.
  • HTF, HTP, OWA_UTIL — The Oracle Web Toolkit packages used to emit HTML and handle browser output.

The package also depends on APPS.ICX_OWA_PARMS, a related Web Toolkit parameter package, and on a single dependency in SYS (STANDARD).

Usage Notes

ICX_REQ_SEARCH is invoked internally by the iProcurement item search and requisitioning pages; it is not intended for direct invocation by external applications, and ETRM records show it is referenced by no other packages. The only documented inbound reference is the package itself (package body and specification referencing each other).

Because the package emits HTML through HTP/HTF and OWA_UTIL, it operates within an Oracle Application Server / mod_plsql or OAF-hosted context and depends on an active web session, an ICX shopping cart, and valid ICX_PARAMETERS settings. Customizations should avoid modifying the package directly; extensions should instead be implemented through supported personalization or by wrapping cart insertion logic via the documented iProcurement and purchasing APIs. Any inspection of behavior in a specific 12.1.1 or 12.2.2 instance should begin with the deployed source, since the ETRM metadata records object dependencies and entry point names but not parameter or return type detail.