Search Results release_result_table




Overview

The APPS.CS_INCIDENT_CTX_PKG package body belongs to the Service (CS) module of Oracle E-Business Suite and supports the incident context-search infrastructure used by Oracle iSupport and TeleService. Its principal role is to manage the execution of dynamic SQL statements that build and populate a temporary context index used when searching incidents by text content. The package is classified under the ETRM as OTHER, indicating it is an internal helper package rather than a public API. The body header (revision 115.1) reflects an early porting-era build, and the implementation relies heavily on the DBMS_SQL built-in to parse and execute SQL strings supplied at runtime — a design pattern common to InterMedia/Oracle Text-driven search features.

Key Procedures and Functions

  • EXECUTE_QUERY_CONTAINS — The core worker procedure. It accepts several optional SQL statement strings plus a result-table name. If a result table is supplied it issues a TRUNCATE TABLE against it; each non-null statement is then opened via DBMS_SQL.OPEN_CURSOR, parsed at dbms_sql.v7, executed, and the cursor closed. Error handling inspects SQLERRM for Oracle Text error codes (notably DRG-10308) and, on failure, closes any open cursor and raises the CS_INC_CTX_NO_SERVER application exception via FND_MESSAGE.
  • UPDATE_CONTEXT_INDEX — Refreshes the context index associated with incident search data, ensuring newly created or modified incidents are reflected in subsequent text queries.
  • GET_CONTEXT_STOP_WORDS — Returns the set of stop words used to filter the context query string; stop-word filtering is explicitly noted in the source as the reason for removing the DRG-10817 error branch.
  • GET_RESULT_TABLE — Provides the name of the temporary/result table into which context query output is written.
  • RELEASE_RESULT_TABLE — Releases or cleans up that result table once the search has completed.

Tables Accessed

The documented table reference for this package is DBMS_SQL, which is not a schema table but the Oracle-supplied PL/SQL package invoked through DBMS_SQL.OPEN_CURSOR, PARSE, EXECUTE, IS_OPEN, and CLOSE_CURSOR. No application tables are recorded in the ETRM metadata; dynamic target tables (the truncated result table and the tables addressed by the passed-in SQL strings) are resolved at runtime and therefore are not statically documented.

Usage Notes

This package is not referenced by any other documented package (referenced by 0). It is most likely invoked indirectly through Oracle iSupport incident-search forms or through concurrent/context-index maintenance routines that require dynamic SQL execution against a designated result table. Because it uses DBMS_SQL with unvalidated string parameters and a v7 parse mode, customizations should avoid calling it directly; any custom integration should instead use the supported Oracle Text and CS search APIs. Its exception path maps Oracle Text failures to the CS_INC_CTX_NO_SERVER message, so callers should expect a raised application exception rather than a returned error code when the context server is unavailable.