sp371_opday_capacity
- Jason Andrew
Used capacity per OperativeDay (sp370_operative_days).Â
On a given OperativeDay, this table will contain one record for each configured capacity category.Â
If capacity checking is not enabled no records will be stored.Â
If an employee is not posted to any team on a particular date, there will be no sp371_opday_capacity record for that OperativeDay.Â
HouseKeeping
This table is tidied by sp_dbtidy's Global group.
Â
Table Definition
Field | Type | Default | Nullable |
|---|---|---|---|
| employee_no | number(9) | Â |  |
| schedule_date | date | Â | |
| capacity_category_no | number(9) | Â | |
| used_mins | number(6) | Â | |
| job_count | number(9) | Â |  |
Keys
primary key (employee_no, schedule_date, capacity_category_no)Â
foreign key (employee_no, schedule_date) references sp370_operative_days (employee_no, schedule_date)Â
foreign key (capacity_category_no) references sp350_capacity_categories (capacity_category_no) Jobs booked into a system before capacity is switched on will have no category. Table sp350 does not contain the 'no capacity' value as it is not a real category. Thus this foreign key is not applicable in the interim period whilst the 'old' jobs are aged out of the system.
Column Descriptions
| Field | Description |
|---|---|
| employee_no | Identifies the employee. |
| schedule_date | Identifies the date. FRU local time. |
| capacity_category_no | Identifies the capacity category. If it's the 'no capacity' category see1Â then this column will have a value of -1. |
| used_mins | Number of minutes of capacity used by jobs in capacity category capacity_category_no on this OperativeDay. |
| job_count | Number of jobs of this capacity category on this OperativeDay. |