FFS_SCHEDULING_PLAN
Contains a full list of configured routing plans.
Details
-
Schema: FUSION
-
Object owner: FFS
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
Name | Columns |
---|---|
FFS_SCHEDULING_PLAN_PK |
SCHEDULING_PLAN_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
SCHEDULING_PLAN_ID | NUMBER | 8 | Yes | Unique identifier of the scheduling plan. | |
SCHEDULING_PROFILE_ID | NUMBER | 8 | Yes | Identifier of the scheduling profile. The foreign key to the table FFS_SCHEDULING_PROFILE. | |
PREDECESSOR_ID | NUMBER | 8 | Yes | Identifier of the scheduling plan that comes prior the SCHEDULING_PLAN_ID if they launched sequentially. | |
NAME | VARCHAR2 | 160 | Scheduling plan name which is defined by the customer. | ||
ACTIVE | NUMBER | 3 | Yes | Actual Status Of The Scheduling Plan. The Field Contains 1 For Active Scheduling Plan And 0 For Plans That Have To Be Skipped If There Is The Sequence Plan Starting, Ignored If It Is The Automatic Starting And Prevented If It Is The Manual Starting. | |
TYPE | VARCHAR2 | 9 | Mode how the run of the scheduling plan has to be launched. If the field is 'automatic' it means that the runs of the plan are started automatically, but value 'manual' means the run has to be initiated by customer from GUI. | ||
GOAL_BASED_OPTIMIZATION | VARCHAR2 | 21 | Optimization goal that is chosen by the customer. | ||
START_DAY_OFFSET | NUMBER | 3 | Yes | Start Day Offset For Activity Processing Regarding The Route Date. The Field Makes Sense For Scheduling Plans That Start Automatically. | |
FROM_TIME | NUMBER | 5 | In the case of the recurrent or immediate scheduling plan it is the time within configured days of weeks when the series of recurrent runs has to begin. In the case of a single run it is just the start time. The time is measured in minutes regarding the midnight. For example, 600 means 10 AM. | ||
TO_TIME | NUMBER | 5 | Time within configured days of week when the series of runs has to end. The field makes sense for recurrent and immediate runs. The time is measured in minutes regarding the midnight. For example, 1080 means 6 PM. | ||
INTERVAL | NUMBER | 5 | Time interval between launching of recurrent scheduling runs of the plan, minutes. If it is set to 5, it means that a new scheduling run will be launched every 5 minutes. The field is empty for non recurrent scheduling plans. | ||
WEEKDAYS | NUMBER | 3 | Bit Mask For Days Of Week When The Routing Plan Has To Be Launched. | ||
TIME_LIMIT | NUMBER | 10 | Yes | Time Limit For A Scheduling Run Duration, Seconds. | |
AUTO_ORDERING | NUMBER | 3 | Yes | Defines the behaviour of not-ordered activities. | |
UNIFORMITY_COEFF | NUMBER | Yes | Boolean coefficient to activate the uniform activity assignment 'Try to schedule activities to service window start'. | ||
FITNESS_COEFF_WINDOW_RESERV | NUMBER | Yes | Deprecated. Will be removed soon. | ||
DYNAMIC_SCHED_TIME | NUMBER | 10 | Yes | Parameter of the dynamic scheduling 'Resources loading interval, minutes'. | |
DYNAMIC_SCHED_NUM_ACTIVITIES | NUMBER | 10 | Yes | Parameter of the dynamic scheduling 'Resources loading amount, activities'. | |
DYNAMIC_SCHED_STOP_CONDITION | NUMBER | 10 | Yes | Parameter of the dynamic scheduling 'Stop loading when'. It has two possible values 'any limit is exceeded' and 'both limits are exceeded'. | |
HOME_ZONE_OVERSTEP_WGHT | NUMBER | 10 | Yes | Weight coefficient for the home zone overstep. It is used by the optimisation engine to prevent field resources to leave their home zones. | |
UPDATED | TIMESTAMP | Yes | Timestamp when the scheduling plan was updated last time. | ||
RESOURCE_OVERTIME | NUMBER | 10 | Yes | Maximal allowed overtime for all field resources within the scheduling plan. | |
UNACCEPTABLE_TRAVEL_TIME | NUMBER | 10 | Yes | Maximal allowed travel time between two neighbouring locations in a route. It is a constraint for activity assignment. | |
UNACCEPTABLE_TRAVEL_DISTANCE | NUMBER | Yes | Maximal allowed distance between two neighbouring locations in a route. It is a constraint for activity assignment. | ||
TRAVEL_OPTIMIZATION_STRATEGY | VARCHAR2 | 8 | Strategy of travel optimization: to minimize either travel time or travel distance. | ||
USE_SLT | NUMBER | 3 | Yes | Boolean flag that allows using the SLT-service to obtain travel data. | |
LIMIT_WORK_BY_POINTS | NUMBER | 3 | Yes | Boolean flag if routes have to be limited by points. | |
DEFAULT_APPT_POINTS | NUMBER | 10 | Yes | Deprecated. Will be removed soon. | |
APPT_POINTS_PROPERTY_ID | NUMBER | 5 | Yes | Deprecated field. Will be removed soon. | |
GET_TECH_POINTS_FROM_CALENDAR | NUMBER | 3 | Yes | Deprecated. Will be removed soon. | |
DEFAULT_TECH_POINTS | NUMBER | 10 | Yes | Deprecated. Will be removed soon. | |
TECH_POINTS_PROPERTYID | NUMBER | 5 | Yes | Deprecated. Will be removed soon. | |
CALENDAR_POINT_SIZE | NUMBER | 10 | Yes | Deprecated field. Will be removed soon. | |
CALENDAR_RESERVED | NUMBER | 10 | Yes | Deprecated field. Will be removed soon. | |
ASSURANCE_STILL_LIMIT | NUMBER | 10 | Deprecated field. Will be removed soon. | ||
INSUFFICIENT_SKILL_FACTOR | NUMBER | Yes | Additional multiplier for the ratio between actual and preferred skill levels. It affects the relevance cost of activity assignment. | ||
DEFAULT_HOME_ZONE_RADIUS | NUMBER | 10 | Yes | Defines the size of the home zone as the radius regarding the home zone center. In turn the home zone center has to be defined for every field resource separately. | |
HOME_ZONE_ENABLE | NUMBER | 10 | Yes | Enables home zone restrictions while scheduling. | |
USE_REQUIRED_INVENTORY | NUMBER | 3 | Yes | Enables the scheduling engine to consider required inventory for activity assignment. | |
REOPT_ENABLE | NUMBER | 3 | Yes | Enables reoptimization for preassigned activities. | |
REOPT_GOAL | VARCHAR2 | 31 | Re-optimization goal. By default the goal is 'optimize routes'. | ||
REOPT_REDUCE_OVERDUE_THOLD | NUMBER | 3 | Parameter 'Preferable overall reduction of activities overdue value, %' for the optimization goal 'Reduce activity overdue'. The result of the optimization is applied if the total overdue for such kind of activities is decreased by the value. | ||
TRIGGER_FILTER_ID | NUMBER | 8 | Yes | Parameter of the immediate scheduling. Scheduling will be performed immediately when the activity that corresponds to the selected filter is detected on the bucket. | |
IMMEDIATE_SCHEDULING_TYPE | VARCHAR2 | 1020 | Parameter of the immediate scheduling. Possible values are 'Urgent', 'Scheduled' and 'Continuous'. | ||
ASSIGNMENT_FROM | NUMBER | 8 | Yes | Starting day of multiday scheduling relatively to the route_date. It is not configurable, is set automatically and usually equals to zero. | |
ASSIGNMENT_TO | NUMBER | 8 | Yes | Number of days for the multiday scheduling. | |
BUNDLING_FROM | NUMBER | 8 | Yes | Makes sense for immediate plans of 'Scheduled type. Fields BUNDLING_FROM and. BUNDLING_TO define the time interval in days within which an activity can be scheduled and bundled to a suitable day. | |
BUNDLING_TO | NUMBER | 8 | Yes | Both fields BUNDLING_FROM and. BUNDLING_TO define the time interval in days within which an activity can be scheduled and bundled to a suitable day. | |
REOPT_MOVE_COST_OVERRIDE | NUMBER | Yes | Allows override default moving activities penalty. | ||
REOPT_MOVE_COST | NUMBER | Yes | Size of the penalty for moving activities. | ||
SW_RESERVATION_OVERRIDE | NUMBER | 3 | Yes | Allows overriding the default value SW_RESERVATION. | |
SW_RESERVATION | NUMBER | Yes | Reserved part of Service Window from its end where activity assignment is not desired. | ||
IMMEDIATE_SCHEDULING_SUBTYPE | VARCHAR2 | 9 | Parameter of the immediate scheduling for activity assignment. It points at the automatic assignment or at the assignment via collaboration. | ||
COLLAB_ROUTING_TIME_LIMIT | NUMBER | 10 | Yes | In the case of the assignment via collaboration it is the interval for users to accept the activity, minutes. | |
FLOW_ID | NUMBER | 10 | Yes | Identifier of the message scenario that should be run if an immediate assignment times out or fails. It is the foreign key to the table FFS_MESSAGE_FLOW. | |
SCHEDULING_TO_CONTRACTOR | NUMBER | 3 | Yes | Boolean flag which defines if the assignment to contractor's resource is allowed or activities have Ito be moved to the bucket instead of the assignment to contractor's resource. | |
ONLY_INTERNAL_RESOURCES | NUMBER | 3 | Yes | Boolean flag restricts the use resources outside the routing bucket. | |
IGNORE_WORK_ZONE_MISMATCH | NUMBER | 3 | Yes | Indicates whether the immediate scheduling may ignore work zone mismatch assigning activities. | |
DESCRIPTION | VARCHAR2 | 254 | Scheduling plan description provided by customer. | ||
ACTIVITY_TYPE_ID_INV_PICKUP | NUMBER | 3 | Identifier of an activity type which will be used as a template to create warehouse visits. | ||
TIME_LIMIT_PERCENT_SLT | NUMBER | 10 | Time limit for SLT-service as percents from total scheduling plan time limit. | ||
TARGET_QUALITY | NUMBER | 3 | Target value of the expected assignment quality, percents. | ||
RECOMM_MIN_TIME_LIMIT | NUMBER | 5 | Minimal recommended time limit for scheduling plan, seconds. | ||
RECOMM_MAX_TIME_LIMIT | NUMBER | 5 | Maximal (the best) recommended time limit for scheduling plan, seconds. | ||
RECOMM_BALANCED_TIME_LIMIT | NUMBER | 5 | Balanced recommended time limit for scheduling plan, seconds. | ||
LABEL | VARCHAR2 | 200 | Scheduling plan label provided by customer. | ||
INVENTORY_REQUIRED_DAYS | NUMBER | 5 | Number of days prior to the activity date that inventory is required. A value of 0 indicates that inventory is required for all days. | ||
DAILY_DISTANCE_LIMIT_IS_USED | NUMBER | 1 | Yes | Is daily travel distance limitation applied. | |
UNACCEPTABLE_DAILY_DISTANCE | NUMBER | Daily travel distance limitation in Scheduling, km. | |||
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. | ||
SEED_DATA_SOURCE | VARCHAR2 | 512 | Source of seed data record. A value of 'BULK_SEED_DATA_SCRIPT' indicates that record was bulk loaded. Otherwise, specifies the name of the seed data file. | ||
ORA_SEED_SET1 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET1. Context values are Y or N. | |
ORA_SEED_SET2 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET2. Context values are Y or N. | |
DELETED_FLAG | VARCHAR2 | 1 | Indicates whether the record is logically deleted (Y - soft deleted, N or NULL - active). | ||
FLAGS | NUMBER | 18 | Yes | It is a bitmask field that defines scheduling plan flags. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
FFS_SCHEDULING_PLAN_N1 | Non Unique | DATA | SCHEDULING_PROFILE_ID |
FFS_SCHEDULING_PLAN_PK | Unique | DATA | SCHEDULING_PLAN_ID, ORA_SEED_SET1 |
FFS_SCHEDULING_PLAN_PK1 | Unique | DATA | SCHEDULING_PLAN_ID, ORA_SEED_SET2 |