Data Dictionary
>
FPSADMIN Tables
> FPSADMIN.CFG_KNOWN_MISS
Table FPSADMIN.CFG_KNOWN_MISS"
Occasionally there are corner cases to the ETL that we simply cannot handle properly in WIP_EVENT_HIST. One example is lots going on hold twice then released and unsure whether still on hold. Another is hold type not correctly populated with the event. This table allows us to record acceptable miss events so they are not reported by SYSMNTR_HEALTH.
-
Schema: FPSADMIN
-
Tablespace: FPSDATA
-
Primary key: EVENT
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
EVENT |
VARCHAR2(48) |
N |
This is the event registered in the MES. This is for the historical record and display only. Each event is mapped to an FPS event_type and the event_type is what is used by FPS applications. (* from FPSINPUT.WIP_EVENTS) |
|
ACCEPTABLE_NUM_PER_HOUR |
NUMBER(3) |
N |
Usually these known cases are infrequent. Enter a number that is above the normal level so that if we start logging significantly more events then we will warn. |
|
INVESTIGATED_BY |
VARCHAR2(64) |
Name of person who is investigating or did investigate this error. (* from FPSADMIN.CFG_KNOWN_ERRORS) |
|
|
INVESTIGATED_ON |
DATE |
Datetime when this error was last investigated. (* from FPSADMIN.CFG_KNOWN_ERRORS) |