Fulfillment Data Extract

The first time the Fulfillments Data Extract job runs it creates a snapshot of fulfillment events from the day prior to the day the job runs. (Fulfillments 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 creates a comma-separated value (CSV) file. The job output is a snapshot of fulfillments created or updated; it does not include fulfillment history data.

The first line of the job output contains the header information for the table described by the CSV. If no fulfillments 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: Fulfillment Data Extract Job

FulfillmentID, Status, ParentFulfillmentID, ActivationID, FulfillmentDate, FulfillCount, OverdraftCount, ExpirationDate, ShipToEmail, CreatedBy, LicenseModel, FulfillmentSource, LifecycleAction, HostEntityID, HostUserId, IsServer, Redundant, Trusted, IsNodelocked, IsCustom,

FID_d43cbaf4_3b97_43bf_be75_be9e9ec52503, bo.constants.states.active, null, 709b-434b-6312-4c30-a3f4-bfdc-c5a9-e329, 2016-10-10 14:35:11.313,1,0, null, my.enduser@mycompany.com, ADMNadmin, Floating Counted, bo.constants.fulfillmentSource.online, null, ANY, null, true, false, false, false, false,

FID_02bafdb9_835e_44c4_a95a_ef37ed846f00, bo.constants.states.active, null, 709b-434b-6312-4c30-a3f4-bfdc-c5a9-e329, 2016-10-10 14:35:12.377,1,0, null, my.enduser@mycompany.com, ADMNadmin, Floating Counted, bo.constants.fulfillmentSource.online, null, ANY, null, true, false, false, false, false,

FID_e0e1ccb4_e62d_408a_a9a1_f1ef0343e132, bo.constants.states.active, null, 709b-434b-6312-4c30-a3f4-bfdc-c5a9-e329, 2016-10-10 14:35:14.457,1,0, null, my.enduser@mycompany.com, ADMNadmin, Floating Counted, bo.constants.fulfillmentSource.online, null, ANY, null, true, false, false, false, false,

...

Notice that, for fulfillments that have multiple host IDs, FlexNet Operations structures the CSV output so that a new row appears for each additional host ID on a given device. On these extra rows, the fulfillment ID is repeated, the fulfillment details between the fulfillment ID and the additional host ID are left empty, and the additional host ID follows. (See “Example for Multiple Host IDs on a Fulfillment,” below.)

Example for Multiple Host IDs on a Fulfillment

FulfillmentID, ..., HostID, ...

FID01, ..., Host101, ...,

FID02, ..., Host201, ...

FID02, ..., Host202, ...

FID03, ..., Host301, ...

...

Above, FID02 has two host IDs mapped to it: Host201 and Host202. FID01 and FID03 both have only one host ID mapped. In an actual output file, the row for FID02 and Host201 would show the status, the parent fulfillment ID, the activation ID (if any), and so forth. Extra rows for FID02 would not show those values.