Schedule Sync Table Definition

Schedule Sync Table Definition

The Schedule Sync feature retrieves job schedule information from a customer’s SQL Server database and uses that data to modify the Eclipse Pro production schedule.

Eclipse Pro is going to reach into your SQL Server and query this table (or view) for job hold information which is then applied to the schedule. The table can have any name (we recommend “ams_SchSync”). This name must be placed into the Schedule Table field on the Schedule Sync configuration editor.

This TSQL create statement would create a suitable table for Eclipse Pro to use.

CREATE TABLE [ams_SchSync](
       [id] [bigint] IDENTITY(1,1) NOT NULL,
       [order_] [varchar](20) NOT NULL,
       [material] [varchar](20) NOT NULL,
       [pcode] [varchar](20) NOT NULL,
       [onhold] [bit] NULL  
)
  • [id] is not required at this time. We expect that in time the Schedule Sync feature will evolve to need it. We suggest including it now.
  • [order_], [material], and [pcode] are required. These three values form the key (identity) of the job in the Eclipse Pro system, and as such cannot be null.
  • [onhold] is technically optional. If it exists then Eclipse Pro will update the corresponding job’s hold status. If it doesn’t exist then Eclipse Pro simply won’t change your schedule at all, but in future versions there will be more schedule manipulation features available through this mechanism. At that time, each feature will have it’s own set of columns, but it will not be necessary to create columns for features that you are not going to use.

How to use this feature

Once the table is set up and Eclipse Pro is talking to your SQL database, you are ready to put the table to use. Your own process should add records for any job that you wish to manipulate. The record must include the (order_, material, pcode) data. From there you can change the value of onhold to affect the job’s hold status in Pro. A 1 (true) value would cause the job to be placed on hold. A 0 (false) value would cause the job to be released to production. And a null value means Schedule Sync will not change the hold status in any way.