FPSBASE.SCH_P_LINK_STEPS_SCHED

FACILITY

Facility is included in almost every join in the DWH so this represents a definitive split. A route must have all steps on tools in the same facility. A tool must process all lots in the same facility. If your site has multiple buildings where lots run on routes using tools in multiple buildings then everything should be one facility. For example, multiple Fab buildings. But if your site has independent facilities like Fab and Test and Assembly where lot may progress from one to the next but on different routes then these should be different facilities. Since this column is in virtually every table it is critical that the value here is exactly matches what is in the MES if the MES has facility. Use facility_display for the display friendly name displayed in applications. See site_name comment for client/site/facility example. (* inherited from FPSINPUT.GEN_FACILITIES)

LINK_ID

LINK_TYPE

This value must be SKIP, TAG, or ALL. If the value is SKIP, then any parent mso decision that is skip will force all child processes to also SKIP. If the value is TAG, then any parent mso decision that is tag will force all child processes to TAG. For ALL, all child processes will match the decision of the parent process. (* inherited from FPSBASE.MSO_RULE_DECISION_LINKS)

LINK_FIRST_KEY

The key for the first step, for example COAT (* inherited from FPSAPP.SCH_C_LINK_STEPS_SCHED)

LINK_NEXT_KEY

The key for the next step, for example STEP (* inherited from FPSAPP.SCH_C_LINK_STEPS_SCHED)

SHOULD_CARRY_DURABLE

LINK_HOURS