Category: IT Configuration

2.2 Prerequisites

It is key prior starting the setup that the target network is well known and defined. All required files for data upload should be prepared and ready before starting the setup. It is highly recommended to prepare the following data for each instance that would be created:

• • Instance type: to choose among HQ, Coordination, Project or SYNC_SERVER
  • Instance code: the code that would be used for identifying the instance through synchronization
  • Parent instance: code of the parent; for HQ=none / for Coordination=HQ / for Project=Coordination
  • Proprietary Instance Code and Name: The proprietary instance is unique per instance and is used for tagging certain objects that are sent to other instances through synchronization. It is recommended to use for Proprietary instance code the same code as the Instance Code.
    Example: We create a bank register at project level. This bank register is tagged in automatic with the project’s proprietary instance code. Once synchronized to coordination, the project’s bank register keeps its original proprietary instance code.
  <li

>Mission: (Only for Coordinations and Projects): Name of the mission. This name will also be used as group name in the Synchronization Server.

• Account Move Prefix: Used for accounting purposes, should be unique per instance. For tests purposes, you may choose any alphanumeric value.
• Reconciliation Prefix: Used for accounting purposes, should be unique per instance. For tests purposes, you may choose any alphanumeric value.
  For each Coordination instance, it is also necessary to define which cost centres should be linked to the instance. This list is automatically replicated in all the project instances belonging to the same mission.
  For each Coordination and Project instance,

   

  • One or several Target cost centres that are used for sync purposes; in case of a coordination one must select the top cost centre representing the mission (eg HT1), the coordination cost centre (eg HT101) and any other cost centre managed from coordination like Eprep or Explo (eg HT190). A cost centre can be set as “Target” in one and only one proprietary instance.
  • The Top cost centre that will be used for budget consolidation.
  • The cost centre that will be used in all PO/FO identification (eg HT101). System uses this parameter as a reference in all PO/FO codes. It is a key reference on the supply side that could be used for international orders billing (from Supply Centre to HQ).

  This manual references several .CSV files used in various instances to setup either your instance (Production or Sandbox). Please refer to the Annexes section to find these files represented by this icon throughout this manual.

</li

2.1 Introduction

This chapter will guide you on the set-up of a local installation for a UniField environment.
If you are seeting up Porduction instances please skip the sections/steps with this icon as it only concerns Sandbox environment.
It is assumed that a full UniField AIO installation has already been done on the target PCs (as per chapter 1 – Installation).
A full local installation consists of the following:

• a HQ instance
• One or several Coordination instances
• One or several Project instances
• a SYNC_SERVER