SAM Pro - Unrecognised subscription identifiers

[Cairns]

Hi everyone,

One of our clients has subscriptions coming in from an integration which brings in subscription identifiers to match these subscriptions to software models. For 6 particular subscriptions, software models were not automatically created when the integration went live. These subscriptions now have their subscription identifiers tagged as unrecognized and sit in the samp_sw_unrecognized_subscription_identifier_list. We understand that simply creating a software model and adding it to these subscription identifiers would resolve this but, if the products are in the product table and the publisher are there also, why would SAM Pro not automatically create a software model to match to these identifiers? Are we missing something?

Any help or clarification on this would be greatly appreciated.

[dreinhardt · Accepted solution]

Hi @Cairns,,

This data is not currently available in the SAM Content Library and is therefore not linked automatically. As you said yourself, the solution is to link it manually and at the same time you should submit an ITAM Content Request so that these identifiers are managed by the Content DB in the future.

Best, Dennis

[Cairns]

Hi Dennis,

Thank you for your reply. Our process will probably go along lines as you've said there, to link the software model manually then submit a ticket to the content request.
As a quick follow up question though. I can understand that the unrecognized subscription identifier table doesn't get updated by the SAM content library. But I have found the Subscription Product Definitions table (samp_sw_subscription_product_definition_list) and this seems to hold subscription identifiers for a lot of different integration profiles, which makes me think this gets updated by the Content Library. Would you know if that's the case?

Thanks,
Cairns

[dreinhardt]

Hi @Cairns,

the "nrecognized subscription identifier table" isn't managed by the SAMP content team, it's an internal table to show data which can't be mapped. During each SaaS import, SAMP tries to map the identifier with the latest content data to establish the link with the correct SW model. As soon new content for SaaS is available and download, the integration will try to map against this.

Best, Dennis

[Cairns]

Hi Dennis,
Thank you again for answer on this, it is much appreciated.