Hi @Supriya25 ,
1. Verify the reconciliation status
Navigate to All → Software Asset → Reconciliation → Historical Results and open the latest reconciliation result.
Check whether the run status is Completed, Failed, or Partially Completed. If it failed or partially completed, inspect the reconciliation results and available job logs to identify any errors affecting your custom publisher or product.
2. Check the Product Results record
From the latest reconciliation result, open the relevant Product Results record and verify that your custom product appears there.
The Product Results related list provides reconciliation information for products under a publisher, including compliance status, license metrics, and installations requiring action.
If your product result is missing, investigate the reconciliation run and whether the custom product and its associated discovery data are being included correctly.
3. Validate the software model and entitlement mapping
verify
The software installations reference the expected Discovery Model.
The Discovery Model's normalized publisher, product, version, and edition correspond to the intended Software Model.
The Software Entitlement is associated with the correct software model and product.
The entitlement has the expected purchased rights, active status, and license metric.
The software model is configured for license management.
Your screenshots show the Per User license metric. Check whether the installation and related user information provide the data required by that metric. Two installation records do not necessarily mean two license rights will be consumed under every licensing configuration.
4. Review License Metric Results
From the relevant Software Model Results record, inspect the License Metric Results related list.
Review the rights owned, rights used, licensed count, and any unlicensed count or allocation details available. These results help determine how SAM Pro is calculating license consumption for the configured metric.
For example, if the entitlement has 50 purchased rights and the two installations each consume one right, the result could be 2 rights used and 48 rights remaining. This is an expected calculation only if the configured metric evaluates those installations that way.
Reconciliation does not reduce the purchased entitlement quantity from 50 to 48.
It calculates license consumption and compliance based on the available discovery data, entitlements, and licensing rules.
5. If Software Model Results is still empty
Software Model Results are not generated for Oracle Database option software models without associated software entitlements by default. The system property com.snc.samp.unlicensed_smr_creation can enable Software Model Results creation for those models even when entitlements are absent.
Since you have already created a software model and entitlement, verify the product/software model/entitlement relationships and inspect the reconciliation results before changing this property.
6. Re-run reconciliation after correcting any issues
Once you have verified the mappings and corrected any configuration or data issues, run reconciliation again for the relevant publisher and review the latest results.
confirm whether a Product Results record is generated, then inspect the associated Software Model Results and License Metric Results.
