FFS_SP_RUN_LOG
Used to store a history of routing plan runs.
Details
-
Schema: FUSION
-
Object owner: FFS
-
Object type: TABLE
-
Tablespace: DATA
Primary Key
| Name | Columns |
|---|---|
|
FFS_SP_RUN_LOG_PK |
SCHEDULING_LOG_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| SCHEDULING_LOG_ID | NUMBER | 10 | Yes | Unique identifier of the log record. In the case of scheduling runs, the filed is the run ID. The field is the primary key. | |
| OPERATION_TYPE | VARCHAR2 | 23 | Type of the operation that is logged. Possible values are 'routing', 'rollback', and 'move to bucket'. | ||
| RESOURCE_ID | NUMBER | 8 | Yes | Identifier of the resource (bucket) where the scheduling run was launched. It is the foreign key to the table FFS_RESOURCE. | |
| SEQUENCE_LOG_ID | NUMBER | 10 | Yes | Identifier of the sequence of runs. In the case of sequential runs the ID equals to the ID of the first run in the sequence. | |
| PREDECESSOR_LOG_ID | NUMBER | 10 | Yes | Equals to the scheduling plan ID of the previous run in the sequence. If it is single scheduling run, it equals to zero. | |
| SUCCESSOR_LOG_ID | NUMBER | 10 | Yes | Equals to the scheduling plan ID of the next run in the sequence. If it is single scheduling run, it equals to zero. | |
| SCHEDULING_PLAN_ID | NUMBER | 8 | Yes | Scheduling plan ID that the run belongs to. It is the foreign key to the table FFS_SCHEDULING_PLAN. | |
| ACTION_ID | NUMBER | 19 | Yes | Who column: identifier of the action which is assigned by the Application server. | |
| USER_ID | NUMBER | 18 | Who column: identifier of the user the operation is performed by. | ||
| RUN_DATE | DATE | Date when scheduling run was launched. The date corresponds to the local time zone. | |||
| ROUTE_DATE_START | DATE | Date the scheduling run was launched for. The date corresponds to the local time zone. | |||
| STARTED | TIMESTAMP | UTC timestamp when exactly the scheduling run was launched. | |||
| FINISHED | TIMESTAMP | UTC timestamp when the scheduling run was actually completed. The difference between FINISHED and STARTED equals to the total duration of the scheduling run that includes all processing steps and infrastructure delays. | |||
| RESOURCE_TZ_DIFF | NUMBER | 5 | Time shift between UTC and local time zone for the resource (bucket) where the scheduling run was launched. | ||
| FILTERS | VARCHAR2 | 1020 | List of filters that the scheduling run passed. | ||
| TOTAL_RESOURCES | NUMBER | 8 | Total number of field resources that were sent to the scheduling engine for optimization. | ||
| RESOURCES_CHANGED_ROUTES | NUMBER | 10 | The number of field resources that have their routes changed after the scheduling run. | ||
| ACTIVITIES_TO_BE_ASSIGNED | NUMBER | 8 | Total number of activities that have to be assigned by the scheduling run. | ||
| ASSIGNED_ACTIVITIES | NUMBER | 8 | Actual number of activities were assigned by the scheduling run. | ||
| NOT_ASSIGNED_ACTIVITIES | NUMBER | 8 | Total number of activities were not assigned by the scheduling run due to different reasons. More details on the activities are provided in the table FFS_SP_RUN_LOG_DETAILS. | ||
| NOT_ASSIGNED_DYNAMIC_SCHED | NUMBER | 8 | Number of activities were not assigned due to the dynamic scheduling. | ||
| OPTIMIZATION_FUNCTION_VALUE | NUMBER | Value of the optimization function that were reached in the scheduling run. | |||
| ASSURANCE | NUMBER | Actual assurance of the scheduling run result. The assurance varies from 0 to 99 where 99 means the optimal solution is found. | |||
| RESULT_STATUS | VARCHAR2 | 9 | Status Of The Scheduling Run. Possible Values Are 'Succeeded', 'Failed', 'Running', 'Stopped', 'Waiting'. | ||
| RESULT_DESCRIPTION | VARCHAR2 | 1020 | Additional information about the scheduling run result. For example, in the case of the failed run, it contains the reason of the failure. For succeeded runs, it points if the reoptimization was allowed, or if the reoptimization was accepted. | ||
| RESULT_DETAILS | CLOB | Details on scheduling run result in xml-format. | |||
| ROUTE_DATE_END | DATE | End date for the multiday routing: multiday routing covers dates from ROUTE_DATE_START to ROUTE_DATE_END including both of them. In the case of the single day routing ROUTE_DATE_END is the same as ROUTE_DATE_START. | |||
| PRIORITY | VARCHAR2 | 9 | The priority level of the scheduling run. | ||
| SLT_TIME | NUMBER | 10 | Time that the run actually spent at SLT service, seconds. | ||
| SCHED_RUN_TIME | NUMBER | 18 | Time that the run actually spent at the scheduling engine, seconds. | ||
| SCHED_RUN_TIME_LIMIT | NUMBER | 10 | Time limit for the scheduling run duration, seconds. | ||
| PREDICT_SCHED_RUN_TIME | NUMBER | 10 | Predicted full run time of the scheduling run, seconds. | ||
| ACTUAL_SCHED_RUN_STRATUP_TIME | NUMBER | 10 | Actual start up time of the scheduling run, seconds. | ||
| ACTUAL_FULL_TIME | NUMBER | 10 | Actual full run time including start up and processing time of the scheduling run, seconds. | ||
| EVENT_FIELDS | BLOB | Fields to be exported in the routingRun event and Daily Export. | |||
| ROLLBACK_LOG_ID | NUMBER | 10 | Scheduling run ID which were rolled back. | ||
| STARTUP_MODE | VARCHAR2 | 18 | Startup Mode For Continuous Routing Plans. | ||
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| FFS_SP_RUN_LOG_N1 | Non Unique | DATA | ROUTE_DATE_START |
| FFS_SP_RUN_LOG_N2 | Non Unique | DATA | RUN_DATE |
| FFS_SP_RUN_LOG_N3 | Non Unique | DATA | ACTION_ID |
| FFS_SP_RUN_LOG_N4 | Non Unique | DATA | RESOURCE_ID, ROUTE_DATE_START |
| FFS_SP_RUN_LOG_PK | Unique | DATA | SCHEDULING_LOG_ID |