We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

SG-SCCM SAMP Usage scheduled import not creating import set

Aman Trivedi1
Tera Contributor

3 weeks ago

Hi All,

I am currently troubleshooting an issue with the Service Graph Connector for Microsoft SCCM and wanted to check if anyone else has experienced something similar.

SG-SCCM SAMP Usage scheduled import not creating import set

AmanTrivedi1_2-1782828988421.jpeg

 



After Investigation I found out the below support article.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2422405
It says this scheduled job has a condition that it only run on 2nd day of the month, if we want to run on any other day for testing purpose, we may need to modify the condition. 

condition script:

if (now.getDayOfMonthLocalTime() == 2) {
    answer = true;
    var statement = new sn_sccm_integrate.SAMPUsage2019Util()
        .initializeDatasourceSqlStatement(connectionAliasSysId, datasourceSysId);
}
answer
 

Is anyone facing this scenario earlier, had anyone make changes in the scheduled job script

AmanTrivedi1_1-1782828872176.png

Thanks in advance for all the help. 

0 Helpfuls
  • 347 Views
1 REPLY 1

pr8172510
Kilo Sage

3 weeks ago

Hi @Aman Trivedi1,

 The SG-SCCM SAMP Usage scheduled import is designed to execute only on the 2nd day of the month, so an Import Set will not be created on other days unless the condition evaluates to true.

 you can temporarily modify the condition or create a copy of the scheduled job instead of changing the OOTB job permanently. This is the recommended approach, as OOTB changes may be overwritten during upgrades.


 verify

  • The scheduled import and its dependent scheduled jobs are Active.
  • The Connection Alias and Data Source are configured correctly.
  • The Scheduled Job and Import Set logs for any execution errors.

According to ServiceNow KB2422405, the monthly condition is intentional and is used to initialize the SAMP Usage SQL statement before the import runs. If the job still doesn't create an Import Set after the condition evaluates to true, review the job logs and data source configuration for any execution issues

0 Helpfuls