Why or How Does the Integration Determine the Data Type Size When the Table Is Built?
Last updated on JUNE 30, 2016
Applies to:Oracle Demantra Demand Management - Version 188.8.131.52 and later
Information in this document applies to any platform.
When we built our Integration Interface data level profile, a table BIIO_IMPORTDATA_PROMOLDHI was created with a field from a series we selected.
The field was created as a data type of VARCHAR2(100 CHAR).
The PROMOTION_DATA table contains this column as data type VARCHAR2(500 BYTE) which is loaded from the staging BIIO table when executed via Workflow Management.
The issue is the BIIO table data type created is to small at 100 CHAR; so we increased it to 255 CHAR needed for input. This worked fine in testing and populated the PROMOTION_DATA table correctly.
1. Why or how does the integration determine the data type size when the table is built?
2. Why does our crosstab worksheet only allow 100 CHAR for manual entry only (it always has)?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms