Datasources

A datasource can be any storage device for data such as a database in on-premise deployments (OP). The application allows the archiving of data in the mode SCHEMA. This mode is the core database to another schema in the same database.

Single-tenant (ST) deployments are granted specific pre-configured, Infor deployed datasources.

Handling Special Policies

Payroll Archive

Since timesheets provide the option of creating default records, this option produces a problem when you try to retrieve data for archived dates outside of ARCHIVE_VIEW_MODE.

Therefore, the customized payroll data archive updates the EMP_UDF_DATA called LAST_ARCHIVE_PAYROLL_DATA_DATE with the last successful archive aging date (format:MM/DD/YYYY) for each employee. Any archive process that fails to update this empUdfData correctly fails since this update is a crucial update for employee's profile.

Whenever timesheets bring the employee's timesheet data prior to this date, the Default Record Engine does not create any default records. You can look at the employee profile and see that dates prior to LAST_ARCHIVE_PAYROLL_DATA_DATE are only available in archive mode. The StartOfDay task behaves in the same manner.

Configuring an Archive Data Source - On-premise deployments only

The Archive schema is included as a part of the core application. Because of this change, you must configure an archive data source, via the Administrative Console.

One archive data source is required for each instance of the application you plan to deploy. You should use the same JDBC provider created when configuring a JDBC provider and data source for the Application Server.

Custom tables in ST deployments

Custom table archiving is your responsibility in a ST environment.