Results for “model_last_struct_update”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CZ_MODEL_PUBLICATIONS table resides in the CZ schema (Oracle Configurator) and serves as the central registry of published TOP (top-level) models within Oracle E-Business Suite releases 12.1.1 and 12.2.2. Each row in this table represents a single published TOP model — that is, a configurable model that has been released from the development environment and made available for runtime configuration, ordering, or deployment to one or more servers. The table functions as the master publication record, binding a model definition to its UI presentation, deployment server, and the various runtime artifacts that consume it.

From a Data Vault modeling perspective, the mined FK structure classifies this table as hub-leaning — it holds the durable business key (PUBLICATION_ID) and acts as the anchor point from which multiple dependent satellite and link relationships radiate. This classification is a heuristic suggestion; in a canonical Data Vault design, PUBLICATION_ID would serve as the hub key, while mutable attributes such as EXPORT_STATUS and PUBLISHED would reside in satellite tables.

Key Information Stored

The table contains 46 documented columns. The most significant are:

• PUBLICATION_ID — Surrogate primary key, enforced by CZ_MODEL_PUBLICATIONS_PK and the unique index CZ_MODEL_PUBLICATIONS_U1. This is the definitive business-key candidate and the join anchor for all dependent tables.
• MODEL_ID — Foreign key to CZ_DEVL_PROJECTS, identifying the source development model that was published.
• SERVER_ID — Foreign key to CZ_SERVERS, indicating the target runtime server for the publication.
• UI_DEF_ID — Foreign key to CZ_UI_DEFS, linking the model to its user-interface definition.
• ORGANIZATION_ID — Operating unit context for the publication.
• TOP_ITEM_ID and PRODUCT_KEY — Identifiers for the top-level configurable item and its product key.
• PUBLICATION_MODE — Indicates the mode of publication (e.g., local versus remote).
• APPLICABLE_FROM / APPLICABLE_UNTIL — Effective date range governing when the publication is active.
• EXPORT_STATUS and PUBLISHED — Lifecycle indicators reflecting whether the model has been exported and successfully published.
• DELETED_FLAG and DISABLED_FLAG — Logical deletion and disabling markers that preserve referential history.
• MODEL_LAST_STRUCT_UPDATE / MODEL_LAST_LOGIC_UPDATE / MODEL_LAST_UPDATED — Timestamps tracking structural, logic, and overall model changes.
• SOURCE_TARGET_FLAG, REMOTE_PUBLICATION_ID, SOURCE_MODEL_ID, SOURCE_UI_DEF_ID — Fields supporting multi-server and migration scenarios where a publication is derived from a source publication.
• OBJECT_TYPE / OBJECT_ID / PAGE_LAYOUT / CONTAINER — Presentation-layer attributes defining how the model renders.
• CONC_PROG_REQ_ID — Links the publication to the concurrent program request that generated it.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and USER_STR01–04 / USER_NUM01–04 descriptive flexfield segments.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include identifying which models are published to a given server, auditing publication history, and reconciling development models against their published counterparts.

• List all active publications for an organization:
  SELECT publication_id, model_id, top_item_id, export_status FROM cz_model_publications WHERE organization_id = :org_id AND deleted_flag = 'N' AND applicable_until IS NULL;
• Publications by server and UI definition: join to CZ_SERVERS and CZ_UI_DEFS on SERVER_ID and UI_DEF_ID to enumerate deployment targets.
• Audit recent publishing activity: filter on CREATION_DATE or MODEL_LAST_UPDATED within a date range to trace recent changes.
• Migration tracking: query MIGRATION_GROUP_ID, MIGRATION_TGT_FOLDER, and MIGRATION_TGT_PATH to follow models moved between environments.
• Remote publication lineage: use SOURCE_TARGET_FLAG, SOURCE_MODEL_ID, and REMOTE_PUBLICATION_ID to reconstruct the source-to-target publication chain.
• Export status reporting: group by EXPORT_STATUS and PUBLISHED to produce operational dashboards of incomplete or failed exports.

Related Objects

The following tables participate in documented FK relationships with CZ_MODEL_PUBLICATIONS:

• CZ_DEVL_PROJECTS — referenced via MODEL_ID; supplies the source development model.
• CZ_SERVERS — referenced via SERVER_ID; identifies the deployment server.
• CZ_UI_DEFS — referenced via UI_DEF_ID; provides the user-interface definition.
• CZ_PB_CLIENT_APPS — child table referencing PUBLICATION_ID; tracks client-application associations.
• CZ_PB_LANGUAGES — child table referencing PUBLICATION_ID; manages language-specific publication content.
• CZ_PB_MODEL_EXPORTS — child table referencing PUBLICATION_ID; records export operations for each publication.
• CZ_PUBLICATION_USAGES — child table referencing PUBLICATION_ID; captures where and how each publication is consumed at runtime.

Together these relationships place CZ_MODEL_PUBLICATIONS at the hub of the Configurator publishing model, connecting development artifacts, deployment infrastructure, presentation definitions, and downstream runtime consumers.