It really depends on how you choose to summarize the cube.
In the case of Job/OpCode: I then bring in JobOper, JobHead, and
JobOpDtl (and the MfgCube where CubeID = " "). The comparison of the
summarized LaborDtl.ScrapQty (or Actual Scrap) is against the planned
scrap, planned setup hrs, planned, prod hours, planned prod qty,
planned run qty, actual qty completed, etc.
It really is a basis of reducing plan where you can to be more lean
in your processes. If you constantly over plan, you can never make
your process lean. Each operation will produce more than what is
necessary building up WIP Product (space) and WIP Cost (less
margin).
Well...at least that is the intent.
Thanks
Patty Buechler
In the case of Job/OpCode: I then bring in JobOper, JobHead, and
JobOpDtl (and the MfgCube where CubeID = " "). The comparison of the
summarized LaborDtl.ScrapQty (or Actual Scrap) is against the planned
scrap, planned setup hrs, planned, prod hours, planned prod qty,
planned run qty, actual qty completed, etc.
It really is a basis of reducing plan where you can to be more lean
in your processes. If you constantly over plan, you can never make
your process lean. Each operation will produce more than what is
necessary building up WIP Product (space) and WIP Cost (less
margin).
Well...at least that is the intent.
Thanks
Patty Buechler
--- In vantage@yahoogroups.com, "mlezivk" <kevin.mleziva@...> wrote:
>
> We have a similar export that I do here. What is your next step
> after getting the detail summarized?
>
>
> --- In vantage@yahoogroups.com, "bpbuechler" <pbuechler@> wrote:
> >
> > I have been successful in summarizing LaborDtl so I can provide
> Scrap
> > Qty by Job by OpCode (given the OpCode is not used more than once
> in
> > a single job) with the use of Executive Queries.
> >
> > For those of you that don't know, EQ's allow you to summarize
data
> in
> > cubes of 2 dimensions (IE: Job#/OpCode, or Job#/PayrollDate, or
> > Resource/PayrollDate, etc). Then the cubed data can be queried
> > against in a BAQ including additional tables of data.
> >
> > I have brought this to the 'higher ground' at Epicor and they are
> > aware of the interest and struggles our company has experienced
at
> > getting at this data. However, in talking to a few Director
level
> > individuals (the people who really know how the product works); I
> do
> > not believe they did anything in E9. But that is not to say we
> > cannot get an alliance going for more focus in future
> > patches/releases.
> >
> > But I have to be honest...I have been asking about this issue for
> the
> > last 4 years, and I finally see other customers ask questions
about
> > it. That must mean there is not a big focus on this acorss the
> > customer base; whereas other major issues is the focus (like
> getting
> > base functionality to work).
> >
> > Thanks
> > Patty Buechler
> >
> > --- In vantage@yahoogroups.com, "Manasa Reddy" <manasa@> wrote:
> > >
> > > Pencil and calculator.....you right that the system does not
> > calculate
> > > this at all!!! Unless you are a programmer, good luck doing
> this.
> > It
> > > was a big issue at Epicor, and I have no idea if they even
> bothered
> > to
> > > fix it in version 9!
> > >
> > > As for flowing through mfg variance, are you sure???? I,
myself,
> > have
> > > never found it there...and I have used this system for over 8
> years.
> > >
> > >
> > > M. Manasa Reddy
> > > manasa@
> > > P: 630-806-2000
> > > F: 630-806-2001
> > >
> > >
> > > ________________________________
> > >
> > > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On
> > Behalf
> > > Of mlezivk
> > > Sent: Wednesday, January 14, 2009 1:49 PM
> > > To: vantage@yahoogroups.com
> > > Subject: [Vantage] Labor Scrap Value
> > >
> > >
> > >
> > > Hello,
> > >
> > > We currently use the full QA module for inspection and scrap.
> > However,
> > > we also allow the production people the option to scrap an item
> > > directly through labor entry without putting it through non-
> > > conforming.
> > >
> > > Question is...anybody have a good way to have Vantage put a
scrap
> > value
> > > on that part when it is scrapped through labor entry. From what
I
> > can
> > > tell, directly scrapping a part in Vantage does not trigger a
> > > transaction, so the cost of a partially completed part is not
> > captured
> > > and cannot be known. The scrap $$'s flow through as a mfg
> variance
> > > after the job is closed.
> > >
> > > We are currently working around this issue by applying a 70%
> factor
> > of
> > > the standard cost to value all labor scrapped parts. Does
anybody
> > know
> > > of a better way of doing this?
> > >
> > > Thanks!
> > >
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>