Re: GLD541 - shows "Journal header" already exists

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.
--
[ Picked text/plain from multipart/alternative ]
Thanks.  A couple of more questions:

Is it necessary (or advisable?) to change the corresponding entries in
RAR to have the same journal entry number?

Can I assume that if the entry is still in GJW with that JE number that
it is not posted?  Meaning, that all entries with the JE number in GJW
should be changed?

Thanks.


>>> Roger.Henady@thorco.com 04/02/02 06:38AM >>>

The GJW is the only place you have to change to Journal Entry number.
Go
to GLD119 Journal Source Maintenance look for the AR source and find
the
next  reference  use this number to fix the GJW record that is in
error,
then increase this by one.     This will also happen when someone does
a
GLD540 Sub system post and there is a open batch in A/R or A/P.
This
will take care of the duplicate error.    In GJW you want to make sure
the
ID is JW.


Roger Henady
Thorco Industries
(417) 682-1340



                    "Tom
                    Jedrzejewicz @         To:
<bpcs-l@midrange.com>
                    San Pedro"             cc:
                    <TJedrzejewicz         Subject:     GLD541 - shows
"Journal header" already exists
                    Sent by:
                    bpcs-l-admin@MI
                    DRANGE.COM


                    04/01/2002
                    05:31 PM
                    Please respond
                    to bpcs-l






I am an experienced AS400 analyst (PRMS is my heritage) but new to
BPCS.  We are Version 4.0 Release 03

One of the users brought me a problem with an AR batch which won't
post
to GL because of a duplicate journal ID.  She tells me that this has
happened from time to time when two folks post to AR at the same time,
and that my predecessor fixed it by renaming the journal.

Makes sense to me, but I am not sure where to do the adjustment.  It
appears that making the change to the relevant entries in GJW and RAR
should do it, but I do not want to get bitten.

Any help that you all can offer would be most appreciated!


Tom Jedrzejewicz
IS Manager, Contessa Food Products
310 832 8000
tjedrzejewicz@contessa.com
--------------------


THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY
TO
WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the
reader of this message is not the intended recipient, or the employee
or
agent responsible for delivering the message to the intended recipient,
you
are hereby notified that any dissemination, distribution, copying,
downloading, storing or forwarding of this communication is prohibited.
 If
you have received this communication in error, please notify us
immediately
via email and delete the message from your computer files and/or data
base.
Thank you.
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
or email: BPCS-L-request@midrange.com
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@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.



THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH 
IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL 
AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the reader of this message 
is not the intended recipient, or the employee or agent responsible for 
delivering the message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, downloading, storing or forwarding of 
this communication is prohibited.  If you have received this communication in 
error, please notify us immediately via email and delete the message from your 
computer files and/or data base.  Thank you.