data-dictionary
data-dictionary
Breadcrumbs

FPSADMIN.EQP_LABOR_ROLES

Data Dictionary

>

FPSADMIN Tables

> FPSADMIN.EQP_LABOR_ROLES

Table FPSADMIN.EQP_LABOR_ROLES"

List of labor roles available. Although the username is logged with each transaction in the EVENT_HIST tables, currently names of actual people are not mapped to roles, just the roles are tracked for capacity modeling. So a report of labor role requirements by shift can be generated but not a report of what labor role capacity is available although this would be a fairly easy extension.

  • Schema: FPSADMIN

  • Tablespace: FPSDATA

  • Primary key: FACILITY, LABOR_ROLE

  • Foreign keys: EQP_LABOR_ROLES_FK_FACILITY: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)


Column

Type

Nullable

Comment

FACILITY

VARCHAR2(6)

N

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. (* from FPSINPUT.GEN_FACILITIES)

LABOR_ROLE

VARCHAR2(36)

N

Labor roles indicate who can support processing on a particular eqp_type. For example, a metrology tool might require a more experienced technician to do the inspection than a processing tool which just needs to be loaded.