BOM Data Export Problem

yeah, I think I'm going to have write that query. The export is in Progress. Also, the export report/import to other dbase, is the less desired option.

--- In vantage@yahoogroups.com, "Brian Roberts" <broberts@...> wrote:
>
> Epicor only stores the BOM one level 1 deep in the database, as you've
> discovered. It builds the full BOM tree at report time only. Your
> choices are to export an Epicor report (you can customize the crystal
> format to reduce the export size), or to write your own query - not that
> hard if you're on SQL.
>
>
>
> Brian.
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Hutchinson Ind
> Sent: Tuesday, July 17, 2012 9:36 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: BOM Data Export Problem
>
>
>
>
>
> Thanks Brian,
>
> I tried the below. Didn't solve the problem. The tables below create a
> listing of BOMs 1 level deep. When you actually look at the BOM listing
> report, it drills down to the lowest part. Thanks for your feedback
> thought!
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Brian Roberts" <broberts@> wrote:
> >
> > PartRev for revisions, PartOpr for operations, PartMtl for child
> > material. Remember to join by RevisionNum & AltMethod (if you have
> > multiple revisions), and PartMtl.RelatedOperation is the link to
> > PartOpr.OprSeq.
> >
> >
> >
> > Brian.
> >
> >
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf
> > Of Hutchinson Ind
> > Sent: Tuesday, July 17, 2012 8:41 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] BOM Data Export Problem
> >
> >
> >
> >
> >
> > ...I've been trying to export BOMs from Epicor 904 but have been
> having
> > problems. Has anyone had any success and could provide tips? What I've
> > tried so far...
> >
> > Action
> > Exporting reports "BOM Listing" and "Summarized BOM"
> >
> > Result
> > XML file generated was too large(600mb) to import into database. Also,
> > due to size, report crashed Epicor
> >
> > Action
> > Extract data from PartBOM table(SQL Server)
> >
> > Result
> > This is a temp table that only contains data as the report is being
> > generated. Data is progressively deleted while report is created.
> >
> > Some other questions
> > Where are the BOMs stored? Epicor has said custom code keeps it
> > temporary storage but the data has to reside "somewhere".
> >
> > Any help would be much appreciated
> >
> > John
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
...I've been trying to export BOMs from Epicor 904 but have been having problems. Has anyone had any success and could provide tips? What I've tried so far...

Action
Exporting reports "BOM Listing" and "Summarized BOM"

Result
XML file generated was too large(600mb) to import into database. Also, due to size, report crashed Epicor

Action
Extract data from PartBOM table(SQL Server)

Result
This is a temp table that only contains data as the report is being generated. Data is progressively deleted while report is created.

Some other questions
Where are the BOMs stored? Epicor has said custom code keeps it temporary storage but the data has to reside "somewhere".

Any help would be much appreciated

John
PartRev for revisions, PartOpr for operations, PartMtl for child
material. Remember to join by RevisionNum & AltMethod (if you have
multiple revisions), and PartMtl.RelatedOperation is the link to
PartOpr.OprSeq.



Brian.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Hutchinson Ind
Sent: Tuesday, July 17, 2012 8:41 AM
To: vantage@yahoogroups.com
Subject: [Vantage] BOM Data Export Problem





...I've been trying to export BOMs from Epicor 904 but have been having
problems. Has anyone had any success and could provide tips? What I've
tried so far...

Action
Exporting reports "BOM Listing" and "Summarized BOM"

Result
XML file generated was too large(600mb) to import into database. Also,
due to size, report crashed Epicor

Action
Extract data from PartBOM table(SQL Server)

Result
This is a temp table that only contains data as the report is being
generated. Data is progressively deleted while report is created.

Some other questions
Where are the BOMs stored? Epicor has said custom code keeps it
temporary storage but the data has to reside "somewhere".

Any help would be much appreciated

John





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

I tried the below. Didn't solve the problem. The tables below create a listing of BOMs 1 level deep. When you actually look at the BOM listing report, it drills down to the lowest part. Thanks for your feedback thought!

--- In vantage@yahoogroups.com, "Brian Roberts" <broberts@...> wrote:
>
> PartRev for revisions, PartOpr for operations, PartMtl for child
> material. Remember to join by RevisionNum & AltMethod (if you have
> multiple revisions), and PartMtl.RelatedOperation is the link to
> PartOpr.OprSeq.
>
>
>
> Brian.
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Hutchinson Ind
> Sent: Tuesday, July 17, 2012 8:41 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] BOM Data Export Problem
>
>
>
>
>
> ...I've been trying to export BOMs from Epicor 904 but have been having
> problems. Has anyone had any success and could provide tips? What I've
> tried so far...
>
> Action
> Exporting reports "BOM Listing" and "Summarized BOM"
>
> Result
> XML file generated was too large(600mb) to import into database. Also,
> due to size, report crashed Epicor
>
> Action
> Extract data from PartBOM table(SQL Server)
>
> Result
> This is a temp table that only contains data as the report is being
> generated. Data is progressively deleted while report is created.
>
> Some other questions
> Where are the BOMs stored? Epicor has said custom code keeps it
> temporary storage but the data has to reside "somewhere".
>
> Any help would be much appreciated
>
> John
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Epicor only stores the BOM one level 1 deep in the database, as you've
discovered. It builds the full BOM tree at report time only. Your
choices are to export an Epicor report (you can customize the crystal
format to reduce the export size), or to write your own query - not that
hard if you're on SQL.



Brian.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Hutchinson Ind
Sent: Tuesday, July 17, 2012 9:36 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: BOM Data Export Problem





Thanks Brian,

I tried the below. Didn't solve the problem. The tables below create a
listing of BOMs 1 level deep. When you actually look at the BOM listing
report, it drills down to the lowest part. Thanks for your feedback
thought!

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Brian Roberts" <broberts@...> wrote:
>
> PartRev for revisions, PartOpr for operations, PartMtl for child
> material. Remember to join by RevisionNum & AltMethod (if you have
> multiple revisions), and PartMtl.RelatedOperation is the link to
> PartOpr.OprSeq.
>
>
>
> Brian.
>
>
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
> Of Hutchinson Ind
> Sent: Tuesday, July 17, 2012 8:41 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] BOM Data Export Problem
>
>
>
>
>
> ...I've been trying to export BOMs from Epicor 904 but have been
having
> problems. Has anyone had any success and could provide tips? What I've
> tried so far...
>
> Action
> Exporting reports "BOM Listing" and "Summarized BOM"
>
> Result
> XML file generated was too large(600mb) to import into database. Also,
> due to size, report crashed Epicor
>
> Action
> Extract data from PartBOM table(SQL Server)
>
> Result
> This is a temp table that only contains data as the report is being
> generated. Data is progressively deleted while report is created.
>
> Some other questions
> Where are the BOMs stored? Epicor has said custom code keeps it
> temporary storage but the data has to reside "somewhere".
>
> Any help would be much appreciated
>
> John
>
>
>
>
>
> [Non-text portions of this message have been removed]
>





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