Importing the Template

For each environment, the following previously configured information will be required:

  • ERP Database Name
  • ERP Schema
  • SEI Custom Schema

  • Template zip file (this file must match the SEI version)

    Download the Template file: TPL_Major.Minor.Build_Sage300.zip, where Build represents the build number of the template.

Running the Import Template Process

  1. In the upper-right hand corner, click the to access the Administration section.

  2. In the Administration section, click the Templates drop-down menu in the left pane.
  3. Select Import Template.

  1. In the Import Template window, click Select files....

  2. Find the folder where you saved the Template.zip file in order to select it then click Open.

  3. In the Data Sources Mapping screen, associate the data sources (ERP) listed in the Received Data Sources Description column (those from the template) with the data sources you previously defined in the Central Point (listed in the Current Data Sources Description column).

    1. In the Received Data Sources Description column, ensure that only the data source options you want to use from the template are selected.

    2. In the Current Data Sources Description column, click Bind a Data Source to access the drop-down list containing the existing data sources.

    3. Click Next.

  4. In the next screen, all of the Templates content is displayed, against what the Central Point already has. By default, on the first install, everything will be set to Add (leave everything by default) .

    • In the case of a first installation, the first four columns will display None and Never Installed, the next three will detail the Template content, and the last three gives you the choice to Add, Updating the Template or Skip during the installation.

    • Click Next (this can take time).

  5. Once this has been completed, a window will prompt you to input the necessary parameters to create the custom objects.

  6. If several environments have been created, you will see a column per environment. You can unselect an environment checkbox, in which case the Global Scripts will not run in it.

  1. Complete the parameters and click Next.

  1. After importing, an execution report will be produced. The first section is for the ERP data source and the one below it is for the Cube data source.

    You can click the button to see the details of each script individually. If no failures are reported, close the window.

  2. If any of the scripts failed to run, a fail icon will be displayed. Click the fail symbol to view the Report Preview window, which shows the respective SQL script.

    Copy this script, debug, and run it separately if needed. Users who are proficient with SQL can debug it straight in the Report Preview window and run it by clicking on the Try to rerun button.

Updating the Template

Important

Some considerations you must take into account before starting:

  • Making fresh backups of both the SEI database and Central Point before doing a template update is highly recommended.
  • Check the SEI data models and custom SQL objects that may have been delivered with the initial template version, as you might lose these customizations upon updating.
  • You must have a template version that matches the software version installed.

When performing an upgrade of the SEI software, it will only update the software and not the template. In other words, the existing SEI data models and views will be affected.

After a software upgrade, it is not mandatory to perform a template update. A template update is useful if you have encountered problems with specific SEI data models or SEI custom SQL objects as it includes fixes.

To update a template:

  1. After having mapped the data sources, select the check boxes of the objects you want to upgrade and click Next.

    By default, no option in the Update column will be selected. If there is a new data models or view, the Add option will be selected. Select Skip if you want to ignore it.

    Important

    If you select the Update option, it will overwrite existing SEI objects associated with that data model or those connected to other objects (dependencies). Please note that any customizations will also be lost.

  1. Select the environment in which the scripts will be executed and click Next.
  2. Complete the parameters and click Next.
  3. In the Execution Report window, If any of the scripts failed to run, a fail icon will be displayed. Click the fail symbol to view the Report Preview window, which shows the respective SQL script.

  4. Copy this script, debug, and run it separately if needed. Users who are proficient with SQL can debug it straight in the Report Preview window and run it by clicking on the Try to rerun button.


Important

Web Browsers have updated their policy regarding Cookies and these changes must be applied to your Web Server if you want SEI embedded into your ERP website, or use Single Sign-On (SSO). Refer to Cookie Management for more details.