Search Results cs_sr_addr_cp_sync_index_pkg
Overview
The CS_SR_ADDR_CP_SYNC_INDEX_PKG package is an Oracle E-Business Suite (EBS) PL/SQL utility that resides in the APPS schema. Its name reflects its functional domain — Customer Support (CS), Service Requests (SR), Address (ADDR), and Contact Point (CP) — together with the operation it performs: synchronization of indexes (SYNC INDEX). The package therefore exists to reconcile and refresh the indexed data structures that support the association between service requests and the address and contact point records used within Oracle's Service / TeleService foundation.
In Oracle EBS 12.1.1 and 12.2.2, address and contact point information is frequently denormalized or indexed to accelerate query and validation operations performed by Service Request processing. When underlying address or contact point data changes — through data migration, bulk updates, patching, or data conversion activities — the associated indexes can become inconsistent with the base tables. This package provides a controlled mechanism to resynchronize that index content.
The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling session rather than the definer. This is significant in EBS: it indicates that the routines are intended to be invoked in a context where the caller already holds the necessary schema privileges, typically a concurrent program or administrative session running under APPS.
Key Procedures and Functions
The ETRM metadata documents a single public procedure:
- SYNC_ALL_INDEX — The sole documented entry point of the package. As the name implies, this procedure synchronizes all addresses and contact point related indexes associated with the Service Request data model. It returns the standard concurrent-program style output parameters
ERRBUFandRETCODE, which carry error text and a status indicator respectively. It also accepts an optional mode parameter,BMODE, allowing the caller to influence how the synchronization is performed without requiring the caller to specify every detail. The procedure signature is designed to be invoked both directly and from within an EBS concurrent program that consumes theERRBUF/RETCODEconvention.
No other procedures or functions are documented in the 12.2.2 ETRM entry, and the package is not referenced by any other package, confirming its role as a standalone administrative utility rather than a reusable library component.
Tables Accessed
The ETRM metadata does not enumerate specific base tables referenced by this package; references via APPS synonyms are not documented. Based on the package's functional scope and naming, the routines operate against the Service Request address and contact point data structures — principally the CS Service Request tables and their associated address/contact point index tables. Because the source specification observed in the metadata header declares no explicit table references at the package specification level, table access occurs inside the procedure body and is not exposed through the public interface.
Usage Notes
Because SYNC_ALL_INDEX follows the ERRBUF / RETCODE convention, the package is most naturally invoked from an Oracle EBS concurrent program. An administrator would register a concurrent executable pointing to this procedure and submit it as a request whenever index drift is suspected — for example, after a data conversion involving customer addresses or contact points, after applying a patch that alters the Service Request address model, or as a corrective maintenance action when Service Request address lookups return stale or missing results.
The package may also be called from a SQL*Plus session, a custom PL/SQL script, or an OAF/Forms-based administrative function. Care should be taken to invoke it only during periods of low transactional activity, since a full index resynchronization can be resource-intensive. As the package is not referenced by any other packaged object, there are no automatic internal callers; all invocations are deliberate and administrative in nature.
-
PACKAGE: APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG
12.1.1
-
PACKAGE BODY: APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG
12.2.2
-
PACKAGE BODY: APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG
12.1.1
-
PACKAGE: APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CS_SR_ADDR_CP_SYNC_INDEX_PKG, status:VALID,
-
PACKAGE: APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CS_SR_ADDR_CP_SYNC_INDEX_PKG, status:VALID,
-
PACKAGE: APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG
12.2.2
-
PACKAGE BODY: APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CS_SR_ADDR_CP_SYNC_INDEX_PKG, status:VALID,
-
PACKAGE BODY: APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CS_SR_ADDR_CP_SYNC_INDEX_PKG, status:VALID,
-
PACKAGE: APPS.CS_SR_ADDR_SYNC_INDEX_PKG
12.1.1
owner:APPS, object_type:PACKAGE, object_name:CS_SR_ADDR_SYNC_INDEX_PKG, status:VALID,
-
PACKAGE: APPS.CS_SR_ADDR_SYNC_INDEX_PKG
12.2.2
owner:APPS, object_type:PACKAGE, object_name:CS_SR_ADDR_SYNC_INDEX_PKG, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG dependencies on CS_SR_ADDR_CP_SYNC_INDEX_PKG
12.1.1
-
APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG dependencies on CS_SR_ADDR_CP_SYNC_INDEX_PKG
12.2.2
-
APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG dependencies on CS_SR_ADDR_SYNC_INDEX_PKG
12.1.1
-
APPS.CS_SR_ADDR_CP_SYNC_INDEX_PKG dependencies on CS_SR_ADDR_SYNC_INDEX_PKG
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
PACKAGE: SYS.STANDARD
12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,