Results for “last_struct_update”

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

Overview

CZ_DEVL_PROJECTS is the master table in the Oracle EBS Configurator (CZ) module that stores the top-level definition of every configurator model and development project authored in the Oracle Configurator Developer repository. Each row represents one configurator model — the container that binds together the UI definition, rule structure, functional component specs, expressions, grid definitions, and publication state used by the Configurator runtime engine. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the CZ schema and is documented as CZ.CZ_DEVL_PROJECTS with 37 columns and status VALID.

From a Data Vault modeling perspective, the heuristic classification inferred from the foreign key structure is hub-leaning. The table behaves as a business hub: it carries the durable identity of a configurator model (DEVL_PROJECT_ID) and is referenced by a wide fan-out of dependent tables holding rules, UI layouts, expressions, publications, and import staging records. Satellite attributes such as version, effective dates, and publication status would typically be split into separate satellite tables in a formal Data Vault design, while the numerous child tables would be modeled as links or satellites keyed to this hub.

Key Information Stored

The surrogate primary key is DEVL_PROJECT_ID, also enforced through the CZ_DEVL_PROJECTS_PK and CZ_DEVL_PROJECTS_UPK unique indexes. It is the single identifier propagated to all dependent Configurator tables. Notable descriptive and operational columns include:

• NAME — the developer-assigned model/project name used for identification in the Configurator Developer UI.
• VERSION — the revision level of the model definition, relevant to checkout and publish cycles.
• DESC_TEXT — free-form description of the model's purpose.
• INTL_TEXT_ID — foreign key to CZ_INTL_TEXTS, providing the translatable text used for the model's name/description.
• PUBLISHED — indicates whether the model has been published for use by the Configurator runtime.
• CHECKOUT_USER and CHECKOUT_TIME — identify the developer currently holding the model checked out, supporting concurrency control in Oracle Configurator Developer.
• ORIG_SYS_REF — reference back to the originating source of the model when imported or copied.
• MODEL_TYPE, PRODUCT_KEY, ORGANIZATION_ID, and INVENTORY_ITEM_ID — link the model to the inventory item and organization context for which it is authored.
• PERSISTENT_PROJECT_ID and MAX_PERSISTENT_REC_ID — support persistence and identifier generation across model versions.
• CHECKOUT_USER/LAST_STRUCT_UPDATE/LAST_LOGIC_UPDATE — timestamps tracking structural versus logical changes to the model.
• DELETED_FLAG, EFF_FROM, EFF_TO, CREATION_DATE, and LAST_UPDATE_DATE — standard EBS audit and soft-delete/effective-dating columns.
• BOM_CAPTION_RULE_ID, NONBOM_CAPTION_RULE_ID, and their associated text IDs — reference rules and text used when rendering BOM and non-BOM captions.

The surrogate key is DEVL_PROJECT_ID; no separate business-key column is documented beyond the unique index on the same column, so external systems must rely on NAME plus version or on ORIG_SYS_REF for reconciliation.

Common Use Cases and Queries

Typical use cases involve inventory of authored models, tracking publication state, auditing checkouts, and migrating or importing models between environments. For example, to list all published models with their owning organization:

• SELECT p.DEVL_PROJECT_ID, p.NAME, p.VERSION, p.PUBLISHED, p.ORGANIZATION_ID, p.INVENTORY_ITEM_ID FROM CZ.CZ_DEVL_PROJECTS p WHERE p.DELETED_FLAG = 'N' AND p.PUBLISHED = 'Y';
• Identify models currently checked out by a developer: SELECT NAME, CHECKOUT_USER, CHECKOUT_TIME FROM CZ.CZ_DEVL_PROJECTS WHERE CHECKOUT_USER IS NOT NULL;
• Trace a model to its runtime definition by joining to CZ_PS_NODES and CZ_RULES on DEVL_PROJECT_ID.
• Report on models linked to a specific inventory item across organizations using INVENTORY_ITEM_ID and ORGANIZATION_ID.

Reporting queries should always filter on DELETED_FLAG = 'N' and consider EFF_FROM/EFF_TO where effective dating is enforced. Because the table is heavily referenced, joins to child tables should be driven from DEVL_PROJECT_ID to leverage indexed access on the primary key.

Related Objects

The FK relationship data shows a broad fan-out of dependent Configurator tables, confirming the hub role of this object:

• CZ_INTL_TEXTS — referenced by CZ_DEVL_PROJECTS.INTL_TEXT_ID; provides translatable name/description text.
• CZ_PS_NODES — references this table via both DEVL_PROJECT_ID and REFERENCE_ID; holds the model's node/PS structure.
• CZ_RULES and CZ_RULE_FOLDERS — reference DEVL_PROJECT_ID; store the model's logic rules and their folder organization.
• CZ_UI_DEFS, CZ_GRID_DEFS, and CZ_EXPRESSIONS — reference DEVL_PROJECT_ID; define the model's user interface, grid layouts, and expressions.
• CZ_FUNC_COMP_SPECS — references DEVL_PROJECT_ID; holds functional component specifications for the model.
• CZ_MODEL_PUBLICATIONS and CZ_MODEL_REF_EXPLS — reference this table via MODEL_ID; track publication and reference explanations.
• CZ_PB_MODEL_EXPORTS — references MODEL_ID and ROOT_MODEL_ID; supports model export between environments.
• CZ_XFR_PROJECT_BILLS — references MODEL_PS_NODE_ID; used when transferring project bills.
• CZ_IMP_DEVL_PROJECT, CZ_IMP_RULES, and CZ_IMP_PS_NODES — staging tables that reference DEVL_PROJECT_ID during model import.
• CZ_LCE_HEADERS and CZ_RP_ENTRIES — reference DEVL_PROJECT_ID and OBJECT_ID respectively, supporting configuration-related processes and report entries.

Collectively these relationships establish CZ_DEVL_PROJECTS as the central anchor for the Oracle Configurator model repository, and any query or integration touching configurator model metadata should begin at this table.