1 1 1 1 1 Rating 0% (0 Votes)

As you can imagine, INTTYPE is just a presentation of DATATYPE in internal SAP format in most of cases. I wrote most of cases because it can also say if the field in internal table is a reference to other type, or for example a table.

Just like DATATYPE, you don’t need to fill this field manually, when you’ll leave it empty, ALV grid will automatically setup a proper type according to referenced internal table field. But if you’ll have unstoppable need of filling it, then the behaviour of the column will be exactly the same like you would use DATATYPE field, means JUST, OUTPUTLEN, INTTYPE, INTLEN and DD_OUTLEN fields will be also field and the difference on the screen will be not that huge.

 

Figure 93 Fieldcatalog of the ZDEMO_AIN_CL37 for Internal ABAP type T

Possible internal ABAP types in NW 7.52 SP04

ABAP Type

Description

C

Character String

N

Character String with Digits Only

D

Date (Date: YYYYMMDD)

T

Time (Time: HHMMSS)

X

Byte Seq. (heXadecimal), in DDIC metadata also for INT1/2/4

I

Integer number (4-byte integer with sign)

b

1-byte integer, integer number <= 254

s

2-byte integer, only for length field before LCHR or LRAW

P

Packed number

F

Floating point number to accuracy of 8 bytes

g

Character string with variable length (ABAP type STRING)

y

Byte sequence with variable length (ABAP type XSTRING)

u

Structured type, flat

v

Structured type, deep

h

Table type

V

Character string (old Dictionary type VARC)

r

Reference to class/interface

l

Reference to data object

a

Decimal Floating Point Number, 16 Digits

e

Decimal Floating Point Number, 34 Digits

j

Static Boxed Components

k

Generic Boxed Components

z

Node Line for Stuctured Objects

8

Whole Number (8-Byte Integer with Sign)

Table 3 Possible ABAP data types in NW 7.52 SP04