Colin_Hugill
Reputable Poster
Julius,
Before anything else, would you please follow the basic protocol for
this list by including in your email (usually included in the signature
text) the JDE Release and CUME levels currently in use at Steamships.
How long has this problem existed? When did it first become apparent?
Check prior history emails on this topic by searching JDEList.
First thing to check is that there are no "manual" journal entries in
the AR control account(s). If there are any, then they should be
reversed out and the PEC for the control account set to "M" and then
rerun the integrity report. If they are not reversed out then their
value must be used to manually adjust the values on the integrity
report.
Second thing, if you are on A7.3 before about cum 10 or 11, then make
sure that your integrity programs have all UQF's applied - there was a
problem with the integrity checking programs (from memory especially AP)
and a UQF was available from the KG.
Thirdly, there is a standard integrity program that checks between AR
and GL by batch - it is on the same standard "G" menu that the AR to GL
by offset program is listed. This will identify which batches are
suspected to be in error. Use this report to determine which batch
transactions to list.
Fourthly, has anyone been adjusting the F0901 balances for the controls
accounts by any method other than the GL post process (ie no DFU, no
SQL, no OBDC, no non JDE programs or interfaces)?
Finally, gut feel and experience lead me to suspect either manual
journals to the control account in GL or a GL Post process that crashed
without updating the control account balance record. Try running the
A/c Balances to Transactions integrity process in general ledger but
make sure you set the selection criteria to select only the AR control
accounts (using specific A/c ID's makes it a faster process).
There is one other possible cause - more than one GL post executing
simultaneously can result in the control account(s) not being updated
correctly. So, make very sure that ALL GL posts execute through one
single threaded job queue. Do not allow users to change job queues for
submitted jobs.
Regards,
Colin
Colin Hugill
Consultant
(World A7.3 cum12)
Before anything else, would you please follow the basic protocol for
this list by including in your email (usually included in the signature
text) the JDE Release and CUME levels currently in use at Steamships.
How long has this problem existed? When did it first become apparent?
Check prior history emails on this topic by searching JDEList.
First thing to check is that there are no "manual" journal entries in
the AR control account(s). If there are any, then they should be
reversed out and the PEC for the control account set to "M" and then
rerun the integrity report. If they are not reversed out then their
value must be used to manually adjust the values on the integrity
report.
Second thing, if you are on A7.3 before about cum 10 or 11, then make
sure that your integrity programs have all UQF's applied - there was a
problem with the integrity checking programs (from memory especially AP)
and a UQF was available from the KG.
Thirdly, there is a standard integrity program that checks between AR
and GL by batch - it is on the same standard "G" menu that the AR to GL
by offset program is listed. This will identify which batches are
suspected to be in error. Use this report to determine which batch
transactions to list.
Fourthly, has anyone been adjusting the F0901 balances for the controls
accounts by any method other than the GL post process (ie no DFU, no
SQL, no OBDC, no non JDE programs or interfaces)?
Finally, gut feel and experience lead me to suspect either manual
journals to the control account in GL or a GL Post process that crashed
without updating the control account balance record. Try running the
A/c Balances to Transactions integrity process in general ledger but
make sure you set the selection criteria to select only the AR control
accounts (using specific A/c ID's makes it a faster process).
There is one other possible cause - more than one GL post executing
simultaneously can result in the control account(s) not being updated
correctly. So, make very sure that ALL GL posts execute through one
single threaded job queue. Do not allow users to change job queues for
submitted jobs.
Regards,
Colin
Colin Hugill
Consultant
(World A7.3 cum12)