Home
Administration
Application Setup
KPI Builder
KPI Builder access.
Run historical reloads
Description of historical reloads of metrics.
Running Historical Loads Efficiently
How to run historical loads efficiently.

Administration
- Application Setup
  - Application Setup Help
  - Access Profiles
    This topic describes how to determine the components that users can access and the types of functions that users can perform.
  - Authentication Upgrade
  - Set up accruals
    Accruals are adjustments for revenues that have been earned but are not yet recorded in the accounts, and expenses that have been incurred but are not yet recorded in the accounts.
  - Activities Setup
  - Attendance configuration sequence
  - Configure Attestation
  - Brazil Device Setup
  - Business Processes Setup
  - Business Structure
  - Calendar Views Setup
  - Common Setup
  - Display preferences
    Display preferences define the information that users see, such as custom URLs and the display format of schedules, labor categories, and timecards.
  - How to Configure Employee Self-Service
  - Employment terms
  - Events and Notifications Configuration Steps
  - Forecaster Setup
  - HCM Profile Setup
  - Integrations Setup
  - KPI Builder
    KPI Builder access.
    - What are Analytics?
      Description of analytics.
    - What is KPI Builder?
      Description of KPI Builder.
    - Auditor Setup
      Description of Auditor setup page.
    - Mapping categories
      Description of mapping categories.
    - Metrics
      Definition and description of metrics.
    - KPIs
      Description of KPIs.
    - Standard mapping categories
      Standard mapping categories.
    - Standard metrics and KPIs
      Definition and description of standard metrics and KPIs.
    - Run historical reloads
      Description of historical reloads of metrics.
      - Run a historical load for one or more metrics
        How to run a historical load for one or more metrics.
      - Running Historical Loads Efficiently
        How to run historical loads efficiently.
  - Leave
  - Pay Policies
    Pay policies are sets of rules that govern how employee hours are interpreted, including rounding of punches, overtime accrual, and holiday credit earnings, as well as the processing of time and attendance information through components like pay codes and work rules.
  - Scheduler Configuration
  - Staffing
  - Statutory reporting
  - System configuration
- Data Import Tool
- Universal Device Manager
- Setup Data Manager
  Setup Data Manager (SDM) uses the system's REST APIs to copy setup data.
- Administer Business Processes
- Mobile App
  A mobile app is available on the iOS App Store for Apple devices and on the Google Play Store for Android devices.
- Communications
- Strategic Workforce Planning
- Extensions
- HCM
  The Human Capital Management (HCM) component provides a comprehensive set of applications for managing all aspects of the employee life cycle — recruitment, benefits, compensation, payroll, HR, and more. Users can configure and personalize configuration of the application for an optimal user experience.

Running Historical Loads Efficiently

How to run historical loads efficiently.

The historical load process is a batch process that will run in the background while the Analytics engine continues to process and compute current data in real time. The historical load process is resource intensive and requesting the load to run for a large number of metrics and/or for long periods of time requires a significant amount of time to complete. The following are guidelines for running a historical load:

Avoid using the “Load All” option to perform a historical load of all metrics. This should not be required except in rare instances. This process may require 12 to 24 hours to complete depending on the defined date range.
Only run historical loads for metrics that are new or have been edited. Edited means that the mapping category related to the metric(s) has been modified or changed..
Run historical loads for smaller periods of time. Break the runs into 3-month windows while still running them for only those metrics that have changed. Allow time after a historical load for the Time Series synchronization process to run. Do not expect the time series data to be updated with the completion of the historical load.
If you have modified metrics related to Scheduling and you want those changes to be reflected for future schedules that have already been created or generated, you can run a historical load for a future time period.
Do not run historical loads as a means to populate time series data. The load will only delay the synchronization process. The Time Series synchronization process runs every 8 hours.