Vantage 8.03.305 - new job traveler

Yahoo Archive
1
Thanks Charles

--- In vantage@yahoogroups.com, "charles06072006" <shadow031449@...>
wrote:
>
> The JobAsmbl table is the table that operations and scheduling
> resources are linked to within a specific job. If your BOM/MOM is
> extremely simple, e.g. only one top level assembly and all of the
> parts underneath it then you will probably only have one JobAsmbl
> record per job. Our BOM is very complicated; up to 11 levels deep
> and as many as 100 subassemlies and 200 or more operations per job.
> The JobAsmbl table ties all those operations together and indicates
> the sequence of events.
>
> Sub-assemblies within a job/BOM can be pulled as an assembly, i.e. it
> will have its own BOM and operations within the top level job and
> therefore would have its own JobAsmbl record, or pulled as material,
> i.e. pulled from stock which would mean you would have to schedule
> the building of those assemblies as seperate jobs and stock them as
> necessary. In the latter MRP would suggest the creation of unfirmed
> jobs in order to meet the requirements.
>
> Hope that helps.
>
2
I would like to create a new job traveler - not modify the current.
The report header will be the operation details followed by the
material components for the operation. I am still learning the Vantage
schema and Crystal and am having a little trouble with the tables and
joins. The database links in the standard Crystal Report are confusing
and doesn't have the jobmtl table. Can someone explain the tables and
relationship for the job travel report?

I am testing by writing my query manually and get all material for the
job but don't see how to filter by an particular operation on the job.

Note: Have written MANY reports manually (Progress) for our previous
ERP software but not familar with the V8 schema.

Thanks in advance...
3
Found the operation field in jobmtl - jobmtl.relatedoperation. Looked
right past it.

But, I still would like a explanation of the tables used in the
standard job traveler as I am still not sure how the they are all used.

An example of my confusion: The V8 travler CR report uses "subasmbl" -
I don't see this table in the schema.

jobhead, jobasmbl, joboper, jobopdtl, jobmtl, jobpart, etc...

Thanks
4
Any experts with knowledge of the table uses and joins for the Vantage
job traveler? The standard "JobTrav" report data definition uses the
following tables:

Company, JobAsmbl, JobHead, JobMtl, JobOpDtl, JobOper, JobPart,
JobShip, ResourceTimeUsed, SubAsmbl, TTJobPartMTL.

My query seems to pull the job header and materials but there must be
more to it:

FOR EACH vantage.jobhead NO-LOCK WHERE jobhead.company = "G3RB" AND
jobhead.jobnum = "020004",
EACH vantage.joboper NO-LOCK WHERE joboper.company =
jobhead.company AND joboper.jobnum = jobhead.jobnum AND joboper.OprSeq
= 40,
EACH vantage.jobopdtl NO-LOCK WHERE jobopdtl.company =
joboper.company AND jobopdtl.jobnum = joboper.jobnum AND
jobopdtl.OprSeq = joboper.OprSeq,
EACH vantage.jobasmbl NO-LOCK WHERE jobasmbl.company =
joboper.company AND jobasmbl.jobnum = joboper.jobnum,
EACH vantage.jobmtl NO-LOCK WHERE jobmtl.company = joboper.company
AND jobmtl.jobnum = joboper.jobnum AND jobmtl.relatedoperation =
joboper.OprSeq AND jobmtl.assemblyseq = jobasmbl.assemblyseq:


Am I the only to have ever tried to re-engineer the Vantage Job Traveler?
5
What if an operation doesn't have material but is milling for example:

Your join to jobmtl would need to be an Outer Join in case no record
exists for that operation to print.



Patrick J. Winter



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of hoomail4me
Sent: Wednesday, February 13, 2008 1:17 PM
To: vantage@yahoogroups.com
Subject: [SPAM] [Vantage] Re: Vantage 8.03.305 - new job traveler.



Any experts with knowledge of the table uses and joins for the Vantage
job traveler? The standard "JobTrav" report data definition uses the
following tables:

Company, JobAsmbl, JobHead, JobMtl, JobOpDtl, JobOper, JobPart,
JobShip, ResourceTimeUsed, SubAsmbl, TTJobPartMTL.

My query seems to pull the job header and materials but there must be
more to it:

FOR EACH vantage.jobhead NO-LOCK WHERE jobhead.company = "G3RB" AND
jobhead.jobnum = "020004",
EACH vantage.joboper NO-LOCK WHERE joboper.company =
jobhead.company AND joboper.jobnum = jobhead.jobnum AND joboper.OprSeq
= 40,
EACH vantage.jobopdtl NO-LOCK WHERE jobopdtl.company =
joboper.company AND jobopdtl.jobnum = joboper.jobnum AND
jobopdtl.OprSeq = joboper.OprSeq,
EACH vantage.jobasmbl NO-LOCK WHERE jobasmbl.company =
joboper.company AND jobasmbl.jobnum = joboper.jobnum,
EACH vantage.jobmtl NO-LOCK WHERE jobmtl.company = joboper.company
AND jobmtl.jobnum = joboper.jobnum AND jobmtl.relatedoperation =
joboper.OprSeq AND jobmtl.assemblyseq = jobasmbl.assemblyseq:


Am I the only to have ever tried to re-engineer the Vantage Job
Traveler?





This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

[Non-text portions of this message have been removed]
6
Are you setting up an ODBC Job Traveler, a BAQ Report Job Traveler or
modified the Report Data Definition Job Traveler?

I have completely modified the Job Traveler to fit our environment. I am
using a modified report Data Definition adding fields that were excluded in
the original data definition creating a new Style to print the Traveler as
we need it. Such as we wanted it Portrait versus Landscape so more operation
could fit on a Page, removed a lot of unnecessary fields, removed the Job
parts subreport that we did not use, and one big one was to remove the Raw
Material Components from the current location and the create a new subreport
to show what part(s) was needed at the operation. Then when the shop
employee is looking at there operation they know what parts are needed for
that operation.

Scott

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
hoomail4me
Sent: Wednesday, February 13, 2008 1:17 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Vantage 8.03.305 - new job traveler.

Any experts with knowledge of the table uses and joins for the Vantage
job traveler? The standard "JobTrav" report data definition uses the
following tables:

Company, JobAsmbl, JobHead, JobMtl, JobOpDtl, JobOper, JobPart,
JobShip, ResourceTimeUsed, SubAsmbl, TTJobPartMTL.

My query seems to pull the job header and materials but there must be
more to it:

FOR EACH vantage.jobhead NO-LOCK WHERE jobhead.company = "G3RB" AND
jobhead.jobnum = "020004",
EACH vantage.joboper NO-LOCK WHERE joboper.company =
jobhead.company AND joboper.jobnum = jobhead.jobnum AND joboper.OprSeq
= 40,
EACH vantage.jobopdtl NO-LOCK WHERE jobopdtl.company =
joboper.company AND jobopdtl.jobnum = joboper.jobnum AND
jobopdtl.OprSeq = joboper.OprSeq,
EACH vantage.jobasmbl NO-LOCK WHERE jobasmbl.company =
joboper.company AND jobasmbl.jobnum = joboper.jobnum,
EACH vantage.jobmtl NO-LOCK WHERE jobmtl.company = joboper.company
AND jobmtl.jobnum = joboper.jobnum AND jobmtl.relatedoperation =
joboper.OprSeq AND jobmtl.assemblyseq = jobasmbl.assemblyseq:


Am I the only to have ever tried to re-engineer the Vantage Job Traveler?







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/links
Yahoo! Groups Links
7
I am not concerned at this point as to the method I will use - ODBC,
BAQ, or Report Data Definition. I was hoping to get an understanding
on what tables store what data and the relationship.

I have written a 4GL query, a BAQ, and looked at the standard
travelers Report Data Definition. I can return most everything I need
but don't want to overlook something for a unique condition that I am
not testing (assemblies, etc.)

Example, many of the tables have the same fields - I don't know what
is stored in the JobAsmbl table or how it relates to the
JobHead/JobOper tables.

My thought is that I will use:

JobHead - job related information
JobOper - operation specific
JobOpDtl - additional operation specific
JobMtl - material details used on an operation

The V8 "JobTrav" data definition uses these Rpt Table IDs and
"JobAsmbl", "JobPart", "JobShip", "ResourceTimeUsed", "SubAsmbl", and
"TTJobPartMtl".

It took me a little time to become familar with our previous ERP db
schema (Styeline) and learning as I go with Vantage.

Thanks in advanced for any assistance.








--- In vantage@yahoogroups.com, "Scott Litzau" <scott.litzau@...> wrote:
>
> Are you setting up an ODBC Job Traveler, a BAQ Report Job Traveler or
> modified the Report Data Definition Job Traveler?
>
> I have completely modified the Job Traveler to fit our environment. I am
> using a modified report Data Definition adding fields that were
excluded in
> the original data definition creating a new Style to print the
Traveler as
> we need it. Such as we wanted it Portrait versus Landscape so more
operation
> could fit on a Page, removed a lot of unnecessary fields, removed
the Job
> parts subreport that we did not use, and one big one was to remove
the Raw
> Material Components from the current location and the create a new
subreport
> to show what part(s) was needed at the operation. Then when the shop
> employee is looking at there operation they know what parts are
needed for
> that operation.
>
> Scott
8
I went back and read your original post regarding this. In Crystal go into
the Database Expert and click on the Links Tab and then the Order Links
button that will show the field links from Table to Table from what field to
what field, but you still need to look at the properties of the Links
between the Tables to see how they are joined (inner, left).

The Report Data Definition does have the JobMtl table but it is not used in
the main report Database design. If you look at the Raw Material Components
subreport you will see the JobMtl Table, along with other tables. The
Sub-reports are Link back to the main report. If you altenate-click on the
subreport you will see a option for Change Subreport Links, click on that
and it will show you how the subreports are linked back to the main report.

I think you want to do what I am doing by linking the Job Materials to the
perticular operation that needs them. I am using the Report Data Definition
and creted my own Subreport called JobMtl (Operation Material). I placed
this subreport in the JobOper.OperSeq Group Header in its own section after
the operation information. My subreport links are JobAsmbl.JobNum,
JobAsmbl.AssemblySeq and JobOper.OpSeq and the Tables I used in the
Subreport are JobAsmbl and JobMtl. I link Jobasmbl to JobMtl by Company,
JobNum and AssemblySeq.

I just added today another subreport in a section below the JobMtl
subreport, still in theJobOper.OpSeq Group Header, called SubAsmPart which I
am shoing if there is a part from a subassembly needed at the particular
operation.

Like I said I am using the Report Data Defintion, copied to my own user
defined one so I can included some excluded fields from Vantage standard
report defintion, because Epicor has a habit of creating temp (Calc_XXX)
fields that you can not grab from a Table but show up in reports and that I
want to use. So I found it beneficial if it is a more complicated report,
such as the Traveler, to use their definiton, Otherwise I am converting my
ODBC reports over to BAQ where it makes sense. Some things are still easier
ODBC.

It takes a bit to figure out how tables are related to each other but I
found by looking at the canned reports in Crystal and then using the Data
Dictionary and the DataSet Relationships I was able to get a grasp on how
tables are related to each other. I also go into Developer mode to look a
certain fields on screens to tell me which Table and Field Name it is, which
a least gets me started.

Hope this helps

Scott

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
hoomail4me
Sent: Wednesday, February 13, 2008 5:16 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Vantage 8.03.305 - new job traveler.

I am not concerned at this point as to the method I will use - ODBC, BAQ, or
Report Data Definition. I was hoping to get an understanding on what tables
store what data and the relationship.

I have written a 4GL query, a BAQ, and looked at the standard travelers
Report Data Definition. I can return most everything I need but don't want
to overlook something for a unique condition that I am not testing
(assemblies, etc.)

Example, many of the tables have the same fields - I don't know what is
stored in the JobAsmbl table or how it relates to the JobHead/JobOper
tables.

My thought is that I will use:

JobHead - job related information
JobOper - operation specific
JobOpDtl - additional operation specific JobMtl - material details used on
an operation

The V8 "JobTrav" data definition uses these Rpt Table IDs and "JobAsmbl",
"JobPart", "JobShip", "ResourceTimeUsed", "SubAsmbl", and "TTJobPartMtl".

It took me a little time to become familar with our previous ERP db schema
(Styeline) and learning as I go with Vantage.

Thanks in advanced for any assistance.








--- In vantage@yahoogroups.com, "Scott Litzau" <scott.litzau@...> wrote:
>
> Are you setting up an ODBC Job Traveler, a BAQ Report Job Traveler or
> modified the Report Data Definition Job Traveler?
>
> I have completely modified the Job Traveler to fit our environment. I
> am using a modified report Data Definition adding fields that were
excluded in
> the original data definition creating a new Style to print the
Traveler as
> we need it. Such as we wanted it Portrait versus Landscape so more
operation
> could fit on a Page, removed a lot of unnecessary fields, removed
the Job
> parts subreport that we did not use, and one big one was to remove
the Raw
> Material Components from the current location and the create a new
subreport
> to show what part(s) was needed at the operation. Then when the shop
> employee is looking at there operation they know what parts are
needed for
> that operation.
>
> Scott




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/links
Yahoo! Groups Links
9
The JobHead is your main table.

JobPart is basically the same as JobHead unless you are using
Advanced Planning and Scheduling. It allows a single job to be
created for multiple top level parts. The JobPart table would then
contain multiple records related to the JobHead.

JobAsmbl would be the next table in sequence since basically
everything else is tied back to it. It is linked back to JobHead by
JobNum.

JobMtl is linked to JobAsmbl by JobNum and AssemblySeq.

JobMtl is also linked to JobOper by JobNum, AssemblySeq and
RelatedOperation, the latter being linked to OperSeq in JobAsmbl.

JobOper is linked to JobAsmbl by JobNum and AssemblySeq.

JobOpDtl is linked to JobOper by JobNum, AssemblySeq, and OperSeq.

I think you will find that most everything links back to the JobAsmbl
table. You will find some of the tables are only used if you have
the Advanced Planning and Scheduling Module. You will also see a lot
of fields in the tables starting with APS. Those fields are also
only used with Advanced Planning and Scheduling. We do not have that
so the only tables I am really ever concerned with are JobHead,
JobAsmbl, JobMtl, JobOper and JobOpDtl.

All of the Job tables ending in WI are for the What-If Scheduling.


--- In vantage@yahoogroups.com, "Scott Litzau" <scott.litzau@...>
wrote:
>
> I went back and read your original post regarding this. In Crystal
go into
> the Database Expert and click on the Links Tab and then the Order
Links
> button that will show the field links from Table to Table from what
field to
> what field, but you still need to look at the properties of the
Links
> between the Tables to see how they are joined (inner, left).
>
> The Report Data Definition does have the JobMtl table but it is not
used in
> the main report Database design. If you look at the Raw Material
Components
> subreport you will see the JobMtl Table, along with other tables.
The
> Sub-reports are Link back to the main report. If you altenate-click
on the
> subreport you will see a option for Change Subreport Links, click
on that
> and it will show you how the subreports are linked back to the main
report.
>
> I think you want to do what I am doing by linking the Job Materials
to the
> perticular operation that needs them. I am using the Report Data
Definition
> and creted my own Subreport called JobMtl (Operation Material). I
placed
> this subreport in the JobOper.OperSeq Group Header in its own
section after
> the operation information. My subreport links are JobAsmbl.JobNum,
> JobAsmbl.AssemblySeq and JobOper.OpSeq and the Tables I used in the
> Subreport are JobAsmbl and JobMtl. I link Jobasmbl to JobMtl by
Company,
> JobNum and AssemblySeq.
>
> I just added today another subreport in a section below the JobMtl
> subreport, still in theJobOper.OpSeq Group Header, called
SubAsmPart which I
> am shoing if there is a part from a subassembly needed at the
particular
> operation.
>
> Like I said I am using the Report Data Defintion, copied to my own
user
> defined one so I can included some excluded fields from Vantage
standard
> report defintion, because Epicor has a habit of creating temp
(Calc_XXX)
> fields that you can not grab from a Table but show up in reports
and that I
> want to use. So I found it beneficial if it is a more complicated
report,
> such as the Traveler, to use their definiton, Otherwise I am
converting my
> ODBC reports over to BAQ where it makes sense. Some things are
still easier
> ODBC.
>
> It takes a bit to figure out how tables are related to each other
but I
> found by looking at the canned reports in Crystal and then using
the Data
> Dictionary and the DataSet Relationships I was able to get a grasp
on how
> tables are related to each other. I also go into Developer mode to
look a
> certain fields on screens to tell me which Table and Field Name it
is, which
> a least gets me started.
>
> Hope this helps
>
> Scott
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of
> hoomail4me
> Sent: Wednesday, February 13, 2008 5:16 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Vantage 8.03.305 - new job traveler.
>
> I am not concerned at this point as to the method I will use -
ODBC, BAQ, or
> Report Data Definition. I was hoping to get an understanding on
what tables
> store what data and the relationship.
>
> I have written a 4GL query, a BAQ, and looked at the standard
travelers
> Report Data Definition. I can return most everything I need but
don't want
> to overlook something for a unique condition that I am not testing
> (assemblies, etc.)
>
> Example, many of the tables have the same fields - I don't know
what is
> stored in the JobAsmbl table or how it relates to the
JobHead/JobOper
> tables.
>
> My thought is that I will use:
>
> JobHead - job related information
> JobOper - operation specific
> JobOpDtl - additional operation specific JobMtl - material details
used on
> an operation
>
> The V8 "JobTrav" data definition uses these Rpt Table IDs
and "JobAsmbl",
> "JobPart", "JobShip", "ResourceTimeUsed", "SubAsmbl",
and "TTJobPartMtl".
>
> It took me a little time to become familar with our previous ERP db
schema
> (Styeline) and learning as I go with Vantage.
>
> Thanks in advanced for any assistance.
>
>
>
>
>
>
>
>
> --- In vantage@yahoogroups.com, "Scott Litzau" <scott.litzau@>
wrote:
> >
> > Are you setting up an ODBC Job Traveler, a BAQ Report Job
Traveler or
> > modified the Report Data Definition Job Traveler?
> >
> > I have completely modified the Job Traveler to fit our
environment. I
> > am using a modified report Data Definition adding fields that were
> excluded in
> > the original data definition creating a new Style to print the
> Traveler as
> > we need it. Such as we wanted it Portrait versus Landscape so more
> operation
> > could fit on a Page, removed a lot of unnecessary fields, removed
> the Job
> > parts subreport that we did not use, and one big one was to remove
> the Raw
> > Material Components from the current location and the create a new
> subreport
> > to show what part(s) was needed at the operation. Then when the
shop
> > employee is looking at there operation they know what parts are
> needed for
> > that operation.
> >
> > Scott
>
>
>
>
> 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/links
> Yahoo! Groups Links
>
10
Thanks for your input Scott and Charles. I got best of both worlds,
an explanation of the tables and how they are used, and an explanation
of how the standard report works and can be changed.

I usually start a reporting task by writing my own manual query to
find data and test relationships. Then I may go to a reporting tool
like Crystal to make it pretty. In the case of the Epicor job
traveler, it is very complex and prevents me from really knowing where
the data resides in the schema.

I have never used high level reporting tools much (Crystal, Report
Builder, etc) as I have more control writing manually (temp tables,
additional processing, etc.).

Sounds like I may end up with something similar to what you are doing
Scott as I don't like the output arrangement of the standard report.
Is there any chance I could get your RPT and an XML source?

Thanks again guys.
11
Charles, do you know how the JobAsmbl table is used? I understand
the purpose of the others, JobHead, JobMtl, JobOper and JobOpDtl.

Thanks

--- In vantage@yahoogroups.com, "charles06072006" <shadow031449@...>
wrote:
>
> The JobHead is your main table.
>
> JobPart is basically the same as JobHead unless you are using
> Advanced Planning and Scheduling. It allows a single job to be
> created for multiple top level parts. The JobPart table would then
> contain multiple records related to the JobHead.
>
> JobAsmbl would be the next table in sequence since basically
> everything else is tied back to it. It is linked back to JobHead by
> JobNum.
>
> JobMtl is linked to JobAsmbl by JobNum and AssemblySeq.
>
> JobMtl is also linked to JobOper by JobNum, AssemblySeq and
> RelatedOperation, the latter being linked to OperSeq in JobAsmbl.
>
> JobOper is linked to JobAsmbl by JobNum and AssemblySeq.
>
> JobOpDtl is linked to JobOper by JobNum, AssemblySeq, and OperSeq.
>
> I think you will find that most everything links back to the JobAsmbl
> table. You will find some of the tables are only used if you have
> the Advanced Planning and Scheduling Module. You will also see a lot
> of fields in the tables starting with APS. Those fields are also
> only used with Advanced Planning and Scheduling. We do not have that
> so the only tables I am really ever concerned with are JobHead,
> JobAsmbl, JobMtl, JobOper and JobOpDtl.
>
> All of the Job tables ending in WI are for the What-If Scheduling.
>
>
12
The JobAsmbl table is the table that operations and scheduling
resources are linked to within a specific job. If your BOM/MOM is
extremely simple, e.g. only one top level assembly and all of the
parts underneath it then you will probably only have one JobAsmbl
record per job. Our BOM is very complicated; up to 11 levels deep
and as many as 100 subassemlies and 200 or more operations per job.
The JobAsmbl table ties all those operations together and indicates
the sequence of events.

Sub-assemblies within a job/BOM can be pulled as an assembly, i.e. it
will have its own BOM and operations within the top level job and
therefore would have its own JobAsmbl record, or pulled as material,
i.e. pulled from stock which would mean you would have to schedule
the building of those assemblies as seperate jobs and stock them as
necessary. In the latter MRP would suggest the creation of unfirmed
jobs in order to meet the requirements.

Hope that helps.

--- In vantage@yahoogroups.com, "hoomail4me" <hoomail4me@...> wrote:
>
> Charles, do you know how the JobAsmbl table is used? I understand
> the purpose of the others, JobHead, JobMtl, JobOper and JobOpDtl.
>
> Thanks
>
> --- In vantage@yahoogroups.com, "charles06072006" <shadow031449@>
> wrote:
> >
> > The JobHead is your main table.
> >
> > JobPart is basically the same as JobHead unless you are using
> > Advanced Planning and Scheduling. It allows a single job to be
> > created for multiple top level parts. The JobPart table would
then
> > contain multiple records related to the JobHead.
> >
> > JobAsmbl would be the next table in sequence since basically
> > everything else is tied back to it. It is linked back to JobHead
by
> > JobNum.
> >
> > JobMtl is linked to JobAsmbl by JobNum and AssemblySeq.
> >
> > JobMtl is also linked to JobOper by JobNum, AssemblySeq and
> > RelatedOperation, the latter being linked to OperSeq in JobAsmbl.
> >
> > JobOper is linked to JobAsmbl by JobNum and AssemblySeq.
> >
> > JobOpDtl is linked to JobOper by JobNum, AssemblySeq, and OperSeq.
> >
> > I think you will find that most everything links back to the
JobAsmbl
> > table. You will find some of the tables are only used if you
have
> > the Advanced Planning and Scheduling Module. You will also see a
lot
> > of fields in the tables starting with APS. Those fields are also
> > only used with Advanced Planning and Scheduling. We do not have
that
> > so the only tables I am really ever concerned with are JobHead,
> > JobAsmbl, JobMtl, JobOper and JobOpDtl.
> >
> > All of the Job tables ending in WI are for the What-If Scheduling.
> >
> >
>