SAP ST OPTION FORMAT

Get Example source ABAP code based on a different SAP table
  SAP Help

• format ABAP_ST_ELEMENT
• decimals ABAP_ST_ELEMENT
• regime ABAP_ST_ELEMENT
• noError ABAP_ST_ELEMENT

ABAP_ST - option, Mapping Rules for Elementary Types

ABAP_SYNTAX
... option='$[format(fmt)$]$[,decimals(dec)$]$[ ,regime(num$|char$|bin)$]$[,noError$]'

ABAP Addition
1 ... format(fmt) ...
2 ... decimals(dec) ...
3 ... regime(num$|char$|bin) ...
4 ... noError ...

What does it do?
Specifies mapping rules for elementary types.

format can be used to specify different formats fmt.

decimals can be used to affect the decimal places of numeric values and of time stamps.

regime can be used to force numeric, character-like, or byte-like handling.

noError can be used to prevent exceptions for invalid values for some ABAP types and for some of the formats.

ABAP Addition

What does it do?
The format option can be used to do the following:

Specify formats fmt based on XML schema data types to create the corresponding XML representation or JSON representation from ABAP-specific representations of specific elementary values and vice versa.

Specify other formats fmt to convert ABAP data to framework-specific representations that do not comply with the standard asXML representation and vice versa.
The following table shows the possible formats fmt, the ABAP types and representations where they can be used, and the associated XML representations and JSON representations. fmtABAP TypeABAP RepresentationXML RepresentationJSON Representation
booleanc, length 1X, blanktrue, falsetrue, false
hexx, xstring0123456789ABCDEF 0123456789ABCDEF0123456789ABCDEF
durationt125814PT12H58M14S PT11H24M22S
dateTimeutclong, lbr TIMESTAMP, lbr TIMESTAMPL2014-12-12 11:24:22.7717230, lbr 20141212112422, lbr 20141212112422.7717230 2014#12#12T11:27:22.7717230Z, lbr2014#12#12T11:27:22Z, lbr 2014#12#12T11:27:22.771723Z 2014#12#12T11:27:22.7717230Z , lbr 2014#12#12T11:27:22Z, lbr 2014#12#12T11:27:22.771723Z
dateTimeOffsetc, length 18 20141212113855+180 2014#12#12T11:38:55+03:002014#12#12T11:38:55+03:00
dateTimeOffsetutclong, lbr TIMESTAMP, lbr TIMESTAMPL2014-12-12 11:24:22.7717230, lbr 20141212112422, lbr 20141212112422.7717230 2014#12#12T11:27:22.7717230+00:00, lbr2014#12#12T11:27:22+00:00 , lbr 2014#12#12T11:27:22.771723+00:00 2014#12#12T11:27:22.7717230+00:00, lbr 2014#12#12T11:27:22+00:00 , lbr 2014#12#12T11:27:22.771723+00:00
dateTimeLocalc, length 14 20141212114245 2014#12#12T11:42:452014#12#12T11:42:45,
dateTimeLocalutclong, lbr TIMESTAMP, lbr TIMESTAMPL2014-12-12 11:24:22.7717230, lbr 20141212112422, lbr 20141212112422.7717230 2014#12#12T11:42:45.7717230, lbr 2014#12#12T11:42:45 lbr 2014#12#12T11:42:45.7717232014#12#12T11:42:45.7717230, lbr 2014#12#12T11:42:45, lbr 2014#12#12T11:42:45.771723
ticksd201412122014#12#12 /Date(1418342400000)/
ticksutclong, lbr TIMESTAMP, lbr TIMESTAMPL 2014-12-12 11:50:38.9922080, lbr20141212115038, lbr 20141212115038.9922080 2014#12#12T11:50:38.9922080Z, lbr 2014#12#12T11:50:38Z, lbr2014#12#12T11:50:38.992208Z /Date(1418383462771)/, lbr /Date(1418383462000)/, lbr /Date(1418383462771)/
ticksOffsetc, length 18 20141212115254+180 2014#12#12T11:52:54+03:00 /Date(1418383462000+0180)/
ticksOffsetutclong, lbr TIMESTAMP, lbr TIMESTAMPL2014-12-12 11:24:22.7717230, lbr 20141212112422, lbr 20141212112422.7717230 2014#12#12T11:27:22.7717230+00:00, lbr 2014#12#12T11:27:22+00:00 , lbr 2014#12#12T11:27:22.771723+00:00 /Date(1418383462771+0000)/, lbr /Date(1418383462000+0000)/ , lbr /Date(1418383462771+0000)/
guidx, length 16; c, length 32, lbr c, length 22 0050569181751ED4A0BED3E86422E104, lbr 051MaO5r7jIWljFeP2BX1000505691#8175#1ed4#a0be#d3e86422e104 00505691#8175#1ed4#a0be#d3e86422e104
qNamestring{uri}name < ... xmlns:...='uri'>...:name < /...>{uri}name
uric, string:; < = > ?[ ]^_``{|}~ :;%3C=%3E?[%5C]%5E_%60%7B%7C%7D~ :;%3C=%3E?[%5C]%5E_%60%7B%7C%7D~
uriFullc, string:; < = > ?[ ]^_``{|}~ %3A%3B%3C%3D%3E%3F%5B%5C%5D%5E_%60%7B%7C%7D~ %3A%3B%3C%3D%3E%3F%5B%5C%5D%5E_%60%7B%7C%7D~
uri1c, stringRock'n'Roll Blues 'Rock''n''Roll%20%26%20Blues''Rock''n''Roll%20%26%20Blues'
uri1x, xstring0123456789ABCDEF binary'0123456789ABCDEF'binary'0123456789ABCDEF'
uri1t125814time'PT12H58M14S' time'PT12H58M14S'
uri1utclong, lbr TIMESTAMP, lbr TIMESTAMPL 2014-12-12 11:24:22.7717230, lbr20141212112422, lbr 20141212112422.7717230 datetimeoffset'2014#12#12T11%3A27%3A22.7717230Z', lbr datetimeoffset'2014#12#12T11%3A27%3A22Z', lbr datetimeoffset'2014#12#12T11%3A27%3A22.771723Z' datetimeoffset'2014#12#12T11%3A27%3A22.7717230Z', lbr datetimeoffset'2014#12#12T11%3A27%3A22Z', lbr datetimeoffset'2014#12#12T11%3A27%3A22.771723Z'
uri2x, length 16; c, length 32 0050569181751ED4A0BED3E86422E104 guid'00505691#8175#1ed4#a0be#d3e86422e104' guid'00505691#8175#1ed4#a0be#d3e86422e104'
uri2d20141212 datetime'2014#12#12T00%3A00%3A00' datetime'2014#12#12T00%3A00%3A00'
uri2utclong, lbr TIMESTAMP, lbr TIMESTAMPL 2014-12-12 11:24:22.7717230, lbr20141212112422, lbr 20141212112422.7717230 datetime'2014#12#12T11%3A27%3A22.7717230', lbr datetime'2014#12#12T11%3A27%3A22', lbr datetime'2014#12#12T11%3A27%3A22.771723' datetime'2014#12#12T11%3A27%3A22.7717230', lbr datetime'2014#12#12T11%3A27%3A22', lbr datetime'2014#12#12T11%3A27%3A22.771723'
languagec, length 1E, D, ...EN, DE, ...EN, DE, ...
currCodec, length 5EUR, USD, ... EUR, USD, ...EUR, USD, ...
unitCodec, length 3KM, MI, ...KMT , SMI, ...KMT, SMI, ...
currency=CURRCODENumeric types 123456, lbr 123,456123456, lbr 123,456 123456, lbr 123,456
unit=UNITCODEp, decfloat16, decfloat34 123,000, lbr 123,456123, lbr 123,456 123, lbr 123,456
alphac, string, n0000123456 123456123456
The following formats match the XML schema data types listed under Mapping Further XML Schema Data Types or other data types. For more details, see

boolean for truth values

dateTime, dateTimeOffset, dateTimeLocal for date/time values

guid for UUIDs

qName for qualified names

language for ISO language codes

currCode for ISO currency codes

unitCode for ISO unit codes
In addition to the time stamp type utclong, packed numbers corresponding to the ABAP Dictionary data types TIMESTAMP or TIMESTAMPL can also be used as ABAP types for dateTimeOffset and dateTimeLocal. For dateTimeOffset, the value 0 is then used for the offset in the XML or JSON representation of time stamps. For boolean, language, currCode, and unitCode , noError can be specified to prevent an exception being raised in the event of invalid values.
The other formats have the following meaning:

The format hex means that byte-like content is mapped to a hexadecimal format and not to base64.

The format duration is based on the XML schema data type with the same name.

The formats ticks and ticksOffset are used for JSON representations of UNIX time stamps (or ticks), which are based on the number of milliseconds since 01.01.1970,00:00:00, for OData. These formats only have special support in JSON. In XML, the regular date format or the associated time stamp formats are used. If ticksOffset is used for the time stamp type utclong or for packed numbers that correspond to the data types TIMESTAMP or TIMESTAMPL, the value 0 is used for the offset in the XML or JSON representation.

The formats uri and uriFull mask special characters like the built-in function escape in serializations with the format E_URI or E_URI_FULL. In deserializations, the escape symbols are transformed to the respective characters.

The format uri1 is used to represent literal values in URIs for OData.

Content of the ABAP types c and string is enclosed in quotation marks. Special characters are handled with the format E_URI_1, like the built-in function escape.

Content of the ABAP types x and xstring is mapped as with the format hex. The XML and JSON representations are enclosed in quotation marks and prefixed with binary.

Content of the ABAP type t is mapped as with the format duration. The XML and JSON representations are enclosed in quotation marks and prefixed with time.

Content of time stamp fields of type utclong or of packed numbers that have the dictionary types TIMESTAMP and TIMESTAMPL is mapped in the same way as with the format datetime. The XML and JSON representations are enclosed in quotation marks and prefixed with datetimeoffset. Colons : are replaced by the escape symbols %3A. The prefix datetimeoffset identifies a UTC time stamp in OData.

The format uri2 is used to represent additional literal values in URIs for OData.

Content of the ABAP types x with length 16 and c with length 32 is mapped as with the format guid. The XML and JSON representations are enclosed in quotation marks and prefixed with guid.

Content of the ABAP type d is handled like a corresponding time stamp of dictionary type TIMESTAMP, in which the time part has the value 00:00:00.

Content of time stamp fields of type utclong or of packed numbers that have the dictionary types TIMESTAMP and TIMESTAMPL is mapped in the same way as with the format uri1. Here, however, the format of a local time stamp with the prefix datetime is used.

The format currency=CURRCODE formats the values of numeric ABAP types in serializations in accordance with a currency code specified in CURRCODE. For CURRCODE, visible character-like data roots of the ST program with a length no greater than 5 can be specified at this position. In the database table TCURX, the line with the content of CURRCODE in the CURRKEY column is searched for, and the decimal places are taken from the CURRDEC column. If no line is found, the default value 2 is used. The numeric content is formatted with these decimal places. Missing decimal places are padded with 0, and surplus decimal places are rounded commercially. If the content of CURRCODE is initial, and in deserializations, the format is ignored. The formatting corresponds essentially to the way the function module CURRENCY_AMOUNT_SAP_TO_IDOC works.

The format unit=UNITCODE formats the values of decimal numbers in serializations in accordance with a unit code specified in UNITCODE . For UNITCODE, visible character-like data roots of the ST program with a length no greater than 3 can be specified at this position. In the database table T006 , the line with the content of UNITCODE in the MSEHI column is searched for, and the decimal places are taken from the ANDEC or DECAN column. If no line is found, the default value 0 is used. The numeric content is formatted in accordance with these decimal places. Missing decimal places are padded with 0 , and surplus insignificant decimal places 0 are cut off. The format is ignored in deserializations.

The format alpha formats strings like the formatting option ALPHA for embedded expressions in string templates:

In serializations, leading zeros are removed as with alpha = out .

In deserializations, leading zeros are inserted as with alpha = in .
In JSON, the values are produced in accordance with the XML representation, except for qName, which is not supported in JSON. In JSON, the format boolean creates real Boolean JSON values.
If the data type or the content do not match of if the current node is typed using tt:type, the option format is ignored or an exception is raised.



Latest notes:
The option format can also be used to map ABAP data objects to XML schema data types that are not typed using a dedicated domain.
NON_V5_HINTS
ABAP_HINT_END

ABAP_EXAMPLE_ABEXA
Formatting Options
ABAP_EXAMPLE_END

ABAP Addition

What does it do?
The decimals option sets the decimal places of numeric values and of time stamps in serializations. It can be applied to all numeric ABAP types and to the time stamp type utclong and works in mainly the same way as the formatting option DECIMALS for embedded expressions in string templates. The decimals option is ignored in deserializations.
Suitable literal integer values can be specified for dec. These values can also be negative for numeric types. Only the values 0 to 7 are allowed for the time stamp type utclong. If dec is not specified (empty parentheses), the option is ignored.
If decimals is used for time stamps of the type utclong, surplus decimal places are cut off in serializations instead of being rounded and are padded to seven decimal places using zeros. The following applies to time stamps in packed numbers of the types TIMESTAMP and TIMESTAMPL:

decimals can be combined with the format option for these numbers. In this case, the decimals option is applied first, then format with a fmt format provided for time stamps.

Packed numbers that are typed with one of the special domains XSDDATETIME_... are first handled with decimals and then formatted as time stamps.
In these cases, the result of decimals must be a valid time stamp.

ABAP_EXAMPLE_ABEXA
Option for Decimal Places
ABAP_EXAMPLE_END

ABAP Addition

What does it do?
The addition regime specifies that the ABAP source type in serializations or the ABAP target type in deserializations is overridden by one of the regimes num, char, or bin. num specifies numeric handling, char specifies character-like handling, and bin specifies binary handling of the data by the transformation. The regime option deactivates the effect of all special domains, but can be combined with the format options, where a fmt format specified with format must be suitable for handling with regime for handling. The num regime can also be combined with decimals.
The num, char, and bin regimes have the following effect on the possible ABAP types:

num regime Forces a numeric handling of the current node.

Apart from deactivating the effect of special domains, the num regime is ignored by numeric types.

All other data types are converted to the decfloat34 type before the actual transformation in serializations, and then further processed as such. Source values of types n, d, and t must be valid. In deserializations, a value is created for decfloat34 and assigned without loss to the target type.

char regime Forces a character-like handling of the current node.

Apart from deactivating the effect of special domains, the char regime is ignored by numeric types, which means that the standard XSD representation of asXML is used.

Apart from deactivating the effect of special domains, the char regime is ignored by character-like data types.

Byte-like data types are handled as with the formatting option format(hex), that is, representation is in hexadecimal format.

Date and time types are handled like the c type of corresponding length, with invalid values accepted.

bin regime Forces a byte-like handling of the current node.

Numeric types are converted to the xstring type before the actual transformation in serializations, and further processed as such. In deserializations, a value is created for xstring and converted to the target type.

Source fields of the character-like data types c and string are converted without loss to xstring in serializations and then processed further. A source field of type n is checked for valid content and also converted to xstring. In deserializations, a value is created for xstring and converted to the target type. There must be no overflow for type n.

Apart from deactivating the effect of special domains, the bin regime is ignored by byte-like data types.

Source fields of the date and time types are checked for valid values in serializations, converted to xstring and then processed further. The source fields are checked for valid content. In deserializations, a value is created for xstring and converted to the target type. There must be no overflow.

ABAP_EXAMPLE_ABEXA
Option for Regime
ABAP_EXAMPLE_END

ABAP Addition

What does it do?
Prevents exceptions that would be raised in the event of invalid values occurring in serializations of certain ABAP types and with certain formats specified using format. The following table shows to which ABAP types and formats noError is applied: TypeFormatEffect
n-Leading and trailing blanks are ignored.
p-An invalid value in the final byte is ignored and interpreted as a plus sign.
XSDBOOLEANboolean Other values apart from X and blank are accepted and return true .
XSDDATE_D-Invalid dates are accepted and formatted as a date.
XSDTIME_T-Invalid times are accepted and formatted as a time.
XSDLANGUAGElanguage An invalid language is accepted with no conversion taking place.
XSDCURRCODEcurrCode An invalid currency code is ignored with no conversion taking place.
XSDUNITCODEunitCode An invalid unit key is ignored with no transformation taking place.

ABAP_EXAMPLE_ABEXA
Option for Invalid Values
ABAP_EXAMPLE_END