Page tree
Skip to end of metadata
Go to start of metadata

Date and Time formatting expressions are used by the <<FlatFile>> parser and composer, and Integer, Float, String, and DateTime objects (e.g. see related pages in the box on the right).

The following Date and Time formatting patterns are supported by the Bridge:

PatternDescriptionExampleRemark
%aAbbreviated weekday nameMon
%AFull weekday nameMonday
%bAbbreviated month nameFeb
%BFull month nameFebruary
%CYear / 100 as decimal number [00,99]20
%dDay of the month as decimal number [01,31]12
%DEquivalent to %m/%d/%y02/12/18
%eDay of the month, single digits with leading space [1,31]12
%FEquivalent to %Y-%m-%d (ISO 8601:2000 standard date format)2018-02-13
%hEquivalent to %bFeb
%HHour (24-hour clock) as decimal number [00,23]15
%iMicroseconds as decimal number [000000,999999]123456
%IHour (12-hour clock) as decimal number [01,12]03
%jDay of the year as decimal number [001,366]043Conflicts with %u, %w, %U, %V, and %W.
%mMonth as a decimal number [01,12]02
%MMinute as a decimal number [00,59]20
%n<newline>\n
%oOffset from UTC as +HH:MM+00:00Only for DateTime composing/printing.
%pam or pm (12-hour clock)pm
%rTime in am/pm notation, equivalent to %I:%M:%S %p03:20:12 pm
%RTime in 24-hour notation, equivalent to %H:%M15:20
%SSecond as decimal number [00,59]12
%t<tab>\t
%TTime in 24-hour notation, equivalent to %H:%M:%S15:20:12
%uWeekday as decimal number [1,7], with 1 representing Monday1
%UWeek number of the year as decimal number [01,53]. The first Sunday of January is the first day of week 1; days in the new year before this are in week 0.06
%vEquivalent to %e-%b-%Y12-Feb-2018
%VWeek number of the year as decimal number [01,53]. If the week containing 1 January has four or more days in the new year, then it is considered week 1. Otherwise, is the last week of the previous year, and the next week is week 1. Both January 4th and the first Thursday of January are always in week 1.07
%wWeekday as a decimal number [0,6], with 0 representing Sunday1
%WWeek number of the year as decimal number [01,53]. The first Monday in January is the first day of week 1; days in the new year before this are in week 0.07
%yLast two digits of the year as decimal number [00, 99]18
%YYear as decimal number [0000,9999]2018
%zLocale time zone as offset from UTC in ISO 8601:2001 standard format (+hhmm or -hhmm).+0100
%+Equivalent to %a, %d %b %Y %H:%M:%S %z (see also rfc2822 below)Mon, 12 Feb 2018 15:20:12 +0000Only for DateTime composing/printing.
%%Percent sign%Only for DateTime parsing.

Standard Patterns

Some very common patterns can be directly abbreviated:

ConstantEquivalent Placeholder ExpressionExampleRemark
rfc822%a, %d %b %y %H:%M:%S %zMon, 12 Feb 2018 15:20:12 +0000Not fully compatible, because %z accepts only the ((+|-)hhmm) format and %y counts year differently.
rfc850%A, %Y-%m-%d %H:%M:%S GMTMonday, 2018-02-12 15:20:12 GMT
rfc1123%a, %d %b %Y %H:%M:%S GMTMon, 12 Feb 2018 15:20:12 GMT
rfc2822%a, %d %b %Y %H:%M:%S %zMon, 12 Feb 2018 15:20:12 +0000Not fully compatible because %z accepts only the ((+|-)hhmm) format and %y counts year differently. (See also %+ above.)
sap-idoc-dats%Y%m%d20180212
sap-idoc-tims%H%M%S152012
ConstantParsed ExpressionExampleRemark
xsd:date CCYY-MM-DD[Z|[+\|-]hh:mm]2018-02-12Z
xsd:dateTimeCCYY-MM-DDThh:mm:ss[.sss][Z|[+\|-]hh:mm]2018-02-12T15:20:12.153688ZMicroseconds are skipped if 0: 2018-02-12T15:20:12Z
xsd:timehh:mm:ss[.sss][Z|[+\|-]hh:mm]15:20:12.224376ZMicroseconds are skipped if 0: 15:20:12Z

Unsupported Patterns

The following patterns are not supported - neither for parsing nor composing:

%c, %g, %G, %k, %l, %x, %X, %Z.

  • No labels