Results for “ddd_model_attribute_values”

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

Overview

DDD_MODEL_ATTRIBUTE_VALUES is a table in the DDD schema, owned by the CADView-3D product within Oracle EBS 12.1.1 and 12.2.2. It stores the actual attribute values assigned to 3D models maintained in the CADView-3D catalog. Where DDD_MODEL_ATTRIBUTE_NAMES defines the metadata (the attribute definitions themselves), DDD_MODEL_ATTRIBUTE_VALUES holds the per-model, per-attribute data points, making it the primary repository for the extended descriptive information attached to each model record.

The table is documented with 15 columns and a primary key constraint DDD_MODEL_ATTRIBUTE_VALU_PK on VALUE_ID. A second documented key, SYS_C00140155, also references VALUE_ID, indicating the same surrogate key participates in more than one uniqueness constraint. Based on the foreign key structure — two references to parent tables (DDD_MODEL_CATALOG and DDD_MODEL_ATTRIBUTE_NAMES) — the heuristic Data Vault classification for this object is link. This is a modeling suggestion: the table resolves the many-to-many relationship between models and attribute definitions, with attribute values stored as an effect of that association.

Key Information Stored

The most significant columns are:

• VALUE_ID — Surrogate primary key, uniquely identifying each attribute value row. Documented as part of both the named PK constraint and SYS_C00140155.
• MODEL_ID — Foreign key to DDD_MODEL_CATALOG, identifying the model to which the value belongs. This is a business-key candidate for the model side of the link.
• ATTRIBUTENAMEID — Foreign key to DDD_MODEL_ATTRIBUTE_NAMES, identifying which attribute definition the value satisfies.
• OBJECTID — Identifier linking the value to a specific object or subcomponent within the model.
• STRINGVAL, LONGSTRINGVAL, HUGESTRINGVAL — Character-based value storage at increasing capacity tiers.
• INTVAL, INT64VAL, SHORTVAL, BYTEVAL — Numeric and small-range value storage.
• FLOATVAL, DOUBLEVAL — Floating-point numeric value storage.
• DATEVAL — Date-typed value storage.
• BINARYVAL — Binary value storage for non-textual attribute data.

The family of typed value columns (BYTEVAL through BINARYVAL) indicates a generic attribute-value schema in which the column selected depends on the data type declared in DDD_MODEL_ATTRIBUTE_NAMES.

Common Use Cases and Queries

Typical reporting involves pivoting attribute values for a given model by joining to the attribute name definitions:

• Listing all attribute values for a model: SELECT v.* FROM ddd.ddd_model_attribute_values v WHERE v.model_id = :model_id
• Resolving attribute names: SELECT n.attribute_name, v.stringval FROM ddd.ddd_model_attribute_values v, ddd.ddd_model_attribute_names n WHERE v.attributenameid = n.attributenameid AND v.model_id = :model_id
• Type-aware extraction: filtering on the appropriate typed column (for example INTVAL or DOUBLEVAL) once the attribute's declared type is known from the names table.
• Catalog enrichment reports that combine DDD_MODEL_CATALOG descriptive fields with the full attribute set for export or audit.

Related Objects

• DDD_MODEL_CATALOG — referenced via MODEL_ID; the parent model record. Join key: DDD_MODEL_ATTRIBUTE_VALUES.MODEL_ID = DDD_MODEL_CATALOG.MODEL_ID.
• DDD_MODEL_ATTRIBUTE_NAMES — referenced via ATTRIBUTENAMEID; supplies attribute definitions and data types. Join key: DDD_MODEL_ATTRIBUTE_VALUES.ATTRIBUTENAMEID = DDD_MODEL_ATTRIBUTE_NAMES.ATTRIBUTENAMEID.
• DDD_MODEL_ATTRIBUTE_VALU_PK — the primary key constraint governing row uniqueness on VALUE_ID.
• SYS_C00140155 — the additional uniqueness constraint documented on VALUE_ID.

All relationships are enforced through the two documented foreign keys; no additional dependent objects are recorded in the supplied metadata.