Target breakdowns migration

  • Release version: Xanadu
  • Updated October 15, 2024
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Target breakdowns migration

    This guide explains the process of migrating target breakdowns in ServiceNow using theMigrate BreakdownInterval To Checkinfrequencyscheduled job. The migration updates how frequency and interval data for targets are managed by consolidating Review frequency and Breakdown interval into a new Check-in frequency field and creating or updating target breakdowns accordingly.

    Show full answer Show less

    Key Features

    • Migrate BreakdownInterval To Checkinfrequency job: Migrates existing values from Review frequency and Breakdown interval fields to the Check-in frequency field on target records.
    • Population of Target Breakdown Fields: The job populates Actual to date on the target and Planned target value and Actual fields on the target breakdowns based on current target values.
    • Handling Targets with Breakdown Interval set to None: Check-in frequency is set from the Review frequency. If Review frequency was not None, target breakdowns are created based on that frequency, despite Breakdown interval being None.
    • Handling Targets with Breakdown Interval set to Quarterly or Yearly: Check-in frequency is set from Review frequency, and target breakdowns are created based on that frequency. Yearly breakdown intervals are converted to quarterly breakdowns with linear target value distribution.

    Practical Scenarios and Outcomes

    • None Breakdown Interval Examples: For targets with Review frequency set to options like Yearly, Quarterly, Monthly, Fortnightly, Weekly, or Daily and Breakdown interval set to None, the Check-in frequency is set accordingly. Target breakdowns are created based on the Review frequency except for Fortnightly, which retains the option but does not create breakdowns until manually updated.
    • Example: A target with Monthly review frequency and Breakdown interval None will have 12 monthly breakdowns created after migration. The current actual value is allocated to the matching monthly breakdown, and planned values are distributed accordingly.
    • Quarterly/Yearly Breakdown Interval Examples: For targets with Quarterly or Yearly Breakdown intervals, Check-in frequency is set to Quarterly or Yearly accordingly. Yearly breakdowns convert to quarterly breakdowns with cumulative value distribution.
    • Example: A target with Quarterly review frequency and Yearly breakdown interval will have quarterly breakdowns created with linear distribution of target values. Actual values are populated for each quarter based on existing data.

    Why This Matters

    This migration improves consistency and accuracy in target tracking by consolidating frequency settings and ensuring target breakdowns reflect current values and intervals. It supports ongoing tracking and reporting by creating appropriate breakdown periods and populating actual and planned values automatically.

    ServiceNow administrators should run the scheduled job post-upgrade to align target data with the new model. Owners or contributors can later adjust Check-in frequency to trigger updated breakdown creation if needed.

    As an administrator, when you run the Migrate BreakdownInterval To Checkinfrequency scheduled job, the existing values in the Review frequency and Breakdown interval fields are migrated to the Check-in frequency field in the target records.

    The value in the Actual to date field for the target and values in the Planned target value and Actual fields for the target breakdowns are populated based on the current actual value of the target and values in the existing target breakdowns.

    Target breakdowns migration for targets with breakdown interval set to None

    After running the job, the value in the Check-in frequency field for a target is populated based on the existing value in the Review frequency field of the target. If the existing value in the Review frequency field was set to any option other than None, then target breakdowns will be created for such targets based on the existing review frequency of the target. Even though Breakdown interval was set to None for a target, target breakdowns will be created for the target based on the existing review frequency of the target.

    The following table describes how the check-in frequency value is populated for targets with different values in the Review frequency and Breakdown interval fields.
    Table 1. Target breakdowns migration with breakdown interval set to None
    Review frequency (Before upgrade) Breakdown interval (Before upgrade) Check-in frequency (After upgrading and running the job)
    Yearly None Yearly
    Quarterly None Quarterly
    Monthly None Monthly
    Fortnightly None Fortnightly

    The Fortnightly option is retained and no target breakdowns will be created because the Fortnightly option is no longer supported.

    After the owner or a contributor of the target updates the check-in frequency for the target, the target breakdowns will be created accordingly.
    Weekly None Weekly
    Daily None Daily
    None None None

    In this case, no target breakdowns will be created.
    For example, consider a scenario where details of a target are as follows before upgrade:
    • The base value and target value of the target is 0 and 100, respectively
    • The review frequency is set to Monthly and Breakdown interval was set to None
    • The start date and end date of the target are 2024-01-01 and 2024-12-31, respectively
    • The current actual value of the target is 60 and the current month is August
    In this case, after running the scheduled job 12 monthly target breakdowns are created for the target and the current actual value as 60 is populated in the August monthly breakdown. Also, the planned target value is populated for each breakdown.

    Target breakdowns migration for targets with breakdown interval set to Quarterly or Yearly

    After running the job, the value in the Check-in frequency field for a target is populated based on the existing value in the Review frequency field of the target. Then, target breakdowns are created for the targets based on the existing review frequency of the target.

    The following table describes how the check-in frequency value is populated for targets with different values in the Review frequency and Breakdown interval fields.
    Table 2. Target breakdowns migration with breakdown interval set to Quarterly or Yearly
    Review frequency (Before upgrade) Breakdown interval (Before upgrade) Check-in frequency (After upgrading and running the job)
    Quarterly Quarterly Quarterly
    Quarterly Yearly Quarterly
    Note:
    For targets with breakdowns interval set to Yearly, irrespective of the target is of type cumulative or non-cumulative, after running the scheduled job quarterly target breakdowns will be created and the Target value distribution is set to Spread linearly across the time period (cumulative) for the target.
    For example, consider a scenario where details of a target are as follows before upgrade:
    • The base value and target value of the target is 0 and 80, respectively
    • The review frequency is set to Quarterly and Breakdown interval was set to Yearly
    • The start date and end date of the target are 2023-01-01 and 2024-12-31, respectively
    • The target is of type non-cumulative
    • The actual value achieved in each quarter is 10 starting from Q1-2023 till Q2-2024
    • The current total actual value of the target is 60 and the current quarter is Q2-2024
    In this case, after running the scheduled job 8 quarterly breakdowns are created and the Target value distribution is set to Spread linearly across the time period (cumulative) for the target. The current actual value for Q1-2023, Q2-2023, Q3-2023, Q4-2023, Q1-2024, and Q2-2024 quarterly target breakdowns are populated as 10, 20, 30, 40, 50, and 60, respectively. Also, the planned target value is populated for each breakdown.