Guidelines for adding custom columns to a default table

You can add custom columns to a default table by following a set of guidelines.

  • You can add columns to tables only as specified in the ERDs.
  • You cannot remove or modify any default columns.
  • You can add columns either before or after installing the application.
  • For all columns that are added to an application database table, it is recommended to use Nullable=true except for the following fields:
    • Primary Key Attributes
    • Entity Relationships
    If column is nullable, you do not need to provide a default value. However, if column is not nullable, you must provide a default value that is relevant to the column.
  • You cannot add columns with a data type of Long.
  • When you use application components (such as events and user exits) that read in a map or publish a map (such as the GetOrderNoUE user exit), extended fields in the maps are prefixed with Extn_.
  • When using non-ASCII characters, ensure that the Name and XMLName attributes are passed where appropriate.
Note: In DB2® database, the Date data type is generated as TIMESTAMP.