Entitlement Data Extract

The first time the Entitlements Data Extract job runs it creates a snapshot of fulfillment events from the day prior to the day the job runs. (Entitlements created or updated from 00:00:00 to 23:59:59, FlexNet Operations server time, on the previous day are captured when the job runs). Subsequently, when this job runs, it creates a snapshot from the end time of the last successful run to the current time.

A successful run of this job results in the extract information getting downloaded as a zip file (not as a CSV file). This is different from the other extracts. The zip file contains two CSV files – one for entitlement line items and the other for maintenance line items. As an example, the name of the zip file would be Entitlements-2017-07-07-02-27-18.zip and inside this the name of the CSV’s would be EntitlementsExtract-2017-07-05-03-07-21.csv (entitlement line items) and MaintenanceLine-2017-07-05-03-07-21.csv (for maintenance line items). The naming format in these files is “YYYY-MM-DD-HH-MM-SS”. The job output is a snapshot of fulfillments created or updated; it does not include entitlement history data. The first line of the job output contains the header information for the table described by the CSV. If no entitlements were created or updated in the job period, the CSV output includes only the header row content.

Note:The date/time format of the data extract is controlled by the Use ISO 8601 time format in extracts configuration option. For more information, see Configuring System Settings | General Options in the FlexNet Operations User Guide.

Sample Output: Entitlement Data Extract Job - Entitlement Line Items

EntitlementID,EntitlementState,EntitlementDescription,AllowPortalLogin,ShipToEmail,Address,End Customer|Account,End Customer|AccountName,End Customer|UserName,End Customer|UserFirstName,End Customer|UserLastName,End Customer|UserEmail,End Customer|UserPhone,Partner Tier 1|Account,Partner Tier 1|AccountName,Partner Tier 1|UserName,Partner Tier 1|UserFirstName,Partner Tier 1|UserLastName,
Partner Tier 1|UserEmail,Partner Tier 1|UserPhone,CurrentOwner,ActivationId,ActivationState,
LineItemQuantity,OrderLineNumber,OrderId,StartDateType,StartDate,IsActivationPermanent,EndDate,EndDurationUnits,EndDuration,VersionDateType,VersionDate,VersionDurationUnits,VersionDuration,OrderType,OrderParent,LineItemDescription,ProductName,ProductVersion,ProductType,ProductCount,PartNumber,LicenseModel,
LM[Embedded Counted|NOTICE],LM[Embedded Counted|SERIAL_NUMBER],LM[Embedded Counted|VENDOR_STRING],
LM[Floating Uncounted|NOTICE],LM[Floating Uncounted|SERIAL_NUMBER],LM[Nodelocked Uncounted|NOTICE],
LM[Nodelocked Uncounted|SERIAL_NUMBER],LM[Embedded Uncounted|NOTICE],LM[Embedded Uncounted|SERIAL_NUMBER],LM[Embedded Uncounted|VENDOR_STRING],LM[Nodelocked Counted|NOTICE],LM[Nodelocked Counted|SERIAL_NUMBER],LM[Floating Counted|NOTICE],LM[Floating Counted|LM_TESTING],LM[Floating Counted|SERIAL_NUMBER]

1ad4-60c4-be37-4df6-a456-584c-51f9-0bd9,Deployed,My Example Entitlement,Yes,test@customer1.org,"100, California Avenue, USA",Acct1,Acme,endUser1,John,Smith,john.smith@earthday.com,111-222-3334,Acct2,Acme2,partnerUser1,Jack,Jill,jack.jill@nurseryrhymes.com,999-999-9998,bo.constants.partnertiernames.endcustomer,enterpriseAct,Deployed,100,,,DefineNow,30:00.0,TRUE,,,,,,,,,1ad4-60c4-be37-4df6-a456-584c-51f9-0bd9,,Enterprise,1,LicensedProduct,1,,Enterprise Activation,,,,,,,,,,,,,,,

The sections Account to UserPhone will be repeated for each reseller/tier. For example, if the entitlement had “End Customer” and “Partner Tier 1” (2 tiers only), then that particular section would look like

•

End Customer|Account

•

End Customer|UserName

•

End Customer|UserFirstName

•

End Customer|UserLastName

•

End Customer|UserEmail

•

End Customer|UserPhone

•

Partner Tier 1|Account

•

Partner Tier 1|AccountName

•

Partner Tier 1|UserName

•

Partner Tier 1|UserFirstName

•

Partner Tier 1|UserLastName

•

Partner Tier 1|UserEmail

•

Partner Tier 1|UserPhone

Notice that, for entitlements that have multiple line items (or activation IDs), FlexNet Operations structures the CSV output so that a new row appears for each activation ID. On these extra rows, the entitlement ID is repeated, the entitlement details between the entitlement ID and the activation ID are left empty.

Example of Multiple Activation IDs on an Entitlement

EntitlementID, ..., ActivationId, ...

EID01, ..., act101, ...,

EID02, ..., act201, ...,

EID02, ..., act301, ...,

EID03, ..., act401, ...,

...

Sample Output: Entitlement Data Extract Job - Maintenance Line Items

EntitlementID,EntitlementState,EntitlementDescription,AllowPortalLogin,ShipToEmail,Address,ActivationId,LineItemLink,ActivationState,ProductName,ProductVersion,PartNumber,OrderLineNumber,OrderId,StartDate,IsActivationPermanent,EndDate,CA[MAINT_LINE|cA_MNT_LI_B2],CA[MAINT_LINE|CA1M],CA[MAINT_LINE|cA_MNT_LI_B1],CA[MAINT_LINE|CAm2],CA[MAINT_LINE|BMLICA1],CA[MAINT_LINE|TESTCA_Ent_MNT],CA[MAINT_LINE|DateCA_MLI]

Nu-a270-0047-487b-651,Deployed,,Yes,,,actmain_01,,Deployed,maintenance19082016,1.1,,8232016,8232016,Mon Aug 22 17:00:00 PDT 2016,FALSE,Wed Aug 30 05:30:00 IST 2017,1234567,A2,123456,A1M|A2M,TRUE,12345,24-Aug-17

In the maintenance CSV file, the ActivationId refers to the maintenance line item ID and the LineItemLink refers to the linked entitlement line item ID. If there are multiple maintenance items linked to the same line item, a new row appears for each activation ID. On these extra rows, the entitlement ID and the line item link are repeated and the details between the entitlement ID and the activation ID are left empty.

The format for custom attribute columns is: CA[MAINT_LINE|name], where name is the name of the custom attribute for a maintenance line item. The custom attribute column can appear as many times as there are custom attributes defined for the maintenance line item.

Example of Multiple Maintenance Items Attached to the Same Line Item

EntitlementID, ..., activationID, LineItemLink..

EID01, ..., act101, lil01, ..,

EID01, ..., act201, lil01, ..,

EID01, ..., act301, lil01, ..,

EID01, ..., act401, lil01, ..,

...