× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I suggest everyone check their inventory calendar (7/INM).  For some reason, at 
the end of every year, a lot of people experience their calendars rolling over 
two periods instead of just one.  It has happened here for the past two years, 
but this year it did not.

We have it on our checklist now to look at before start of business in the new 
year.

_____________________________________

Randy Rasp
AER Manufacturing


---- Chris Payne <CPayne@xxxxxxxxxxxxxxx> wrote: 

=============
We had this very problem yesterday, and the files that we updated to correct it 
were:

osld1f3.inp96
osld1f3.inp96
osld1f3.inp95
osld1f3.inp95
oslpdf3.pcp56
oslpdf3.pcp62
oslpdf3.pcp59
oslpdf3.pcp58
oslpdf3.pcp53
oslpdf3.pcp93

PCP58, PCP53 and PCP93 would have been affected but did not actually have any 
data in them. The SQL statements that we ran to fix the problem are as follows:

update osld1f3.inp96 set perd96 = 1 WHERE YRPR96 = 10602
update osld1f3.inp96 set yrpr96 = 10601 WHERE YRPR96 = 10602
update osld1f3.inp95 set perd95 = 1 WHERE YRPR95 = 10602
update osld1f3.inp95 set yrpr95 = 10601 WHERE YRPR95 = 10602
update oslpdf3.pcp56 set cper56 = 1 WHERE CYER56=106 and CPER56=2
update oslpdf3.pcp62 set cper62 = 1 WHERE CYER62=106 and CPER62=2
update oslpdf3.pcp59 set cper59 = 1 WHERE CYER59=106 and CPER59=2

anyone running mass updates against live production files should be VERY 
careful, and when we did all this, we had GEAC on the phone, which I think is 
probably a very good idea for anyone planning on changing large amounts of data 
by hand. Another potential problem is whether or not these transactions have 
hit the financial side yet.

Christopher

-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx] On 
Behalf Of Ostrowski, Bruce
Sent: Thursday, January 05, 2006 10:44 AM
To: System 21 Users
Subject: [SYSTEM21] Transaction Posting to the wrong period.

We had 1 ½ days of transaction post to the wrong period at the beginning of 
this year.  The transactions were invoices and inventory transactions.  Does 
anyone know all the files that need change to correct the posting period?  We 
have correct the posting problem but know need to clean up the incorrect 
transactions.

 

Bruce Ostrowski            

Utilimaster

 

_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.


_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.