Search Results transfer_row_to_column




Overview
Explore in AI Chat

Overview

ICX_UTIL is a shared PL/SQL utility package owned by the APPS schema and classified by ETRM as a UTIL (utility) object. It is part of the Oracle iProcurement / Internet Commerce Exchange (ICX) technology stack and is declared with AUTHID CURRENT_USER, meaning that its unqualified database references resolve against the privileges of the calling user rather than the definer. The package supplies a library of low-level helper routines used throughout the ICX product family, most prominently for generating HTML list-of-values (LOV) widgets, resolving user-interface prompts and lookup values, constructing error pages, and performing miscellaneous string and flexfield segment parsing. It is referenced by 81 other packages, confirming its role as foundational shared infrastructure rather than an end-user-facing API. The searched term category_flex_seg corresponds to the CATEGORY_FLEX_SEG function documented in this package, which resolves a descriptive flexfield segment value for the category flexfield, typically used to render category context in ICX shopping and requisition pages.

Key Procedures and Functions

The package exposes 28 documented procedures and functions. The LOV family generates and renders HTML list-of-values controls within Oracle Forms and web pages:

  • LOVSCRIPT — emits the JavaScript support code required by the LOV widgets.
  • LOVBUTTON — returns an HTML LOV button for a given attribute and region context.
  • LOV — renders the LOV control itself for an attribute/region combination.
  • LOVHEADER — builds the LOV header row, including column labels and formatting.
  • LOVVALUES — populates and returns the LOV result values.

A second group provides prompt, lookup, and display helpers:

  • GETPROMPTS / GETPROMPT — retrieve one or many translatable prompt strings.
  • GETLOOKUPS / GETLOOKUP — retrieve one or many lookup code meanings.
  • GET_COLOR — returns configured color values for ICX pages.
  • COPYRIGHT — emits the standard copyright notice.

Error-handling routines include:

Data-conversion and flexfield routines include:

  • PARSE_STRING — splits a delimited string into components.
  • TRANSFER_ROW_TO_COLUMN — transposes a row-oriented result into column-oriented PL/SQL table structures, returning char240_table or char4000_table collections defined in the package.
  • ITEM_FLEX_SEG — resolves an item flexfield segment value.
  • CATEGORY_FLEX_SEG — resolves a category flexfield segment value, the object associated with the user's search term.

Tables Accessed

The package reads from several Application Object Library (AK) and FND tables through APPS synonyms. AK_ATTRIBUTES, AK_OBJECT_ATTRIBUTES, and AK_REGIONS / AK_REGIONS_TL supply attribute and region metadata that drive LOV rendering and prompt resolution, with the _TL tables providing translated text. AK_REGION_ITEMS and AK_REGION_ITEMS_TL define the individual items within a region and their translated labels. FND_LANGUAGES supports language-specific prompt selection. ICX_COLORS provides color configuration for rendered pages, while ICX_PARAMETERS holds ICX system parameters. DUAL is used for scalar evaluations, and the PL/SQL-supplied packages HTF, HTP, OWA_UTIL, and PLITBLM generate HTML output and manage output buffering.

Usage Notes

ICX_UTIL is not intended to be called directly by end users. Within Oracle EBS 12.1.1 and 12.2.2 it is invoked from ICX forms, JSP/HTML regions, and other PL/SQL packages (81 known referrers) that need to render LOV controls, resolve prompts and lookups, display error pages, or extract flexfield segment values. The CATEGORY_FLEX_SEG function in particular is called when a page must resolve a category descriptive flexfield segment, such as during iProcurement catalog or requisition category display. Customizations and extensions that reuse ICX_UTIL must account for its AUTHID CURRENT_USER declaration, since object resolution and privileges are evaluated against the calling schema, and should rely only on the documented signatures. Because the package is a shared utility referenced across the ICX stack, modifications or overrides risk broad impact, and Oracle-supplied source should be treated as read-only.