Job current operation - for PBuechler

Bob - Can you send me your full email address so I can send you the export file?

Thanks
Patty

--- In vantage@yahoogroups.com, Robert Carlson <rcarlson@...> wrote:
>
> Hi Patty,
>
> Followed it all up to the P&S which I still havn't figured out a use
> for. I'd like to take you up on your offer and get the dashboard to
> see how all three elements come together.
>
> Thanks,
>
> Bob Carlson
> Flanagan Industries
> bcarlson@...
>
>
>
>
>
> At 11:03 AM 9/1/2009, you wrote:
> >
> >
> >What I did is created a dashboard that shows all operations that
> >were marked complete. I added an advanced search option so they can
> >click on the date drop down to filter the transactions
> >(JobOper.LastLaborDate >= and JobOper.LastLaborDate <=)
> >
> >They use this to compare against manual production logs to ensure
> >operations that should have marked complete are complete with
> >accurate #'s. In addition, finding operations that were marked
> >complete that should not have been.
> >
> >Brian's query is probably the same...but here is what my query looks
> >like in the Phrase Builder:
> >
> >for each JobOper no-lock , each JobAsmbl where (JobOper.Company =
> >JobAsmbl.Company and JobOper.JobNum = JobAsmbl.JobNum and
> >JobOper.AssemblySeq = JobAsmbl.AssemblySeq) no-lock , each JobHead
> >where (JobOper.Company = JobHead.Company and JobOper.JobNum =
> >JobHead.JobNum) no-lock , each OpMasDtl where (JobOper.Company =
> >OpMasDtl.Company and JobOper.OpCode = OpMasDtl.OpCode) no-lock ,
> >each ResourceGroup where (OpMasDtl.Company = ResourceGroup.Company
> >and OpMasDtl.ResourceGrpID = ResourceGroup.ResourceGrpID) no-lock by
> >JobOper.OpComplete by JobOper.AssemblySeq by JobOper.OprSeq.
> >
> >Then I built another query that grabs all Labor Detail and
> >Materials. With the use of Publish and Subscribe in the
> >dashboard...I then only show the related Job/Asm/Opr detail
> >transactions if there are futher drilldown needed.
> >
> >If you attended Perspectives last year...I did a session on this
> >exact scenario. If you want me to export and send to you
> >directly...let me know and I will send it to you offline.
> >
> >Hopefully this helps.
> >Patty Buechler
> >
> >--- In <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com,
> >"Randy Weber" <rweber@> wrote:
> > >
> > > Patty,
> > >
> > >
> > >
> > > True. I just discovered that issue while testing Brian's query (thanks
> > > Brian). The first job I looked at had op 10 complete, op 20 not
> > > complete, and op 30 complete. It's not due to your scenario where
> > > multiple ops can be running at the same time, but rather sloppiness in
> > > completing ops that sometimes are completed together in one step. But
> > > using Brian's query on a dashboard will help push production into
> > > checking complete on skipped operations. An alternative would be to use
> > > last op complete = true. This will at least tell them the last complete
> > > operation.
> > >
> > >
> > >
> > > Randy
> > >
> > >
> > >
> > > From: <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com
> > [mailto:vantage@yahoogroups.com] On Behalf
> > > Of bpbuechler
> > > Sent: Tuesday, September 01, 2009 9:39 AM
> > > To: <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com
> > > Subject: [Vantage] Re: Job current operation
> > >
> > >
> > >
> > >
> > >
> > > Unless you are setup in an environment where the next operation cannot
> > > start until the previous operation is marked complete...you shouldn't
> > > assume the job has one 'current' Operation.
> > >
> > > I bring this up as we have struggled with this concept for years.
> > > In our environment...a Job can literly be in in several operation stages
> > > all reporting qty feeding the next operation in the routing of the job.
> > > There are also scenarios where we may have 4 operations running all
> > > within multiple subassemblies. So you have to ask the question...what
> > > does 'current' operation mean for your environment.
> > >
> > > Thanks
> > > Patty Buechler
> > >
> > > --- In <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com
> > <mailto:vantage%40yahoogroups.com> ,
> > > "Brian W. Spolarich " <bspolarich@> wrote:
> > > >
> > > > I think this will do what you want:
> > > >
> > > > for each JobHead where ( JobHead.JobClosed <> True) no-lock , first
> > > JobOper where ( JobOper.OpComplete <> True) and (JobHead.Company =
> > > JobOper.Company and JobHead.JobNum = JobOper.JobNum) no-lock by
> > > JobHead.JobNum by JobOper.OprSeq.
> > > >
> > > > Basically do a BAQ selecting JobHead and then JobOper. Change the
> > > relationship to 'first' instead of 'each' for JobOper. Filter so you're
> > > only looking at Open jobs and Uncompleted JobOpers. Sort by JobNum and
> > > then JobOper.OprSeq. This should give you the first uncompleted JobOper
> > > for each open job.
> > > >
> > > > -bws
> > > >
> > > > --
> > > > Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix
> > > / Picometrix
> > > > bspolarich@ ~ 734-864-5618 ~ www.advancedphotonix.com
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com
> > <mailto:vantage%40yahoogroups.com>
> > > [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> > > Behalf Of randyweb
> > > > Sent: Monday, August 31, 2009 12:07 PM
> > > > To: <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com
> > <mailto:vantage%40yahoogroups.com>
> > > > Subject: [Vantage] Job current operation
> > > >
> > > > v8.03.407C Progress
> > > >
> > > > I am struggling with a query to determine which operation is currently
> > > in progress on jobs.
> > > >
> > > > I can determine if the last operation is complete, or use labor detail
> > > to determine which is the last operation with a labor detail record, but
> > > I want to just return one record - the last one with labor detail.
> > > >
> > > > In BAQ, I can summarize but in the help screen for summarize, there is
> > > no mention of a MAX function. If I had that, I should be able to
> > > determine the last operation sequence with a labor record, or if the
> > > labor detail is null - then it has not been started.
> > > >
> > > > Is there anything that I can easily use to flag that a job has been
> > > started and which op is current without complex queries?
> > > >
> > > > Maybe I'm missing something, but this seems very tricky.
> > > >
> > > > Randy Weber
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
> > > have already linked your email address to a yahoo id to enable access. )
> > > > (1) To access the Files Section of our Yahoo!Group for Report Builder
> > > and Crystal Reports and other 'goodies', please goto:
> > >
> > <http://groups.yahoo.com/group/vantage/files/.>http://groups.yahoo.com/group/vantage/files/.
> > > <http://groups.yahoo.com/group/vantage/files/>
> > > > (2) To search through old msg's goto:
> > >
> > <http://groups.yahoo.com/group/vantage/messages>http://groups.yahoo.com/group/vantage/messages
> > > > (3) To view links to Vendors that provide Vantage services goto:
> > >
> > <http://groups.yahoo.com/group/vantage/linksYahoo>http://groups.yahoo.com/group/vantage/linksYahoo!
> > Groups Links
> > > >
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
v8.03.407C Progress

I am struggling with a query to determine which operation is currently in progress on jobs.

I can determine if the last operation is complete, or use labor detail to determine which is the last operation with a labor detail record, but I want to just return one record – the last one with labor detail.

In BAQ, I can summarize but in the help screen for summarize, there is no mention of a MAX function. If I had that, I should be able to determine the last operation sequence with a labor record, or if the labor detail is null – then it has not been started.

Is there anything that I can easily use to flag that a job has been started and which op is current without complex queries?

Maybe I'm missing something, but this seems very tricky.

Randy Weber
Contact me directly and I'll send you screen cuts
of a departmental dashboard based on employee
names that looks at all labor transactions for a
payroll date (like today) and if an active
transaction gives you the job/operation and clock
times as well as the active checkmark or shows
what indirect activity is being worked on.

If you like it I'll ship you the dashboard.

bcarlson@...

At 12:07 PM 8/31/2009, you wrote:
>
>
>v8.03.407C Progress
>
>I am struggling with a query to determine which
>operation is currently in progress on jobs.
>
>I can determine if the last operation is
>complete, or use labor detail to determine which
>is the last operation with a labor detail
>record, but I want to just return one record – the last one with labor detail.
>
>In BAQ, I can summarize but in the help screen
>for summarize, there is no mention of a MAX
>function. If I had that, I should be able to
>determine the last operation sequence with a
>labor record, or if the labor detail is null – then it has not been started.
>
>Is there anything that I can easily use to flag
>that a job has been started and which op is current without complex queries?
>
>Maybe I'm missing something, but this seems very tricky.
>
>Randy Weber
>
>


[Non-text portions of this message have been removed]
I think this will do what you want:

for each JobHead where ( JobHead.JobClosed <> True) no-lock , first JobOper where ( JobOper.OpComplete <> True) and (JobHead.Company = JobOper.Company and JobHead.JobNum = JobOper.JobNum) no-lock by JobHead.JobNum by JobOper.OprSeq.

Basically do a BAQ selecting JobHead and then JobOper. Change the relationship to 'first' instead of 'each' for JobOper. Filter so you're only looking at Open jobs and Uncompleted JobOpers. Sort by JobNum and then JobOper.OprSeq. This should give you the first uncompleted JobOper for each open job.

-bws

--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix / Picometrix
    bspolarich@... ~ 734-864-5618 ~ www.advancedphotonix.com


-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of randyweb
Sent: Monday, August 31, 2009 12:07 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Job current operation

v8.03.407C Progress

I am struggling with a query to determine which operation is currently in progress on jobs.

I can determine if the last operation is complete, or use labor detail to determine which is the last operation with a labor detail record, but I want to just return one record - the last one with labor detail.

In BAQ, I can summarize but in the help screen for summarize, there is no mention of a MAX function. If I had that, I should be able to determine the last operation sequence with a labor record, or if the labor detail is null - then it has not been started.

Is there anything that I can easily use to flag that a job has been started and which op is current without complex queries?

Maybe I'm missing something, but this seems very tricky.

Randy Weber



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
Unless you are setup in an environment where the next operation cannot start until the previous operation is marked complete...you shouldn't assume the job has one 'current' Operation.

I bring this up as we have struggled with this concept for years.
In our environment...a Job can literly be in in several operation stages all reporting qty feeding the next operation in the routing of the job. There are also scenarios where we may have 4 operations running all within multiple subassemblies. So you have to ask the question...what does 'current' operation mean for your environment.

Thanks
Patty Buechler



--- In vantage@yahoogroups.com, "Brian W. Spolarich " <bspolarich@...> wrote:
>
> I think this will do what you want:
>
> for each JobHead where ( JobHead.JobClosed <> True) no-lock , first JobOper where ( JobOper.OpComplete <> True) and (JobHead.Company = JobOper.Company and JobHead.JobNum = JobOper.JobNum) no-lock by JobHead.JobNum by JobOper.OprSeq.
>
> Basically do a BAQ selecting JobHead and then JobOper. Change the relationship to 'first' instead of 'each' for JobOper. Filter so you're only looking at Open jobs and Uncompleted JobOpers. Sort by JobNum and then JobOper.OprSeq. This should give you the first uncompleted JobOper for each open job.
>
> -bws
>
> --
> Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix / Picometrix
> Â Â Â Â bspolarich@... ~ 734-864-5618 ~ www.advancedphotonix.com
>
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of randyweb
> Sent: Monday, August 31, 2009 12:07 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Job current operation
>
> v8.03.407C Progress
>
> I am struggling with a query to determine which operation is currently in progress on jobs.
>
> I can determine if the last operation is complete, or use labor detail to determine which is the last operation with a labor detail record, but I want to just return one record - the last one with labor detail.
>
> In BAQ, I can summarize but in the help screen for summarize, there is no mention of a MAX function. If I had that, I should be able to determine the last operation sequence with a labor record, or if the labor detail is null - then it has not been started.
>
> Is there anything that I can easily use to flag that a job has been started and which op is current without complex queries?
>
> Maybe I'm missing something, but this seems very tricky.
>
> Randy Weber
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
Patty,



True. I just discovered that issue while testing Brian's query (thanks
Brian). The first job I looked at had op 10 complete, op 20 not
complete, and op 30 complete. It's not due to your scenario where
multiple ops can be running at the same time, but rather sloppiness in
completing ops that sometimes are completed together in one step. But
using Brian's query on a dashboard will help push production into
checking complete on skipped operations. An alternative would be to use
last op complete = true. This will at least tell them the last complete
operation.



Randy



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of bpbuechler
Sent: Tuesday, September 01, 2009 9:39 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Job current operation





Unless you are setup in an environment where the next operation cannot
start until the previous operation is marked complete...you shouldn't
assume the job has one 'current' Operation.

I bring this up as we have struggled with this concept for years.
In our environment...a Job can literly be in in several operation stages
all reporting qty feeding the next operation in the routing of the job.
There are also scenarios where we may have 4 operations running all
within multiple subassemblies. So you have to ask the question...what
does 'current' operation mean for your environment.

Thanks
Patty Buechler

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Brian W. Spolarich " <bspolarich@...> wrote:
>
> I think this will do what you want:
>
> for each JobHead where ( JobHead.JobClosed <> True) no-lock , first
JobOper where ( JobOper.OpComplete <> True) and (JobHead.Company =
JobOper.Company and JobHead.JobNum = JobOper.JobNum) no-lock by
JobHead.JobNum by JobOper.OprSeq.
>
> Basically do a BAQ selecting JobHead and then JobOper. Change the
relationship to 'first' instead of 'each' for JobOper. Filter so you're
only looking at Open jobs and Uncompleted JobOpers. Sort by JobNum and
then JobOper.OprSeq. This should give you the first uncompleted JobOper
for each open job.
>
> -bws
>
> --
> Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix
/ Picometrix
> bspolarich@... ~ 734-864-5618 ~ www.advancedphotonix.com
>
>
> -----Original Message-----
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of randyweb
> Sent: Monday, August 31, 2009 12:07 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Job current operation
>
> v8.03.407C Progress
>
> I am struggling with a query to determine which operation is currently
in progress on jobs.
>
> I can determine if the last operation is complete, or use labor detail
to determine which is the last operation with a labor detail record, but
I want to just return one record - the last one with labor detail.
>
> In BAQ, I can summarize but in the help screen for summarize, there is
no mention of a MAX function. If I had that, I should be able to
determine the last operation sequence with a labor record, or if the
labor detail is null - then it has not been started.
>
> Is there anything that I can easily use to flag that a job has been
started and which op is current without complex queries?
>
> Maybe I'm missing something, but this seems very tricky.
>
> Randy Weber
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
<http://groups.yahoo.com/group/vantage/files/>
> (2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>





[Non-text portions of this message have been removed]
I didn't read the original request very closely obviously, but using the 'last' instead of 'each' modifier on the table join would get you the last LaborDtl record for a given Job.

--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix / Picometrix
    bspolarich@... ~ 734-864-5618 ~ www.advancedphotonix.com


-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Randy Weber
Sent: Tuesday, September 01, 2009 10:41 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Job current operation

Patty,



True. I just discovered that issue while testing Brian's query (thanks
Brian). The first job I looked at had op 10 complete, op 20 not
complete, and op 30 complete. It's not due to your scenario where
multiple ops can be running at the same time, but rather sloppiness in
completing ops that sometimes are completed together in one step. But
using Brian's query on a dashboard will help push production into
checking complete on skipped operations. An alternative would be to use
last op complete = true. This will at least tell them the last complete
operation.



Randy



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of bpbuechler
Sent: Tuesday, September 01, 2009 9:39 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Job current operation





Unless you are setup in an environment where the next operation cannot
start until the previous operation is marked complete...you shouldn't
assume the job has one 'current' Operation.

I bring this up as we have struggled with this concept for years.
In our environment...a Job can literly be in in several operation stages
all reporting qty feeding the next operation in the routing of the job.
There are also scenarios where we may have 4 operations running all
within multiple subassemblies. So you have to ask the question...what
does 'current' operation mean for your environment.

Thanks
Patty Buechler

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Brian W. Spolarich " <bspolarich@...> wrote:
>
> I think this will do what you want:
>
> for each JobHead where ( JobHead.JobClosed <> True) no-lock , first
JobOper where ( JobOper.OpComplete <> True) and (JobHead.Company =
JobOper.Company and JobHead.JobNum = JobOper.JobNum) no-lock by
JobHead.JobNum by JobOper.OprSeq.
>
> Basically do a BAQ selecting JobHead and then JobOper. Change the
relationship to 'first' instead of 'each' for JobOper. Filter so you're
only looking at Open jobs and Uncompleted JobOpers. Sort by JobNum and
then JobOper.OprSeq. This should give you the first uncompleted JobOper
for each open job.
>
> -bws
>
> --
> Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix
/ Picometrix
> bspolarich@... ~ 734-864-5618 ~ www.advancedphotonix.com
>
>
> -----Original Message-----
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of randyweb
> Sent: Monday, August 31, 2009 12:07 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Job current operation
>
> v8.03.407C Progress
>
> I am struggling with a query to determine which operation is currently
in progress on jobs.
>
> I can determine if the last operation is complete, or use labor detail
to determine which is the last operation with a labor detail record, but
I want to just return one record - the last one with labor detail.
>
> In BAQ, I can summarize but in the help screen for summarize, there is
no mention of a MAX function. If I had that, I should be able to
determine the last operation sequence with a labor record, or if the
labor detail is null - then it has not been started.
>
> Is there anything that I can easily use to flag that a job has been
started and which op is current without complex queries?
>
> Maybe I'm missing something, but this seems very tricky.
>
> Randy Weber
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
<http://groups.yahoo.com/group/vantage/files/>
> (2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>





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



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
What I did is created a dashboard that shows all operations that were marked complete. I added an advanced search option so they can click on the date drop down to filter the transactions (JobOper.LastLaborDate >= and JobOper.LastLaborDate <=)

They use this to compare against manual production logs to ensure operations that should have marked complete are complete with accurate #'s. In addition, finding operations that were marked complete that should not have been.

Brian's query is probably the same...but here is what my query looks like in the Phrase Builder:

for each JobOper no-lock , each JobAsmbl where (JobOper.Company = JobAsmbl.Company and JobOper.JobNum = JobAsmbl.JobNum and JobOper.AssemblySeq = JobAsmbl.AssemblySeq) no-lock , each JobHead where (JobOper.Company = JobHead.Company and JobOper.JobNum = JobHead.JobNum) no-lock , each OpMasDtl where (JobOper.Company = OpMasDtl.Company and JobOper.OpCode = OpMasDtl.OpCode) no-lock , each ResourceGroup where (OpMasDtl.Company = ResourceGroup.Company and OpMasDtl.ResourceGrpID = ResourceGroup.ResourceGrpID) no-lock by JobOper.OpComplete by JobOper.AssemblySeq by JobOper.OprSeq.

Then I built another query that grabs all Labor Detail and Materials. With the use of Publish and Subscribe in the dashboard...I then only show the related Job/Asm/Opr detail transactions if there are futher drilldown needed.

If you attended Perspectives last year...I did a session on this exact scenario. If you want me to export and send to you directly...let me know and I will send it to you offline.

Hopefully this helps.
Patty Buechler



--- In vantage@yahoogroups.com, "Randy Weber" <rweber@...> wrote:
>
> Patty,
>
>
>
> True. I just discovered that issue while testing Brian's query (thanks
> Brian). The first job I looked at had op 10 complete, op 20 not
> complete, and op 30 complete. It's not due to your scenario where
> multiple ops can be running at the same time, but rather sloppiness in
> completing ops that sometimes are completed together in one step. But
> using Brian's query on a dashboard will help push production into
> checking complete on skipped operations. An alternative would be to use
> last op complete = true. This will at least tell them the last complete
> operation.
>
>
>
> Randy
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of bpbuechler
> Sent: Tuesday, September 01, 2009 9:39 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Job current operation
>
>
>
>
>
> Unless you are setup in an environment where the next operation cannot
> start until the previous operation is marked complete...you shouldn't
> assume the job has one 'current' Operation.
>
> I bring this up as we have struggled with this concept for years.
> In our environment...a Job can literly be in in several operation stages
> all reporting qty feeding the next operation in the routing of the job.
> There are also scenarios where we may have 4 operations running all
> within multiple subassemblies. So you have to ask the question...what
> does 'current' operation mean for your environment.
>
> Thanks
> Patty Buechler
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Brian W. Spolarich " <bspolarich@> wrote:
> >
> > I think this will do what you want:
> >
> > for each JobHead where ( JobHead.JobClosed <> True) no-lock , first
> JobOper where ( JobOper.OpComplete <> True) and (JobHead.Company =
> JobOper.Company and JobHead.JobNum = JobOper.JobNum) no-lock by
> JobHead.JobNum by JobOper.OprSeq.
> >
> > Basically do a BAQ selecting JobHead and then JobOper. Change the
> relationship to 'first' instead of 'each' for JobOper. Filter so you're
> only looking at Open jobs and Uncompleted JobOpers. Sort by JobNum and
> then JobOper.OprSeq. This should give you the first uncompleted JobOper
> for each open job.
> >
> > -bws
> >
> > --
> > Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix
> / Picometrix
> > bspolarich@ ~ 734-864-5618 ~ www.advancedphotonix.com
> >
> >
> > -----Original Message-----
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf Of randyweb
> > Sent: Monday, August 31, 2009 12:07 PM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Job current operation
> >
> > v8.03.407C Progress
> >
> > I am struggling with a query to determine which operation is currently
> in progress on jobs.
> >
> > I can determine if the last operation is complete, or use labor detail
> to determine which is the last operation with a labor detail record, but
> I want to just return one record - the last one with labor detail.
> >
> > In BAQ, I can summarize but in the help screen for summarize, there is
> no mention of a MAX function. If I had that, I should be able to
> determine the last operation sequence with a labor record, or if the
> labor detail is null - then it has not been started.
> >
> > Is there anything that I can easily use to flag that a job has been
> started and which op is current without complex queries?
> >
> > Maybe I'm missing something, but this seems very tricky.
> >
> > Randy Weber
> >
> >
> >
> > ------------------------------------
> >
> > Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
> have already linked your email address to a yahoo id to enable access. )
> > (1) To access the Files Section of our Yahoo!Group for Report Builder
> and Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> <http://groups.yahoo.com/group/vantage/files/>
> > (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> > (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Hi Patty,

Followed it all up to the P&S which I still havn't figured out a use
for. I'd like to take you up on your offer and get the dashboard to
see how all three elements come together.

Thanks,

Bob Carlson
Flanagan Industries
bcarlson@...





At 11:03 AM 9/1/2009, you wrote:
>
>
>What I did is created a dashboard that shows all operations that
>were marked complete. I added an advanced search option so they can
>click on the date drop down to filter the transactions
>(JobOper.LastLaborDate >= and JobOper.LastLaborDate <=)
>
>They use this to compare against manual production logs to ensure
>operations that should have marked complete are complete with
>accurate #'s. In addition, finding operations that were marked
>complete that should not have been.
>
>Brian's query is probably the same...but here is what my query looks
>like in the Phrase Builder:
>
>for each JobOper no-lock , each JobAsmbl where (JobOper.Company =
>JobAsmbl.Company and JobOper.JobNum = JobAsmbl.JobNum and
>JobOper.AssemblySeq = JobAsmbl.AssemblySeq) no-lock , each JobHead
>where (JobOper.Company = JobHead.Company and JobOper.JobNum =
>JobHead.JobNum) no-lock , each OpMasDtl where (JobOper.Company =
>OpMasDtl.Company and JobOper.OpCode = OpMasDtl.OpCode) no-lock ,
>each ResourceGroup where (OpMasDtl.Company = ResourceGroup.Company
>and OpMasDtl.ResourceGrpID = ResourceGroup.ResourceGrpID) no-lock by
>JobOper.OpComplete by JobOper.AssemblySeq by JobOper.OprSeq.
>
>Then I built another query that grabs all Labor Detail and
>Materials. With the use of Publish and Subscribe in the
>dashboard...I then only show the related Job/Asm/Opr detail
>transactions if there are futher drilldown needed.
>
>If you attended Perspectives last year...I did a session on this
>exact scenario. If you want me to export and send to you
>directly...let me know and I will send it to you offline.
>
>Hopefully this helps.
>Patty Buechler
>
>--- In <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com,
>"Randy Weber" <rweber@...> wrote:
> >
> > Patty,
> >
> >
> >
> > True. I just discovered that issue while testing Brian's query (thanks
> > Brian). The first job I looked at had op 10 complete, op 20 not
> > complete, and op 30 complete. It's not due to your scenario where
> > multiple ops can be running at the same time, but rather sloppiness in
> > completing ops that sometimes are completed together in one step. But
> > using Brian's query on a dashboard will help push production into
> > checking complete on skipped operations. An alternative would be to use
> > last op complete = true. This will at least tell them the last complete
> > operation.
> >
> >
> >
> > Randy
> >
> >
> >
> > From: <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com
> [mailto:vantage@yahoogroups.com] On Behalf
> > Of bpbuechler
> > Sent: Tuesday, September 01, 2009 9:39 AM
> > To: <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com
> > Subject: [Vantage] Re: Job current operation
> >
> >
> >
> >
> >
> > Unless you are setup in an environment where the next operation cannot
> > start until the previous operation is marked complete...you shouldn't
> > assume the job has one 'current' Operation.
> >
> > I bring this up as we have struggled with this concept for years.
> > In our environment...a Job can literly be in in several operation stages
> > all reporting qty feeding the next operation in the routing of the job.
> > There are also scenarios where we may have 4 operations running all
> > within multiple subassemblies. So you have to ask the question...what
> > does 'current' operation mean for your environment.
> >
> > Thanks
> > Patty Buechler
> >
> > --- In <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com
> <mailto:vantage%40yahoogroups.com> ,
> > "Brian W. Spolarich " <bspolarich@> wrote:
> > >
> > > I think this will do what you want:
> > >
> > > for each JobHead where ( JobHead.JobClosed <> True) no-lock , first
> > JobOper where ( JobOper.OpComplete <> True) and (JobHead.Company =
> > JobOper.Company and JobHead.JobNum = JobOper.JobNum) no-lock by
> > JobHead.JobNum by JobOper.OprSeq.
> > >
> > > Basically do a BAQ selecting JobHead and then JobOper. Change the
> > relationship to 'first' instead of 'each' for JobOper. Filter so you're
> > only looking at Open jobs and Uncompleted JobOpers. Sort by JobNum and
> > then JobOper.OprSeq. This should give you the first uncompleted JobOper
> > for each open job.
> > >
> > > -bws
> > >
> > > --
> > > Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix
> > / Picometrix
> > > bspolarich@ ~ 734-864-5618 ~ www.advancedphotonix.com
> > >
> > >
> > > -----Original Message-----
> > > From: <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com
> <mailto:vantage%40yahoogroups.com>
> > [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> > Behalf Of randyweb
> > > Sent: Monday, August 31, 2009 12:07 PM
> > > To: <mailto:vantage%40yahoogroups.com>vantage@yahoogroups.com
> <mailto:vantage%40yahoogroups.com>
> > > Subject: [Vantage] Job current operation
> > >
> > > v8.03.407C Progress
> > >
> > > I am struggling with a query to determine which operation is currently
> > in progress on jobs.
> > >
> > > I can determine if the last operation is complete, or use labor detail
> > to determine which is the last operation with a labor detail record, but
> > I want to just return one record - the last one with labor detail.
> > >
> > > In BAQ, I can summarize but in the help screen for summarize, there is
> > no mention of a MAX function. If I had that, I should be able to
> > determine the last operation sequence with a labor record, or if the
> > labor detail is null - then it has not been started.
> > >
> > > Is there anything that I can easily use to flag that a job has been
> > started and which op is current without complex queries?
> > >
> > > Maybe I'm missing something, but this seems very tricky.
> > >
> > > Randy Weber
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
> > have already linked your email address to a yahoo id to enable access. )
> > > (1) To access the Files Section of our Yahoo!Group for Report Builder
> > and Crystal Reports and other 'goodies', please goto:
> >
> <http://groups.yahoo.com/group/vantage/files/.>http://groups.yahoo.com/group/vantage/files/.
> > <http://groups.yahoo.com/group/vantage/files/>
> > > (2) To search through old msg's goto:
> >
> <http://groups.yahoo.com/group/vantage/messages>http://groups.yahoo.com/group/vantage/messages
> > > (3) To view links to Vendors that provide Vantage services goto:
> >
> <http://groups.yahoo.com/group/vantage/linksYahoo>http://groups.yahoo.com/group/vantage/linksYahoo!
> Groups Links
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>


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