Appendix E :Configuration at Company Level

E.1 Introduction

OFSLL supports defining multiple Portfolio Companies in an Organization and facilitates to configure these Portfolio Companies to operate in different time zones. The nightly batch jobs for processing can also be configured to run as per the operating hours of the Portfolio Companies.

Using this, system can be configured in Setup to either process at Organization level or at Company level. To process at Organization level, no specific change is required since it is the default setup.

The below details in this section is intended to give an overview of the changes required to setup the system to process at Company level.

E.2 Existing Configuration

In the default setup, there is no definition of GL date at company level and this implies that organization can define the independent companies to which accounts belongs. But the EOD scheduling and job run happens at organization level and ‘not’ at each company level. Also the GL date is defined at 'System Parameters' Level.

E.3 Configuration at Company Level

In the configuration at Company level (not Branch level), the following options are supported:

However in this setup, note that:

E.4 Setup Company Definition

In this setup, define the company and company parameters.

  1. Define Company and date format
    • Define the company in 'Companies Definition' screen and ensure to maintain 'Company Time Zone'.
    • Define company code with 'Alphanumeric' characters only.
    • Ensure to define the 'Display Format' organization Definition ' Division Definition ' Display Formats.

Note

Fixed simple date format definition is one time setup for each company and Admin user is not expected to change it again in life time. Currently it is allowed to select only MM/DD/YYYY format.

  1. Define the following company parameters:

The default shipped seed data of Company level GL date is set to All.

    • GL POST DATE - COMPANY IN MM/DD/YYYY FORMAT (UPDATED BY SCHEDULER IF ENABLED)
    • CMN_SYSTEM_UNDER_MAINTENANCE - SYSTEM UNDER MAINTENANCE
    • JSC_START_OF_BUSINESS_TIME (COMPANY START OF BUSINESS TIME (24HR FORMAT)
    • PTX_TXN_LAST_PURGE_DT - LAST PURGE DATE OF TXNS
    • PUP_TUP_LAST_PURGE_DT - LAST PURGE DATE OF TXNS UPLOAD

Example: The following is an illustration on how 3 companies are defined with 3 different time Zones in USA, UK and Australia.

Parameter

USA

UK

AUS

GL Post Date

31 Dec 2019

02 Jan 2020

02 Jan 2020

CMN_SYSTEM_UNDER_MAINTENANCE

Y

N

N

JSC_START_OF_BUSINESS_TIME

0500

0500

0500

PTX_TXN_LAST_PURGE_DT

01/01/2019

01/01/2019

01/01/2019

PUP_TUP_LAST_PURGE_DT

01/01/2019

01/01/2019

01/01/2019

E.4.1 Holiday Setup and Processing

The holiday defined in setup is processed as indicated below:

E.4.2 Batch Jobs Processing

The default shipped seed data of Batch Jobs is set to All. Define the company and copy the batch jobs. Note that the ‘Copy’ option copies all the batch jobs at one go.

E.5 Setup Multiple Companies in Same/Different Time Zone

As part of creating company, following are automated:

E.5.1 Setup for New Company Added Subsequently

For New Company Added Subsequently (not on Day zero), follow the same steps to be followed on Day zero setup. Raise SR to execute script of directory creation of new company for file upload.

E.6 Impact on Defining Configuration at Company Level

System displays the following details at each configured Company level.

E.6.1 Company Level Configuration Settings

Company level LOV selection is available at following screens to configure:

E.6.2 Scheduler

Once the batch jobs are completed for that specific company, scheduler picks-up the company specific scheduled batch jobs and updates the GL Post Date of that specific company.

Note

E.6.3 Debug Logs

E.6.4 Setup Screens

All setup screens refers to system date for validation. Example: Start and End Date.

E.6.5 File Uploads

If only ALL Company Definition is used, the file upload process continues to use the existing folder and infrastructure.

E.6.5.1 Input File

E.6.5.2 Output File

Output file name is appended with ‘Company Name’ and is generated in one folder.

Note

A script ‘crt_company_directories.sh’ is provided with installer in the path ‘core_db\ofslldb.zip\dba_utils\’ to create directories and to create folders for each defined Company. The same is to be run during installation. The same is to be run during installa­tion. Also, the CLOB indicator is retained at system parameter level.

E.6.6 Transactions

E.6.7 Web Services

E.6.8 Letters, Correspondence

E.6.9 Reports

E.6.10 Credit Bureau & Metro II

E.6.11 GL

Current GL Setup (Attributes, Translations and Transaction Links and so on) is at Company level and hence there is no impact.

E.6.12 ODD1, ODD2, ODD3

If job is run at company level,

E.6.13 Migration

For all screens where company has been added, the default value ALL is provided and user is expected to enable this in seed data screen.

E.6.14 Conversion

No specific impact since API tables have definition of company. User can upload the conversion files based on company.

E.6.15 Archive

Parameter to specify the archive days are defined at system level but user can run the Archive batch jobs at each company level and the same archives data for that specific company.

E.6.16 Purge

Parameter to specify the purge days and following parameters are moved to company level.

E.6.17 Standard Payees

E.6.18 Data Masking

Not handled and hence data masking can be configured at organization level only.

E.6.19 WFP Module

Not handled.

E.6.20 Batch Jobs and File uploads

For list of batch jobs and File uploads handled to run at company level, refer to product release notes.

E.6.21 Assumptions

System considers the criteria defined for company in Queues > Criteria Based Condition screen and ignores the branch level differentiation across application. Hence, even if user defines multiple records (as indicated below), system considers the combination as same and executes records are company level.

Company = AUS and Branch = ALL

Company = AUS and Branch = Sydney