SQL Server data item mapping bug?


We're exploring the possible migration from AS400 to SQL Server. In the creation of SQL Server tables, data items configured as Numeric data types in the Data Dictionary are being created with float data types in SQL Server (i.e. WADOCO in the F4801 table). According to the JDE Data Dictionary guide on page 22, a Numeric data type represents a long integer. A long integer should map to the bigint SQL Server data type and not a float. The evils of float data types in SQL Server are well documented and a float is most definitely not equivalent to a long integer and certainly should not be used as an identifying field. Is this a bug or is there a rational explanation for why Numeric data types are being mapped to floats in SQL Server?