|
midrange.com
The GLUP96 flag gets updated when the extract is done so you should have an
unposted session in AFI. As this has only happened to me a few times (it
happened just last week) and the recovery is simple, we have never spent
the time to identify the specific lock.. A check is made prior to calling
the update portion of the process. Have you tried running this process
manually (1/FIP) to see if it will run OK or give you an error message?
FIP51 is the AFI header and will tell you the status of the extract and
update - each flag will be set to '1' if completed. The AFI extract
file(FIP45) has a flag (GPST45) which is set to '1' when the updates have
been processed. Hopefully everything will be set so you can simply run the
update. You may then need to change the timing of your run at night.
Richard Caldicott
Director of Implementations
& Efficiency
Tandy Brands Accessories
817-548-0090 extn 146
<mon.ferriols@ion
ics-ems.com>
Sent by: To
system21-bounces@ <system21@xxxxxxxxxxxx>
midrange.com cc
Subject
04/13/2005 08:50 [SYSTEM21] RE: SYSTEM21 Digest,
PM Vol 3, Issue 54
Please respond to
System 21 Users
<system21@midrang
e.com>
Hello Richard, what jobs shouldn't be running when the AFI extract is
run? What happened is when we ran the extract, some were posted and some
were not. If we compare the transactions in INP96 vs what was posted,
there's a difference. What's more is the GLUP96 flag for the unposted
transactions is 1.
Regards,
Mon
-----Original Message-----
From: system21-request@xxxxxxxxxxxx
[mailto:system21-request@xxxxxxxxxxxx]
Sent: Thursday, April 14, 2005 1:02 AM
To: system21@xxxxxxxxxxxx
Subject: SYSTEM21 Digest, Vol 3, Issue 54
Send SYSTEM21 mailing list submissions to
system21@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/system21
or, via email, send a message with subject or body 'help' to
system21-request@xxxxxxxxxxxx
You can reach the person managing the list at
system21-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of SYSTEM21 digest..."
Today's Topics:
1. AFI error message (mon.ferriols@xxxxxxxxxxxxxx)
2. Re: AFI error message (Richard_Caldicott@xxxxxxxxxxxxxxx)
----------------------------------------------------------------------
message: 1
date: Wed, 13 Apr 2005 16:51:43 +0800
from: <mon.ferriols@xxxxxxxxxxxxxx>
subject: [SYSTEM21] AFI error message
We get the ff: error message whenever we choose any option in /FIM.
Happened right after March month-end closing. Where exactly has it been
detected? Is it INP96 versus?
Outstanding transactions not yet
processed into the General Ledger
have been detected.
MAINTENANCE OF DATA MUST BE DONE
WITH CAUTION AS CHANGES MAY GIVE
RISE TO UNPREDICTABLE RESULTS
Any inputs would be greatly appreciated. Thanks.
Mona
------------------------------
message: 2
date: Wed, 13 Apr 2005 08:54:45 -0500
from: Richard_Caldicott@xxxxxxxxxxxxxxx
subject: Re: [SYSTEM21] AFI error message
This happens when an extract has been done but the actually posting has
not
been performed. You can run the extract and post as 2 separate jobs but
most companies have the flag set to automatically post. Occasionally
the
post job will not run due to a lock on a file - it has happened to us
twice
and I have seen it before at other S/21 users a few times.
If you do the 2 step process then you need to complete the posting. If
you
do the automatic method then you can still go to the FIP menu and take
option 1 to complete the posting. As AFI is not a company specific
application it could even be a test company that is causing the problem.
If you go into the inquiry program, 31/FIP you should be able to check
for
the extract that is causing your problem. Usually they sort themselves
out
when the next run takes place - unless of course you have an ongoing
conflict between 2 jobs.
Richard Caldicott
Director of Implementations
& Efficiency
Tandy Brands Accessories
817-548-0090 extn 146
<mon.ferriols@ion
ics-ems.com>
Sent by:
To
system21-bounces@ <system21@xxxxxxxxxxxx>
midrange.com
cc
Subject
04/13/2005 03:51 [SYSTEM21] AFI error message
AM
Please respond to
System 21 Users
<system21@midrang
e.com>
We get the ff: error message whenever we choose any option in /FIM.
Happened right after March month-end closing. Where exactly has it been
detected? Is it INP96 versus?
Outstanding transactions not yet
processed into the General Ledger
have been detected.
MAINTENANCE OF DATA MUST BE DONE
WITH CAUTION AS CHANGES MAY GIVE
RISE TO UNPREDICTABLE RESULTS
Any inputs would be greatly appreciated. Thanks.
Mona
_______________________________________________
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) digest 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.
End of SYSTEM21 Digest, Vol 3, Issue 54
***************************************
_______________________________________________
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 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.
