Results for “get_item”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.ICX_AK_JAVA_QUERY is a PL/SQL package body that acts as a server-side bridge between Oracle EBS self-service web pages and the Oracle Application Framework (AK) query engine. Its principal role is to accept a region application identifier, a region code, and dynamic WHERE and ORDER BY clauses supplied by the calling page, pass that criteria to AK_QUERY_PKG, and render the returned item and result collections back to the browser through the HTP (HTML toolkit) output buffer. The package is therefore part of the Oracle iProcurement / Internet Computing Architecture (ICX) stack, where it supports the generation of dynamically filtered result sets for search and summary pages without requiring a dedicated database object for each query.

Key Procedures and Functions

• EXECUTE_QUERY — The central entry point. It first confirms that a valid session exists via ICX_SEC.VALIDATESESSION, then invokes AK_QUERY_PKG.EXEC_QUERY with the supplied parent region application identifier, region code, WHERE clause, and ORDER BY clause, requesting parent rows and suppressing children. After execution it emits the item and result row counts and iterates over both the item table and the results table. Only items whose OBJECT_ATTRIBUTE_FLAG equals 'Y' are treated as displayable, which is the filter most relevant to the user's search term. For each qualifying item, the procedure writes the attribute code, value identifier, long label, display sequence, object attribute flag, node display flag, and display value length. For the results themselves it converts each row to a columnar array using ICX_UTIL.TRANSFER_ROW_TO_COLUMN and then emits only the column positions corresponding to flagged attributes.
• GET_ITEM — A retrieval routine that returns the descriptive metadata for a single query item. Its output parameters expose the attribute code, value identifier, long attribute label, display sequence, object attribute flag, and node display flag, allowing a caller to interrogate one item without iterating the full collection.
• GET_RESULT_ROW — Returns a single row from the AK results collection, providing programmatic access to query output outside of the HTP streaming path used by EXECUTE_QUERY.
• UPDATE_OC_KIDS — Maintains the child relationship data associated with an object collection (OC), supporting the parent/child hierarchy that AK query regions rely upon.

Tables Accessed

The documented data sources are HTP and PLITBLM, both accessed through APPS synonyms. HTP is the Oracle HTML toolkit package rather than a data table; the package uses it purely for output generation (HTP.P). PLITBLM is the standard Oracle PL/SQL integer table type used to hold result column positions, consistent with the container row produced by ICX_UTIL.TRANSFER_ROW_TO_COLUMN. All substantive query data is drawn from the AK_QUERY_PKG global collections, G_ITEMS_TABLE and G_RESULTS_TABLE, which the package consumes after AK_QUERY_PKG.EXEC_QUERY populates them.

Usage Notes

ICX_AK_JAVA_QUERY is an internal supporting package rather than a public API. It is invoked in response to user interactions on ICX and iProcurement pages that render AK-based query regions, typically after the user submits filter criteria. It should not be called from concurrent programs, since its output path depends on an active HTP buffer and a validated web session; a null or expired session causes EXECUTE_QUERY to exit silently without emitting content. Because the package relies on the AK_QUERY_PKG global collections, it is not reentrant and callers must execute it serially within a single request. Custom code extending AK query regions should reuse the OBJECT_ATTRIBUTE_FLAG convention shown here to distinguish displayable object attributes from internal metadata.