Search Results get_ui_element_id

Overview

APPS.CZ_MODEL_CONVERT is a PL/SQL package within the Oracle E-Business Suite Configure-to-Order (Cz) schema that provides the public API for model conversion. Its primary business function is to migrate model definitions from one Configurator repository to another, typically in support of release upgrades, environment refreshes, or consolidations of configuration data. The package name derives from the conversion of models and is catalogued under ETRM with the classification OTHER, indicating it is a programmatic utility rather than a documented user-facing API. The header revision dates the source to 2007, placing the package within the Oracle Configurator lineage that was subsequently incorporated into EBS 12.1.1 and 12.2.2.

The package exposes a package-level Boolean, CONVERT_MODEL, initialized to FALSE, which acts as an internal switch or status flag for conversion processing. The conversion workflow centres on a conversion request created by a developer. That request is stored in CZ_MODEL_PUBLICATIONS, keyed by MIGRATION_GROUP_ID, and enumerates all models selected from the source Configurator repository for conversion.

Key Procedures and Functions

• CONVERT_MODELS — the principal public API for model conversion. It accepts a model conversion set identifier that corresponds to the MIGRATION_GROUP_ID of the conversion request recorded in CZ_MODEL_PUBLICATIONS. Invoking it processes the list of models selected for conversion from the source repository.
• MODEL_CONVERT_CP — a concurrent program wrapper. Its signature follows the standard EBS concurrent program convention of errbuf (OUT NOCOPY VARCHAR2) and retcode (OUT NOCOPY NUMBER), with an optional request identifier parameter. It is designed to be registered and submitted as a concurrent program.
• GET_UI_PATH — returns a VARCHAR2 UI path for a given parent identifier, supporting navigation or rendering logic in the conversion user interface.
• GET_UI_ELEMENT_ID — returns a numeric element identifier for a supplied page element identifier, allowing the conversion UI to resolve elements to their internal identifiers.

Parameter lists are deliberately omitted here; the documented source excerpt and ETRM metadata do not establish full parameter contracts for every routine, and none should be inferred.

Tables Accessed

Because CZ_MODEL_CONVERT depends on fourteen documented APPS synonyms, it touches a broad slice of the Configurator data model rather than a narrow set of staging tables. The conversion request and model publication records are held in CZ_MODEL_PUBLICATIONS, the anchor table for the MIGRATION_GROUP_ID. Model content is read from CZ_PB_MODEL_EXPORTS and CZ_MODEL_REF_EXPLS. Rules, expressions, and presentation data referenced during conversion include CZ_RULES, CZ_RULES_S, CZ_RULE_FOLDERS, CZ_EXPRESSION_NODES, CZ_EXPRESSION_NODES_S, CZ_DES_CHART_FEATURES, and CZ_PS_NODES. Project metadata is sourced from CZ_DEVL_PROJECTS. Localized and internationalized text is handled through CZ_INTL_TEXTS, CZ_INTL_TEXTS_S, and CZ_LOCALIZED_TEXTS. Finally, CZ_DB_LOGS records diagnostic output generated during conversion processing. The mix of base and _S tables confirms that the package works with both the current and seeded or translated definition rows that make up a Configurator model.

Usage Notes

CZ_MODEL_CONVERT is invoked in upgrade and migration scenarios rather than in day-to-day configuration maintenance. The documented concurrent program entry point, MODEL_CONVERT_CP, is the expected invocation path for batch execution: a conversion request is first assembled as a developer-owned set of models in CZ_MODEL_PUBLICATIONS with an associated MIGRATION_GROUP_ID, and the concurrent program is then submitted against that identifier. The ETRM metadata records that the package is referenced by zero other packages, indicating it is a top-level entry point rather than a building block called by other Configurator APIs. The UI helper functions suggest the package also supports an interactive conversion screen. Because the package is shipped in the APPS schema with a proprietary Oracle header, any direct calls should be treated as unsupported customization, and the concurrent program route should be preferred. The relevance to the user's search for a Honeywell auto scanner to manual scanner converter appears to be coincidental or mis-tagged: nothing in the documented metadata describes barcode scanner or device configuration behaviour.