Question

Reason Type Id in Appointment Offer

  • 15 June 2022
  • 2 replies
  • 209 views

Badge +2

When we receive payload, it contains Reason Type Id. It is only a numeric figure. Where I can find what it is meant by Reason Type Id.


2 replies

Userlevel 6
Badge +21

Hi,

Reason Type section in Administration Guide (Page 137 onwards) contains what is meant by the numerical value.

 

Eg: 320 - Activity cannot be scheduled within window

470 - The current plan does not schedule this activity

Userlevel 1
Badge +3

I believe this is the set:

  • 0 "Allocated"
  • 1 "Error retrieving unallocated reason."
  • 10 "Unallocated pre-requisite."
  • 15 "Unallocated post-requisite."
  • 20 "Unallocated co-requisite."
  • 30 "Could not allocate first co-requisite."
  • 40 "Could not allocate all co-requisites."
  • 50 "Could not meet min/max pre-requisite timing constraint."
  • 60 "Call not required as satisfied by alternate constraint."
  • 70 "No acceptable resources."
  • 80 "All suitable resources excluded."
  • 90 "No resource in region."
  • 100 "No resource with correct skill."
  • 110 "No resource within travel time."
  • 120 "There are no SLAs for this activity."
  • 130 "No pre-requisite min max/call SLA time overlap."
  • 140 "No overlap with allocation window."
  • 150 "No resource shift overlapping call pre-requisite min/max time."
  • 160 "No available resources in correct team."
  • 170 "No shifts overlapping allocation window."
  • 180 "Activity was completed before start time."
  • 190 "Cannot move a fixed visit."
  • 200 "Insufficient resources or unavailable resource, location or activity."
  • 210 "Unable to insert breaks."
  • 220 "Resource has no parts."
  • 230 "Resource has insufficient parts."
  • 240 "Cannot meet target SLA."
  • 250 "Would require travel after end of shift."
  • 251 "Would require shift utilisation to be exceeded."
  • 260 "Activity target date not met."
  • 270 "No suitable resource can reach activity."
  • 280 "Activity not processed - SLAs out of schedule time."
  • 290 "Not cost effective to schedule this activity."
  • 291 "Could not arrive early enough for a fixed activity."
  • 300 "Could not arrive early enough for a co-requisite."
  • 310 "No resource with required parts."
  • 320 "Activity cannot be scheduled within window."
  • 330 "Travel time not defined."
  • 340 "Not travelling with specified resource."
  • 350 "Not suitable activity time."
  • 360 "Maximum travel time exceeded."
  • 370 "Activity end time invalid."
  • 380 "Pre-requisite scheduled after."
  • 390 "Pre-requisite not immediately before."
  • 400 "Pre-requisite all-or-nothing constraint violated."
  • 410 "Not in any clusters."
  • 420 "No suitable route time."
  • 430 "Fixed activity overlaps previous activity."
  • 440 "Fixed activity overlaps unstarted activity."
  • 450 "Fixed activity not in schedule period."
  • 460 "Unable to {schedule} to any {resource}."
  • 470 "The current plan does not {schedule} this {activity}."
  • 480 "No automatic allocation attempted."
  • 490 "Old activity ignored."
  • 500 "Invalid activity location."
  • 510 "Invalid or missing activity duration."
  • 520 "Invalid or missing activity status."
  • 530 "Invalid resource location."
  • 540 "Activity has status "do not schedule"."
  • 550 "Invalid fixed time."
  • 560 "Invalid fixed resource."
  • 570 "{activity|u} fixed at invalid {resource} time."
  • 580 "Activity fixed or committed to unknown resource."
  • 590 "Activity fixed or committed to resource without parts."
  • 600 "Activity fixed or committed to resource exceeding max travel."
  • 610 "Invalid travel time weighting will be ignored."
  • 620 "{activity|u} not {schedulable} in existing visit to {location}."
  • 630 "Activity not passed to DSE."
  • 640 "Invalid activity separation."
  • 650 "Invalid modelling pattern."
  • 660 "Activity of invalid class fixed to bucket resource."

Reply