How SAM Advanced Metering / Total Usage data is processed and why usage may not reach the staging tableSummary<!-- /*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: ; } } SAM Advanced Metering collects process-level software usage from an ACC endpoint. Seeing the process and usage counters in the ECC Queue confirms that the endpoint collection and transmission succeeded, but it does not by itself mean that a record will be created in the SAM software usage staging table. After the data reaches the instance, ACC Visibility Content processes the sam_advanced payload through EnhancedDiscoveryHandler.persistSAMAdvancedStagingData(). For the usage to be stored, ACC/SAM must be able to resolve the collected information to the required SAM records. The overall processing is: ACC endpoint → sam advanced metering check → sam_advanced data returned in ECC Queue → instance-side ACC-V processing → user/product/software-install validation → sn_acc_vis_content_sam_software_usage_staging The sam_advanced payload contains data grouped by username. For example: user_name: service_userad_domain: example.comprocess: application.exeusage count/time values User association For each collected user, ACC attempts to associate the endpoint username with an existing sys_user record. The property: sn_acc_vis_content.column_name_for_user_mapping controls which sys_user field is used for the mapping. When a domain is provided, ACC can look for values in the form: domain\username or username@domain using the configured mapping field. If the collected user cannot be resolved to sys_user, ACC checks the affected CI's assigned_to field as a fallback. Collected username → sys_user mapping If found → continue processing. If not found → check CI assigned_to. If assigned_to is populated → use that user and continue. If both fail → usage for that user is not stored in the staging table. ACC does not automatically create sys_user records from local or service-account names collected from the endpoint. When user resolution fails, OOB processing logs a message similar to: EnhancedDiscoveryHandler.persistSAMAdvancedStagingData() : software usage data for CI with users [...] is not stored in the sn_acc_vis_content_sam_software_usage_staging table because users doesn't exists in the sys_user table Process and product association The collected process name must also have a SAM product mapping. ACC uses: samp_sw_product_process to associate the executable name with a SAM software product. Example: sqlservr.exe → SQL Server If the process does not have the expected product mapping, the collected process usage cannot be associated with the corresponding SAM software. Software Installation association A matching Software Installation must exist for the same CI in: cmdb_sam_sw_install The Software Installation must have a Discovery Model and the normalized product must correspond to the SAM product associated with the process. The relationship is: process → samp_sw_product_process → SAM product → cmdb_sam_sw_install on the CI → discovery_model → normalized product If a qualifying Software Installation cannot be found, the usage is not written to the staging table. Reclamation / Total Usage eligibility For the standard Total Usage processing path, the product must also meet the applicable SAM reclamation-rule configuration. Relevant records include: samp_m2m_rule_productsamp_reclamation_rule For the standard rule path, the applicable rule is expected to be configured for Total Usage and Installed Software. Staging When the required user, process/product, Software Installation, and eligibility conditions resolve successfully, ACC-V creates or updates the usage in: sn_acc_vis_content_sam_software_usage_staging The staging record is associated with the CI, Software Installation, user, time period, and collected usage values. This means that assigning the same user to multiple CIs does not make the different servers the same CI. The CI and Software Installation remain part of the usage association, although the attributed user may be the same. Troubleshooting If the process is missing from the ECC Queue, investigate the ACC check/endpoint collection. If sam_advanced exists in ECC but there is no staging record, validate: 1. The collected user resolves to sys_user using sn_acc_vis_content.column_name_for_user_mapping, or the CI has a valid assigned_to fallback. 2. The executable exists in samp_sw_product_process and maps to the expected SAM product. 3. A cmdb_sam_sw_install exists on the same CI. 4. The Software Installation has a valid discovery_model and normalized product. 5. The mapped product is eligible for the applicable Total Usage processing. 6. Check System Logs for EnhancedDiscoveryHandler.persistSAMAdvancedStagingData messages. A useful troubleshooting path is: Process collected in ECC → user mapping → process/product mapping → Software Installation → normalized product → Total Usage eligibility → staging record Summary The presence of usage data in ECC confirms collection, but staging requires successful instance-side association. The main conditions are: Collected process → valid user → SAM product → Software Installation on the CI → normalized product → Total Usage eligibility → SAM software usage staging. When any required association fails, identify the first failed condition rather than treating the issue as an ACC collection failure.