Epicor 9.05.700 to 10.1

Will all of our BAQs have to be re-written if we go to 10.1 or can they be exported and imported straight in?

Many thanks in advance.

Not all will have to be re-written most simple BAQ’s will work fine. Any BAQ with Summary Tables will have to be adjusted.

Thanks Jose, the main reason i ask is that i understood some of the table and/or field names may have changed in 10.1…to our current version of 9.05.700

Yes that is correct and those will have to be fixed, but the great majority didn’t change.

We were able to test 10.1.400 on several remote sessions…i had a quick look at some of the fields and they seem to be defaulted with either ERP or ECL (if i rememeber correctly).

so for eg…in 9.05.700 i would see
Table PART
Field PARTNUM

in 10.1.400 i would see
Table PART
Field ERPPartNum

This is why i was worried we wouldn’t be able to export from 9 to 10.

At the moment, we don’t have access to the 10.1 remote session so i can’t confirm the defaulted 3 letter characters.

Thanks.
Mark

No that is not the case
The table schemas changes from dbo.Table to ERP.Table or ICE.Table but the conversion process translates that automatically.

so, we can simply EXPORT from 9 and IMPORT to 10 ?

That might be the best news i’ve heard all day!

Hmm you keep saying Export from 9 and Import to 10 are you not doing a conversion? (did I misunderstand?)

If you are not doing a conversion then a lot of the stuff that would happen during… erm… a “conversion” won’t happen. So you may be SOL there, I believe the BAQ’s might be the only thing that still SORTA convert when you export / import but don’t quote me on that.

From 9 I recommend a conversion vs a DMT, unless your data is just utter crap…

In the very least if you are not doing a conversion, you should do 1 conversion pass to have all those BAQ’s and most of your Customizations “converted” then export those out of your converted 10 and import into your “BLANK” 10

Mark, I haven’t tried to import an exported Epicor 9 BAQ into our Epicor 10
environment. I know the conversion process will convert BAQs in the Epicor
9 database. It got the majority of ours, we had some with summaries,
mentioned before by Jose, that we had to adjust. Also a few others that
needed tweaks.

Forgive me for being thick…i’m familiar with DMT…but what is involved in a conversion? How is this process done exactly?
I take it your not referring to the “conversion” fixes we run in epicor admin tools?

Thanks again.

You have 2 ways to get to E10 form 9

  1. You go through the database conversion process, this is the standard upgrade process, you install 10, run the conversion scripts and epicor uplifts your data / data schema to the new version. This is by far the easiest way to do it and the less error prone, it also ensures that you keep your transaction data for historical purposes. Epicor wrote several conversions that run via this process which convert your BAQ’s and some customizations and BPMs. If your data in E9 is good data and you are not planning on abandoning your history this is the way to do the upgrade. There is no Export / Import it is a single smooth transition for the entire DB.
  2. Option 2 you can DMT your data in (Customer Data, Invoice Data, PO Data , Order Data etc) this makes for a clean DB and allows you to start over (Re do GL’s , Re-Do Parts etc) but your historical data won’t come through and none of the conversions will take place (you’ll have to manually import everything)

I mean the standard migration from Epicor 9 to Epicor 10 process, using the
“Migration Guide” from Epicor.

thanks guys…we’ll be interested in point1…if epicor includes BAQs in this process when they uplift the data…No problem!

The database migration from E9 to E10 would convert the BAQ, but BAQ summary, and first/last behaves differently in E10, so you have to modify or rewrite some of them.
For BAQ without using summary, first / last, you’ll be probably fine.
You can check BAQ conversion result under E10 System Management->Upgrade/Mass Regeneration. It’ll tell you everything you need to know.