|
From what you say, your project has serious issues:1) ERP is slow and has many bugs
We have an instance of BO tied in to our iSeries DB2 using ODBC. We--
also got BO when it came bundled with a Financial Package we purchased
so we decided to try and use it to also provide reporting services to
all of our i based data. What we did was write our own custom
Extract/transform/load
(ETL) application that runs nightly on the iSeries and pulls all the
data needed for reporting and puts it in a different set of tables in
a different library formatted for reporting. BO then points to this
library only. Most Data warehouse setups to the same including the
Financial Package we purchased. In their case they take the data out
of one MSSQL database server and replicate it all to a second MS SQL server used by BO.
After training everyone to use BO and the reports then can get from
the data and all the 'cool' things it can do, we have exactly 0 users using it.
Even after years of complaining that they had no reporting package
like other colleges had. We do have our research office using the i
data for many reports but they prefer to use Access. The database is
the same, we just allowed them ODBC access to the special library. They love it.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Hoteltravelfundotcom
Sent: Thursday, August 01, 2013 5:50 PM
To: Midrange Systems Technical Discussion
Subject: Business Objects with DB2 data
I am interested in hearing of any Iseries shops which use Business Objects.
We are interested
in that product to use for reports and allowing users to create their
own reports.
I am concerned in that that AS/400 ERP we have is rather old product,
basically RPG from back in the 90's and data base is very bulky - any
experiences would be welcome.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.