Software Asset Workspace: Potential Savings Indicator Amount Does Not Match samp_sw_reclamation_candidate Table Sum<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue The Potential Savings amount displayed in the Software Asset Workspace (Software Asset Overview) does not match the sum of the potential_savings field when queried directly on the samp_sw_reclamation_candidate table. Symptoms The Potential Savings indicator value shown in Software Asset Workspace > Software Asset Overview differs from the total calculated by summing records directly on the samp_sw_reclamation_candidate table.The discrepancy may appear as a higher or lower value than expected when compared against a manual query or list view aggregate. Facts The Potential Savings value displayed in the Software Asset Overview is populated by the Performance Analytics (PA) Indicator: SAM Potential Savings from Removal Candidates. Indicator sys_id: f33f5b8d08e26010f877a5cec59e9751Measurement: Daily, unit = USD ($)No goal is configured for this indicator.Data Source: SAM Potential Savings from Removal CandidatesSource Table: samp_sw_reclamation_candidateFilter Applied: Active = true The indicator score is collected by the scheduled job SAM - Daily Job. Job sys_id: ffc55a94dbfb22003fc57bfdae9619d9Collection Window: 1 Day ago to 1 Day ago (relative)Timezone: US/Eastern (as configured in the Run as tz field)Indicator Source Used: SAM Active Removal Candidates DailySource Table: samp_sw_reclamation_candidateFilter Applied: Active = true Cause The Potential Savings value displayed in the Software Asset Overview reflects a PA indicator score collected during the previous day's scheduled job run, not a real-time sum of the current samp_sw_reclamation_candidate table. As a result, the displayed value may differ from a live table query due to one or more of the following: Data staleness: The indicator is collected once daily. Any changes to reclamation candidates (additions, removals, or active flag updates) after the last job run will not be reflected until the next execution of SAM - Daily Job.Timezone offset: The job collects scores based on the US/Eastern timezone. If the instance or user is in a different timezone, the collection window may not align with expectations.Active filter timing: Records deactivated or activated between job runs will affect the live table sum but will not impact the stored indicator score until the next collection cycle. Solution Step 1: Confirm the PA Indicator Configuration Navigate to Performance Analytics > Indicators > All Indicators.Search for and open the indicator: SAM Potential Savings from Removal Candidates (sys_id: f33f5b8d08e26010f877a5cec59e9751).Verify the data source points to samp_sw_reclamation_candidate with the filter Active = true. Step 2: Review the SAM Daily Job Last Run Time Navigate to System Scheduler > Scheduled Jobs (or use sysauto_pa.do?sys_id=ffc55a94dbfb22003fc57bfdae9619d9).Open the SAM - Daily Job scheduled job.Confirm the Last run time and verify it executed successfully.Check the Run as tz field and confirm the US/Eastern timezone is correctly configured for your environment. Step 3: Manually Trigger the Scheduled Job (If Needed) From the SAM - Daily Job record, click Execute Now to force an immediate score collection.After execution completes, refresh the Software Asset Workspace > Software Asset Overview and verify the Potential Savings value updates. Step 4: Validate the Live Table Sum Navigate to samp_sw_reclamation_candidate.list in a new browser tab.Apply the filter: Active = true.Use the list view aggregate or a background script to sum the potential_savings field.Compare this value against the PA indicator score collected during the last job run — expect a difference if records have changed since the last collection window. Step 5: Assess Ongoing Discrepancy If the discrepancy persists after the job runs successfully, review whether any business rules, data policies, or transforms are modifying the potential_savings field on reclamation candidate records outside of the standard SAM reclamation process.If the timezone configuration does not match the instance's primary operating region, consider adjusting the Run as tz field on the SAM - Daily Job to align collection timing with business expectations. For additional assistance, engage your ServiceNow support team or reference the ServiceNow documentation for Performance Analytics Indicator configuration.