Data Mappings, Gaps, and Impacts

IT Asset Management (Cloud)

The following topics provide a mapping between the source tables (and their columns) in the Normalize v5 database, and the corresponding destination tables and columns in the compliance database within IT Asset Management. This mapping covers only the first stage of the process, into the tables with names starting Imported.... These are effectively staging tables that hold the data between the upload from Data Platform, and the major transition (or import) into the operational tables in the compliance database, normally followed immediately by the license compliance calculations (the calculations of consumption against entitlements). The descriptions also identify the operational tables where the data eventually resides, and for a more detailed understanding of those tables and their columns, see IT Asset Management Schema Reference.

The topics are separated by the target Imported... tables, each of which is aligned with a particular data object within IT Asset Management. Within each listing, the columns are in the same order that they appear in the Schema Reference, for your convenience if you are cross-referencing both documents.

As well as the list of imported data, a second list within each topic identifies the values that cannot be imported through Data Platform v5, together with notes on the impact that these gaps have on compliance calculations. Some gaps affect the suitability of this data source when you are managing certain types of licenses.

Each topic lists every column within the relevant Imported... table, so that if you are working across both this and the Schema Reference, there is no ambiguity about any column: it is either listed in the imports, or in the list of items missing from the import. Notice that this means some columns included for completeness appear in the list of "missing" items when in fact there is no expectation that they should be imported from any inventory source (or, to put it another way, they are correctly omitted from the import). These items are marked as "internally generated" by IT Asset Management.

Exempted kinds of data

The following kinds of data are not imported from Data Platform v5 to IT Asset Management:

• File evidence — this evidence type is not needed from Data Platform, as the import of installer evidence includes all required information
• WMI evidence — this evidence type is not needed from Data Platform, as the import of installer evidence includes all required information
• Client access evidence (used for Microsoft Client Access Licenses, or CALs) — this evidence is not available in Data Platform v5
• App-V evidence — this evidence is not available in Data Platform v5, and App-V application usage cannot be tracked if Data Platform v5 is the single inventory source
• Oracle Database and Oracle option evidence, and Oracle GLAS evidence — this evidence is not imported from Data Platform v5, so that recognition of Oracle Database version and edition, or of Oracle options, is not possible if Data Platform v5 is the single inventory source (but this information, along with detailed content to deliver to Oracle License Management Service, is fully available within IT Asset Management using the FlexNet Inventory Agent).