This section describes the properties that OracleAppsODA generates for each attribute. For more information about the attributes, see Business object attribute properties.
OracleAppsODA obtains the value of the attribute's name from the column name in the database table, view, stored procedure, or synonym/nickname.
When setting the type of an attribute, OracleAppsODA converts the data type of a column in the table or view to a corresponding Business Object type. This conversion is done in two steps. First, the data type in the database is converted to a JDBC type. Then, the JDBC type is converted to Business Object type. The first conversion is done by the JDBC driver that you are using. Please refer to the JDBC specification (2.0 and above) for details on individual database type mapping to a JDBC type. Table 14 shows the conversion from the JDBC Type to the corresponding Business Object type.
JDBC type | Business Object Type |
---|---|
BIT |
BOOLEAN |
CHAR |
STRING |
VARCHAR |
STRING |
LONGVARCHAR |
STRING |
INTEGER |
INTEGER |
NUMERIC |
INTEGER |
SMALLINT |
INTEGER |
TINYINT |
INTEGER |
BIGINT |
INTEGER |
DATE |
DATE |
TIME |
DATE |
TIMESTAMP |
DATE |
DECIMAL |
STRING |
DOUBLE |
DOUBLE |
FLOAT |
DOUBLE |
REAL |
FLOAT |
BINARY |
STRING,add BYTEARRAY=TRUEto AppSpecificInfo |
VARBINARY |
STRING,add BYTEARRAY=TRUEto AppSpecificInfo |
OracleAppsODA sets the cardinality of all simple attributes to 1.
OracleAppsODA obtains the length of a string from the length specified for the varchar, char, or text data type.
If the column is a primary key in the table, OracleAppsODA marks it as a key attribute. However, if a view, stored procedure, or synonym/nickname, instead of a table, is selected as the source node to generate Business Objects, OracleAppsODA does not mark the column as a key attribute. In this case, the key attribute needs to be set manually.
OracleAppsODA does not set the IsForeignKey property. You can set it in Business Object Designer Express.
If a field is designated not null in the table, view, stored procedure, or synonym/nickname, OracleAppsODA marks it as a required attribute. However, OracleAppsODA does not mark the key field as required because there may be a sequence associated with it, or it may be an identity column.
OracleAppsODA includes two parameters for the AppSpecificInfo property at the attribute level. The syntax of the specified parameters are:
CN=ColumnName
where ColumnName is the name of the column in the database table, view, stored procedure, or synonym/nickname associated with the specific attribute.
BYTEARRAY=true|false
OracleAppsODA recognizes columns with binary data and creates an attribute of type String with an AppSpecificInfo property of BYTEARRAY=true.