About Execution History Tab
- Kavitha Thangaswamy (Unlicensed)
- Pamela Totas (Deactivated)
The Execution History tab on the Execution Log window displays a list of submit processes executed for individual effective dates at the Data Mart Manager Engine level.
Execution history includes the user account by which a process was run, run date, start and stop times, effective date, and execution status.
About Execution Status
The status of the submit process is displayed in the Status column. Status values indicate the following:
S. Submitted
SS. Security details processing (indicates the final step in the Submit process)
Other statuses appear when the engine has finished its operation. The statuses you see depend on whether you selected the Set Data Mart Manager Engine Status from Models check box in the Configuration screen. If you did select the box, then status is one of the following:
C. All underlying Model Manager engines finished with a status of C.
N. At least one underlying Model Manager finished with a status of N. Others may have a status of C, but none finished with a status of E.
E. At least one underlying Model Manager finished with a status of E.
If you did not select the check box, then the status is one of the following:
C. Process completed, though some errors may have been encountered.
E. Process ended in a severe error, and no data was built.
View Log Details at the Model Manager Engine Level
You can view execution log details at the Model Manager Engine level.
To view execution log detail at the Model Manager Engine level:
Double-click a submit process at the Data Mart Manager Engine level on the Execution History tab.
The Execution Log window contents expand, allowing you to view a list of all models submitted by one or more Model Manager engines.
A new tab is added to the window with the date and time of the entry, as shown in the following figure.Â
The status of a Model Manager submission is C (process successfully completed) if all of its underlying OLAP processes completed with a status of C. It is E (process ended in error) if at least one OLAP process ended with a status of E, and it is N (no data to report) if all of its underlying OLAP processes ended with a status of N or C, with at least one N.
View Log Details at the Concentration Engine Level
You can view execution log details at the Concentration Engine (OLAP) level.
To view execution log detail at the Concentration Engine level:
Double-click the Model Manager level entry.
The window contents expand to list the OLAP process run for each entity and each of the model's data types. Another tab is added to the window with the name of the model.If the OLAP process is complete, the Report Results link is provided in the line entry for that process.
Use the tabs for Execution History, log entry (date and time), and OLAP process to move between the detail levels in the window. If the main level or detail level tab is not visible, use the right and left scroll button beside the tabs to move a tab into view.
When Data Mart populates the Security Details and Issuer Details tables, it must first build a list of securities for which to build data.
If you chose to populate all securities via the Configuration window, the engine goes through your entire security master and builds data for all securities.
If you did not choose to populate all securities via the Configuration window, the engine looks at all detail level tables for the effective date in question, and makes a list of all securities represented, which are referred to as "held securities." Then, if you chose to build security data using criteria, the engine follows your criteria (or filter rule) to find another list of securities. These two lists are merged, and the Security Details table is built for those securities. In any situation, the Issuer Details table is built for all issuers associated with all built securities.