[Vantage 6.10.518] Issue with GL Journal vs Labor

Goodness sakes I know you can't change the details after capture has
been completed. Never tried to actually delete the day's labor. I am
glad no one here was that bold to try.





[Non-text portions of this message have been removed]
Our Controller just discovered an issue where Period Posting totals do
not match up with some journal entries. I'm not sure exactly on what
report he is looking but what he showed me is using Account Tracker we
went to our WIP Labor account, selected our last period and Details,
selected Periodic Posting Process for a specific day and then Cost
Transaction. What we see is the amount on the detail lines does not
match the total on the header of the screen. After digging into it, I
traced the GLJrnlDtl back to the GLJrnSrc transactions. Those
transactions added up correctly to the amount on the header
(GLJrnDtl.TransAmt). I then found the field GLJrnSrc.LaborHedSeq field
for one of the records has a value for a LaborHed record that doesn't
exist. The amount of the missing Labor transaction is exactly the
amount that the entry is off. It is almost like someone deleted a labor
record but the corresponding GLJrnSrc record did not get deleted as well
(hopefully this makes sense to someone out there).

I'm wondering if anyone has seen this before or can verify the latest
version of Vantage doesn't exhibit this problem. I'm trying to validate
the latest release and upgrade at the end of the month so knowing this
works will help justify the work to get upgraded. If you want to see if
your database has this issue, below is an Access query that can be used
to find orphaned GLJrnSrc records:

SELECT PUB_GLJrnDtl.FiscalYear, PUB_GLJrnDtl.FiscalPeriod,
PUB_GLJrnDtl.JEDate, PUB_GLJrnDtl.GLDept, PUB_GLJrnDtl.GLChart,
PUB_GLJrnDtl.GLDiv, PUB_GLJrnSrc.TransAmt
FROM PUB_GLJrnDtl INNER JOIN (PUB_GLJrnSrc LEFT JOIN PUB_LaborHed ON
(PUB_GLJrnSrc.LaborHedSeq = PUB_LaborHed.LaborHedSeq) AND
(PUB_GLJrnSrc.Company = PUB_LaborHed.Company)) ON
(PUB_GLJrnDtl.JournalLine = PUB_GLJrnSrc.JournalLine) AND
(PUB_GLJrnDtl.JournalNum = PUB_GLJrnSrc.JournalNum) AND
(PUB_GLJrnDtl.FiscalYear = PUB_GLJrnSrc.FiscalYear) AND
(PUB_GLJrnDtl.Company = PUB_GLJrnSrc.Company)
WHERE (((PUB_GLJrnSrc.TransAmt)>0) AND ((PUB_LaborHed.LaborHedSeq) Is
Null) AND ((PUB_GLJrnSrc.TranSource)="L"))
ORDER BY PUB_GLJrnDtl.FiscalYear DESC , PUB_GLJrnDtl.FiscalPeriod DESC ,
PUB_GLJrnDtl.JEDate DESC;

For the account that is displayed, check in Vantage if the sum of the
detail records match the value on the top of the screen (maybe it's not
supposed to and I'm just chasing my tail!) for the Cost Transactions.
When I run the query I get over 800 records with the issue occuring
anywhere from never to several times per month.

Thanks,
Butch





[Non-text portions of this message have been removed]
We have had some places where the screen just doesn't show you all the
transactions ... could it be as simple as that?





[Non-text portions of this message have been removed]
To further elaborate on this message, it appears the problem is due to
deleted labor records. Here's the scenario:

1) Enter labor information for a day for a job(s)
2) Capture COS/WIP activity
3) The Detail menu item is unavailable so you cannot modify a detail
record
4) Select Time | Delete Time to delete the entire day's captured entries

After checking with our production manager, some techs had mis-entered
labor (they use the Labor Edit report to do their time cards) so they
went in and deleted the days activity and then re-entered it. Also
found a few cases where a user entered their information for Sunday, it
was captured, then they deleted the entries and entered them again for
Friday. As a result for both cases during the next capture, more labor
was charged against the account code. Epicor has confirmed this is an
issue that has been fixed in 8.0 but has no plans at this time to fix it
in 6.1. Only action right now is to train the users to not delete labor
records and to write a BAM to notify me if anyone does so.

Butch

________________________________

From: Butch Menge
Sent: Wednesday, June 14, 2006 4:55 PM
To: 'vantage@yahoogroups.com'
Subject: [Vantage 6.10.518] Issue with GL Journal vs Labor


Our Controller just discovered an issue where Period Posting totals do
not match up with some journal entries. I'm not sure exactly on what
report he is looking but what he showed me is using Account Tracker we
went to our WIP Labor account, selected our last period and Details,
selected Periodic Posting Process for a specific day and then Cost
Transaction. What we see is the amount on the detail lines does not
match the total on the header of the screen. After digging into it, I
traced the GLJrnlDtl back to the GLJrnSrc transactions. Those
transactions added up correctly to the amount on the header
(GLJrnDtl.TransAmt). I then found the field GLJrnSrc.LaborHedSeq field
for one of the records has a value for a LaborHed record that doesn't
exist. The amount of the missing Labor transaction is exactly the
amount that the entry is off. It is almost like someone deleted a labor
record but the corresponding GLJrnSrc record did not get deleted as well
(hopefully this makes sense to someone out there).

I'm wondering if anyone has seen this before or can verify the latest
version of Vantage doesn't exhibit this problem. I'm trying to validate
the latest release and upgrade at the end of the month so knowing this
works will help justify the work to get upgraded. If you want to see if
your database has this issue, below is an Access query that can be used
to find orphaned GLJrnSrc records:

SELECT PUB_GLJrnDtl.FiscalYear, PUB_GLJrnDtl.FiscalPeriod,
PUB_GLJrnDtl.JEDate, PUB_GLJrnDtl.GLDept, PUB_GLJrnDtl.GLChart,
PUB_GLJrnDtl.GLDiv, PUB_GLJrnSrc.TransAmt
FROM PUB_GLJrnDtl INNER JOIN (PUB_GLJrnSrc LEFT JOIN PUB_LaborHed ON
(PUB_GLJrnSrc.LaborHedSeq = PUB_LaborHed.LaborHedSeq) AND
(PUB_GLJrnSrc.Company = PUB_LaborHed.Company)) ON
(PUB_GLJrnDtl.JournalLine = PUB_GLJrnSrc.JournalLine) AND
(PUB_GLJrnDtl.JournalNum = PUB_GLJrnSrc.JournalNum) AND
(PUB_GLJrnDtl.FiscalYear = PUB_GLJrnSrc.FiscalYear) AND
(PUB_GLJrnDtl.Company = PUB_GLJrnSrc.Company)
WHERE (((PUB_GLJrnSrc.TransAmt)>0) AND ((PUB_LaborHed.LaborHedSeq) Is
Null) AND ((PUB_GLJrnSrc.TranSource)="L"))
ORDER BY PUB_GLJrnDtl.FiscalYear DESC , PUB_GLJrnDtl.FiscalPeriod DESC ,
PUB_GLJrnDtl.JEDate DESC;

For the account that is displayed, check in Vantage if the sum of the
detail records match the value on the top of the screen (maybe it's not
supposed to and I'm just chasing my tail!) for the Cost Transactions.
When I run the query I get over 800 records with the issue occuring
anywhere from never to several times per month.

Thanks,
Butch





[Non-text portions of this message have been removed]