This feature allows for a JDE OneWorld
Julian dates (ie, CCYYJJJ) to be converted to a standard date format and visa
versa. This feature is only
available on column mapping and allows you to specify the following conversion
on a per column bases:
|
OW Julian to date |
Format (using example OW Julian
012365 eg. 31 December 1999) |
|
date(owjulian) |
The standard date representation
based on the systems locale setting. Eg, Australasian = 31/12/1999, USA =
12/31/1999. |
|
dd/mm/yyyy(owjulian) |
31/12/1999 |
|
dd/mm/yy(owjulian) |
31/12/99 |
|
dd mmm yyyy(owjulian) |
31 Dec 1999 |
|
mm/dd/yyyy(owjulian) |
12/31/1999 |
|
yyyy-mm-dd(owjulian) |
1999-12-31. Note, this is the
standard representation used by ODBC when selecting and inserting date
values (as char columns) between source and destination databases. |
|
day(owjulian) |
31 |
|
month(owjulian) |
12 |
|
year(owjulian) |
1999 |
|
Date to OW Julian |
Format (using example 31
December 1999 eg, OW Julian 012365) |
|
owjulian(date) |
<locale date format>=012365 |
|
owjulian(dd/mm/yyyy) |
31/12/1999=012365 |
|
owjulian(dd/mm/yy) |
31/12/99=012365 |
|
owjulian(dd/mmm/yyyy) |
31/Dec[ember]/1999=012365 |
|
owjulian(mm/dd/yyyy) |
12/31/1999=012365 |
|
owjulian(yyyy/mm/dd) |
1999/31/12=012365 |
To support the conversion of different
source and destination data types (i.e, numeric to DB date) the destination
column data type and length if specified (i.e, not null) are used by the SLIK
Server to perform the appropriate ODBC data bindings. The use of the user defined column data type information is
only used for conversions.
The processing option "Ignore
errors on date conversion" allows the insert to be attempted even if a
conversion error occurs. Note
however the insert can still fail because of bad data.