|
----- Original Message ----- From: <Paul.Bogle@xxxxxxxxxx> To: "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx> 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 > +44 7979 745404 > > > > vincent.byrne@ah. > novartis.com > Sent by: To > bpcs-l-bounces@mi "SSA's BPCS ERP System" > drange.com <bpcs-l@xxxxxxxxxxxx> > cc > > 25/03/2004 15:32 Subject > Re: Fixing G/L Payroll Entries > > Please respond to > "SSA's BPCS ERP > System" > <bpcs-l@midrange. > com> > > > > > > > As far as I'm aware no other files are effected as long at these journals > are unposted. > When the journals are posted the period balances in GGM are updated. > > Regards, > Vincent > > > > > > > > "David A Parnin" <daparnin@xxxxxxxxxxxxxxxxxx> > Sent by: bpcs-l-bounces@xxxxxxxxxxxx > 25/03/2004 15:09 > Please respond to "SSA's BPCS ERP System" > > > To: bpcs-l@xxxxxxxxxxxx > cc: > 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 > daparnin@xxxxxxxxxxxxxxxxxx > > > _______________________________________________ > This is the SSA's BPCS ERP System (BPCS-L) mailing list > To post a message email: BPCS-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/bpcs-l > or email: BPCS-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/bpcs-l. > > > > _______________________________________________ > This is the SSA's BPCS ERP System (BPCS-L) mailing list > To post a message email: BPCS-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/bpcs-l > or email: BPCS-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/bpcs-l. > > > > _______________________________________________ > This is the SSA's BPCS ERP System (BPCS-L) mailing list > To post a message email: BPCS-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/bpcs-l > or email: BPCS-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/bpcs-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.