Get Example source ABAP code based on a different SAP table
WRITE, Predefined Formats The predefined output format of the statements WRITE ... TO and WRITE depends on the data type and user-specific default settings. It is partly dependent on the length available. In the case of WRITE ... TO, this is the length of the target variable; in the case of WRITE, this is the output length. If the length is not sufficient, the variables are truncated as specified in the predefined truncation behavior. ITOC
Alignment The following table shows the predefined alignment for the built-in ABAP types. Data TypeAlignment Numeric data typesRight-aligned Character-like data types Left-aligned Byte-like data typesLeft-aligned Date types/time typesLeft-aligned
Example ABAP Coding
The text field text is padded with blanks on the left by WRITE. ABEXA 01411 ABAP_EXAMPLE_END
General Format
Numeric Data Types
In the numeric data types (b, s), i, int8, and p, the last place on the right is reserved for the sign (this also applies to b, even though these numbers are always positive). Here, negative values are given a minus - in the result and positive values a blank. The thousands separators defined in the user master record are inserted if the available length is sufficient. If data type p is used, decimal places are respected regardless of the program property fixed point arithmetic and a decimal separator is inserted if necessary (see below).
If the available length is sufficient, decimal floating point numbers with the data types decfloat16 and decfloat34 are displayed in mathematical notation and with the thousands separators defined in the user master record. If the available length is not sufficient for the decimal places of the number, it is rounded commercially to the number of positions available. If the available length is not sufficient for the places in front of the decimal separator, the value is formatted in scientific notation without thousands separators. Negative numbers are prefixed with a minus sign in both cases. An exponent is always displayed with a plus/minus sign, but without leading zeros. Trailing zeros in the decimal places are not shown.
A binary floating point number with the type f is formatted in scientific notation with a preceding plus/minus sign (empty if the number is positive), a place before the decimal separator, a maximum of 16 decimal places, the character E, and a three-figure exponent, including a plus/minus sign. For, information about the number format with respect to decimal and thousands separators, see.
Latest notes:
If there is not enough space available to display a number using these rules, an exception is raised for decimal floating point numbers only. Other numeric types are truncated and flagged with *.
For the data types b and s, it should be noted that the predefined output lengths for lists ignore the place that is reserved for the plus/minus sign, which can lead to unexpected results. ABAP_HINT_END
Example ABAP Coding
If nothing else is defined in the formatting settings, the example produces the output shown below. It should be noted that the place on the far right is reserved for the sign for type i. ABEXA 01412 nbsp 123,456
nbsp 123,456
nbsp1.2345600000000E+05 ABAP_EXAMPLE_END
Character-Like Data Types Data objects of character-like data types are passed without formatting. In the case of character-like data types with a fixed length (c, n), trailing blanks are cut off. The content of text strings with the type string is passed completely.
Example ABAP Coding
After the assignment, the variable text contains the left-aligned character string Hello World!. ABEXA 01413 ABAP_EXAMPLE_END
Byte-Like Data Types Byte-like data objects are formatted in hexadecimal format, where one byte is represented by two characters.
Example ABAP Coding
After the assignment, the variable text contains the left-aligned character string 48656C6C6F20576F726C. ABEXA 01414 ABAP_EXAMPLE_END
Date Types and Time Types The content of a date field or time field of type d or t or the content of a time stamp field of type utclong is formatted in accordance with the rules for date and time formats listed below. Here, the content is not checked for the character-like types d and t.
Example ABAP Coding
If nothing else is defined in the formatting settings, the example produces the output shown below. ABEXA 01415 XX/XX/XXXX
XX:XX:XX ABAP_EXAMPLE_END
Number, Date, and Time Formats Apart from one exception, numbers, date formats, and time formats are determined by the current formatting setting of the language environment, which can be set using SET COUNTRY.
Number Output The predefined number format for the output of numeric fields, that is, decimal and thousands separators, depends on the current formatting setting. The possible formats correspond to the country-specific number formats. Thousands separators are inserted only if the length is sufficient.
Example ABAP Coding
If nothing else is defined in the formatting settings, the example produces the output shown below. ABEXA 01416 1,000,000
1,000,000 ABAP_EXAMPLE_END
Date Output The predefined date format for the output of date fields of type d depends on the current formatting setting. The possible formats correspond to the country-specific date formats. The respective separators are inserted only if the length is sufficient. A date field is formatted regardless of its content.
Example ABAP Coding
If nothing else is defined in the formatting settings, the example produces the format shown below. ABEXA 01417 04/04/2019
04.04.2019 ABAP_EXAMPLE_END
Time Output Time fields of type t are by default always displayed in 24-hour format with colons as separators. Separators are inserted only if the length is sufficient. To use a 12-hour format defined in the current formatting settings, the addition ENVIRONMENT TIME FORMAT must be used. A time field is formatted regardless of its content.
Example ABAP Coding
The example produces the format shown below. ABEXA 01418 13:07:35
130.735 ABAP_EXAMPLE_END
Time Stamp Output The output of time stamp fields with the time stamp type utclong and time stamps in packed numbers where the addition TIME ZONE is specified is constructed from a date and time output in their current formats, separated by a blank.
The date format is taken from the current formatting setting for time stamp fields with the type utclong and for time stamps in packed numbers.
The time format is determined as follows:
The time format is taken from the current formatting settings for time stamp fields with the type utclong. In the case of initial time stamp fields, the target area is padded with blanks. A time stamp field whose value is greater than or equal to the last second or between 9999-12-31 23:59:59.0000000 and 9999-12-31 23:59:59.9999999 is represented as 9999-12-31 23:59:59.9999999.
In the case of time stamps in packed numbers, the time format is always the 24 hour format with colons as separators. The 12 hour time format is not possible. In front of second fractions, the decimal separator is always a comma (,). An initial packed number is considered invalid by the addition TIME ZONE and its output is *00.00.0000 00:00:00.000000.
Latest notes:
The addition TIME ZONE must be specified for time stamp fields with the type TIME ZONE.
Time stamps in packed numbers for which the addition TIME ZONE is not specified are handled as data type p. ABAP_HINT_END
Example ABAP Coding
If nothing else is defined in the formatting settings, the example creates the format shown below. ABEXA 01419 04.04.2019 12:42:48.2006610
