Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Performance Management
Lawson Business Intelligence/Reporting/Crystal
YTD MM280 to Crystal using Lawson OLE DB
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:
267
Members:
0
Total:
267
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 Business Intelligence/Reporting/Crystal
YTD MM280 to Crystal using Lawson OLE DB
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Latoria
New Member
Posts: 3
4/17/2013 12:21 PM
We have a Crystal report built that uses the MM280 as a datasource. We have been able to successfully run the report to pull in 5 months of data, but when we add a 6th month, it errors out. Has anyone ever experienced or know of any limitations on data size or run time using the OLE DB connector that would cause the report to throw an error? Crystal is describing it as a parsing error, but the individual monthly reports run fine--with no errors. Infor Support has told us to just split the report up, but that means it is no longer a true YTD report. Any help/guidance provided would be greatly appreciated!
Attachments
MM280_Crystal_Error.docx
dcaiani
Veteran Member
Posts: 52
4/17/2013 12:51 PM
We run something similar but we generally run a month at a time. Twice a year we do run the report for the previous 6 months. I've never had an issue with running it. Obviously we don't have quite the same amount of volume that you have. We are also running IC transactions only and are summing in Item Summary mode (report level). If you are running at a greater level of detail perhaps you can try it in Summary instead of detail.
Latoria
New Member
Posts: 3
4/17/2013 3:20 PM
Yes, our users have requested the data in detail. We're also pulling in both IC and AP transactions. We do run monthly reports, but the request was made for a YTD report for budgeting purposes. We have resolved to running the report quarterly, but would really prefer one report.
Greg Moeller
Veteran Member
Posts: 1498
4/17/2013 4:15 PM
What specifically are you looking for? We have TONS of Crystal written right out of the database that would be faster for you. And won't error for a true YTD report.
Have you got LBI, as well?
Greg Moeller
Veteran Member
Posts: 1498
4/17/2013 4:17 PM
How about something like this:
Attachments
MMDist_Distributions_ALL.rpt
Latoria
New Member
Posts: 3
4/17/2013 4:49 PM
We basically need everything that's on the MM280--item information, unit cost, quantity, extended cost, vendor & invoice information. I've been reading through some of the other posts on the site and I keep seeing that the MM280 is virtually impossible to create using the Lawson tables. Is this still true?
Yes, we are currently using LBI. But, we're posting this report as a saved instance instead of a scheduled job. Would that make a difference, say if the Crystal wasn't ran on an individual's computer but by LBI?
John Henley
Senior Member
Posts: 3348
4/17/2013 5:59 PM
Not impossible, but difficult and problematic mostly due to bugs which have periodically wiped out critical data required to tie the tables together. If you can train users to create unique MM280 job names, and/or save off MM280 instances (either in Crystal or directly in Lawson print manager), you will get better results.
Michael
New Member
Posts: 1
4/18/2013 7:58 PM
Regarding Latorias Post:
Here was the response from Infor's support which did not resolve the problem. They also susggested it could be the crystal report howerver it works fime for any darte range less than 6 months.
From INFOR SUPPORT:
I am fairly certain that this report is just too large for OLEDB and IOS to handle. Looks to be nearly 3 GB of data running through IOS for this. You'll probably have to break it up.
But, a couple of things to try:
1. Uninsall OLEDB and install the latest one.
From inforxtreme.com, go to Downloads > Products > Lawson and Infor MERGED > Performance Management > Lawson Business Intelligence > OLE DB Object Services - S3 and Landmark > OLEDB 9.0.5.0 - Full Product Update 9.0.5293.
2. Remove Page N of M from the report and just use Page Number instead. With Page N of M, Crystal has to process the report twice.
You are not authorized to post a reply.