Initial Setup

This section contains the list of steps to follow to Setup a NEW OMNI Instance. This assumes that a new server has already been created on the cloud and all networking related functions implemented.

System Setup

• In case of LIVE Servers - change the UserUploads directory to point to an S3 Bucket created especially for the Customer.
  • To do this create the S3 Bucket using Admin -> File Management to modify the User Uploads Directory to point to the S3 Bucket created.

DB Configuration

In order to execute the statements - DIRECT access to the database server is required - and should be performed by users with the skill to execute DB queries directly.

1. Execute the following SQL Statements:
   1. exec omni_spADMINResetOMNIDatabase
   2. delete from omni_approval_job_based
   3. delete from omni_scope_milestones
   4. exec omni_spADMINResetOMNIDatabase (ONCE MORE - to ensure that the foreign keys are setup correctly)
      1. Verify that FKs are enabled - if not troubleshoot the reason and resolve it before proceeding further.
   5. Delete all companies except the company with the company_id 1
      • You may have to execute the query :
        • delete from omni_user_companies where company_id != 1
   6. Modify the Company with the company_id 1 with the details of the company.
      1. Add other companies if required
2. Execute the following statements to clear the Event Logs
   • delete from dnn_EventLog
   • delete from dnn_Exceptions
3. Execute SQL statement : delete from omni_material_usage_master where material_usage_id != 1
4. Modify the Accounting Centre
   1. Generally make the accounting centre correspond to the company created.
   2. If there are multiple companies - make multiple accounting centres.
   3. To modify the name of the main accounting centre use SSMS on the database directly.
   4. Create a Party for the account centre - execute the following query:
      • insert into omni_party_master(party_type_id,party_root_id,party_code) select 10,account_centre_id,account_centre_code from omni_account_centre_master
5. Make at least one Business Unit. You may upload the WBS before this if you wish the BU to be made automatically.
6. Make the Head Office Job.
7. Make the Trading Job
8. Modify omni_system_configuration table (System Configuration Keys in Setup):
   1. Modify the value of the key : payroll.bookexpenses_tojobcode - to the head office job.
   2. Modify the value of the key : scm.collatemrtojobcode - to the head office job.
   3. Modify the value of the key : crm.tradingjobcode- to the Trading Job
9. Delete the Ledgers in the table omni_account_ledger that are setup as Test Bank or Test Cash Ledgers.
10. Copy the Job Based Approvals into the table - omni_approval_job_based.
    • Execute the query:

insert into omni_approval_job_based(user_id,job_id,role_id)

select

Users.UserID,

jm.job_id, ar.role_id

from omni_approval_document_type adt

inner join omni_approval_rule ar on ar.approval_document_type_id = adt.document_type_id

inner join omni_job_master jm on jm.job_code = '<HEADOFFICEJOBCODE>'

inner join Users on Username = 'portaluser'

where is_job_based = 1

• Replace <HEADOFFICEJOBCODE> with the job code of the head office job created earlier.
• This query creates the starting permissions for approving all job related documents (MR, WR etc.) for the HEAD office job - and gives them to the Portal Administrator User.
• If you want to do this for all created jobs - simply execute this query for the user that you want to give the permission to.

Load the Master Data

1. Upload the WBS Template (Use attached for a sample).
   1. By default every package in the upload creates a new Business Unit - If you don't want that, proceed with the upload as normal then run a query to update the Business units in the Parent Packages created to an existing Business Unit. Then delete the Business Units created automatically by the upload.
2. Upload the Material Master (See attached for sample).
   • Remove existing material usage except 1
     • delete from omni_material_usage_master where material_usage_id != 1
3. Upload the Vendor Master (see attached for sample)
   1. Ensure that the Vendor Type in the upload file already exists in the Vendor Type Master (column vendor_type)

Recording of a Server Setup