Search Results get_context_stop_words




Overview

APPS.CS_INCIDENT_CTX_PKG is a PL/SQL context-search utility package in Oracle E-Business Suite. It belongs to the Customer Support (CS) schema, which underpins the Service / TeleService modules used to log, track, and resolve incidents and service requests. The package provides the database-side machinery for a text-context search feature over incident data; the procedure name Execute_Query_Contains and the parameter names str1, str2, str3, str4, and result_table indicate that it accepts one or more query terms and a target staging table, performs a "contains" style match, and writes the matching rows to the result table for the calling form to consume.

The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the invoking user rather than the definer, and its header stamp ($Header: cssrctxs.pls 115.0 99/07/16) shows the specification dates back to a very early release and has been carried forward unchanged into 12.1.1 and 12.2.2. It is classified in ETRM as API classification OTHER, meaning it is an internal utility rather than a formally published or certified public API.

Key Procedures and Functions

Five procedures are documented in the package specification:

  • Execute_Query_Contains — the core search entry point. It accepts the search terms and the name of a result table, runs the contains-style query against incident text, and populates the supplied result table. The result table is passed by name so that each session or concurrent run can use its own work table.
  • Update_Context_Index — takes a policy name and a primary key and refreshes the context (text) index for the identified incident record, keeping the searchable index synchronized with the underlying incident text.
  • Get_Context_Stop_Words — returns the stop-word list, i.e. the terms excluded from context indexing and searching, so that callers can present or apply the same exclusions.
  • Get_Result_Table — supplies the name of the result table into which matches are written, allowing the caller to discover or allocate the work table before invoking the search.
  • Release_Result_Table — releases (drops or returns) the result table named by the caller once the results have been consumed, providing cleanup for the temporary staging structure.

Tables Accessed

The documented metadata records only DBMS_SQL as an object referenced via APPS synonyms. This is significant: rather than embedding static SQL against incident tables, the package uses dynamic SQL through DBMS_SQL, which is consistent with its role as a generic context-search driver in which the table and column names may be supplied or resolved at runtime. The actual incident and index tables it targets (for example the CS incident tables and the Oracle Text / context index structures) are therefore accessed dynamically and are not enumerated in the documented metadata. The result table named by the caller is likewise created, written, and released through dynamic operations.

Usage Notes

This package is not invoked directly by end users. It is the supporting layer behind the incident search and "contains" query facilities exposed through Service / TeleService forms, and it may also be called from concurrent programs or custom extensions that need to run a context search against incident text. Oracle EBS 12.1.1 and 12.2.2 behavior is effectively identical because the specification is unchanged. The typical call sequence is to obtain the result table with Get_Result_Table, invoke Execute_Query_Contains with the search terms, read the staging table, and then call Release_Result_Table. Because the package is AUTHID CURRENT_USER and relies on dynamic SQL through DBMS_SQL, integrity and privilege checks (including any EXECUTE grant on DBMS_SQL) and read access to the target objects must be in place for the calling user. It is referenced by zero other packages per the ETRM metadata, and it should be treated as an internal utility rather than a supported public API; customizations that call it directly should be revalidated against each patched release.