Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

EDI - SOX compliance

109 views
Skip to first unread message

John Skibicki

unread,
Nov 11, 2004, 8:17:51 PM11/11/04
to
How to import an (EDI) Electronic Data Interchange mappings,
documents,Trading Partner Setup,etc from a development AS/400 machine
to a production AS/400 machine without actually making the changes
there which is against (SOX) Sarbanes-Oxley standards. Currently, we
are using Inovis (EDI) software for our data exchange. Your quick
response is truly welcomed.

Dale Berta

unread,
Nov 13, 2004, 8:51:41 AM11/13/04
to
I think I know what you're getting at, but this is not really against SOX
standards. You could view EDI mappings and other definitions as either
environmental changes, or a data changes (since they're most likely stored
in tables). Either way, as long as you have necessary approvals and
documentation, you should be OK with SOX.

I'm not familiar with Inovis. (Is this the latest incarnation of EDI/400,
which was Prememos, Harbinger, etc., etc.?) If everthing is in tables, you
could move the definitions in as a production database change. But that
could get messy

I don't think you need to get that crazy with it. SOX doesn't prevent you
from making the changes. It just mandates that you have approval,
auditability, and accountability; the restriction is on programmers updating
production systems. EDI software probably has a separate administration user
profile, right? So you get approval to use the admin profile to make the
change, and print all definitions before and after the change. The printouts
become part of the audit trail (read: evidence of control), which could then
be examined by auditors.

"John Skibicki" <iski...@wiley.com> wrote in message
news:189244b5.04111...@posting.google.com...

Bob Bergstrom

unread,
Dec 2, 2004, 3:46:35 PM12/2/04
to
Invois has an import export feature, that allows you to select the user
file definitions, relationships and translation formats that you need to
export. You then use the communications file interface to move the files
across to production and use the import feature to apply the
modifications.

Bob Bergstrom
Technology Solutions Inc.
Phone: (888)366-8911
Web: http://www.iseries-edi.com

Doug Hart

unread,
Dec 4, 2004, 8:23:23 PM12/4/04
to
Nothing in the SOX language mentions EDI. Or even change to production
systems.
Your auditor are telling you this.


"Bob Bergstrom" <bob.be...@rejbi.com> wrote in message
news:pan.2004.12.02....@rejbi.com...

0 new messages