Dave,
I would be interested in hearing how you would create the BPM for the UD field. Our part tag currently shows the next op for next op, however for the current op it always show op 10 regardless if it is 20, 30 ,40 ....or whatever. We are on E9.05.701.
I could add a UD field, but not sure what to do on the BPM side of it.
Any help is appreciated.
--- In vantage@yahoogroups.com, "dswmaom" <dwalker@...> wrote:
>
> I am paraphrasing this issue on behalf of our crystal developer and
I
> am a newbee myself but I'll do my best...
>
> We need to print the next operation number and operation
description on
> our part tags and have linked the partopr table in on the parttag
data
> definition. The problem is that when we print a tag for a
particular
> job operation....we get duplicate tags for each of the remaining
> operations.
>
> For example: if a job has operations 10-20-30-40 and we print a tag
for
> oper 10 we want the op10 tag to print the next operation as being
20.
> This works great. The problem is that we get two more op10 tags.
One
> prints next op as bein 30, and the other prints next op as being 40.
>
> How do we insure that we only print one tag with the "next"
operation
> on it and suppress all of the other tags?
> thx,
> Dale.
>
--- In vantage@yahoogroups.com, "dswmaom" <dwalker@...> wrote:
>
> I am paraphrasing this issue on behalf of our crystal developer and I
> am a newbee myself but I'll do my best...
>
> We need to print the next operation number and operation description on
> our part tags and have linked the partopr table in on the parttag data
> definition. The problem is that when we print a tag for a particular
> job operation....we get duplicate tags for each of the remaining
> operations.
>
> For example: if a job has operations 10-20-30-40 and we print a tag for
> oper 10 we want the op10 tag to print the next operation as being 20.
> This works great. The problem is that we get two more op10 tags. One
> prints next op as bein 30, and the other prints next op as being 40.
>
> How do we insure that we only print one tag with the "next" operation
> on it and suppress all of the other tags?
> thx,
> Dale.
>
--- In vantage@yahoogroups.com, "that_guyy" <rbird@...> wrote:
>
> We are trying to do something similarly, but we're not quite sure how to write the BAQ for it, or maybe design the Crystal for it.
> We are on version .409a, and here is what we need to do:
>
> When our Welding operation (OP 10) is finished they use either Report Qty or End Activity to report their labor and Qty. On both of those screens there is a "Print Tags" button for printing WIP tags. The next operation is Paint (OP 20), so when weld (OP 10) reports their labor/qty they will print a WIP tag and it should have the following:
>
> Reporting Job/AsmSeq/OpSeq/Qty
> Next OpSeq
>
> So a sample would be like this:
> Job 123456
> ASM 2
> OpSeq 10 - Weld
> ------------------------------------
> Next OpSeq: 20 - Paint.
>
> Then the paint line will use the WIP tag to log that operation into the job.
>
> Our paint line does not get the job traveler and it would be very difficult to manage all that paper in their work area. We are currently using a WIP tag but it only has the Job Number and Asm number, and our developer is having a terrible time finding the next operation.
> As a bonus we would like to print the next Assembly/OpSeq, if there are not any other operations to be completed for the current Assembly.
>
> If anyone can help, it would be greatly appreciated!!!
>
> -Rick
>
> --- In vantage@yahoogroups.com, "dswmaom" <dwalker@> wrote:
> >
> > I am paraphrasing this issue on behalf of our crystal developer and I
> > am a newbee myself but I'll do my best...
> >
> > We need to print the next operation number and operation description on
> > our part tags and have linked the partopr table in on the parttag data
> > definition. The problem is that when we print a tag for a particular
> > job operation....we get duplicate tags for each of the remaining
> > operations.
> >
> > For example: if a job has operations 10-20-30-40 and we print a tag for
> > oper 10 we want the op10 tag to print the next operation as being 20.
> > This works great. The problem is that we get two more op10 tags. One
> > prints next op as bein 30, and the other prints next op as being 40.
> >
> > How do we insure that we only print one tag with the "next" operation
> > on it and suppress all of the other tags?
> > thx,
> > Dale.
> >
>
--- In vantage@yahoogroups.com, "laraines422" <laraines422@...> wrote:
>
> Hi Rick,
>
> We did something similar; I wrote a BAQ and CR for our Production Group, which basically tells them what the last completed operation was and what the next operation is. The BAQ is based on a copy of the Job Tracker-Job Oper Query, but the CR does the heavy lifting of determining what the last and next operations are (Min and Max summaries of the JobOper.OprSeq) based on the logic that the Last OP has a completed quantity and the Next OP has zero completed quantity.
>
> Send me an email if you'd like my files.
> Laraine
>
>
> --- In vantage@yahoogroups.com, "that_guyy" <rbird@> wrote:
> >
> > We are trying to do something similarly, but we're not quite sure how to write the BAQ for it, or maybe design the Crystal for it.
> > We are on version .409a, and here is what we need to do:
> >
> > When our Welding operation (OP 10) is finished they use either Report Qty or End Activity to report their labor and Qty. On both of those screens there is a "Print Tags" button for printing WIP tags. The next operation is Paint (OP 20), so when weld (OP 10) reports their labor/qty they will print a WIP tag and it should have the following:
> >
> > Reporting Job/AsmSeq/OpSeq/Qty
> > Next OpSeq
> >
> > So a sample would be like this:
> > Job 123456
> > ASM 2
> > OpSeq 10 - Weld
> > ------------------------------------
> > Next OpSeq: 20 - Paint.
> >
> > Then the paint line will use the WIP tag to log that operation into the job.
> >
> > Our paint line does not get the job traveler and it would be very difficult to manage all that paper in their work area. We are currently using a WIP tag but it only has the Job Number and Asm number, and our developer is having a terrible time finding the next operation.
> > As a bonus we would like to print the next Assembly/OpSeq, if there are not any other operations to be completed for the current Assembly.
> >
> > If anyone can help, it would be greatly appreciated!!!
> >
> > -Rick
> >
> > --- In vantage@yahoogroups.com, "dswmaom" <dwalker@> wrote:
> > >
> > > I am paraphrasing this issue on behalf of our crystal developer and I
> > > am a newbee myself but I'll do my best...
> > >
> > > We need to print the next operation number and operation description on
> > > our part tags and have linked the partopr table in on the parttag data
> > > definition. The problem is that when we print a tag for a particular
> > > job operation....we get duplicate tags for each of the remaining
> > > operations.
> > >
> > > For example: if a job has operations 10-20-30-40 and we print a tag for
> > > oper 10 we want the op10 tag to print the next operation as being 20.
> > > This works great. The problem is that we get two more op10 tags. One
> > > prints next op as bein 30, and the other prints next op as being 40.
> > >
> > > How do we insure that we only print one tag with the "next" operation
> > > on it and suppress all of the other tags?
> > > thx,
> > > Dale.
> > >
> >
>
--- In vantage@yahoogroups.com, "dswmaom" <dwalker@...> wrote:
>
> I am paraphrasing this issue on behalf of our crystal developer and I
> am a newbee myself but I'll do my best...
>
> We need to print the next operation number and operation description on
> our part tags and have linked the partopr table in on the parttag data
> definition. The problem is that when we print a tag for a particular
> job operation....we get duplicate tags for each of the remaining
> operations.
>
> For example: if a job has operations 10-20-30-40 and we print a tag for
> oper 10 we want the op10 tag to print the next operation as being 20.
> This works great. The problem is that we get two more op10 tags. One
> prints next op as bein 30, and the other prints next op as being 40.
>
> How do we insure that we only print one tag with the "next" operation
> on it and suppress all of the other tags?
> thx,
> Dale.
>
--- In vantage@yahoogroups.com, "that_guyy" <rbird@...> wrote:
>
> Dale,
> Did you ever get this problem resolved? It sounds to me like what you are trying to do is exactly what we are trying to do, but you seem further down the path, but with one problem.
> If you haven't got your crystal problem solved, I think I may know what the problem is with getting multiple tags of the rest of the operations. Depending on how your crystal is designed, it might be an issue of just configuring it to select the first record that meets your next operations criteria. If you could supply me with your crystal and instructions on getting our Data Definition set up, I can test this theory out and see.
> If you have been able to get this to work, would you be willing to share your files to see if what you have put together will work for us as well?
>
> Thanks
>
> -Rick
>
> --- In vantage@yahoogroups.com, "dswmaom" <dwalker@> wrote:
> >
> > I am paraphrasing this issue on behalf of our crystal developer and I
> > am a newbee myself but I'll do my best...
> >
> > We need to print the next operation number and operation description on
> > our part tags and have linked the partopr table in on the parttag data
> > definition. The problem is that when we print a tag for a particular
> > job operation....we get duplicate tags for each of the remaining
> > operations.
> >
> > For example: if a job has operations 10-20-30-40 and we print a tag for
> > oper 10 we want the op10 tag to print the next operation as being 20.
> > This works great. The problem is that we get two more op10 tags. One
> > prints next op as bein 30, and the other prints next op as being 40.
> >
> > How do we insure that we only print one tag with the "next" operation
> > on it and suppress all of the other tags?
> > thx,
> > Dale.
> >
>
I would be careful here. If I remember correctly we found that if you print a tag from the MES "Report Quantity" screen then the XML dataset "Next Operation" shows the current operation you are clocked in to. If you print a tag from the MES "End Operation" then it prints only the next open operation for that ASM. It does NOT climb back up the BOM.
You might be better off using a BPM and 4GL to assign the next operation to a UDfield. Then just include the UD field in your tag XML dataset.
Just and idea.
DaveO