Data Model of Jobs (Epicor 9.05.606)

Yahoo Archive
1
Now that I'm testing this I have two fields. One in PartRev.ShortChar01, the other in JobAsmbl.ShortChar01. Both are called Build Instruction Revision.

What I've done thus far is:
1) Insert a textbox on Part Entry >> Revisions tab and bind PartRev.ShortChar01 to the textbox
2) Insert a textbox on Job Entry >> Job tab and bind JobAsmbl.ShortChar01 to the similar textbox
**These are the locations that the stakeholders want the textboxes
3) Labeled and filled in the descriptions for the DB fields using Extended Properties
4) Connected JobAsmbl.ShortChar01 as the target field to PartRev.ShortChar01 as the source field
5) I've put in a value for Build Instruction Revision (PartRev.ShortChar01) of 1.5

Result:
1) I can select differing Revs on the Job Entry screen, but the Build Instruction Revision textbox pulls nothing and it's greyed out.
2) Values are saving and storing in PartRev.ShortChar01 on the Part Revisions screen.

What I need:
1) The Build Instruction Revision (BIR) pulls from the PartRev onto the Job Entry >> Job screen's BIR textbox. BIR is not currently pulling from PartRev.
2) Once number one works, it needs to save the revision for completed jobs separately from what the current Rev is in the PartRev table. (already completed jobs do not have the current revisions included in them)

Hopefully this is clear.

Thanks,

Justin

--- In vantage@yahoogroups.com, "swenson.justin" <swenson.justin@...> wrote:
>
> Thanks Brian. I probably won't be able to test this for another day, but you seem to get exactly what I'm looking for. I understand your descriptions of each table as well.
>
> I'll get back to you when I've had a chance to work through it.
>
>
> --- In vantage@yahoogroups.com, "Brian Roberts" <broberts@> wrote:
> >
> > If I understand what you want correctly... you have some info in
> > PartRev.Character01, and when a job is created from that rev, you want
> > it copied to a Job???.Character01 field - based on the part rev selected
> > for that job, not necessarily the current rev? In that case, try Custom
> > Field Map (under system management -> utilities). Choose JobAsmbl for
> > the target (I think that's what you're trying to do), PartRev for the
> > source, and fill in Character01 or whatever.
> >
> >
> >
> > In general, JobAsmbl is the finished good you're making, JobOper is the
> > work (operations) to make it, JobMtl is the raw material, and JobProd is
> > what happens to the finished good once complete. JobHead is the master
> > record that links them together.
> >
> >
> >
> > Brian.
> >
> >
> >
> > ________________________________
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> > Of swenson.justin
> > Sent: Tuesday, March 20, 2012 12:07 PM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Re: Data Model of Jobs (Epicor 9.05.606)
> >
> >
> >
> >
> >
> > Thanks John. My apologies for taking so long to get back to you.
> >
> > We're trying to add new fields to be tracked by part revision. (Such as
> > the current build instruction version, the image ID, the test rev, etc.)
> > Each of these will be attached to a part rev. Now each of these part
> > revs will be attached to a job and the most current part rev is not
> > necessarily the one used on a job. So it has to pull from the possible
> > part revs, but are not necessarily attached to what's current.
> >
> > These fields also need to stay updatable in case specific things (like
> > the build instructions) are swapped out at any point in the jobs
> > lifecycle.
> >
> > We have them added to the part maintenance screen and the new fields are
> > stored in the PartRev table, but connecting the functionality to work
> > with the Job Entry screen (and the relationship with the JobHead table)
> > is something we haven't been able to get working.
> >
> > No one here is well versed when it comes to working with the Epicor
> > database, so any help would be great.
> >
> > Thanks,
> >
> > Justin
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , John
> > Driggers <waffqle@> wrote:
> > >
> > > Sadly I don't have anything like that, but if you have an example of
> > what
> > > you need, I'd be happy to explain the link
> > >
> > > On Fri, Mar 16, 2012 at 2:43 PM, swenson.justin
> > <swenson.justin@>wrote:
> > >
> > > > **
> > > >
> > > >
> > > > I'm slowly figuring out the Epicor database, at the moment I've been
> > able
> > > > to find rough entity data models for parts and ECOs, not I want to
> > get into
> > > > jobs and their relationships with parts.
> > > >
> > > > Anyone already have something like that laid out in a PDF or Viso?
> > > >
> > > > Thanks,
> > > >
> > > > Justin M. Swenson
> > > > IT Programmer
> > > > EmbedTek, LLC
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > *John Driggers*
> > > *High End Dev, System Design, Profit Drinking*
> > > *
> > > **:: 904.404.9233*
> > > *:: waffqle@*
> > > *:: NO FAXES*
> > >
> > > *
> > >
> > > *
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
2
I'm slowly figuring out the Epicor database, at the moment I've been able to find rough entity data models for parts and ECOs, not I want to get into jobs and their relationships with parts.

Anyone already have something like that laid out in a PDF or Viso?

Thanks,

Justin M. Swenson
IT Programmer
EmbedTek, LLC
3
Sadly I don't have anything like that, but if you have an example of what
you need, I'd be happy to explain the link

On Fri, Mar 16, 2012 at 2:43 PM, swenson.justin <swenson.justin@...>wrote:

> **
>
>
> I'm slowly figuring out the Epicor database, at the moment I've been able
> to find rough entity data models for parts and ECOs, not I want to get into
> jobs and their relationships with parts.
>
> Anyone already have something like that laid out in a PDF or Viso?
>
> Thanks,
>
> Justin M. Swenson
> IT Programmer
> EmbedTek, LLC
>
>
>



--
*John Driggers*
*High End Dev, System Design, Profit Drinking*
*
**:: 904.404.9233*
*:: waffqle@...*
*:: NO FAXES*

*

*


[Non-text portions of this message have been removed]
4
Thanks John. My apologies for taking so long to get back to you.

We're trying to add new fields to be tracked by part revision. (Such as the current build instruction version, the image ID, the test rev, etc.) Each of these will be attached to a part rev. Now each of these part revs will be attached to a job and the most current part rev is not necessarily the one used on a job. So it has to pull from the possible part revs, but are not necessarily attached to what's current.

These fields also need to stay updatable in case specific things (like the build instructions) are swapped out at any point in the jobs lifecycle.

We have them added to the part maintenance screen and the new fields are stored in the PartRev table, but connecting the functionality to work with the Job Entry screen (and the relationship with the JobHead table) is something we haven't been able to get working.

No one here is well versed when it comes to working with the Epicor database, so any help would be great.

Thanks,

Justin

--- In vantage@yahoogroups.com, John Driggers <waffqle@...> wrote:
>
> Sadly I don't have anything like that, but if you have an example of what
> you need, I'd be happy to explain the link
>
> On Fri, Mar 16, 2012 at 2:43 PM, swenson.justin <swenson.justin@...>wrote:
>
> > **
> >
> >
> > I'm slowly figuring out the Epicor database, at the moment I've been able
> > to find rough entity data models for parts and ECOs, not I want to get into
> > jobs and their relationships with parts.
> >
> > Anyone already have something like that laid out in a PDF or Viso?
> >
> > Thanks,
> >
> > Justin M. Swenson
> > IT Programmer
> > EmbedTek, LLC
> >
> >
> >
>
>
>
> --
> *John Driggers*
> *High End Dev, System Design, Profit Drinking*
> *
> **:: 904.404.9233*
> *:: waffqle@...*
> *:: NO FAXES*
>
> *
>
> *
>
>
> [Non-text portions of this message have been removed]
>
5
Are we talking about the production part, or the job material in this case?

On Tue, Mar 20, 2012 at 12:06 PM, swenson.justin
<swenson.justin@...>wrote:

> **
>
>
> Thanks John. My apologies for taking so long to get back to you.
>
> We're trying to add new fields to be tracked by part revision. (Such as
> the current build instruction version, the image ID, the test rev, etc.)
> Each of these will be attached to a part rev. Now each of these part revs
> will be attached to a job and the most current part rev is not necessarily
> the one used on a job. So it has to pull from the possible part revs, but
> are not necessarily attached to what's current.
>
> These fields also need to stay updatable in case specific things (like the
> build instructions) are swapped out at any point in the jobs lifecycle.
>
> We have them added to the part maintenance screen and the new fields are
> stored in the PartRev table, but connecting the functionality to work with
> the Job Entry screen (and the relationship with the JobHead table) is
> something we haven't been able to get working.
>
> No one here is well versed when it comes to working with the Epicor
> database, so any help would be great.
>
> Thanks,
>
> Justin
>
>
> --- In vantage@yahoogroups.com, John Driggers <waffqle@...> wrote:
> >
> > Sadly I don't have anything like that, but if you have an example of what
> > you need, I'd be happy to explain the link
> >
> > On Fri, Mar 16, 2012 at 2:43 PM, swenson.justin <swenson.justin@
> ...>wrote:
> >
> > > **
>
> > >
> > >
> > > I'm slowly figuring out the Epicor database, at the moment I've been
> able
> > > to find rough entity data models for parts and ECOs, not I want to get
> into
> > > jobs and their relationships with parts.
> > >
> > > Anyone already have something like that laid out in a PDF or Viso?
> > >
> > > Thanks,
> > >
> > > Justin M. Swenson
> > > IT Programmer
> > > EmbedTek, LLC
> > >
> > >
> > >
> >
> >
> >
> > --
> > *John Driggers*
> > *High End Dev, System Design, Profit Drinking*
> > *
> > **:: 904.404.9233*
> > *:: waffqle@...*
> > *:: NO FAXES*
> >
> > *
> >
> > *
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>



--
*John Driggers*
*High End Dev, System Design, Profit Drinking*
*
**:: 904.404.9233*
*:: waffqle@...*
*:: NO FAXES*

*

*


[Non-text portions of this message have been removed]
6
If I understand what you want correctly... you have some info in
PartRev.Character01, and when a job is created from that rev, you want
it copied to a Job???.Character01 field - based on the part rev selected
for that job, not necessarily the current rev? In that case, try Custom
Field Map (under system management -> utilities). Choose JobAsmbl for
the target (I think that's what you're trying to do), PartRev for the
source, and fill in Character01 or whatever.



In general, JobAsmbl is the finished good you're making, JobOper is the
work (operations) to make it, JobMtl is the raw material, and JobProd is
what happens to the finished good once complete. JobHead is the master
record that links them together.



Brian.



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of swenson.justin
Sent: Tuesday, March 20, 2012 12:07 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Data Model of Jobs (Epicor 9.05.606)





Thanks John. My apologies for taking so long to get back to you.

We're trying to add new fields to be tracked by part revision. (Such as
the current build instruction version, the image ID, the test rev, etc.)
Each of these will be attached to a part rev. Now each of these part
revs will be attached to a job and the most current part rev is not
necessarily the one used on a job. So it has to pull from the possible
part revs, but are not necessarily attached to what's current.

These fields also need to stay updatable in case specific things (like
the build instructions) are swapped out at any point in the jobs
lifecycle.

We have them added to the part maintenance screen and the new fields are
stored in the PartRev table, but connecting the functionality to work
with the Job Entry screen (and the relationship with the JobHead table)
is something we haven't been able to get working.

No one here is well versed when it comes to working with the Epicor
database, so any help would be great.

Thanks,

Justin

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , John
Driggers <waffqle@...> wrote:
>
> Sadly I don't have anything like that, but if you have an example of
what
> you need, I'd be happy to explain the link
>
> On Fri, Mar 16, 2012 at 2:43 PM, swenson.justin
<swenson.justin@...>wrote:
>
> > **
> >
> >
> > I'm slowly figuring out the Epicor database, at the moment I've been
able
> > to find rough entity data models for parts and ECOs, not I want to
get into
> > jobs and their relationships with parts.
> >
> > Anyone already have something like that laid out in a PDF or Viso?
> >
> > Thanks,
> >
> > Justin M. Swenson
> > IT Programmer
> > EmbedTek, LLC
> >
> >
> >
>
>
>
> --
> *John Driggers*
> *High End Dev, System Design, Profit Drinking*
> *
> **:: 904.404.9233*
> *:: waffqle@...*
> *:: NO FAXES*
>
> *
>
> *
>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]
7
Thanks Brian. I probably won't be able to test this for another day, but you seem to get exactly what I'm looking for. I understand your descriptions of each table as well.

I'll get back to you when I've had a chance to work through it.


--- In vantage@yahoogroups.com, "Brian Roberts" <broberts@...> wrote:
>
> If I understand what you want correctly... you have some info in
> PartRev.Character01, and when a job is created from that rev, you want
> it copied to a Job???.Character01 field - based on the part rev selected
> for that job, not necessarily the current rev? In that case, try Custom
> Field Map (under system management -> utilities). Choose JobAsmbl for
> the target (I think that's what you're trying to do), PartRev for the
> source, and fill in Character01 or whatever.
>
>
>
> In general, JobAsmbl is the finished good you're making, JobOper is the
> work (operations) to make it, JobMtl is the raw material, and JobProd is
> what happens to the finished good once complete. JobHead is the master
> record that links them together.
>
>
>
> Brian.
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of swenson.justin
> Sent: Tuesday, March 20, 2012 12:07 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Data Model of Jobs (Epicor 9.05.606)
>
>
>
>
>
> Thanks John. My apologies for taking so long to get back to you.
>
> We're trying to add new fields to be tracked by part revision. (Such as
> the current build instruction version, the image ID, the test rev, etc.)
> Each of these will be attached to a part rev. Now each of these part
> revs will be attached to a job and the most current part rev is not
> necessarily the one used on a job. So it has to pull from the possible
> part revs, but are not necessarily attached to what's current.
>
> These fields also need to stay updatable in case specific things (like
> the build instructions) are swapped out at any point in the jobs
> lifecycle.
>
> We have them added to the part maintenance screen and the new fields are
> stored in the PartRev table, but connecting the functionality to work
> with the Job Entry screen (and the relationship with the JobHead table)
> is something we haven't been able to get working.
>
> No one here is well versed when it comes to working with the Epicor
> database, so any help would be great.
>
> Thanks,
>
> Justin
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , John
> Driggers <waffqle@> wrote:
> >
> > Sadly I don't have anything like that, but if you have an example of
> what
> > you need, I'd be happy to explain the link
> >
> > On Fri, Mar 16, 2012 at 2:43 PM, swenson.justin
> <swenson.justin@>wrote:
> >
> > > **
> > >
> > >
> > > I'm slowly figuring out the Epicor database, at the moment I've been
> able
> > > to find rough entity data models for parts and ECOs, not I want to
> get into
> > > jobs and their relationships with parts.
> > >
> > > Anyone already have something like that laid out in a PDF or Viso?
> > >
> > > Thanks,
> > >
> > > Justin M. Swenson
> > > IT Programmer
> > > EmbedTek, LLC
> > >
> > >
> > >
> >
> >
> >
> > --
> > *John Driggers*
> > *High End Dev, System Design, Profit Drinking*
> > *
> > **:: 904.404.9233*
> > *:: waffqle@*
> > *:: NO FAXES*
> >
> > *
> >
> > *
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>