Search Results g_app_shortname

Overview

APPS.CSC_CORE_UTILS_PVT is a private PL/SQL utility package body in the Oracle E-Business Suite Customer Service (TeleService / Common Services) schema. Despite its classification as a private ("PVT") API, it is one of the most widely depended-upon modules in the CS product family: the ETRM metadata records that it is referenced by 39 other database objects, even though it is not itself referenced by any database object. This makes it a foundational, low-level service layer rather than a public, callable API.

Its business function is to consolidate the common technical services required by the Customer Service modules — interaction logging, lookup and message resolution, counter management, dynamic SQL execution, transaction control, currency validation, and concurrent-plan administration. By centralizing these activities in a single private package, Oracle maintains consistent error handling, message propagation, and standards across the callable Customer Service APIs and their associated AOL components.

Key Procedures and Functions

The documented interface exposes 46 procedures and functions. The most significant fall into identifiable groups.

• Global constants: G_CREATE, G_UPDATE, G_MISS_NUM, G_MISS_CHAR, G_MISS_DATE, G_RET_STS_SUCCESS, G_RET_STS_ERROR, G_RET_STS_UNEXP_ERROR, G_VALID_LEVEL_NONE, G_VALID_LEVEL_FULL, G_VALID_LEVEL_INT, G_TRUE and G_FALSE. These define the standard API return statuses, validation levels, missing-value markers and boolean tokens used throughout the Customer Service API family.
• Concurrent plan administration: ENABLE_PLAN, DISABLE_PLAN, APPLY_PLAN, REMOVE_PLAN, MERGE_PLAN and TRANSFER_PLAN create, activate, modify, migrate or delete request-set and concurrent request plans. These support the setup and deployment of scheduled concurrent processing in the EBS environment.
• Statistics collection: GATHER_TABLE_STATS wraps the collection of optimizer statistics for a named table, supporting Cost-Based Optimizer (CBO) behaviour and performance tuning.

These procedures use the standard EBS API conventions of FND_API-based return status, and they propagate errors through FND_MSG_PUB. Parameter lists are not documented here and must not be assumed.

Tables Accessed

The package references several base and AOL tables through APPS synonyms:

• CS_COUNTERS — stores Customer Service counter values, used for sequence and numbering generation.
• FND_APPLICATION — the application registration table, used to resolve application identity and context.
• FND_CURRENCIES — the currency definitions table, used to validate and default currency values in Customer Service transactions.
• DBMS_SQL and DBMS_TRANSACTION — dynamic SQL execution and transaction control (commit/rollback/savepoint) facilities invoked directly rather than through tables.

Additional dependencies include CSC_LOOKUPS, CS_INTERACTION_PVT and FND_LOOKUPS for lookup and interaction data, and FND_MESSAGE and FND_MSG_PUB for message resolution and error stacking.

Usage Notes

Because CSC_CORE_UTILS_PVT is a private package, it is not intended to be called from external custom code. It is invoked internally by the Customer Service APIs and by concurrent programs, forms and workflows that rely on CS_INTERACTION_PVT and its related modules. Customizations that must behave consistently with delivered Customer Service processing should call the public APIs (for example, the CS_INTERACTION_PVT public entry points) rather than this utility directly.

The package is valid in both EBS 12.1.1 and 12.2.2. The 12.2.2 ETRM documentation records the same structural shape, indicating that the package remains stable across these releases.