This dialog box displays the properties of a table, which is part of Relational Models.
You can click Naming Rules to apply the current naming rules to specified types of objects related to this table definition.
For example,
if you applied naming rules to Check Constraints
and if a table-level constraint was named PRODUCTS_Check,
the name would be changed to PRODUCTS_CK (if the table name was PRODUCTS).

Name of the table.
Long name in the form: relational-model-name:table-name
Controls whether the table will be considered during reverse engineering operations.
If this option is disabled,
this table and its properties are not considered when the relational model is
reverse engineered into the logical model.
Name of the primary key of the table.
Classification type, from the list defined in the General Options.
Examples: Fact, Dimension, Logging, Summary, Temporary.
For a table classified as Temporary, you can specify a scope,
such as Session or Dimension.
For a table with a column of type SDO_GEOMETRY,
creates the spatial index and inserts the appropriate entry in the SER_SDO_GEOM_METADATA view.
For a structured type with Reference disabled,
or for a structured type applied to a table,
controls whether a substitutional structured type generation in the DDL is allowed.

Lists the columns currently defined for the table.
The properties for each column include its name and data type,
and whether it is the primary key (PK), a foreign key (FK), or a required field (M, for mandatory).
To add a column, click the Add (+) icon;
to delete a column, select it and click the Remove (X) icon;
to view the properties of a column, double-click in the cell to the left of the name.

Lists the indexes currently defined for the table.
The properties for each index include its name,
its state, and whether to generate the index when the table is created.
To add an index, click the Add (+) icon;
to delete an index, select it and click the Remove (X) icon;
to view the properties of an index, double-click in the cell to the left of the name.

Lists the foreign keys currently defined for the table.
The properties for each key include its name, its parent table, its delete rule,
and whether to generate a foreign key constraint for it when the table is created.

For each column based on a structured data type that has attributes,
lists each attribute (in column-name.attribute-name format).
For each attribute, you can specify whether it is the primary key (PK),
a foreign key (FK), or a required field (M, for mandatory).

Displays any OID (object identifier) settings and primary key columns based on a structured type.
Indicates whether the OID is the primary key of the table.
User Defined or System Generated: Indicates whether the OID is user-defined or generated by the database system.
Displays the column name and data type for primary key columns that are based on a structured type.

| No | キーワード | 意味 |
| 1 | Volumes: Minimum | Minimum data volume for the table. |
| 2 | Volumes: Expected | Expected or typical data volume for the table. |
| 3 | Volumes: Maximum | Maximum data volume for the table. |
| 4 | Growth Rate: Percent: | Expected growth rate percentage for the table, for each period as specified in the next field. |
| 5 | Growth Rate: Year/Month/Day | The period (year, month, or day) to which the expected growth rate applies. |
| 6 | Normal Form | The required normal form (database normalization) for the table: None, First, Second, Third, or Fourth. |
| 7 | Adequately Normalized? | YES indicates that the model is sufficiently normalized. |
| NO indicates that the model is not sufficiently normalized, and that additional normalization may be required on the relational model. |

Displays any currently defined Oracle Spatial properties,
each being a data column (type SDO_GEOMETRY or a function that evaluates to an SDO_GEOMETRY object) in the table.
You can double-click an item's name to display its Spatial Definition Properties.
Comment text to be included in database objects that are generated based on this modeling object.

Enables you to view and specify information to be used by Oracle Warehouse Builder for impact analysis.

Enables you to specify scripts to be run automatically at specified times or stages: before the table is dropped or renamed, before the table is created, after the table is created, and at the end of any script specified for the table.

Controls whether the text of the specified scripts is included into the DDL script for operations on the table.