• Subject: RE: Should you Summarize?
  • From: "George Sagen" <gsagen@xxxxxxxxxxxxxxxxxxx>
  • Date: Wed, 9 Feb 2000 10:48:29 -0700
  • Importance: Normal

<Don't count on GXR.  I have found that it is one record per Journal entry
only.  Therefore, if you group, and you summarize, you're out of luck.>

Paul,

I haven't verified personally, but according to the 6.04 Net Change
Document, Page 72:

"Enhancement: Subsystem Cross Reference
Scope
Enhancements to ATP and CEA provide improved reconciliation capabilities of
journal postings from subsystem transactions. Changes cover:
· recording subsystem Cross Reference between subsystem and journals when
journal grouping and/or summarization are utilized.
· CEA inquiry windows
· drill down to subsystem inquiry application(s)
Cross Reference
Standard transaction Cross Reference information is stored, linking each
subsystem transaction and the journal(s) is generated.
In prior releases, only one Cross Reference was kept for each journal but
when journal grouping is enabled, there can be multiple subsystem
transactions contributing to any particular journal."

Is your (or anyone's out there) experience contrary to this? I have never
turned on grouping or summarization when a line-by-line audit procedure was
required, so I have never had opportunity to put the Net Change Doc's claim
to the test.

Geo.


+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.