Job schedules

The Job Schedules page lets you create, organize, and run jobs in Financial Consolidation. You can group jobs into Processes — a powerful way to run multiple jobs in a defined order, with built-in rules for handling errors and retries.

The Job Schedules page has two clearly separated sections: Standalone and Processes .

• A Standalone Job is a job that runs independently, on its own schedule, without being part of a Process.

• A Process is a container for one or more jobs that run in a defined sequence.

• Action buttons and a search field appear at the top of the page.

• The search field filters results across both the Standalone Jobs and Processes sections in real time as you type.

• Hovering over any job or process displays a Delete icon. A confirmation prompt appears before any deletion is completed.

• Deleting a process also removes all jobs inside it.

• When a section contains more than 10 jobs, a scroll bar is provided for easier navigation.

  Note:  You can run jobs that were defined in Data Integration in Financial Consolidation. See details.

Add a Standalone Job

A Standalone Job is a job that runs independently, without being part of a Process.

  Note:  All jobs created before release 2026.2.0 are automatically treated as Standalone Jobs.

To add a standalone job:

1. Click New Job at the top of the page.

   

2. Select Add Standalone Job.

   Standalone jobs have the following tabs:

   

   • Details

   • Schedule

   • Jobs

3. Complete the job information and save.

     Note:  The Job Type you select determines the information displayed for you to fill out.

Details tab

The Details tab is where you enter the job information.

  Note:  The layout of the Details tab depends on the Job Type selected.

Schedule tab

The Schedule tab lets you set when and how often a standalone job runs. You can also configure email notifications for job executions.

To schedule a job:

1. Select the job you want to schedule from the left panel.

2. Choose one of the following scheduling options:

   • Repeat — Runs the job at a set interval (hours, minutes, or seconds) on specific days, weeks, or months.

   • Interval — Runs the job at a set interval (hours, minutes, or seconds) with no day, week, or month restrictions.

   • Fixed — Runs the job once at a specific date and time.

3. If needed, set an Execution Period by entering the start (Period) and end (To) dates and times to define how long the schedule is active.

4. For email notifications, in Send Email Notification choose when and who receives notifications:

   • In case of failure: The notification includes the process name, the name of the job where the error occurred, and the error message.

   • In case of success: The notification includes the process name in addition to the standard success message.

5. Click to apply the schedule.

Jobs tab

The Jobs tab displays the execution history and current status of a scheduled job. Select a job from the left panel to view its details.

• Status — Shows whether the job completed successfully (Done) or encountered a problem (Error). Use the Status drop-down to filter the list by status.

    Tip:

  Use these visual indicators in the last column to determine the job status:

  • - indicates errors while running the job. Click on the icon to see the error details.

  • - indicates warnings on the job. Click on the icon to see the warning details.

• Action — Shows whether the job has already run or is still pending. Use the Action drop-down to filter the list by action.

• Process Name — Not applicable to standalone jobs.

• Scheduled Date — The date and time the job was scheduled to run. Use the Scheduled drop-down to filter by date range.

• Started Date — The date and time the job began running.

• Ended Date — The date and time the job finished.

  Tip:  If a job run produced an error or warning, an icon appears at the end of that row. Click the icon to view the details.

Create a Process

A Process is an organized container for one or more jobs that run in a defined sequence. Use it to run multiple jobs in a defined order, with built-in rules for handling errors and retries.

To create a process:

1. Click at the top of the page.

2. Enter the process Name and Description.

3. Set the Active status.

4. Click . The Details tab is displayed.

5. In the Details tab, you have the option to edit the basic information of the process: process name, description, and active status. Process names must be unique. An error message appears if a duplicate name is used.

     Note:  The button is available when the process and at least one of its jobs are active.

6. In the Schedule tab, define when the process runs and configure email notifications. See Schedule tab.

7. Save the new process.

8. Proceed to add jobs to the process.

Add multiple jobs to a Process

Before proceeding, ensure that a process exists for you to add or assign jobs.

To add a job to a process:

1. Click New Job at the top of the page.

2. Select Add Job to Process.

3. Enter required information in the following tabs:

   

   • Details
     • Enter the job code and type,
     • Enter a description,
     • Select a process,
     • Select active status. Inactive jobs are skipped when the process runs.

   • Execution Rules — This tab replaces the Schedule tab for jobs that belong to a process. Configure the following:

     • Dependencies: Define whether the job runs at the start of the process or after a specific job completes. Circular dependencies are automatically excluded from the available options.

     • Run Conditions: Choose to run the job only after the previous job succeeds, or to ignore errors and run regardless.

     • Enable automatic Retries (optional): Enable retries and set the number of attempts and the delay between each retry (in seconds).

4. Save the process.

     Note:  After a job is saved to a process, its assigned process cannot be changed directly. Use to reassign it. See Copy or Move Job.

Copy or Move a Job

The feature lets you duplicate or reassign a job to a different location — either to an existing process or to Standalone Jobs.

To copy or move a job:

1. Click .

   

2. Select the job to copy or move. If the job belongs to a process, the process name is displayed for reference.

3. Select the target location: an existing Process or Standalone Jobs.

4. Choose Copy or Move. The default selection is Copy job (keep original). If you want to move the job, clear the default selection to enable the button

   • Copy: The original job is kept unchanged. You are redirected to the new job with the Job Name field empty so you can assign a unique name.

   • Move: The job is relocated. You are redirected to the job in its new location.

Delete a Job or Process

• Hover over any job or process to reveal a Delete icon with a confirmation prompt before any deletion is performed.

• Deleting a process will also remove all jobs inside it.

  

Job Types

Use the Job drop-down to select a job type when creating or scheduling a job. The fields on the Details tab change based on the job type you select.

The following table describes each available job type:

Job type	What it does
Backup	Creates a backup of selected consolidation periods on a recurring schedule.
Restore	Restores consolidation periods from a backup file or URL.
Cleanup	Removes old files, logs, and temporary data to keep the system running efficiently.
SysIndexRebuild	Automatically rebuilds database indexes weekly to maintain system performance. Enabled by default.
Index Rebuild	Rebuilds database indexes on demand, targeting specific tables as needed.
System Logs	Automatically emails system logs to selected users.
Export cube	Synchronizes the database with an OLAP cube.
Data Integration	Runs jobs defined in Data Integration (DI Studio).
Validation report	Runs validation reports for all companies at the same time.
Import adjustment data	Loads adjustment data from Prophix Staging into the application using Data Integration.
Export to reporting solutions	Transfers consolidated data to reporting solutions.
Export for external applications	Enables customers to access and process data stored in the Consolidation database within their own applications.

Job activation and trigger options

You have these common options to trigger the job:

• Active — Select this option to activate and run the job immediately using the default Fixed Time schedule.

• To run the job on a custom schedule instead, leave the Active option clear and save the job first. Then open the Job Schedule tab to define when the job should run. The job will not execute until it is activated.

• Run Now — Executes the job immediately without changing its existing schedule. Use this option when a job has a defined schedule but needs to run manually outside of it. This option is available only when the job/process is Active.

Backup job

Use this job to create backups of selected consolidation periods on a recurring schedule. You can password-protect backups and set an expiry date to control who can restore them and when.

To configure a Backup job:

• Code — Enter a unique code for the job.

• Description — Enter a description of the job’s purpose.

• Backup Type — Select the scope of the backup, for example, all periods or open periods only.

• Periods — Select the consolidation periods to include. Use the checkbox in the table header to select all periods. Use the toggle switch to filter the view:

  • Click once to show only selected periods.

  • Click again to show only unselected periods.

  • Click a third time to show all periods.

• Password — Enter a password to prevent unauthorized restores.

• Expiration Date — Set the last date on which the backup file can be restored.

• Custom filename — Enter a descriptive name for the backup file.

• Available for download — Select this option to let other users download the backup file.

Run the job as desired. See Job activation and trigger options.

Restore job

Use this job to restore consolidation periods from an existing backup. You can restore from a file stored in the system or from a backup located at a URL.

Restore from a file

• Job Type — Select Restore.

• Code — Enter a unique code for the job.

• Description — Enter a description of the job’s purpose.

• Restore Method — Select From File.

• File — Select the backup file to restore. The Name and Description fields populate automatically.

• Periods — Select the periods to restore. Use the Overwrite column to overwrite existing consolidation periods. Use the checkbox in the table header to select all periods. Use the toggle switch to filter the view:

  • Click once to show only selected periods.

  • Click again to show only unselected periods.

  • Click a third time to show all periods.

Run the job as desired. See Job activation and trigger options.

Restore from a URL using an API key

• Job Type — Select Restore.

• Code — Enter a unique code for the job.

• Description — Enter a description of the job’s purpose.

• Restore Method — Select From URL.

• URL — Enter the URL where the backup is located.

• User — Leave this field blank.

• URL Password — Enter the API key provided by your administrator.

• Click the load button to retrieve the file. Enter the Password used when the backup was created. The Name and Description fields populate automatically.

• Periods — Select the periods to restore. Use the toggle switch to filter the view as described above.

Run the job as desired. See Job activation and trigger options.

Cleanup job

• Use this job to remove old data from the system, such as imported files, backups, temporary sessions, and log entries. It is recommended to run this job at least once per day.

• Code — Enter a unique code for the job.

• Description — Enter a description of the job’s purpose.

• Delete imported data / Excel bundles older than — Number of days to keep uploaded bundle files in the history before cleanup. If unsure, set to 31.

• Delete files older than (in days) — Number of days to keep period backups, report batches, and other generated files before cleanup. If unsure, set to 365 for period backups, and 30 for report batches and other files.

• Delete temporary data sessions (in hours) — Number of hours to keep temporary database sessions. If unsure, set unfinished sessions to 24 hours and completed sessions to 2 hours.

• Delete database entries generated since more than — Configure retention for the following:

  • Modification log — Number of days to keep system log entries. If unsure, set to 365.

  • Jobs — Number of days to keep job overview entries. If unsure, set to 365.

  • Concurrency detection — Number of hours to keep multi-user concurrency detection entries. If unsure, set to 6.

• Delete HUB entries generated since more than (in days) — Number of days to keep HUB database entries. If unsure, set to 31.

Run the job as desired. See Job activation and trigger options.

SysIndexRebuild and Index Rebuild jobs

These jobs rebuild database indexes to resolve performance issues, particularly when data imports stall.

• SysIndexRebuild — A system-managed job that is enabled by default. It runs automatically every Saturday at 11:59 PM.

• Index Rebuild — A user-initiated job that lets you rebuild indexes on demand. You can target specific tables as needed.

System Logs job

Use this job to automatically email system logs to designated users.

• Code — Enter a unique code for the job.

• Description — Enter a description of the job’s purpose.

• Users — Select the users who should receive the system logs by email.

Run the job as desired. See Job activation and trigger options.

Export cube job

Use this job to synchronize the database with an OLAP cube. Run this job whenever you need cube data to reflect recent consolidation changes.

• Code — Enter a unique code for the job.

• Description — Enter a description of the job’s purpose.

• Include Dimensions — Select to include dimensions in the export.

• Include Closed Periods — Select to include closed periods in the export.

• Cube Definitions — Select a cube definition created under the Transfer menu.

Run the job as desired. See Job activation and trigger options.

Data Integration job

Use this job to run jobs that were defined in Data Integration (DI Studio). This job type connects Financial Consolidation scheduling to your existing DI Studio workflows.

• Code — Enter a unique code for the job.

• Description — Enter a description of the job’s purpose.

• Data Integration Jobs — Select the DI Studio job you want to run.

Run the job as desired. See Job activation and trigger options.

Validation report job

Use this job to run validation reports for all companies at the same time. This is useful when you need a consistent snapshot of validation results across companies for a given period.

• Code — Enter a unique code for the job.

• Description — Enter a description of the job’s purpose.

• Current and Ref. Periods — The current period is selected by default. Click to select a different period.

• Company — Displays the companies you are authorized to access for the selected period.

• Validation report — Select the validation report to generate from the list of available reports for the selected period.

• Journal view — Defaults to CONSO. Click to select a different journal view.

Run the job as desired. See Job activation and trigger options.

Export to reporting solutions job

Refer to Move consolidated data to reporting solutions for details.

Export for external applications job

Refer to Export data for external applications for details.

Import adjustment data job

Use this job to load adjustment data from Prophix Staging into the application using Data Integration. After the job runs, imported data packages are available in Transfers > HUB > Authorization, where you can accept or reject them.

• Code — Enter a unique code for the job.

• Description — Enter a description of the job’s purpose.

• Source — Select Prophix Staging.

• Overwrite Option — Select one of the following:

  • Overwrite journals known in file — Overwrites only the adjustments included in the import file.

  • Overwrite journals of period — Overwrites all existing journals for the period.

• Use journal entries from the import file — Uses journal entries from the import file. No new entries are generated.

• Available tables — Select the staging table to import from.

• Package ID prefix — Enter a prefix for the package ID (for example, your initials). The prefix appears before the year and month, making it easy to identify the package after import.

• Split by company — Select to split the package into separate packages per company. The company code is added as a suffix to each Package ID.

Run the job as desired. See Job activation and trigger options.

Import adjustments table structure (Prophix Staging)

The following table structure is required in Prophix Staging for the Import Adjustment Data job:

Column	Data type	Nullable
ConsoCode	nvarchar(12)	NULL
CompanyCode	nvarchar(20)	NULL
JournalType	char(1)	NULL
JournalCategory	nvarchar(3)	NULL
JournalEntry	bigint	NULL
JournalSequence	int	NULL
Account	nvarchar(20)	NULL
PartnerCompanyCode	nvarchar(20)	NULL
Amount	decimal(24, 6)	NULL
Flow	nvarchar(20)	NULL
FlowTransRate	decimal(28, 12)	NULL
FlowTransactionAmount	decimal(24, 6)	NULL
TransRate	decimal(28, 12)	NULL
JournalDescription	nvarchar(max)	NULL
Behaviour	tinyint	NULL
BeforeAfter	bit	NULL
AdjCurrency	char(1)	NULL
AssociatedJournalType	char(1)	NULL
AssociatedJournalCategory	nvarchar(3)	NULL
CurrCode	nvarchar(3)	NULL
TransactionCurrCode	nvarchar(3)	NULL
TransactionAmount	decimal(24, 6)	NULL
DimensionGroup	nvarchar(25)	NULL
Dimension1Detail	nvarchar(25)	NULL
Dimension2Detail	nvarchar(25)	NULL
Dimension3Detail	nvarchar(25)	NULL