This is the column description of each data column of WI_JOBSBYPENDREASONDAILY and how each column is filled with data.
Column Name |
Description |
Key |
CLUSTER_CODE |
This comes from the CLUSTER_NAME field in the raw table. Once we get the cluster_name, we then look it up in the WI_DIMENSIONCODE table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the WI_DIMENSIONCODE table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing sequence+1. |
Primary key |
TIME_STAMP |
This is in GMT and is always end in the day. The record is aggregated in a localized day. After the aggregation, the time_stamp is then transformed back at GMT and stored in this field. Thus, this time_stamp always in the GMT form of the localized day in midnight. |
Primary key |
GROUP_NAME |
This indicates what kind of grouping this record belongs to. The different group types are: "By Pending Reason Type" or "By Pending Reason". |
Primary key |
GROUP_CODE |
This could comes from different source and it is depends on the group_type. If the group_type is "By Pending Reason Type", then it comes from the "PendReasonType" field from the raw data table. If it is "By Pending Reason", then it comes from the field of "PendReason" of the raw data table. Once we get the fields, we then look it up in the wi_dimensioncode table to see if we have already has a record of it in there by matching the dimension_name. If we do, then we'll get the code back, otherwise, we will insert it into the wi_dimensioncode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing code+1. |
Primary key |
PEND_REASON_TYPE_CODE |
This comes from the "PendReasonType" field from the raw data table or it may come from each pending reason of the PendReason field. Once we get the fields, we then look it up in the wi_dimensioncode table to see if we have already has a record of it in there by matching the dimension_name. If we do, then we'll get the code back, otherwise, we will insert it into the wi_dimensioncode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing code+1. |
|
PEND_REASON_CODE |
This comes from the "PendReason" field from the raw data table or it may come from each pending reason of the PendReason field. Once we get the fields, we then look it up in the wi_dimensioncode table to see if we have already has a record of it in there by matching the dimension_name. If we do, then we'll get the code back, otherwise, we will insert it into the wi_dimensioncode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing code+1.
It will be -1 if the grouping is "By Pending Reason Type". |
Primary key |
TOTAL_JOB_NUMBER |
This comes from the result of two aggregation. First, the "Count" field is summed at the same interval for the grouping "CLUSTERNAME", "GROUPNAME" "PENDREASONCODE", "PENDREASONTYPE" AND "TIMEDIFF".
Then the aggregation of the grouping of "ClusterName", "PendreasonType" and "TimeDiff" for the day for the group type of "By Pending Reason Type". Or it may comes from the aggregation of the grouping of "ClusterName", "Pendreason", "PendreasonType" and "TimeDiff" for the day for the group type of "By Pending Reason". The sum of the sums from the second aggregation will be put into this column. |
|
MIN_JOB_NUMBER |
This comes from the result of two aggregation. First, the "Count" field is summed at the same interval for the grouping "CLUSTERNAME", "GROUPNAME" "PENDREASONCODE", "PENDREASONTYPE" AND "TIMEDIFF".
Then the aggregation of the grouping of "ClusterName", "PendreasonType" and "TimeDiff" for the day for the group type of "By Pending Reason Type". Or it may comes from the aggregation of the grouping of "ClusterName", "Pendreason", "PendreasonType" and "TimeDiff" for the day for the group type of "By Pending Reason". The minimum of the sums from the second aggregation will be put into this column. |
|
MAX_JOB_NUMBER |
This comes from the result of two aggregation. First, the "Count" field is summed at the same interval for the grouping "CLUSTERNAME", "GROUPNAME" "PENDREASONCODE", "PENDREASONTYPE" AND "TIMEDIFF".
Then the aggregation of the grouping of "ClusterName", "PendreasonType" and "TimeDiff" for the day for the group type of "By Pending Reason Type". Or it may comes from the aggregation of the grouping of "ClusterName", "Pendreason", "PendreasonType" and "TimeDiff" for the day for the group type of "By Pending Reason". The maximum of the sums from the second aggregation will be put into this column. |
|
COUNTER |
This comes from the result of two aggregation. First, the "Count" field is summed at the same interval for the grouping "CLUSTERNAME", "GROUPNAME" "PENDREASONCODE", "PENDREASONTYPE" AND "TIMEDIFF".
Then the aggregation of the grouping of "ClusterName", "PendreasonType" and "TimeDiff" for the day for the group type of "By Pending Reason Type". Or it may comes from the aggregation of the grouping of "ClusterName", "Pendreason", "PendreasonType" and "TimeDiff" for the day for the group type of "By Pending Reason". The number of the records from the second aggregation will be put into this column. |
|
CORE_HOUR |
The core hour is resulted from a mapping of the original time_stamp in local time. If the time_stamp is within the range from Monday to Friday, 9am to 5pm, then the core_hour will be 1, otherwise it will be 0. |
|
INSERT_SEQ |
This is a system generated sequence number. For each new record inserted, an unique sequence number is being assigned to this column. |
|