Cloud Upgrade to 10.2.500 - a few key points

Epicor ERP 10
1

A couple key points with the Cloud upgrade.

  1. If you haven’t done so yet, go in and do a “simple” Quote to Cash, Procure to Pay and Revision with the engineering workbench. A few of my customers found an issue with creating a basic purchase order which Epicor is currently resolving

  2. Check the Unique Business Components dashboard (search the menu for it). It will show which customizations may have failed the conversion process.

  3. Request the UBC (Unique Business Components) that you want moved from Pilot to Production

I sent the following message to all of the customers that I work with.

To the cloud customers that I know of:

This is a reminder to send in a case to Epicor to move all UBC’s from 10.2.440 to 10.2.500, if you don’t you will have to move them manually over to 10.2.500

What do you need to do?

Based on the answer to question 1 below – you will need to send in a request to EpiCare;

Basically:

Subject –

Please move all UBCs

In the body state -

All UBCs that are in the database that are one the menu or not, used or not should be moved.

Thank you for your help in keeping our system the way it is in 10.2.400 in the new release of 10.2.500

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Message from Epicor Support

2019-07-29 08:55:53 -Anand Gupta

Good Day Bruce,

As an update,

  1. Do I need to submit a case for each UBC, list them or is it sufficient to state, “I want to keep all of my UBCs”?
    Support - If you want all - just say move all UBCs

What happens if I do not submit a case?
Support:- They are not moved

Will all customizations not be moved forward?
Support:- Correct - they will be validated during the upgrade process as normal but if you don’t want them moved we do not move them in a solution from pilot into live without a request

Will they be deleted from the database?
Support:- No

  1. When production is upgraded will the newly upgraded production database be restored into Pilot, eliminating any chance to restore UBCs worked on in
    Support:- normally we have a week between in MT and in public cloud, we do not refresh so you will have options to get what you want.

This is a change because we did in out option and caused for major issues with many newer customers in the cloud that did NOT want them moved. So, we had to change with the number of customers in the cloud - we could not blindly move Pilot stuff into a production database.

Do let me know if you have any further questions.

AnandKumarD Gupta

Epicor 10 Technical support.

2 Likes
2

There seems to be a little confusion about the Opt-In and UBC Tracker - hopefully this will help.

When Epicor upgrades the Live environments from 10.2.400 to 10.2.500, all your Unique Business Components (BAQs, BPMs, Customizations, Dashboards, etc.) will get upgraded to 500 regardless of Opt-In or not.

The only reason to Opt-In and tag UBC elements in the 10.2.500 Pilot environment is if you have made changes to those elements in Pilot and you want them copied to Live when Live gets upgraded to 500.

If you do Opt-In, Tagged UBC elements will be copied and will overwrite the elements that got upgraded from 400. If you have a UBC in 400 that is not tagged in Pilot, it will still exist in 500. Opting-In does not cause your existing UBC components to be deleted.

1 Like