I would love to hear some dialog from other customers on how you deal with
SOX requirements as it relates to putting in changes around Enterprise
Integrator. This is primarily around how you handle the export/import of
business objects along with putting in the User Exit code related to
them. (For example you use your normal process for the program objects,
but then someone has to still do the Export/Import). There typically are
some clean-up tasks and verification of user exits after an import is
done.
I've see a few ways this is handled. None of them see perfect. How is the
segregation of duties handled for example. What do you do when the import
"blows up". What are your process steps around this? Do you handle simple
customization changes within SOX?. Do you hit security issues related to
the Export/Import? Just a lot of messy details when you get into
Enterprise Integrator development. It's not as clean.
Just wondered if someone had any comments or suggestions. I think Infor
has plans to address this (or improve it) so maybe we can get some
statement of direction in regards to that as well at some point.
Kevin
-------------------------------------------
REGISTER NOW | Inforum 2008 | The Venetian Hotel and Sands Expo | Las
Vegas | October 14 - 16 |
http://www.inforum2008.com
Kevin Gerard, Senior Technical Consultant
TriMin Systems, Inc. - Infor Channel Partner
Direct 309-932-3103
Mobile 309-883-1689
www.triminmfg.com
"We are committed to helping manufacturing companies improve their
Visibility, Productivity, Growth and Profitability"
-----mapics-l-bounces@xxxxxxxxxxxx wrote: -----
To: "MAPICS ERP System Discussion" <mapics-l@xxxxxxxxxxxx>
From: "Greg Wenzloff" <GWenzloff@xxxxxxxxxxx>
Sent by: mapics-l-bounces@xxxxxxxxxxxx
Date: 07/25/2008 09:09AM
Subject: Re: [MAPICS-L] Change Management
Bryan,
The person who has the detailed answers is on vacation today. I'm sure
she would answer you on Monday.
We are currently only using the helpdesk ticket part of Track-It. It
was easy to install as far as I know. Our corporate HQ controls the
license so I don't know the cost. I'm not much help.
For SOX you are channeled into having some type of logging system for
tickets which you already have. None of our auditors have asked about
asset tracking but Track-It has that module. You already seem to have
the key piece of software, you may not need something else.
Greg
-----Original Message-----
From: Burns, Bryan [mailto:Bryan_Burns@xxxxxxxxxxxx]
Sent: Friday, July 25, 2008 9:55 AM
To: MAPICS ERP System Discussion
Subject: Re: [MAPICS-L] Change Management
Greg,
Our network specialist recommended Track-It and we're looking at buying
it to help us with our J SOX requirements. He likes it for the asset
management functionality. But I already installed a ticket logging
system on the iSeries that's free and browser based - MANTIS400.
It seems that the scope involved in implementing a help desk package to
assist with J SOX documentation has creeped into asset management. How
long do you think it would take us to buy, install, configure, and make
use of Track-It for SOX purposes? We've got a very short timeline for
this SOX stuff.
If you were to start anew with a help desk package, what would you do?
Also, is the annual maintenance fee for Track-It reasonable?
Bryan
-
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/mapics-l.
midrange.com
