Extend the Batch Schedule table

Scheduled tickets are stored within the BatchSchedule table within Historical, and cached within RealTime in the schTicket table. RealTime applications periodically synchronize the contents of the BatchSchedule table with the schTicket table. The schTicket table is a replication of the contents of the BatchSchedule table in Historical of the next 10 pending tickets for each batch transfer (BatchXfer) record.

Important: Since values in the BatchSchedule table will overwrite any changes made to the schTicket table, never modify default field values in the latter table.

You can extend the BatchSchedule and schTicket tables with additional columns to support project-specific requirements. When a synchronization event occurs, the Batch Transfer application attempts to populate fields in schTicket records with fields from the BatchSchedule table. If a column with the same name is added to both the schTicket table and the BatchSchedule table, the system will automatically synchronize it.

Note: If a field exists in Historical, but no corresponding fields exists in RealTime, the system ignores the field value.

AVEVA recommends that the data types of the columns in the schTicket and BatchSchedule tables remain consistent to ensure that the system can write values in Historical to RealTime. If the data types are different, the Batch Transfer application attempts to transform the data. If it is unable to transform the data (for example, the value thirteen exists in a field in Historical that the system will write to an integer field in RealTime), the system:

1. Reports an error for the field in the AVEVA Enterprise SCADA error log

2. Skips the problem field

3. Continues to synchronize all other non-problematic fields in the ticket

   Notes: Only primitive, path, or slot type fields can be synchronized. These fields must also be non-virtual.
   
   The system will not truncate values if the source data type is float and the target data type is an integer, or if the target field cannot fit the string value coming from the source field.
   
   The Hot RealTime server performs synchronization for all Batch Transfer records owned by that system.