Scheduling Revenue Management Processes to Run Automatically

You can schedule the following Revenue Management processes to run automatically at regular intervals:

Process

Scheduled Job Name

Description

More Information
Deferred Revenue True-Up Deferred Revenue True-Up

Runs deferred revenue true-up for all eligible source records. Whether the resulting true-up transactions are created as "In Progress" or "Committed" is determined by the Scheduled True-Up Creates Committed RRTs field in the Revenue Management Batch Settings.

Note:

By default this job processes all source records linked to valid recognition settings regardless of whether they are set to Include in True-Up, and creates a log line for each source record. If you want the job to process only source records that are set to Include in True-Up, select the Run True-Up All on Included Records Only field in the Revenue Management Batch Settings.

 Deferred Revenue True-Up
Generate Recognition Schedules Generate Recognition Schedules Generates recognition schedules for all source records linked to valid recognition settings. This process creates recognition schedules for a source record if they do not already exist. If recognition schedules already exist for a source record, this process updates them to reflect any changes to the source record. About Recognition Schedules

To schedule either of these processes:

  1. On the Foundations Setup tab, click Scheduled Jobs.
  2. Find the process you want to schedule in the list of jobs.
  3. Click Pencil icon to configure when the process runs. When you have made your changes, click Apply Changes.
  4. Select the Scheduled checkbox for the process you have configured.
  5. Click Save.

For more detailed instructions about how to configure scheduled jobs, see Configuring a Scheduled Job.

You are notified by email each time these scheduled jobs complete. You can access log information from the process run records created by both jobs.

Note:

The scheduled job will not start if it clashes with a process that is already running. For example, this can happen if a user starts the same process manually. You will then be notified by email that the scheduled job did not run.