Sage X3

Introduction

The Templates installation provides you with a ready-to-use set of Views, Dashboards and Reports.

The installation (assuming the Central Point is freshly installed and empty), will consist of two steps:

• Configuring the Data Sources for the ERP and Data Warehouse (optional) databases.
• Importing the Templates into the Central Point.

There may be other steps including building and loading the OLAP Cubes.

Data Source Configuration

Environments and Data Sources

The following information is needed to configure the Data Sources:

• Database server credentials: Server name, Instance, Authentication strategy.
• Main ERP database information: Database and schema name.

ERP Data Source

1. In the upper-right hand corner, click on the to access the Administration section.
   
2. On the left pane, select Env. & Data Sources.
3. By default, there is already an environment called Production, which you can rename by double-clicking in the name box. Once changed, press the Enter key.
   
4. In the Data Sources section, click on Add to create the first Data Source.
   
5. Complete the ERP Data Source configuration. See instructions for MS SQL Server and Oracle below.

Microsoft SQL Server

Oracle instructions follow

Datasource description:

Sage X3 Data Source

Type:

SQLSERVER

Server:

Database server of Sage X3

Database name:

Name of the Sage X3 database (beware of the case sensitivity)

Database schema name:

Create the two following entries by clicking on the icon (replace DatabaseName by the appropriate value):

DatabaseName.FOLDER (replace FOLDER by the folder name)

DatabaseName.NEC_FOLDER (replace FOLDER by the folder name)

Note

This second line contains the Nectari Custom Schema.

You can use a different one, but we highly recommend following this naming convention:

• Start with NEC
• Use all capitals
• Separate words by an underscore

Important

Choose a unique Custom Schema name for each Environment.

Nectari schema:

Enter the chosen Nectari custom schema for the current environment

Authentication stategy:

UseSpecific

User Name:

SQL User accessing the Sage X3 database. For example, sa.

Password:

The user's password.

6. Click on Validate then on Save to complete the configuration of the Data Source.

For Oracle Database

Datasource description:

Sage X3 Data Source

Type:

ORACLE

Server:

Name of the Oracle server

SID and Port:

SID and Port of the Sage X3 database instance

Database schema name:

Create 2 entries by clicking on the + icon:

FOLDER (replace FOLDER by the folder name)

NEC_FOLDER (replace FOLDER by the folder name)

Nectari schema:

Enter the chosen Nectari custom schema for the current environment.

Authentication stategy:

UseSpecific

User Name:

For example: system.

Password:

Password of the user.

• Click on Validate then on Save to complete the configuration of the Data Source.

Cube Data Source

In the same Environment as the ERP Data Source, create a new Data Source for the OLAP Cube.

Complete the Data Source Definition with all the appropriate information.

Microsoft SQL Server

Oracle instructions follow

The screenshot below provides an example of this.

Server:

Database server where the Nectari OLAP For SQL Server package is installed.

Database name:

NectariCube.

Database schema name:

NectariCube.NEC_FOLDER (replace FOLDER by the folder name).

Where NEC_FOLDER (replace FOLDER by the folder name) is the schema used in the ERP Database of the same environment.

Nectari schema:

Enter the chosen custom schema for the current environment

• Click on Validate then on Save.
• Click on Set as Data Warehouse to define the Data Source as a Data Warehouse then enter the following information:

Database warehouse schema:

Enter the chosen Nectari custom schema again.

Use MARS during the cube loading:

Unchecked

• Click on Validate then on Save.

For Oracle Database

Server:

Name of the database server where the Central Point is installed

SID and Port:

SID and Port of the Oracle database instance

Pooling:

Activating this option will improve performance (Refer to Environments and Data Sources for more details).

Database schema name:

NEC_FOLDER (replace FOLDER by the folder name)

Where NEC_FOLDER (replace FOLDER by the folder name) is the custom schema used in the ERP database of the same environment

Nectari schema:

Enter the chosen Nectari custom schema for the current environment.

Database warehouse schema:

After saving the data source and set it as a data warehouse, enter the chosen Nectari custom schema for the current environment.

• Click on Validate then on Save to complete the configuration of the Data Source.

Importing Templates

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

• ERP Database Name
• Nectari Custom Schema
• ERP Schema
  Note

  If you want to manage the Budget in Nectari, you can attach up to 10 budgets in the Finance Cube. Budget Number will be equal to the Budget Code, its corresponding version will be Budget Number Version.

Download the Template file: TPL_9.5.XXX_SageX3.zip.

The X represents the build number of the template (use the highest available).

Running the Import Template

1. In the upper-right hand corner, click on the to access the Administration section.
   
2. In the Administration section, click on the Templates drop-down menu in the left pane.
3. Select Import Template.
4. Choose the specific location where the new templates will be installed and click on Next.
   
   Note

   Usually, the Root folder is used.

5. In the Import Template window, click on Select files....
   
6. Find the folder where you saved the Template.zip file in order to select it then click on Open.
7. 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)
• In the Received Data Sources Description column, ensure that only the Data Sources checkboxes you want to use from the template are ticked off.
• In the Current Data Sources Description column, click on Bind a Data Source to access the drop-down list containing the existing Data Sources and click on Next.
  

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, Update or Skip during the installation.
  Note

  In the case of an update, you can refer to Updating template for more details.

1. Click on Next (this can take time).
   

2. Once this has been completed, a window will be prompted to input the necessary parameters to create the custom objects.
3. If more than one Environment have been created, you will see a column per Environment. You can untick an Environment checkbox, in which case the Global Scripts will not run in it.

4. Complete the parameters, see examples below, and click on Next.
   

SQL Server

5. After importing, an Execution Report will be produced, as shown below.
   Note

   The first section is for the ERP Data Source and the one below it is for the Cube Data Source.

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

6. If any of the scripts failed to run, a fail icon will be displayed. Click on 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 template

When performing an upgrade of the Nectari software, it will only update the software and not the template. In other words, the existing Nectari Data Models and Views won't be affected.

To update a template:

1. After having mapped the Data sources, tick the checkboxes of the objects you want to upgrade and click on Next.
   
   Note

   By default, no checkbox in the Update column will be ticked. If there is a new Data Model / View the Add checkbox will be ticked. Select Skip if you want to ignore it.

   Important

   If you tick the Update checkbox, it will overwrite the existing Nectari objects associated with that Data Model or connected to the others (dependencies). Please note that if any customizations have been done, they will be lost.

2. Select the environment in which the scripts will be executed and click on Next.
3. Complete the parameters and click on Next.
4. In the Execution report window, If any of the scripts failed to run, a fail icon will be displayed. Click on the fail symbol to view the Report Preview window, which shows the respective SQL script.
5. 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.
   

Building and Loading the OLAP Cubes

To create the Cubes database structure in the NectariCube database previously installed, you need to Build the Cube.

1. In the upper right-hand corner, click on the to access the Administration section.
   
2. In the left pane, click on OLAP Manager.
3. In the right pane, click on Manage.
   
4. In the left section, select all the Cubes to build by ticking the checkbox next to the Description column.
5. In the Manage window, select Build in the Action drop-down list then the environment(s) and click Confirm.
   
6. In the Confirmation window, tick the checkbox and click on Yes.
   
7. If errors occur refer to Logs to activate the logging feature.

Now that the Cubes are built, you can now populate them.

1. In the right pane, click on Manage.
2. In the left section, select all the Cubes to load by ticking the checkbox next to the Description column.
3. In the Manage window, select Load All in the Action drop-down list then the environment(s) and click Confirm.
   
4. In the Confirmation window, tick the checkbox and click on Yes.
   

The template installation is now complete.

Regular data refresh jobs for the Cubes can now be scheduled. For more details on how to do this, refer to Scheduler.

,
                security:{
                "http": {
                        // HTTP headers added
                        "headers": {
                                "content-security-policy": {
                                         "child-src": [
                                                "'self'",
                                                "https://biprod.yourcompany.com:444","https://bidev.yourcompany.com:444"
                                         ]
                                },
                        }
                },
                "client": {
                        "iframe": {
                                "sandbox": {
                                        // The html vignettes allow 3 levels of security ('low', 'medium' and 'high') for sandboxing iframes
                                        "low": "allow-same-origin allow-forms allow-scripts allow-downloads allow-popups",
                                        "medium": "allow-same-origin allow-forms allow-scripts allow-downloads allow-popups",
                                        "high": "allow-same-origin allow-forms allow-scripts allow-downloads allow-popups"
                                }
                        }
                }
        }

	USE [x3]
	GO
		EXEC	[NEC_SEED].[ZREFCNVRATES] 'USD'

	BEGIN
		NEC_SEED.ZREFCNVRATES('USD');
	END;
		

USE [x3]
GO
	EXEC	[NEC_SEED].[ZREFCNVRATES] 'USD'

	BEGIN
		CUSTOM_SCHEMA.ZREFCNVRATES ('USD');
	END;