Classic Reporting Data Model

For increased reporting efficiency, FlexNet Manager for Engineering Applications uses the FlexNet Reporting database to store usage data and generate report output. When report log data is imported into FlexNet Manager for Engineering Applications (whether on a scheduled or manual basis), that data is parsed and put into the FlexNet Reporting database.

This appendix provides information about the Classic reporting data model, including table names, column names, data types and lengths, descriptions, and any constraints.

FlexNet Manager for Engineering Applications Classic Reporting schema

The CATALOG_ID columns

Every report log that is imported is assigned a unique numeric identifier by the loading process. All data in the database that is extracted from this report log is tagged with this identifier so that their source can be easily identified.

This numeric ID can be matched back to the ID of the ReportLogCatalog object (stored in the RPT_LOG_CATALOG table of the FlexNet database). The information on the ReportLogCatalog object includes the name of the report log file, its import date, and file size.

The CATALOG_SECTION_ID columns

Every report log consists of one or more sections. A section is the period between the vendor daemon's start and stop or re-reads and where the set of features is static. Typically, the set of features for a section is read at the start of the section and does not change until the section ends.

A section can start because of a vendor daemon start, a report log rotation, or a reread command executed by a vendor daemon. A section can end because of a vendor daemon shutdown, a report log rotation, a reread command executed by a vendor daemon, or a server crash. In the last case, the report log section is not ended by the vendor daemon (because it has crashed), but is synthesized by the report data loader. The CATALOG_SECTION_ID is guaranteed to be unique across the sections of all report logs.