ImmuBaan
28th February 2005, 22:48
How do you handle correcting Baan Integration errors to be Sarbanes Oxley (SOX) compliant?
The issue is with session tfgld4115m000 Maintain Integration Additions. We are ok with adding or modifying Integration mapping and other master data to correct errors. The problem is with errors that require corrections to tfgld415 data. This session allows user to modify transactional data that is not erroneous, in addition to data that is causing errors.
Does anyone know what SOX says about this type of corrections, and who in the organization should be making these data corrections? We are particularly interested in the aspect of users having access to modify all transactions, not only erroneous ones. Do you need to turn on audit on table tfglf415? Or is a procedural (outside Baan) control acceptable?
The issue is with session tfgld4115m000 Maintain Integration Additions. We are ok with adding or modifying Integration mapping and other master data to correct errors. The problem is with errors that require corrections to tfgld415 data. This session allows user to modify transactional data that is not erroneous, in addition to data that is causing errors.
Does anyone know what SOX says about this type of corrections, and who in the organization should be making these data corrections? We are particularly interested in the aspect of users having access to modify all transactions, not only erroneous ones. Do you need to turn on audit on table tfglf415? Or is a procedural (outside Baan) control acceptable?