Epicor SOX audit report?

If you're sql, you can just enable change tracking on the DB.
I'm not sure what affect it would have on the performance if you enabled it
across the board, but I've done it on other systems without incurring any
substantial issues.

*John Driggers*
**
*Chief Data Wrangler*
*
*
*I have an Epicor blog <http://usdoingstuff.com/>. How useful is that?*
*
*:: 904.404.9233
:: waffqle@...
:: http://www.usdoingstuff.com <http://www.usdoingstuff.com/>

*

*


On Wed, Feb 20, 2013 at 9:42 AM, Vic Drecchio
<vic.drecchio@...>wrote:

> **
>
>
> Jim, not sure what others in public companies do, but in the past I've set
> up a plethora of SQL Triggers to track the things past SOX auditors thought
> was necessary to appease themselves. I set up triggers on various tables
> which subsequently populated a UD table with the necessary details. Then I
> could run a report on that table. I chose to not use ChangeLog or BPMs
> because BPMs aren't available on every table (at least in 8.03.xxx).
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Jim Chance
> Sent: Wednesday, February 20, 2013 9:33 AM
> To: vantage@yahoogroups.com
> Subject: Re: [Vantage] Epicor SOX audit report?
>
>
> Aren't the change logs solely data/record/field based?
>
> This SOX report is to look at technical, customizations, configurations,
> BAQ's, BAM's, BPM's that have changed due to their potential of impacting
> the logic of the applications behavior - something SOX auditors want to
> track.
>
> >________________________________
> > From: Manasa Reddy mreddy@... >
> >To: "vantage@yahoogroups.com vantage@yahoogroups.com >
> >Sent: Wednesday, February 20, 2013 9:04 AM
> >Subject: RE: [Vantage] Epicor SOX audit report?
> >
> >
> >
> >Have you tried Change logs? Depending on what your auditors are looking
> for you can set these up to automatically record changes to certain fields.
> Of course the system only starts recording once you turn these on...it will
> not look back at history.
> >
> >Manasa
> >
> >From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com ] On
> Behalf Of jim_chance
> >Sent: Wednesday, February 20, 2013 7:39 AM
> >To: vantage@yahoogroups.com
> >Subject: [Vantage] Epicor SOX audit report?
> >
> >Are you aware of anything in Epicor or of a developed report that can
> provide...........
> >
> >Our SOX and internal auditors want us to have the ability to run a report
> that will identify over a period of time (like a month) all the changes
> made to the Epicor system. They want us to be able to have this report
> identify all changed, configuration settings, reports, BAQ, BAMs, screens,
> filed additions, etc. They are basically looking for a way to have the
> system tell us all changes made so we can then match up a ticket to that
> change.
> >
> >Epicor has suggested we use Solution Manager but I think you only get
> information out of that when a human inputs information. The auditors want
> to have the report identify changes that may have been made and not
> reported in a ticket (external to the system).
> >
> >[Non-text portions of this message have been removed]
> >
> >
> >
> >
> >
>
> [Non-text portions of this message have been removed]
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2238 / Virus Database: 2639/5618 - Release Date: 02/20/13
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2238 / Virus Database: 2639/5618 - Release Date: 02/20/13
>
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]
Are you aware of anything in Epicor or of a developed report that can provide...........

Our SOX and internal auditors want us to have the ability to run a report that will identify over a period of time (like a month) all the changes made to the Epicor system. They want us to be able to have this report identify all changed, configuration settings, reports, BAQ, BAMs, screens, filed additions, etc. They are basically looking for a way to have the system tell us all changes made so we can then match up a ticket to that change.

Epicor has suggested we use Solution Manager but I think you only get information out of that when a human inputs information. The auditors want to have the report identify changes that may have been made and not reported in a ticket (external to the system).
Have you tried Change logs? Depending on what your auditors are looking for you can set these up to automatically record changes to certain fields. Of course the system only starts recording once you turn these on...it will not look back at history.

Manasa













From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of jim_chance
Sent: Wednesday, February 20, 2013 7:39 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Epicor SOX audit report?



Are you aware of anything in Epicor or of a developed report that can provide...........

Our SOX and internal auditors want us to have the ability to run a report that will identify over a period of time (like a month) all the changes made to the Epicor system. They want us to be able to have this report identify all changed, configuration settings, reports, BAQ, BAMs, screens, filed additions, etc. They are basically looking for a way to have the system tell us all changes made so we can then match up a ticket to that change.

Epicor has suggested we use Solution Manager but I think you only get information out of that when a human inputs information. The auditors want to have the report identify changes that may have been made and not reported in a ticket (external to the system).



[Non-text portions of this message have been removed]
Aren't the change logs solely data/record/field based?Â

This SOX report is to look at technical, customizations, configurations, BAQ's, BAM's, BPM's that have changed due to their potential of impacting the logic of the applications behavior - something SOX auditors want to track.Â




>________________________________
> From: Manasa Reddy <mreddy@...>
>To: "'vantage@yahoogroups.com'" <vantage@yahoogroups.com>
>Sent: Wednesday, February 20, 2013 9:04 AM
>Subject: RE: [Vantage] Epicor SOX audit report?
>
>

>Have you tried Change logs? Depending on what your auditors are looking for you can set these up to automatically record changes to certain fields. Of course the system only starts recording once you turn these on...it will not look back at history.
>
>Manasa
>
>From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of jim_chance
>Sent: Wednesday, February 20, 2013 7:39 AM
>To: vantage@yahoogroups.com
>Subject: [Vantage] Epicor SOX audit report?
>
>Are you aware of anything in Epicor or of a developed report that can provide...........
>
>Our SOX and internal auditors want us to have the ability to run a report that will identify over a period of time (like a month) all the changes made to the Epicor system. They want us to be able to have this report identify all changed, configuration settings, reports, BAQ, BAMs, screens, filed additions, etc. They are basically looking for a way to have the system tell us all changes made so we can then match up a ticket to that change.
>
>Epicor has suggested we use Solution Manager but I think you only get information out of that when a human inputs information. The auditors want to have the report identify changes that may have been made and not reported in a ticket (external to the system).
>
>[Non-text portions of this message have been removed]
>
>
>
>
>

[Non-text portions of this message have been removed]
Jim, not sure what others in public companies do, but in the past I've set up a plethora of SQL Triggers to track the things past SOX auditors thought was necessary to appease themselves. I set up triggers on various tables which subsequently populated a UD table with the necessary details. Then I could run a report on that table. I chose to not use ChangeLog or BPMs because BPMs aren't available on every table (at least in 8.03.xxx).



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Jim Chance
Sent: Wednesday, February 20, 2013 9:33 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Epicor SOX audit report?





Aren't the change logs solely data/record/field based?

This SOX report is to look at technical, customizations, configurations, BAQ's, BAM's, BPM's that have changed due to their potential of impacting the logic of the applications behavior - something SOX auditors want to track.

>________________________________
> From: Manasa Reddy mreddy@... <mailto:mreddy%40mccoyglobal.com> >
>To: "vantage@yahoogroups.com <mailto:%26%2339%3Bvantage%40yahoogroups.com> vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> >
>Sent: Wednesday, February 20, 2013 9:04 AM
>Subject: RE: [Vantage] Epicor SOX audit report?
>
>
>
>Have you tried Change logs? Depending on what your auditors are looking for you can set these up to automatically record changes to certain fields. Of course the system only starts recording once you turn these on...it will not look back at history.
>
>Manasa
>
>From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On Behalf Of jim_chance
>Sent: Wednesday, February 20, 2013 7:39 AM
>To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
>Subject: [Vantage] Epicor SOX audit report?
>
>Are you aware of anything in Epicor or of a developed report that can provide...........
>
>Our SOX and internal auditors want us to have the ability to run a report that will identify over a period of time (like a month) all the changes made to the Epicor system. They want us to be able to have this report identify all changed, configuration settings, reports, BAQ, BAMs, screens, filed additions, etc. They are basically looking for a way to have the system tell us all changes made so we can then match up a ticket to that change.
>
>Epicor has suggested we use Solution Manager but I think you only get information out of that when a human inputs information. The auditors want to have the report identify changes that may have been made and not reported in a ticket (external to the system).
>
>[Non-text portions of this message have been removed]
>
>
>
>
>

[Non-text portions of this message have been removed]



No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2238 / Virus Database: 2639/5618 - Release Date: 02/20/13




-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2238 / Virus Database: 2639/5618 - Release Date: 02/20/13


[Non-text portions of this message have been removed]