Configuring Booking Behaviour
- Jason Andrew
Owned by Jason Andrew
Sept 17, 2024
1 min read
Loading data...
An FRU Process relies on Database sp083_system_parameters and Database sp213_scheduler_parameters to configure how the offering and booking processes work.
The business needs to determine how these parameters should be set to meet their business requirements. Ideally, the business users should update the parameters using the appropriate screens within the ServiceManager web application.
They are given below for information only.
Global parameters
| Parameter | Mandatory/ Optional | Description |
|---|---|---|
abs_allow_book_dealloc | M | Enables deallocation of jobs of lower importance to be used in order to fit in new jobs through booking or ABS allocate. . |
Per FRU parameters
Parameter Name | Mandatory/ Optional | Description |
|---|---|---|
| M | Controls whether In-Tray allocate is run (bit-significant field) 1 – run before every optimiser run 2 - allow deallocate before optimizer 4 – run after every optimiser run 8 – allow deallocate after optimizer |
| M | Limit time spent in auto-allocation phases |
| M | Maximum value for ApptBook Importance parameter |
| M | Cost (weighting) of job of importance 0…9 being in In-tray |