SCCM data import process and source tables

Both supported SCCM versions offer the same features and selected data.

Data import process

  1. A schedule called SCCM System <version> Import determines when the SCCM tables are imported into the ServiceNow® instance. Imports can be executed immediately or scheduled to run at defined intervals.
  2. A MID Server retrieves the SCCM data and imports it into staging tables on the instance.
  3. Transforms run on the data in the staging tables and map the SCCM data to existing fields in the CMDB.
SCCM data import process

SCCM data imported

This table shows the SCCM source tables, the corresponding import set staging tables in the ServiceNow® instance, and the target tables in the CMDB.
SCCM table Staging table CMDB table
  • v_GS_Computer_System
  • v_GS_Workstation_Status
  • v_GS_System
  • v_GS_PC_Bios
  • v_GS_Operating_System
  • v_GS_Computer_System_Product
  • v_GS_System_Enclosure
  • v_GS_Baseboard
SCCM <version> Computer Identity [imp_sccm<version>_computer_id] Computer [cmdb_ci_computer]
v_GS_Disk SCCM <version> Disk [imp_sccm<version>_disk] Disk [cmdb_ci_disk]
v_GS_Network_Adapter_Configuration SCCM <version> Network [imp_sccm<version>_network] Network Adapter [cmdb_ci_network_adapter]
v_GS_Operating_System SCCM <version> Operating System [imp_sccm<version>_os] Computer [cmdb_ci_computer]
v_GS_Processor SCCM <version> Processor [imp_sccm<version>_processor] Computer [cmdb_ci_computer]
  • v_GS_Add_Remove_Programs
  • v_GS_Add_Remove_Programs_64)t
SCCM <version> Software [imp_sccm<version>_software]
  • Software [cmdb_ci_spkg]
  • Software Installation [cmdb_sam_sw_install] (when Software Asset Management is enabled)
SCCM_Ext.Add_Remove_Programs_DATA_DD SCCM <version> Removed Software [imp_sccm<version>_removed_sw]
  • Software [cmdb_ci_spkg]
  • Software Installation [cmdb_sam_sw_install] (when Software Asset Management is enabled)
SCCM_Ext.Add_Remove_Programs_64_DATA_DD SCCM <version> Removed Software [imp_sccm<version>_removed_sw]
  • Software [cmdb_ci_spkg]
  • Software Installation [cmdb_sam_sw_install] (when Software Asset Management is enabled)

SCCM data sources

The ServiceNow® SCCM integration uses JDBC data sources to import software data from the SCCM database. Each data source contains the connection specifics for the SCCM database and names the MID Server the instance will use to import the data. The transforms that map the SCCM fields to the CMDB are defined in a related list in each data source record.

Transform maps

Transform maps are accessed from the Transforms related list in each data source record. The source fields in SCCM and the target fields in the CMDB are listed in the Field Maps related list in each Table Transform Map record. The SCCM integration uses the transform map utility provided with the ServiceNow® platform. For instructions on editing or creating a transform map, see Transform maps.

The SCCM integration provides two transform maps for incremental software imports. Only one transform map can be enabled (Active) at a time.
  • Incremental Import: Enabled by default. This map should be configured as Active when Software Asset Management is not enabled on the instance.
  • Incremental Import (SAM enabled): If the Software Asset Management plugin is activated, set this transform to Active
Note: To force a one-time full import of all software data from the SCCM database, clear the value in the Last run datetime field. This operation can take a long time to execute, so the most efficient method is to use an incremental transform after the first full import.

Transforming the assigned user

The SCCM <version> Computer Identity transform script attempts to set the Assigned to field in the CMDB record by looking up the name of the user in the SCCM source table and comparing the value with the matching field in the ServiceNow sys_user table. If a match is found, that user is assigned to the record. If no match is found, the Assigned to field is left blank. The matching field is controlled by the glide.discovery.assigned_user_match_field system property, which is set to user_name by default.


The SCCM integration uses CI identification to update CIs created from data imported from SCCM with a resource ID. The Hardware Rule identifier returns the resource ID of a computer from SCCM and stores it in a table called Source [sys_object_source]. When resource IDs are first imported, either from SCCM or Discovery, the system populates the sys_object_source table with IDs for each CI it identifies. In subsequent imports, if an incoming ID matches that of an existing CI, the system updates the information for that CI in the CMDB. If the incoming resource ID does not match that of an existing CI, the system creates a new CI and populates it with the resource ID.


Data population scripts populate the related data in the CMDB for each target CI discovered by the Hardware Rule identifier.


The Microsoft SCCM integration reconciles the software package count in the records for a CI and removes a software instance from the Software Instance [cmdb_software_instance] table if the software package is uninstalled from the CI. For a full software import, the transform populates the Software [cmdb_ci_spkg] and Software Instance [cmdb_software_instance] tables. If the Software Asset Management plugin is enabled, the transform populates the Software Installation [cmdb_sam_sw_install] table.
Caution: The table data imported from SCCM must contain complete data for the CI. The instance assumes that the import represents all relationships that exist and adjusts the CMDB accordingly. Partial data received from SCCM tables can cause the deletion of active relationships.