Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Human Capital Management
Lawson S3 HR/Payroll/Benefits
TAEMPTRANS table missing records in 901 conversion
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
221
Members:
0
Total:
221
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson S3 HR/Payroll/Benefits
TAEMPTRANS table missing records in 901 conversion
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Margie Gyurisin
Veteran Member
Posts: 538
5/16/2012 2:53 PM
We just completed our first migration to 901 and are attempting to begin testing. When running LP264 to compare totals betwee 900 and 901, we discovered totals didn't match and then discovered records were missing. We are also going from oracle to sequel server.
It appears as if the reason for the failure is that some records in the TAEMPTRANS table have invalid reset dates along with blank date fields.
Has anyone else had this issue and if so, how did you fix it?
Thanks for your help.
John Henley
Senior Member
Posts: 3348
5/16/2012 4:06 PM
Please explain what order you are doing this and how your product lines are set up. In other words, are going from Oracle to SQL in different product lines, or are you trying to do it within the same product line? Are you upgrading from 900->901 by installing 901 over top of existing 900 product line, etc. ? Lawson stores empty/null dates values in Oracle as 1/1/1700, but in MSSQL as 1/1/1753. So my guess would be that the "empty date" values from that table in Oracle are getting dropped when trying to load into SQL since 1/1/1700 is not a valid date in SQL.
Margie Gyurisin
Veteran Member
Posts: 538
5/16/2012 8:53 PM
We are going from oracle to sql in a different product line. As I understand, they did a dbcopy from oracle to sql and then upgraded apps to 901. Everything is on a new server as well.
You are not authorized to post a reply.