SG-SCCM last used data not getting populated

[swetham1]

Hi ,

We have SG-SCCM in our instance (dev). We have gone through the guided setup, however, the last used data is not populating into usage table.

We ran a custom query to check the behavior and it also ignores the records.

The OOTB creates a query dynamically based out of reclamation rules, and we have OOTB reclamation rules in place. When the query gets generated, we see the product process files in the query but doesnt process anything. The same query when ran in db directly also doesnt bring any results.

Anything im missing here?

[KKM]

Hi Swetha M,

It looks like the SCCM integration in your ServiceNow instance is not populating the usage table as expected, despite going through the guided setup. Since your custom query also ignores records, here are a few troubleshooting steps to consider:

1. Check SCCM Data Ingestion
Ensure that SCCM discovery jobs are running properly and that SCCM data is actually being imported into ServiceNow.
Validate that SCCM data is present in the cmdb_sam_sw_install and cmdb_sam_sw_usage tables.

2. Review OOTB Reclamation Rule Conditions
Since reclamation rules drive the query, verify that the conditions in the Software Reclamation Rules (samp_sw_reclamation_rule) are correct.
Ensure that the last used date filter aligns with the available data in the usage table.

3. Enable Debugging and Logging
Navigate to System Logs → System Log → All and filter for SCCM import-related messages to check for errors.
Increase logging levels for com.snc.samp to capture more details.
Try running the SAM - Transform Reconciliation Results (SAMReconcileTransform) job and check for logs.

4. Manually Inspect SCCM Raw Data
Run a query directly in ServiceNow to check if cmdb_sam_sw_usage has any data:

SELECT * FROM cmdb_sam_sw_usage WHERE last_used IS NOT NULL;
If no records exist, check if the SCCM import jobs are populating cmdb_sam_sw_install, but failing to populate cmdb_sam_sw_usage.

5. Validate Import Set and Transform Maps
Ensure that the SCCM import set data includes usage information.
Confirm that the transform maps correctly map SCCM usage data to the cmdb_sam_sw_usage table.

6. Verify Query Behavior Outside ServiceNow
You mentioned running the generated query in the DB and getting no results. Try adjusting the query conditions to see if there’s an issue with date formats or filtering logic.
If the last used date format in SCCM differs from what ServiceNow expects, it may be getting ignored.

This should solve your issue!

Kindly mark it as "Accepted Solution"/"helpful", as it resolves your query. Please press like button for the resolution provided.

With Regards,
Krishna Kumar M - Talk with AIT3ch
LinkedIn: https://www.linkedin.com/in/mkrishnak4/
YouTube: https://www.youtube.com/@KrishAIT3CH
Topmate: https://topmate.io/mkrishnak4 [ Connect for 1-1 Session]

[Saiganeshraja]

1. Verify SCCM Import: Confirm data is correctly imported into ServiceNow import sets.
2. Analyze Query: Inspect the generated query for errors, especially WHERE clauses.
3. Direct DB Check: Run the query directly in the SCCM database; if no results, the query/data is the issue.
4. Review Rules: Check reclamation rules for accuracy and test with simplified rules.
5. ServiceNow Check: Ensure SG-SCCM plugin, jobs, and logs are error-free.
6. Data Mismatch: Check for case sensitivity, formatting, and null values.
7. Isolate, simplify, and validate the query: Test the query step by step.
8. Check transform maps: ensure data is being mapped correctly.