Search Results drop_index




Overview
Explore in AI Chat

Overview

APPS.CS_SR_CONC_PROG_PKG is a thin wrapper package body in the Oracle E-Business Suite Service (CS) schema. Its sole business function is to expose index maintenance operations on Service Request (SR) related text and summary indices so they can be invoked from Oracle Concurrent Manager. The package contains no business logic of its own; every procedure delegates directly to the corresponding routine in CS_SR_SYNC_INDEX_PKG, which performs the actual index synchronization and maintenance work.

The naming convention confirms its role: "CONC_PROG" indicates that the procedures here are entry points intended to be registered as concurrent programs. The header comment (revision 120.1, dated 2005/08/29) and the "noship" designation indicate a long-standing, internally maintained object carried forward into both 12.1.1 and 12.2.2. The package follows a standard concurrent program signature pattern, returning ERRBUF and RETCODE to the Concurrent Manager to signal success (0), warning (1), or error (2).

Key Procedures and Functions

  • SYNC_ALL_INDEX — Wrapper entry point for synchronizing all Service Request indices. Accepts ERRBUF, RETCODE, and a BMODE parameter, and delegates to CS_SR_SYNC_INDEX_PKG.SYNC_ALL_INDEX.
  • SYNC_SUMMARY_INDEX — Synchronizes the summary index used by SR searching. Accepts ERRBUF, RETCODE, and BMODE, and delegates to CS_SR_SYNC_INDEX_PKG.SYNC_SUMMARY_INDEX.
  • SYNC_TEXT_INDEX — Synchronizes the text index for Service Requests. In addition to ERRBUF, RETCODE, and BMODE, it accepts a pindex_with and pworker parameter, and delegates to CS_SR_SYNC_INDEX_PKG.Sync_Text_Index. The header comment explicitly marks this as the "TEXT" index routine.
  • DROP_INDEX — Removes the specified index, taking p_index_name and returning x_msg_error and x_return_status. It delegates to CS_SR_SYNC_INDEX_PKG.Drop_Index. This is the procedure most relevant to the "drop_index" search: it is the documented, supported way to drop an SR index through the concurrent program interface.

Tables Accessed

The ETRM metadata documents no tables referenced directly by APPS.CS_SR_CONC_PROG_PKG. This is expected given its wrapper role: all data access occurs inside CS_SR_SYNC_INDEX_PKG, which manages the underlying Service Request index and synchronization tables via APPS synonyms. Because no DML is performed at this layer, there is no direct read or write dependency to report.

Usage Notes

In typical Oracle EBS deployments, this package is invoked in two ways. First, it is registered as one or more concurrent programs (for example, a "Synchronize Service Request Indices" or "Drop Index" program) whose executable is PL/SQL Stored Procedure; the Concurrent Manager passes ERRBUF and RETCODE automatically. Second, it can be called from custom PL/SQL code or a form trigger when an administrator needs to rebuild or remove an SR index programmatically. The BMODE parameter controls the underlying indexing mode (for example, optimize fast or optimize full), allowing DBAs to tune the operation. Because DROP_INDEX is a destructive operation, it should be executed only by users authorized to manage SR indexing, and generally during a maintenance window. No other packages in the ETRM inventory reference this package, so its impact is confined to its wrappers and the procedures it delegates to.