SAM - reclamation candidate generationSummary<!-- /*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: ; } } Removal candidates reclaim software resources in your environment. They are created from reclamation rules, or can be created manually.1. Closed Skip state is set when the reclamation record's Software Installation reference field is empty and the State is NOT in 'Awaiting Revocation' State. This means the software was not reclaimed as there is no software installation record populated for the software product for the reclamation on the CI. A use case would be where the installation record was removed via SCCM remove software import transform or Discovery software installation scan did not find the software on the CI and removed it. The weekly job would catch it once the software installation record is removed and set it to closed skip if the status is not 'Awaiting Revocation'.[-] Please refer KB document below about the stage "Awaiting Revocation".https://docs.servicenow.com/bundle/tokyo-it-asset-management/page/product/software-asset-management2/concept/reclaiming-user-subscriptions-saas.htmlhttps://docs.servicenow.com/bundle/tokyo-it-asset-management/page/product/software-asset-management2/task/t_AddAReclCandidate.htmlSAM - Identifying New Reclamation Candidates' will insert/update reclamation candidates after looping through the installs. So initially, the reference to the install is present in a reclamation candidate. Once a user hits 'reclaim' or 'reclaim all', those installs are deleted from the external system.On the next run of Discovery, since the install is not present in the external system, it will delete the record in the SN install table. So now the reference of that install is gone from the reclamation record.SAM has a job "SAM - Updating Existing Reclamation Candidates" that will go through reclamation candidates and if the install reference is removed - it will move the reclamation candidate to close complete.Removal candidates have generated again with the scheduled job 'SAM - Identifying New Reclamation Candidates' if they don't exist, and updated in only a few cases. The documentation specifies when the state changes from 'Awaiting Revocation' to 'Closed Complete' after running the job 'SAM — Updating Existing Reclamation Candidates'. The state changes to Closed Skipped if the installs are missing.https://docs.servicenow.com/en-US/bundle/utah-it-asset-management/page/product/software-asset-management2/concept/c_SAMOptimization.html