SAM PRO - Unrecognized dentifier

AnikpreetS
Tera Contributor

Tuesday - last edited Tuesday

Hi Team,

 

We previously had a working Adobe Cloud integration in SAM Pro, but a new unrecognized subscription identifier “ARCH” has appeared in the latest import. This identifier currently contains X users, and SAM Pro cannot map it to any known Adobe product
 
How can I fix this?

 

Preview file
58 KB
0 Helpfuls
  • 63 Views
2 REPLIES 2

Matthew_13
Mega Sage

Tuesday - last edited Tuesday

We ran into this after the latest Adobe Cloud import as well. The ARCH value isn’t an actual Adobe product or SKU — it’s an internal subscription / profile identifier coming from the Adobe Admin Console. SAM Pro is importing it correctly, but since it doesn’t represent a licensable product, it can’t be mapped to any Software Model.

Nothing is broken with the integration. This usually shows up when a new product profile or org-level profile is created on the Adobe side, or when Adobe changes what identifiers are exposed through their API.

The cleanest way to handle it is to either:

  • Leave ARCH unmapped and exclude it from compliance reporting, or

  • Create a non-licensable/custom software model (Adobe – ARCH (Non-Licensable)) and map it there so reports stay clean.

If needed, you can also review the Adobe Admin Console to confirm what profile ARCH is tied to and clean it up at the source, but in most cases it’s safe to ignore since it has no licensing impact.

 
@AnikpreetS  - Please mark Accepted Solution and Thumbs Up if you find Helpful!

mikew_samexpert
Mega Guru

yesterday - last edited yesterday

Create a software model for Adobe Assigned Reconciliation Characteristic and link it to the Unrecognized Subscription identifier and then you'll be good to go.

0 Helpfuls