Showing results for 
Show  only  | Search instead for 
Did you mean: 

What information are actually stored in SKU, ARL and PURL apart from specific application's name or description against an unique Part Number?

By Anonymous
Not applicable

Hi Team,

I have the following queries regarding license libraries:

1. I would like to know what further details or information are being stored in license blades or license libraries, such as SKU, ARL and PURL etc. apart from a specific application or software's name against the provided unique part number for that app.

2. How these libraries are helping in SAM BAU?

3. If an application is being uploaded with incomplete or incorrect Part Number or SKU, what posible issues may occur in SAM BAU?

4. If an application is reaching its EOL, is it possible to feed that information into Flexera by uploading SKU/license Libraries or by any other means?

5. Are those information viewable from FNMS GUI or somewhere else?


Thanks & regards,


(1) Reply

PURL--> Gives license types information along with application it is related to.

Blades-SKU > Provides complete use rights that purchased SKU provides, in addition to related/linked application/s e.g. Upgrade, downgrade, 2nd use rights, covers number of installations etc.  when SKU is processed in the present of blade, it automatically set all the use rights automatically on the license created by processing the SKU.

Setting use rights accurately is important part of accurately calculate license optimisation.

Blades also enable complex license types for certain publishers e.g. In the absence of Oracle Blade, Oracle Process and NUP license types would not be available.

ARL provides application/Suite recognition rules to recognise the installed application.

Most of the products have multiple SKU's, as each SKU provide unique set of use rights,  If application is not linked any SKU it mean user have to select license type manually and set use rights.

If you mean linked SKU is not valid, in that case when user processed, SKU process will fall back to generic license type.

ARL does provide EOL data for some applications, I think  SupportedUntil and ExtendedSupportUntil date value represent that. If missing and goal is for informational purpose you can create customer properties and update EOL date into those fields. Good to ask Flexera Support.

Some information is available but not all e.g you can check SKU definition by entering  the SKU  to Part no./SKU field on create purchase order page  and expand details if SKU is recognised.

You can view End of life information by opening application properties on the general tab under heading Details.