Export Purchase Orders and Licenses

[dbeckner]

I am looking for a clean way to export our purchase orders and licenses from one FNMS system and then import using a business adapter into another FNMS system. In this scenario we have an FNMS system built in 2 different networks that consume the same entitlements from the same purchases.

Purchase orders seem straight forward. In the All Purchases management view I can add all the columns for the purchase orders, export to csv, and use a business adapter to import these purchases in bulk into the other FNMS system.

Licenses seem trickier since the All Licenses page does not offer all data associated to the license. Is there a way to single or bulk export a license(s) to be ingested into another system?

Additionally, if we bulk import the purchase orders first and then bulk import the licenses second (assuming its possible) will FNMS automatically link the purchase order to the license or will we need to perform some mapping after the fact?

Looking to avoid rebuilding 1100+ purchases and licenses by hand so any input is welcome.

TIA

[kclausen · Accepted solution]

@dbeckner - Your observations are correct.  For purchases and contracts, you can go to a View within FNMS and export the information to Excel and then use a Business Adapter to import them.

Recreating all of the Software Licenses in another FNMS system is a pretty manual process.  With a Business Adapter you can create a "Shell" license (License Name, Publisher and License Metric), but all other information is manual:

1) Linking the correct purchases and contract to the license

2) Setting up all of the correct Use Rights

3) Linking applications and setting Upgrade/Downgrade rights

[dbeckner]

Thanks @kclausen Appreciate your input.

[mfranz]

Hi,

If both systems are on-prem, you can re-create the complete situation, including PO-License-Linking. PurchaseOrderDetail and SoftwareLicense are linked in EntitlementTransaction. Be aware that object IDs (e.g. for PurchaseOrderDetailID & SoftwareLicenseID) will change when they're created in a new database. So you'll need to make sure to have proper mapping for linking these in the new system.

As an alternative, you can temporarily disable the autoincrement if you want to import the original IDs.

Best regards,

Markward