Data Dictionary
>
FPSINPUT Tables
> FPSINPUT.MHS_VEHICLE_ROUTES
Table FPSINPUT.MHS_VEHICLE_ROUTES"
Vehicle routes and sub-routes enable routes for NextMove and will enable carriers to be scheduled to a sub routes externally and through MHS_DELIVERY_NEXT logic. These cart routes need to be created to enable routing. 1) Configure routes in MHS_VEHICLE_SUB_ROUTES through ETL, manually, up to client lead. 2) In MHS_VEHICLES carts will need to be assigned to a route. 3) Using the extl procedure or delivery next, schedule lots to sub routes. For example, CART1 can be assigned to BLUE LINE and carriers can be scheduled to any sub route like OHARE or LOOP. A carrier scheduled to OHARE can be only picked up by a cart on the BLUE LINE route and any carrier scheduled to LOOP can be picked by cart on either BLUE LINE or GREEN LINE route.
-
Schema: FPSINPUT
-
Tablespace: FPSDATA
-
Primary key: VEHICLE_ROUTE
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
VEHICLE_ROUTE |
VARCHAR2(36) |
N |
A route that vehicles (carts) can take to pick up and drop off carriers around the site. |
|
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) |