"don't tell the auditors" ----> fixing the G/L

Paul is exactly correct!  You don't want to fix general ledger
entries with SQL and DFUs. Congress invented the Sarbanes-
Oxley Act (SOX) to halt exactly that genre of creative
financial management.

But --- how would you prove to an auditor that your general
ledger was never adjusted that way?

If Stitch-in-Time® Data Integrity Software had been
operational on your system, the auditor would receive a
decisive, documented answer in minutes.
   http://www.unbeatenpathintl.com/stitch_in_time/source/1.html

That robust internal control functionality has impressed
enterprises under SOX scrutiny, companies looking to improve
security, and the judges at Search400.com who awarded this
"Security Product of the Year" recognition:
   http://www.unbeatenpathintl.com/award/source/1.html

You can get a free demo copy for your iSeries. The software
works on any iSeries file, not just BPCS. 

Here's several more clever/affordable SOX compliance ideas: 
Stocking Stuffers (tm) for SOX:
   http://www.unbeatenpathintl.com/SOXstuffers/source/1.html

Happy Easter,

Thomas Garvey
Unbeaten Path International

toll free North America: (888) 874-8008
international voice line: (262) 681-3151
upi@xxxxxxxxxx
www.unbeatenpathintl.com



++++++++++++++++++++++++++++++++++++++++++++++++++
From: Paul.Bogle@xxxxxxxxxx
To: SSA's BPCS ERP System
Sent: Thursday, March 25, 2004 11:17 AM
Subject: Re: Fixing G/L Payroll Entries

Don't tell the auditors that you are modifying files in the General Ledger
with SQL and DFUs !
I usually copy the journal data and create a journal in the correct period
that reverses out in the next period to contra the error.

Paul Bogle
Business Systems Manager



++++++++++++++++++++++++++++++++++++++++
From: daparnin@xxxxxxxxxxxxxxxxxx
To:     bpcs-l@xxxxxxxxxxxx
25/03/2004 15:09
Subject:   Fixing G/L Payroll Entries

Good morning all,

We are on 4.05CD.  Our payroll cycle for hourly workers pulls time data
from Kronos into Software Plus where salaried employees are added and
checks are generated, then the G/L data gets dumped into the GJW file for
posting by GLD540 in BPCS.  Payroll is run a week ahead of when the checks
are issued.  Our next pay day is March 31 but our period-end is March 28.
The payroll person didn't get the date changed when payroll was run this
week and the checks posted into the next period when accounting really
wanted them posted in the current period.

I know that the GJH and GJD files are affected and it's a simple matter to
changed the affected journal entries with SQL and DFU.

My question is are there any other files that may be affected?  I've worked
for years with BPCS manufacturing but have had limited experience
with the financial side. Thanks.

Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571