Results for “ddd_model_attribute_names”

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

Overview

DDD_MODEL_ATTRIBUTE_NAMES is a table owned by the DDD schema and belongs to the CADView-3D product module within Oracle E-Business Suite (documented for 12.1.1 and applicable to 12.2.2). It stores the definitions of model attributes — the named characteristics that can be associated with 3D models registered in the CADView-3D catalog. In effect, it is the attribute dictionary for the CADView-3D data model: each row declares a single attribute (its name, type, and size) that can subsequently be populated with per-model values in the companion DDD_MODEL_ATTRIBUTE_VALUES table.

Based on the foreign key topology mined from the physical schema, the object is heuristically classified as hub-leaning in a Data Vault sense: it holds a stable, uniquely identified business concept (the attribute definition) referenced by dependent satellite-style tables. This classification is offered as a modeling suggestion only; the table is a conventional relational entity in the EBS schema, not an actual Data Vault construct.

Key Information Stored

The table is physically documented with five columns in ETRM 12.1.1. The most significant are:

• ATTRIBUTENAMEID — the surrogate primary key, enforced by the constraint SYS_C00140152. This is the identifier referenced by downstream tables and is the column most commonly used in joins.
• MODEL_ID — the foreign key pointing to DDD_MODEL_CATALOG, tying each attribute definition to a specific model in the catalog. This is the principal business-key candidate for scoping attributes to a model.
• ATTRIBUTENAME — the human-readable name of the attribute (for example, a dimension, material, or part characteristic). This is the descriptive label surfaced in reporting and UI screens.
• ATTRIBUTETYPE — the data type or category of the attribute (text, numeric, date, etc.), which governs how values are interpreted.
• ATTRIBUTESIZE — the declared size or precision of the attribute, used for validation and storage expectations.

The composite of MODEL_ID and ATTRIBUTENAME would typically serve as the natural (business) key ensuring an attribute name is unique per model, while ATTRIBUTENAMEID remains the technical surrogate referenced throughout the schema.

Common Use Cases and Queries

Typical usage centers on discovering which attributes are defined for a given model, resolving attribute IDs to their names in reports, and validating attribute definitions before inserting values.

• Listing all attributes for a model:
  SELECT ATTRIBUTENAMEID, ATTRIBUTENAME, ATTRIBUTETYPE, ATTRIBUTESIZE FROM DDD.DDD_MODEL_ATTRIBUTE_NAMES WHERE MODEL_ID = :model_id;
• Joining to the catalog to show model context:
  SELECT c.MODEL_ID, n.ATTRIBUTENAME, n.ATTRIBUTETYPE FROM DDD.DDD_MODEL_CATALOG c JOIN DDD.DDD_MODEL_ATTRIBUTE_NAMES n ON n.MODEL_ID = c.MODEL_ID;
• Resolving stored values to attribute names via DDD_MODEL_ATTRIBUTE_VALUES:
  SELECT v.ATTRIBUTENAMEID, n.ATTRIBUTENAME, v.ATTRIBUTEVALUE FROM DDD.DDD_MODEL_ATTRIBUTE_VALUES v JOIN DDD.DDD_MODEL_ATTRIBUTE_NAMES n ON n.ATTRIBUTENAMEID = v.ATTRIBUTENAMEID;

These queries support catalog browsing, attribute completeness audits, and reconciliation of model metadata against actual stored values.

Related Objects

• DDD_MODEL_CATALOG — parent catalog table; joined on DDD_MODEL_ATTRIBUTE_NAMES.MODEL_ID = DDD_MODEL_CATALOG.MODEL_ID.
• DDD_MODEL_ATTRIBUTE_VALUES — child values table; joins on DDD_MODEL_ATTRIBUTE_VALUES.ATTRIBUTENAMEID = DDD_MODEL_ATTRIBUTE_NAMES.ATTRIBUTENAMEID. This dependent table stores the actual per-model attribute data keyed to the definitions held here.

The asymmetric FK pattern — one parent (catalog) and one child (values) — establishes DDD_MODEL_ATTRIBUTE_NAMES as the central attribute-definition hub within the CADView-3D schema, mediating between model registration and model data.