FPSAPP.RTG_DURABLE_STATES

Data Dictionary

>

FPSAPP Tables

> FPSAPP.RTG_DURABLE_STATES

Table FPSAPP.RTG_DURABLE_STATES"

List of FPS defined values allowed for the durable state. Restricting durable_state to a value defined in this table allows our applications to make specific references to these values.

Schema: FPSAPP
Tablespace: FPSDATA
Foreign keys: RTG_DURABLE_STATES_BG_COLOR_FK: BG_COLOR REFERENCES FPSADMIN.GEN_COLORS (COLOR)

Column	Type	Nullable	Comment
DURABLE_STATE	VARCHAR2(36)		Durable state indicates the current state of the durable The value must be one of those defined by FPS in FPSADMIN.MHS_CARRIER_STATES. This is a short list of simple states like OK or WARN or DOWN in contrast to the complex options available for equipment states. This would be used as a filter/sort on what durables could be used for scheduling. For example, if there are two durables in the durable_family and one is OK and the other is DOWN then we schedule using the OK durable. But if there is only one durable in the family then we cannot schedule any lots which require this family if that lone durable is DOWN. (* from FPSINPUT.RTG_DURABLES)
BG_COLOR	VARCHAR2(24)		Background color assigned. BG_COLOR is in English like red or blue or light green and we look up the HTML color like #FF0000 in the GEN_COLORS table. BG_COLOR must be set manually but the FPSADMIN view BLD_POPULATE_COLORS will generate queries to randomly set bg_color for all values in a table. (* from FPSINPUT.GEN_CUSTOMERS)
IS_IN_PRODUCTION	CHAR(1)		Boolean indicating whether a durable is in production or not.
IS_LOT_BLOCKED	CHAR(1)		Boolean indicating whether a durable state causes associated lots needing to use the durable to show as blocked.
IS_OK_TO_USE	CHAR(1)		Boolean indicating whether a durable is ok to use immediately.
SORT_ORDER	NUMBER(4)	N	This is used to sort within the grouping. SORT_ORDER always has a deferrable unique key to ensure uniqueness while allowing the user to make changes without erroring until the commit is attempted. Because of this you must be careful to not violate the unique key otherwise you will lose all of your edits. (* from FPSINPUT.GEN_FACILITIES)
WAIT_SEC_TO_SCHED	NUMBER(7)		The lot may be scheduled but must not be allowed to dispatch or start until this number of seconds has elapsed. (* from FPSINPUT.WIP_LOTS_STATIC)