First-Time Running Capture COS/WIP Activity

If the costs are posted to whatever account is set up in GL, then I
would have expected the dollar-value shown on one (or more) of the
accounts in GL to have changed on my test system when I ran the
procedure. Nothing changed. What does that tell me?

--Ari

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of RSN
Sent: Tuesday, June 24, 2008 3:29 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: First-Time Running Capture COS/WIP Activity



Your COS/WIP posted costs are posted to the Material COS account
whatever that may be set up in your GL.

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






[Non-text portions of this message have been removed]
Can anyone tell me what might be the consequences of running the Capture
COS/WIP Activity process for the very first time after 4 years of
production use?

I was trying to figure out what jobs we actually had in-process, and
when the report crested 170 pages, I went looking for a reason why jobs
from 4 years ago were still shown as "WIP." I'd like to run the Capture
process to clear out the old jobs from WIP.

On my test system, it turned the 174 pages into 26 pages, and I compared
the balances of all GL accounts from before and after the process - none
of the balances changed.

Why would I need to "adjust transaction dates" when running the process?
Is there anything else I need to watch out for?

Thanks in advance.
--Ari


[Non-text portions of this message have been removed]
Hi, we're in a similar boat,

Are you running 6.10?
For the jobs, you'll need to manually close them with Job Close

I'm not sure if it happened to anyone else, but when I tried closing
jobs, the job close function will run and run and run for a couple of
days! and the BI file will grow to over 25 gigabyte in size before the
job is finally closed.

Just a heads up to you, in case it happens.


--- In vantage@yahoogroups.com, "Ari Footlik" <ari@...> wrote:
>
> Can anyone tell me what might be the consequences of running the Capture
> COS/WIP Activity process for the very first time after 4 years of
> production use?
>
> I was trying to figure out what jobs we actually had in-process, and
> when the report crested 170 pages, I went looking for a reason why jobs
> from 4 years ago were still shown as "WIP." I'd like to run the Capture
> process to clear out the old jobs from WIP.
>
> On my test system, it turned the 174 pages into 26 pages, and I compared
> the balances of all GL accounts from before and after the process - none
> of the balances changed.
>
> Why would I need to "adjust transaction dates" when running the process?
> Is there anything else I need to watch out for?
>
> Thanks in advance.
> --Ari
>
>
> [Non-text portions of this message have been removed]
>
You need to close the job first. If the job is not closed, the cost will be
still stayed in WIP.



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
eltaria.foong
Sent: Wednesday, June 18, 2008 2:29 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: First-Time Running Capture COS/WIP Activity



Hi, we're in a similar boat,

Are you running 6.10?
For the jobs, you'll need to manually close them with Job Close

I'm not sure if it happened to anyone else, but when I tried closing
jobs, the job close function will run and run and run for a couple of
days! and the BI file will grow to over 25 gigabyte in size before the
job is finally closed.

Just a heads up to you, in case it happens.

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com, "Ari
Footlik" <ari@...> wrote:
>
> Can anyone tell me what might be the consequences of running the Capture
> COS/WIP Activity process for the very first time after 4 years of
> production use?
>
> I was trying to figure out what jobs we actually had in-process, and
> when the report crested 170 pages, I went looking for a reason why jobs
> from 4 years ago were still shown as "WIP." I'd like to run the Capture
> process to clear out the old jobs from WIP.
>
> On my test system, it turned the 174 pages into 26 pages, and I compared
> the balances of all GL accounts from before and after the process - none
> of the balances changed.
>
> Why would I need to "adjust transaction dates" when running the process?
> Is there anything else I need to watch out for?
>
> Thanks in advance.
> --Ari
>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]
Thanks for the responses. Yes - the jobs in question are already closed
(though the process we follow for actually closing jobs is another
headache). Nobody knew that the COS/WIP rollup had to be run to
finalize the process, so it was never done. Since we're not really
using Vantage for "costing" purposes (yet - I'm working on that),
nobody's really ever noticed.

Where will I see "cost" info updated after I do the rollup?

--Ari

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Keith Kwok
Sent: Wednesday, June 18, 2008 2:39 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: First-Time Running Capture COS/WIP Activity



You need to close the job first. If the job is not closed, the cost will
be
still stayed in WIP.

_____

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of
eltaria.foong
Sent: Wednesday, June 18, 2008 2:29 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: First-Time Running Capture COS/WIP Activity

Hi, we're in a similar boat,

Are you running 6.10?
For the jobs, you'll need to manually close them with Job Close

I'm not sure if it happened to anyone else, but when I tried closing
jobs, the job close function will run and run and run for a couple of
days! and the BI file will grow to over 25 gigabyte in size before the
job is finally closed.

Just a heads up to you, in case it happens.

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com, "Ari
Footlik" <ari@...> wrote:
>
> Can anyone tell me what might be the consequences of running the
Capture
> COS/WIP Activity process for the very first time after 4 years of
> production use?
>
> I was trying to figure out what jobs we actually had in-process, and
> when the report crested 170 pages, I went looking for a reason why
jobs
> from 4 years ago were still shown as "WIP." I'd like to run the
Capture
> process to clear out the old jobs from WIP.
>
> On my test system, it turned the 174 pages into 26 pages, and I
compared
> the balances of all GL accounts from before and after the process -
none
> of the balances changed.
>
> Why would I need to "adjust transaction dates" when running the
process?
> Is there anything else I need to watch out for?
>
> Thanks in advance.
> --Ari
>
>
> [Non-text portions of this message have been removed]
>

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






[Non-text portions of this message have been removed]
----quote fom eltaria.foong-----
I'm not sure if it happened to anyone else, but when I tried closing
jobs, the job close function will run and run and run for a couple of
days! and the BI file will grow to over 25 gigabyte in size before the
job is finally closed.
------------------

We've had this happen but it has always been a messed up production rate conversion factor....hrs/pc instead of pcs/hr. In some cases this results in a HUGE qty than does indeed run for days and in one case the BI file consumed the entire drive...crashing the DB. Now if a job close takes more than a few minutes we kill the process and go looking for the cause.
-Todd C.



[Non-text portions of this message have been removed]
I once had the same problem with the BI file. The cause was that the
Job Number Generation length in Company setup was too small. Once I
increased the job number length the problem was resolved.

David Pfiester
NuStep, Inc.

--- In vantage@yahoogroups.com, Todd Caughey <caugheyt@...> wrote:
>
> ----quote fom eltaria.foong-----
> I'm not sure if it happened to anyone else, but when I tried closing
> jobs, the job close function will run and run and run for a couple
of
> days! and the BI file will grow to over 25 gigabyte in size before
the
> job is finally closed.
> ------------------
>
> We've had this happen but it has always been a messed up production
rate conversion factor....hrs/pc instead of pcs/hr. In some cases
this results in a HUGE qty than does indeed run for days and in one
case the BI file consumed the entire drive...crashing the DB. Now if
a job close takes more than a few minutes we kill the process and go
looking for the cause.
> -Todd C.
>
>
>
> [Non-text portions of this message have been removed]
>
Hi, Todd, Dave,

Thanks for the information, I raised this with epicor support, but
they never was able to let me know what the root cause is.

I had the DB crash too, when I was closing off some jobs left over
from the early stages of the us going live. It's good to finally know
the cause of it.

--- In vantage@yahoogroups.com, "Dave Pfiester" <dpfiester@...> wrote:
>
> I once had the same problem with the BI file. The cause was that the
> Job Number Generation length in Company setup was too small. Once I
> increased the job number length the problem was resolved.
>
> David Pfiester
> NuStep, Inc.
>
> --- In vantage@yahoogroups.com, Todd Caughey <caugheyt@> wrote:
> >
> > ----quote fom eltaria.foong-----
> > I'm not sure if it happened to anyone else, but when I tried closing
> > jobs, the job close function will run and run and run for a couple
> of
> > days! and the BI file will grow to over 25 gigabyte in size before
> the
> > job is finally closed.
> > ------------------
> >
> > We've had this happen but it has always been a messed up production
> rate conversion factor....hrs/pc instead of pcs/hr. In some cases
> this results in a HUGE qty than does indeed run for days and in one
> case the BI file consumed the entire drive...crashing the DB. Now if
> a job close takes more than a few minutes we kill the process and go
> looking for the cause.
> > -Todd C.
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
I'm confused. We just migrated from Ver 4.4 to 8.03.403D back in
January, and didn't realize the Capture WIP/Recon process needed to
be run. Until we ran WIP/Recon our accounts were going nuts trying
to figure out what was happeing to the General Ledger. So I don't
know how you managed without doing it.

To understand what WIP/Recon does, I did a lot of 'experimenting' in
the test company. There is a document that does an OK job of
explaining all the GL transactions that will occur when the WIP/Recon
is run. The basic diagram can be found in the help under the
topic "Inventory/WIP Reconciliation Report", scroll to the bottom and
select the link for "How are G/L account numbers assigned to
inventory transactions?"

Calvin


--- In vantage@yahoogroups.com, "Ari Footlik" <ari@...> wrote:
>
> Can anyone tell me what might be the consequences of running the
Capture
> COS/WIP Activity process for the very first time after 4 years of
> production use?
>
> I was trying to figure out what jobs we actually had in-process, and
> when the report crested 170 pages, I went looking for a reason why
jobs
> from 4 years ago were still shown as "WIP." I'd like to run the
Capture
> process to clear out the old jobs from WIP.
>
> On my test system, it turned the 174 pages into 26 pages, and I
compared
> the balances of all GL accounts from before and after the process -
none
> of the balances changed.
>
> Why would I need to "adjust transaction dates" when running the
process?
> Is there anything else I need to watch out for?
>
> Thanks in advance.
> --Ari
>
>
> [Non-text portions of this message have been removed]
>
Your COS/WIP posted costs are posted to the Material COS account whatever that may be set up in your GL.



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