Search Results cfg_input_list

Overview

APPS.CZ_BATCH_VALIDATE is a configuration validation package in Oracle E-Business Suite that supports the Configurator (Oracle Configurator / CZ) module. Its principal role is to validate a batch of configuration selections — a set of component codes, quantities, sequence numbers, and optionally explicit configuration item identifiers — against a remote or external configuration validation service. The package exposes a single public procedure, VALIDATE, which performs a "single-call" validation: all multi-valued input data is exchanged in one round trip rather than through multiple calls.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than the definer, and it carries a header version of 120.0.12010000.2 dated 2009/07/16. It is classified under API classification "OTHER" in the ETRM repository, and it is referenced by two other packages, indicating it plays a supporting role in a larger Configurator validation flow rather than serving as a top-level entry point.

Key Procedures and Functions

The package documents one procedure: VALIDATE. It performs batch validation of a configuration input list and returns configuration messages and a numeric status indicator to the caller. Rather than returning a single boolean, it communicates results through an output table of configuration messages and a status code, allowing the caller to distinguish among several outcome categories.

Although the procedure's parameter list is not reproduced in detail here, the package defines supporting types that shape its interface. The INPUT_SELECTION record carries component_code, quantity, input_seq, and an optional config_item_id. The CFG_INPUT_LIST type is a collection of these records indexed by BINARY_INTEGER, used to pass multi-valued input. The subtype CFG_OUTPUT_PIECES is based on UTL_HTTP.HTML_PIECES, so returned messages are handled as a table of text pieces (typically XML fragments).

A defined set of status constants gives callers a precise return vocabulary: CONFIG_PROCESSED (0), CONFIG_PROCESSED_NO_TERMINATE (1), INIT_TOO_LONG (2), INVALID_OPTION_REQUEST (3), CONFIG_EXCEPTION (4), DATABASE_ERROR (5), UTL_HTTP_INIT_FAILED (6), UTL_HTTP_REQUEST_FAILED (7), CONFIG_ITEM_UNSUPPORTED_PRE_H (8), and INVALID_ALTBATCHVALIDATE_URL (9). A message length limit constant, INIT_MESSAGE_LIMIT, is also declared.

Tables Accessed

The documented data sources are the package UTL_HTTP and the PLITBLM package, both referenced through APPS synonyms. UTL_HTTP is a PL/SQL-supplied package used to make outbound HTTP requests; this is central to the design, since the validation status codes include URL-related and HTTP failure codes (UTL_HTTP_INIT_FAILED, UTL_HTTP_REQUEST_FAILED, INVALID_ALTBATCHVALIDATE_URL). This confirms that VALIDATE transmits the batch of configuration selections to an external validation endpoint and interprets the response. PLITBLM supports the internal table and collection handling used for multi-valued lists. No configuration base tables are documented as directly accessed by this package; persistence of validation results is the responsibility of the calling layers.

Usage Notes

CZ_BATCH_VALIDATE is typically invoked programmatically rather than from a Form or Concurrent Program interface. The procedure is designed for integration scenarios in which a caller—often the Configurator UI manager or a batch validation process—assembles a CFG_INPUT_LIST of selections, optionally supplies an additional XML init_message, and receives back both a message table and a validation status code. Callers must interpret the returned numeric status against the package's declared constants and, on HTTP client errors, retry or surface the appropriate message to the user. The default URL parameter is derived from the profile option CZ_UIMGR_URL, so environments must have this profile configured correctly for validation to succeed. Because it is referenced by two other packages, it should be treated as an internal dependency: changes to its interface or status semantics may affect dependent validation logic across the Configurator module.