Weston
We are in the process of installing it with XA 7.8.
Understand that XA 9 (formerly 7.9) has the integration via the EBS
(Enterprise Bus System) which is the foundation of the SOA applications
going forward.
From an iSeries view, the resources are negligible. There are 19 manuals
for the PM application suite. And they are large manuals (all pdf files).
Your affiliate is the right channel to share these. My understanding is
that the manuals are not license, but they are copy righted.
There are several things to consider.
1. Network infrastructure. If you don't have good infrastructure, don't
think about it because you'll be sorry. PM (and all SOA) applications are
true multi-tier applications. That means that you run the database server
on one box (or more if you split the services), the application server on
another box (or more if you split the apps) and the web services on a third
box (or more if you split the access). In addition, you'll need to be
concerned with level loading across your network.
2. In addition, the EBS requires its own set of services and database boxes.
3. Security integration is incomplete at this time. Most XA shops put up
with a separate network and XA login because the integration has never been
done correctly. However, as you add these apps, you have the most likely
scenario of having 6 or 7 different login's (each with different ID's,
passwords and un-synchronized expiration timing). You will want to do a
complete review of your security practices and begin the process of creating
role based groups that can be synchronized with the future role based
security that INFOR is rolling out. (In part with R9).
4. XA table setup and database control. Most XA shops do a very poor job of
controlling data. By this I mean, controlling and enforcing discipline on
the extended data codes such as Item Class, Item Group, Item Commodity,
Sales Rep, Territory, Customer Class, etc. PM works on the concept of data
cubes. In other words, the relationship between one view of data and another
view. For example, suppose that I want to view my sales by product group
within a sales territory by quantity, by market share, by value, etc. If I
don't have the relationships of the data pre-defined, and the data control
enforced through policy, procedure, audit and enforcement...you'll be stuck
with a bunch of worthless code. You can't create rules that say..."when if
the item class from this date to that date is XYX, but after that date it's
1234, and now I'd like to merge the data..."
However, if you do have good definitions in place and good quality data and
enforcement (proven with audit reports) then proceed. Because the benefits
are truly awesome.
Note, if you looking at it only for financial reporting you still need to
know the data relationships unless all you want is to print P&L, Balance
Sheet and cash flow. Then a typewriter will work too.
One final note: It is a suite of applications not "an" application just as
XA is a suite of applications and not "an" application.
I am a big proponent of the PM suite and think it a great tool to improve
performance of an organization. Just proceed with your eyes wide-open.
Make certain your C-level executives are involved. It would be nearly
impossible to correctly implement and fully utilize the power of the
application without their involvement.
Kevin Fox
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx]
On Behalf Of Weston Wheat
Sent: Friday, October 09, 2009 12:42 PM
To: MAPICS ERP System Discussion
Subject: [MAPICS-L] Performance Management Financial Reporting
Hello All
We are looking at buying the Flex Upgrade bundle from Infor.
One of the applications in the bundle is Performance Management Financial
Reporting.
However I can't find any manuals or documentation on the application for
XA..
Is anyone using this application with XA? And if so, can you forward me the
manual.
Trying to figure out what it does and what system resources it going to
need.
Thanks in advance.
As an Amazon Associate we earn from qualifying purchases.