Results for “csc_color_codes_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.CSC_COLOR_CODES_PKG package body is a data-maintenance API within the Oracle E-Business Suite Customer Care (CSC) schema. It provides the standard insert, update, lock, delete, and load operations for the CSC_COLOR_CODES table, which stores the color-code-to-rating-code mapping used by CSC service and call-center functionality for associating color classifications with rating values.

The package follows Oracle's conventional table-handler (TP) API pattern, exposing a small set of DML procedures that encapsulate all direct manipulation of the underlying table. The header comment traces the object's history to November 2000, when a Load_row procedure was added to support NLS migration (bug #1487340), and records a July 2005 modification in which load_row was reworked to retrieve l_user_id from a FND API as part of the R12 ATG project. The package is classified as OTHER in the ETRM repository and is referenced by one other package.

Key Procedures and Functions

• INSERT_ROW — Inserts a new color-code record into CSC_COLOR_CODES. The COLOR_CODE is defined as an IN OUT NOCOPY parameter, allowing the generated key value to be returned to the caller. The procedure applies DECODE against the FND_API G_MISS sentinels (G_MISS_DATE, G_MISS_NUM) so that unspecified attributes are stored as NULL rather than as sentinel values.
• UPDATE_ROW — Updates the color-code attributes for an existing record identified by rating code. The procedure explicitly raises NO_DATA_FOUND when SQL%NOTFOUND is true, ensuring callers are notified if no matching row exists.
• LOCK_ROW — Obtains a row-level lock on the target color-code record, providing the concurrency control required before an update or delete is attempted.
• DELETE_ROW — Removes a color-code record from CSC_COLOR_CODES, typically invoked after a successful lock.
• LOAD_ROW — Performs the load/upsert-style operation used for data migration and NLS seed data. Per the header history, this procedure was modified to source l_user_id from a FND API rather than relying on a caller-supplied value, aligning it with R12 audit-column conventions.

Tables Accessed

The package operates exclusively on the CSC_COLOR_CODES table, accessed through its APPS synonym. The table holds the color-code and rating-code columns together with the standard EBS audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. All five documented procedures read from or write to this single table; no other application tables are referenced by the package body itself.

Usage Notes

As a table-handler package, CSC_COLOR_CODES_PKG is normally invoked indirectly. Oracle Forms and OA Framework pages that maintain color-code setup data call these procedures through the standard DML API stack rather than issuing direct SQL against CSC_COLOR_CODES. The LOAD_ROW procedure is the entry point typically used by concurrent programs, NLS installation scripts, and data-migration routines that seed or update color-code definitions in bulk, particularly where audit-column population must follow R12 FND API conventions.

Custom extensions and interfaces should call these procedures instead of writing directly to the table, so that the FND_API G_MISS handling, audit-column logic, and the NO_DATA_FOUND exception behaviour are preserved. In Oracle EBS 12.1.1 and 12.2.2 the package remains an APPS-owned, non-public API; the single dependent package reference indicates it is consumed within the CSC product family rather than by general-purpose application code.