Search Results ieo_string_varr

Overview

APPS.CCT_VALIDATION_PUB is a public PL/SQL API package belonging to the Oracle E-Business Suite (EBS) Advanced Product Catalog / iStore configuration and setup layer. Its role is to validate parameter definitions for various server-side "engines" (OTM, ITS, and IQD) configured against server groups and individual servers. The package is declared with AUTHID CURRENT_USER, and its package specification header indicates it is a legacy object shipped under internal versioning ("cctpvals.pls 115.6", dated 2004), meaning it has remained functionally stable across 12.1.1 and 12.2.2. The public (PUB) classification signals that it is intended to be called by external consumers such as forms, concurrent programs, or other packages rather than being invoked internally within the owning module. The central purpose of the API is to receive a set of parameter identifiers and their corresponding values, evaluate them against the server-side configuration context (server group and server), and return a structured list of error messages that callers can surface to end users or logs. The search term "ieo_string_varr" corresponds directly to the collection type used throughout the package: IEO_STRING_VARR is a PL/SQL associative-array or varray type used to pass lists of strings (parameter IDs, parameter values, and error messages) in and out of the validation procedures. This type is central to the package's interface, enabling bulk parameter validation in a single API call rather than per-parameter round trips.

Key Procedures and Functions

Three public procedures are documented in the package specification. All three share an identical parameter signature shape, differing only in the engine context they validate:

• VALIDATE_OTM_PARAMS — Validates parameters associated with the OTM (Order-to-Money / Order Tracking Management) processing engine. It accepts a server group ID, server ID, environment language, lists of parameter IDs and values (using IEO_STRING_VARR), and returns an error count, an error message list (IEO_STRING_VARR), the standard return status, message count, and message data.
• VALIDATE_ITS_PARAMS — Validates parameters for the ITS engine context. Its signature mirrors VALIDATE_OTM_PARAMS exactly, receiving the same server context, parameter ID/value lists, and the same set of error message output collections.
• VALIDATE_IQD_PARAMS — Validates parameters for the IQD engine context, again using the same signature as the other two procedures.

The consistent pattern across all three procedures reflects a common validation framework applied to three distinct server engine types. Each procedure populates x_err_msgs and x_err_msg_count so that callers can retrieve per-parameter validation feedback, and each sets x_return_status along with the standard message-count/message-data pair.

Tables Accessed

The package references the following tables (via APPS synonyms) as documented in the ETRM metadata:

• IEO_SVR_GROUPS — server group definitions, used to resolve and validate the target server group context.
• IEO_SVR_SERVERS — individual server definitions belonging to those groups.
• IEO_SVR_PARAMS — parameter metadata (definitions) for each server or engine, used to validate parameter IDs and expected characteristics.
• IEO_SVR_VALUES — parameter values configured for the servers, used to compare and validate supplied values.
• FND_NEW_MESSAGES — the Oracle Application Object Library message repository, used to retrieve localized validation messages based on the p_env_lang argument.
• DUAL — a single-row utility table, typically leveraged for lightweight SQL evaluations.
• PLITBLM — a PL/SQL index-by-table type support table, related to the IEO_STRING_VARR handling.

Usage Notes

CCT_VALIDATION_PUB is typically invoked from the Oracle EBS configuration user interfaces (forms) that maintain server groups, servers, and their parameters, and from concurrent programs or setup validation routines that pre-validate configuration before activating an engine. Because the procedures use bulk IEO_STRING_VARR collections, callers must first populate the parameter ID and parameter value lists, then invoke the appropriate procedure for the target engine (OTM, ITS, or IQD). Custom code can call these procedures directly, but must define and pass variables compatible with IEO_STRING_VARR. After execution, callers should inspect x_return_status and, if non-success or if x_err_msg_count is greater than zero, iterate over x_err_msgs to present or log the individual validation failures. The AUTHID CURRENT_USER declaration means the package executes with the privileges of the calling schema, so appropriate grants on the referenced IEO and FND tables are required by the caller. The package is not referenced by any other documented packages (referenced by zero), indicating it is an entry-point API relied upon by external callers rather than internal modular dependencies.