Results for “ddd_model_catalog”

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

Overview

The DDD_MODEL_CATALOG table is a repository object belonging to the DDD – CADView-3D product, a legacy Oracle E-Business Suite module that provided 3D CAD visualization and model management capabilities. Its documented purpose is to store models (3dx) and information related to those models. The table therefore acts as the master registry for each 3D model known to the CADView-3D application, holding both descriptive metadata and a set of generic business-key attributes.

In Oracle EBS 12.1.1 and 12.2.2, DDD_MODEL_CATALOG is documented in the ETRM as not implemented in this database. This indicates that in a standard installation the table is not created, since CADView-3D is designated obsolete. It will only exist where the legacy product was explicitly deployed or where remnants of an earlier upgrade remain. Environments that still carry the table should treat it as a deprecated, read-only legacy object rather than a supported integration point.

The metadata's heuristic Data Vault classification is hub-leaning. Modeling guidance would therefore suggest treating DDD_MODEL_CATALOG as a hub, with MODEL_ID as the business key that anchors the surrounding attribute tables. No satellite column set is formally documented, so the descriptive attributes (name, status, description) can be considered hub-adjacent descriptive payload rather than a separate satellite.

Key Information Stored

The table is documented with 19 columns. The principal columns and their roles are as follows.

• MODEL_ID — the primary key column, constrained by unique index DDD_MODEL_CATALOG_N and by the system-named constraint SYS_C00140144. It uniquely identifies each model and is the join key referenced by all related tables.
• NAME — the descriptive name of the model, the most likely business-key candidate alongside MODEL_ID.
• DESCRIPTION — free-text description of the model.
• VERSION and STREAMGUID — model version and the stream GUID used to track the model record across copies or publishing streams.
• PUBLISHSTATUS — indicates the publication state of the model within the CADView-3D workflow.
• CREATEUSER, CREATEDATE, LASTMODUSER, LASTMODDATE — the standard Oracle EBS who-columns recording creation and last modification audit information.
• BOMCREATESTATUS and BATCHBOMCREATE — status and batching flags governing generation of bills of material from the model.
• PK1_VALUE through PK5_VALUE and PK_TYPE — a generic, type-tagged set of primary key values that allow the catalog entry to be linked to external or upstream business entities.
• TOP_BILL_SEQUENCE_ID — identifies the top-level bill sequence associated with the model.

The surrogate primary key MODEL_ID is distinct from the business-key candidate recorded in the DDD_MODEL_CATALOG_N unique index, which is also MODEL_ID; the generic PK1_VALUE–PK5_VALUE columns provide additional, loosely typed business-key linkage.

Common Use Cases and Queries

Because the module is obsolete, the practical use cases are historical reporting, data migration, and cleanup verification. A typical query retrieves the model header and its audit context:

• SELECT MODEL_ID, NAME, VERSION, PUBLISHSTATUS, LASTMODDATE FROM DDD_MODEL_CATALOG ORDER BY LASTMODDATE DESC;
• Join to dependent tables to reconstruct a model and its parts: SELECT c.NAME, o.* FROM DDD_MODEL_CATALOG c JOIN DDD_MODEL_OBJECTS o ON o.MODEL_ID = c.MODEL_ID;
• Attribute reporting across models: SELECT c.MODEL_ID, a.ATTRIBUTE_NAME, v.ATTRIBUTE_VALUE FROM DDD_MODEL_CATALOG c JOIN DDD_MODEL_ATTRIBUTE_VALUES v ON v.MODEL_ID = c.MODEL_ID JOIN DDD_MODEL_ATTRIBUTE_NAMES a ON a.MODEL_ID = c.MODEL_ID;
• Reconciliation of generic keys: filtering on PK_TYPE and PK1_VALUE to map catalog entries back to source business objects.
• Migration and decommissioning checks counting rows per PUBLISHSTATUS or BOMCREATESTATUS.

Related Objects

The foreign-key metadata documents the following dependent objects, all joined on MODEL_ID.

• DDD_MODEL_ATTRIBUTE_VALUES — child table keyed by MODEL_ID, storing attribute values for each model (listed twice in the documented FK set).
• DDD_MODEL_ATTRIBUTE_NAMES — child table keyed by MODEL_ID, holding attribute name definitions.
• DDD_MODEL_OBJECTS — child table keyed by MODEL_ID, storing the individual objects that compose a model.

These three children make DDD_MODEL_CATALOG the hub of the CADView-3D data model. No dependent views or public APIs are documented in the ETRM excerpt. Where the table remains in a production instance, it should be treated as a legacy hub whose dependents must be migrated or purged together.