× 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.



We have had some instances where the updnog flag in FLP007 is marked as 
posted and the updnog flag in the flp008 is not marked as posted.  When 
this happens all you have to do is set the updnog flag in FLp007 to zero 
and it will post.  We run a query every night to check this.   I believe 
if you look at the details for that part of the transaction when looking 
in the session, it will tell you it is not posted. 
Margaret 



"Lemon, Michael" <MLemon@xxxxxxxxxxx> 
Sent by: system21-bounces@xxxxxxxxxxxx
07/22/2004 01:39 PM
Please respond to
System 21 Users <system21@xxxxxxxxxxxx>


To
"'System 21 Users'" <system21@xxxxxxxxxxxx>
cc

Subject
RE: [SYSTEM21]   General Journal in GL Problem






Sorry, UPDNOG is in the FLP008 and FLP007 files for that Company, Source,
Type, Doc Ref #.

-----Original Message-----
From: Lemon, Michael [mailto:MLemon@xxxxxxxxxxx]
Sent: Thursday, July 22, 2004 1:36 PM
To: 'System 21 Users'
Subject: RE: [SYSTEM21] General Journal in GL Problem


Its possible that there was some sort of error while posting part of the
transaction.  Check to see if the UPDNOG field on the record says zero or
-1.  If it is a negative one, then system 21 recognized an error while
posting the transaction.  If it is zero, then something happened (maybe 
the
GLBACK3 job went down) while it posted the transaction.

I doubt that it has a zero though.  If it is, you may want to see if your 
GL
background job has a message waiting (or is down altogether).

-----Original Message-----
From: GREGORY WIECZOREK [mailto:greg@xxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, July 22, 2004 1:29 PM
To: System 21 Users
Subject: RE: [SYSTEM21] General Journal in GL Problem


Hi Scott

I don't think we have a purge or archied situation
here. The "good" portion of the session was for the
current GL period.

Greg
--- "Grinstead, Scott" <SAGrinstead@xxxxxxxxxxxxxx>
wrote:
> Is it possible that the session detail has been
> archived or purged?
>
> Scott
>
> -----Original Message-----
> From: GREGORY WIECZOREK
> [mailto:greg@xxxxxxxxxxxxxxxxxxxxx]
> Sent: Thursday, July 22, 2004 12:56 PM
> To: JBAUSERLIST
> Subject: [SYSTEM21] General Journal in GL Problem
>
> Group
>
> A user reported that they were unable to drill down
> to
> the account posting detail in session inquiry. The
> session in question contained 2 references, both
> source G, type GJ. Drill down to the first reference
> works, the 2nd does not. I think we have a corrupted
> session. The second document is not in the DOCTRANS
> file. The SESSION record has nothing in the finish
> time and the number of transtions fields.
>
> I think if we soft remove the 2nd document from
> SESTRANS and give SESSION a complete time and
> transaction count things should be OK.
>
> Does anyone have another suggestion as to how to
> deal
> with this?
>
> Greg
>
>
>
> _______________________________________________
> 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.
>
>

_______________________________________________
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.
_______________________________________________
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-Ups:
Replies:

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.