While importing data using Exchange Scheme, All the dates are converted as 01 - 01- 1970 though the data input was mmddyy format and the exchanges scheme also we defined in the masterdata as mmddyy.

Is it a processing issue or LN Bug?

__________________
"Success is not in howmany things we are doing but in how differently we are doing"

Hi binoy000,

It should import properly if in your ASCII File Fields session, Field Type is set to Numeric and Date Format is set to MMDDYY.

Mike

Do we need to put any values for time other than mmddyy?
I have put the asci data in the following way...

DPCMNMxxxxxx|1|LCP000062|1|051310|1|USD|325000.00|||070510|062010|LC2|FB2|Fxxxxx
DPCMxxxxx|1|LCP000069|1|052310|1|USD|569304.00|||071510|063010|LC2|FB2|xxxxxx

__________________
"Success is not in howmany things we are doing but in how differently we are doing"

The time will import as 12:00:00 AM.

All setting is same .But result is still 1970 date...I have registered an incident to Infor.
This problem was there from beginning of LN Implementation.

__________________
"Success is not in howmany things we are doing but in how differently we are doing"

I got the solution from Infor- we have to use the asci file with hrmnssmmddyyyy format.
Thanks everybody.

__________________
"Success is not in howmany things we are doing but in how differently we are doing"

Hi binoy000,
I still only get as result the 1970 date. How did you define the Ascii field file - Numeric and MMDDYYYY?

Markus

the best way to import dates with exchange is to write a condition.

somthing like

long yy mon dd hh min ss

yy = lval(date(1;4))
....
....

return date.to.utc(yy,mon, ...)

or for dte date

return date.to.num(yy,mon, ...)

this condition can be changed to agree with the format in the import file

define the input field as string

Regards

peter

__________________
Peter J Campbell

Hi Peter,
that works great, thanks

Kind Regards
Markus

Yes, the problem with this example you presented, is that the date is not a date field truly but a UTC field. UTC is an acronym that stands for Coordinated Universal Time. An UTC field handles Date and Time. So, the value a UTC field can take is represented by a numeric value, using this international standard. This numeric value which is stored in the database also as a numeric value is

In ERP LN: the number of seconds from January 1st, 1970 12:00am.
In other words, 01/01/1970 00:00 = 0; 01/01/1970 00:02 = 120; 01/04/2007 00:00 = 1167868800

In BAAN IV: The number of days from January 1st, 1970 12:00am.

Peter's condition handles this conversion correctly but I figured it would not hurt to provide more information.

Regards,

In BAAN IV: The number of days from January 1st, year 0
dte date as tfgld.date in LN

__________________
Peter J Campbell