Search Results test_ui_pages

Overview

APPS.CZ_XML is an Oracle E-Business Suite utility package belonging to the Oracle Configurator (CZ) product family, which underlies the Configurator models, user interface definitions, and runtime UI infrastructure used by Oracle EBS order management, quoting, and configuration workflows. The package is compiled with AUTHID CURRENT_USER and, judging from its header comment, dates back to early Configurator releases (circa 2006) yet remains present in the ETRM metadata for 12.1.1 and 12.2.2. Its central purpose is the parsing, inspection, repair, and persistence of XML documents that describe Configurator UI definitions, UI pages, templates, rules, and the attributes and elements that compose them.

The package is best understood as a maintenance toolkit. Configurator stores much of its UI and rule configuration as XML or XML-derived structures, and over time these can accumulate malformed attributes, invalid element identifiers, orphaned parent references, or dangling rule identifiers. CZ_XML provides procedures that detect and remediate these conditions in bulk, so administrators do not have to edit individual documents manually. It also provides the low-level operation that persists an in-memory XML DOM document back to the repository.

Key Procedures and Functions

• TEST_UI_PAGES — Validates UI page definitions for a given UI definition identifier, supporting quality checks of Configurator UI content.
• PARSE_JRAD_DOCUMENT — A function that parses a JRAD (Java Runtime Attribute Definition) document supplied by full name and returns an XML DOM document handle for further processing.
• SAVE_DOCUMENT — Persists an in-memory XML DOM document under a specified document name. This is the procedure most closely associated with the search term "save_document" and is the write counterpart to PARSE_JRAD_DOCUMENT.
• DETECT_DOC_BAD_ATTRIBUTES — Scans a named document and reports whether invalid attributes are present.
• REMOVE_BAD_ATTRIBUTES_IN_DOC — Removes detected bad attributes from a named document.
• DETECT_UIS_WITH_BAD_ATTRIBUTES — Identifies UI definitions affected by bad attributes, optionally scoped to one UI definition, returning a run identifier and standard return status, message count, and message data.
• REMOVE_BAD_ATTRIBUTES_IN_UIS — Cleans bad attributes from affected UI definitions using the same run/status messaging convention.
• DETECT_TMPLS_WITH_BAD_ATTRS — Detects templates containing invalid attributes, optionally scoped to a single template identifier.
• REMOVE_BAD_ATTRIBUTES_IN_TMPLS — Removes invalid attributes from affected templates.
• REPLACE_BAD_ELEMENT_IDS — Substitutes invalid element identifiers within UI definitions, preserving referential integrity of page elements.
• RESTORE_PARENT_ELEMENTS — Rebuilds or repairs parent-child element relationships that have become inconsistent.
• RESTORE_UI_RULE_IDS — Restores missing or corrupted UI rule identifiers referenced by UI content.
• RESTORE_TMPL_RULE_IDS — Performs the equivalent restoration for template rule identifiers.
• ADD_TEMPLATE_REFERENCES — Establishes template reference records, linking templates into the UI reference structure.

Tables Accessed

Via APPS synonyms, the package touches the core Configurator repository tables. CZ_UI_DEFS, CZ_UI_PAGES, CZ_UI_PAGE_ELEMENTS, and CZ_UI_PAGE_ELEMENTS_S hold UI definitions, their pages, and page element definitions, which are the primary targets of the attribute, element-ID, and parent-restoration routines. CZ_UI_TEMPLATES and CZ_UI_REFS support template detection and the ADD_TEMPLATE_REFERENCES procedure. CZ_RULES and CZ_RP_ENTRIES back the rule-ID restoration logic, while CZ_INTL_TEXTS holds translatable text. CZ_DB_LOGS and CZ_XFR_RUN_INFOS_S record run-level diagnostics for the detection and removal procedures. JDR_ATTRIBUTES stores Java runtime attribute definitions relevant to the bad-attribute checks, and XMLDOM and DBMS_LOB provide the XML parsing and large-object handling infrastructure used by PARSE_JRAD_DOCUMENT and SAVE_DOCUMENT. DUAL is used for simple singleton queries.

Usage Notes

CZ_XML is classified as OTHER rather than a formal public API and is referenced by zero other packages in the ETRM metadata, indicating that it is invoked directly rather than through a wrapper chain. It is typically called from ad hoc SQL*Plus or PL/SQL scripts during Configurator troubleshooting and data-repair exercises, from custom concurrent programs built for periodic integrity checks of UI content, and from Configurator forms logic where documents must be parsed and re-saved. Because the package depends on XMLDOM and JDR structures that evolved across releases, remediations should be executed against a validated backup and scoped to specific UI definition or template identifiers where the procedures permit it, using the returned run identifier to review the corresponding CZ_DB_LOGS entries.