SQL Data Types
To be able to transfer the query results, PCo uses SQL Data Types. These SQL data types need to be converted to ABAP Data Types for integration with the Business Suite.
The table provides an overview of the supported SQL data types:
|
PCo Code |
SQL Data Type |
Data Type Description |
Size in Bytes |
ABAP Data Type |
|
-7 |
BIT |
Single bit value; value range: 0,1 |
1 byte |
INT1 |
|
-6 |
TINYINT |
Very small number; value range: -128 to 127 |
1 byte |
INT2 |
|
5 |
SMALLINT |
Small number; value range: -32,768 to 32,767 |
2 bytes |
INT2 |
|
4 |
INTEGER |
Whole number; value range: -2,147,483,648 to 2,147,483,647 |
4 bytes |
INT4 |
|
6 |
FLOAT |
Floating point; value range: -1.7E308 to 1.7E308 |
8 bytes floating points |
f or FTPT |
|
7 |
REAL |
Floating point; -3.4E38 to 3.4E38 |
4 bytes floating points |
f or FTPT |
|
8 |
DOUBLE |
Large floating point value; value range: -1.7E308 to 1.7E308 |
8 bytes floating points |
f or FTPT |
|
1 |
CHAR |
UTF-8 encoded String with a length up to 254 Structure: 1 byte length + n character |
1 byte + n UTF-8 sequences |
SSTRING |
|
12 |
VARCHAR |
UTF-8 encoded String with a length up to 65,536 Structure: 2 byte length + n character |
2 byte + n UTF-8 sequences |
STRING |
|
-1 |
LONGVARCHAR |
UTF-8 encoded String with a length up to 4,294,967,296 Structure: 4 byte length + n character |
4 byte + n UTF-8 sequences |
STRING |
|
91 |
DATE |
Date/time structure represented by the number of milliseconds since January 1, 1970 UTC. |
8 bytes |
Conversion to the format d required |
|
92 |
TIME |
Date/time structure represented by the number of milliseconds since January 1, 1970 UTC. |
8 bytes |
Conversion to the format t required |
|
93 |
TIMESTAMP |
Date/time structure represented by the number of milliseconds since January 1, 1970 UTC. |
8 bytes |
Conversion to the format TIMESTAMPL required |
|
16 |
BOOLEAN |
Boolean value; value range: false, true |
1 byte |
Boole_D |