YTD MM280 to Crystal using Lawson OLE DB

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.

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.

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?

How about something like this:

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?

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.

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.