Search Results deep_model_copy

Overview

APPS.CZ_MODELOPERATIONS_PUB is a public API package body within the Oracle E-Business Suite (EBS) 12.1.1/12.2.2 environment, belonging to the Oracle ETRM (Enterprise Transaction and Regulatory Management) product family, also branded as Oracle Application Integration Architecture or Oracle Risk Management components in certain releases. The package exposes a controlled programmatic interface for managing the lifecycle of ETRM "models" — the development project artifacts, user interface definitions, populators, publications, and supporting metadata that drive the ETRM configuration and data-processing engine. It abstracts complex multi-step operations such as generating model logic, importing bills, copying models, publishing and republishing models, and executing populators, allowing Forms, concurrent programs, and other PL/SQL packages to invoke these operations through a consistent API classification (PUB).

Key Procedures and Functions

The package body exposes 39 documented procedures and functions. Core logic-generation and model-management routines include:

• GENERATE_LOGIC — initiates logic generation for a development project, allocating a run identifier and validating compatibility.
• CREATE_UI, CREATE_JRAD_UI, REFRESH_UI, REFRESH_JRAD_UI — create and refresh user interface definitions, including JRAD-specific variants.
• IMPORT_SINGLE_BILL, IMPORT_GENERIC — import transactional bill data into the model framework.
• PUBLISH_MODEL, REPUBLISH_MODEL — publish or republish a model for downstream consumption.
• REFRESH_SINGLE_MODEL, DEEP_MODEL_COPY, MIGRATE_MODELS — refresh, deep-copy, and migrate models between environments.
• EXECUTE_POPULATOR, REPOPULATE — execute or rerun populators that seed model data.
• RP_FOLDER_EXISTS, CREATE_RP_FOLDER — manage report/publication folders.
• FORCE_UNLOCK_MODEL, FORCE_UNLOCK_TEMPLATE — administratively release locks on models and templates.
• USAGE_ID_FROM_USAGE_NAME — resolve a usage identifier from a usage name.
• CREATE_PUBLICATION_REQUEST — create a publication request record.

The user search term g_status_error refers to a package-level constant used across these routines to signal failure outcomes. In the documented GENERATE_LOGIC body, G_STATUS_ERROR is assigned to x_status when the minimum log urgency is 0, and again when the incompatible-API exception is raised.

Tables Accessed

• CZ_RP_ENTRIES / CZ_RP_ENTRIES_S — model/report entries used for project validation.
• CZ_DB_LOGS — log records written during API execution, queried for urgency status.
• CZ_DEVL_PROJECTS, CZ_IMP_DEVL_PROJECT — development project definitions.
• CZ_MODEL_USAGES — model usage metadata.
• CZ_POPULATORS — populator definitions consumed by EXECUTE_POPULATOR and REPOPULATE.
• CZ_SERVERS — server registration for execution routing.
• CZ_UI_DEFS — user interface definitions.
• CZ_XFR_PROJECT_BILLS — imported bill data.
• CZ_XFR_RUN_INFOS_S — sequence source for run identifiers.
• DUAL, PLITBLM — utility references.

Usage Notes

CZ_MODELOPERATIONS_PUB is invoked from ETRM administrative Forms, concurrent programs, and by one other dependent package. Callers should pass a compatible p_api_version; an incompatible version raises G_INCOMPATIBLE_API, which the package translates into G_STATUS_ERROR and logs a localized error message via CZ_UTILS.GET_TEXT. Status return values map to urgency levels: success, warning, or error. Custom code should reference the package's public procedures only and never bypass the logging built into CZ_DB_LOGS.