SOX????


Thank you very much and best regards
Himanshu Jani

----- Original Message -----
From: "Mary Ann Salas "
<mssqldba-ezmlmshield-x52685271.[Email address protected]
To: "LazyDBA Discussion" <[Email address protected]
Sent: Friday, November 30, 2007 8:53 PM
Subject: RE: Silly Question


> I'm not sure if there is a law governing those kinds of changes but I
> would be more careful and make sure it's not going to be questionable.
> You know, like putting the date entered as 11/01 of this year and the
> date it was posted to accounting was last year. It's like, it's posted
> first before data was entered, but I'm sure you'd catch that.
>
> For us, when those case happens, we put up a process that there is a
> request (has to be approved by only one person within the company who is
> more of a treasury or a finance person), a request to change the status
> of that invoice or that batch from "Posted to Accounting" to a status
> prior to that, something they can still mess with. Once request is
> approved, it's not a change of date, but a change of status and the
> process removes the entries it made to the other tables, it's like a
> clean-up. When status is changed, then users can go ahead and make
> their changes (so I don't do the change), then they can "re-post it to
> accounting", treasury or finance/accounting department does it still so
> they are always in the loop.
> As much as possible, minimal changes are done in the back-end, most will
> be from the front-end.
>
> What you don't want to happen is do a change and create a precedence, as
> they know you can easily correct that careless data entry. Then it may
> happen again and you may be putting yourself in the mud. But as far as
> laws are concerned, I am not sure.
>
> Thanks a lot! HTH!
>
>
> -----Original Message-----
> From: Marty Galvan
> [mailto:mssqldba-ezmlmshield-x20174406.[Email address protected]
> Sent: Friday, November 30, 2007 11:09 AM
> To: LazyDBA Discussion
> Subject: Silly Question
>
> Hi gang,
> can someone tell me if there are any laws against changing data in a
> database. I had a shipper put an incorrect date on the shipment date and
> the only way for me to correct the issue is to go and change the date.
> The problem is that the batch has been closed and invoices have been
> sent out on it. I just want to know if there's any laws on auditing or
> anything that I can reference to not do this? I'm trying to make a case
> against careless data entry.
>
> Thank you,
>
> Marty Galvan
> Database Admin/EDI Coordinator
> Making Memories
> [Email address protected] <mailto:[Email address protected]
> 801-294-0430 x185
>
>
>
>
> ---------------------------------------------------------------------
> TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
> To post a dba job: http://jobs.lazydba.com
> To subscribe : http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>
>
> mailgate2.profitline.com made the following
> annotations---------------------------------------------------------------------The
> information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient is prohibited. If you
> received this message in error, please contact the sender and delete
> the material from any computer.
> ---------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
> To post a dba job: http://jobs.lazydba.com
> To subscribe : http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>
>



MS Sql Server LazyDBA home page