OOTB REPORT FOR SAM

devanshsing
Tera Contributor

Hi

 

Is there is any OOTB report which can provide the details of software discovery models which do not have lifecycle phase date populated for all of its phases?

1 REPLY 1

Shahjay
Mega Guru

Hi @devanshsing ,

Not one built for discovery models specifically, no. The closest OOTB source is the Software Lifecycle Report table, sam_sw_product_lifecycle_report. The SAM - Generate Data For Software Lifecycle Report job rebuilds it. It holds one row per normalized publisher/product/version/full version/edition that has installs, with each phase in its own column: General availability start date, End of support start date, End of extended support start date and End of life start date.

So the quickest way to get your gap list is sam_sw_product_lifecycle_report.list with an OR filter on any of those four dates being empty. Save it as a report if you need to share it. The OOTB Software Product Lifecycle report under Reports > View/Run uses the same table, but it’s aimed at upcoming EOL rather than missing data.

If you need it per discovery model, current docs show a Lifecycle report reference on cmdb_sam_sw_discovery_model pointing at that table. If you have it on your release, you can run the same filter from the discovery model list by dot-walking through it. Discovery models where that reference is empty deserve their own look. They never made it into the report because they aren’t fully normalized or have no installs, and that’s often the bigger gap.

A blank date doesn’t always mean the data is missing, though. When a publisher hasn’t published a date, the content library often gives an approximated date or a lifecycle code explaining why there isn’t one (KB1642485 lists the codes). Plenty of products simply have no extended support phase, so a strict “every phase populated” filter will flag rows that are actually fine. Add the lifecycle code for each phase next to the dates so you can tell the two apart. You may need to dot-walk to get them.

For closing the gaps, look at Software Asset Workspace > Software asset analytics > Lifecycle management (needs SAM Pro). On recent releases, the Add lifecycle data playbook there walks you through report rows missing GA dates and rows missing EOS/EOES/EOL. Dates you enter go into sam_custom_sw_product_lifecycle. Where you have a GA date but no end dates, calculated lifecycles can fill a lot of them: define lifecycle averages, set com.snc.samp.generate.calculated.lifecycles to true, and let SAM - Create Calculated Software Lifecycles run. Rerun the report job afterwards, since the table is only a snapshot.

 

If this response helped, please mark it as correct and close the thread ✅ — it helps future readers find the solution faster.

Thanks