Creating allocations for already onboarded entitlements

[iamkurt]

We are onboarding Adobe subscription models.

We got a raw extract from our legacy ITAM system which had entitlements as well as users assigned to those licenses (allocations). It had almost 6696 lines in excel sheet in which quantity (purchased) was just 1 in every row, so we have a total of 6696 entitlements.

As a first step, I just extracted entitlement details, I have imported some 6.7k Adobe subscription entitlements in SAM.

Now, as a second step, I have to upload corresponding allocations.

How can I do that?

[dreinhardt]

Hi @iamkurt,

6696 individual orders for Adobe subscriptions doesn't sound correct to me and unfortunately doesn't match the data I've seen in my previous SAM projects. An Adobe customer usually purchases a certain number of subscriptions and then distributes/allocates them over time. If there is further demand, a new package is purchased. Purchasing certain quantities often results in a discount.

Please check all your data again carefully to see if there are any possible overlaps in the PO number/invoice number or other unique identifiers your SAM or procurement team uses, which, in my opinion, should reduce the number of entitlements down to 50-100, or less.

Regarding your  question about  allocations, all user allocations are stored in the [alm_entitlement_user] table. Based on your data, a new 1:1 relationship between the entitlement, the user, and the quantity to be consumed needs to be created for each data record. This can probably best be implemented using Import Set based on your existing data.

Best, Dennis

[iamkurt]

@dreinhardt-

>>6696 individual orders for Adobe subscriptions doesn't sound correct to me and unfortunately doesn't match the data I've seen in my previous SAM projects.

Its 6696 individual entitlements, not orders. Every line in the excel sheet has the model name, unit cost, PO number and the individual to whom that specific Adobe license is assigned. 

>>Regarding your  question about  allocations, all user allocations are stored in the [alm_entitlement_user] table. Based on your data, a new 1:1 relationship between the entitlement, the user, and the quantity to be consumed needs to be created for each data record. This can probably best be implemented using Import Set based on your existing data.

Do I need to leverage SysID's from alm_license here by any chance? 
I have already uploaded the entitlements and the corresponding allocations now needs to be created. 

How can I create allocations so that the right Adobe entitlement is mapped to the correct person?

[dreinhardt]

Hi @iamkurt 

interesting how your company is you managing the procurement process for new subscriptions. Could it be an internal PO numbers and from a global procurement view your company is buying in bundles instead of single entitlement? Sorry for asking again, but never seen a process like this while consulting companies from 5000 up to 250.000 employees using various SaaS licenses

Within the import set you‘ve to define a unique identifier (coalesce field) to get the sysID for the entitlement record. Based on your information I would recommend the unique PO number or asset tag (if available) to map it with the user ID to store it into the table.

Hope this helps. Best, Dennis