[Home] [Help] [Dependency Information]
Object Name: | MST_EXCEPTION_DETAILS |
---|---|
Object Type: | TABLE |
Owner: | MST |
Subobject Name: | |
Status: | VALID |
Entity for storing TP exception summary
Tablespace: | APPS_TS_TX_DATA |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
MST_EXCEPTION_DETAILS_U1 | NORMAL | UNIQUE | APPS_TS_TX_IDX |
EXCEPTION_DETAIL_ID
PLAN_ID |
MST_EXCEPTION_DETAILS_N1 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX |
PLAN_ID
EXCEPTION_ID |
MST_EXCEPTION_DETAILS_N2 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX |
PLAN_ID
ORGANIZATION_ID |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
EXCEPTION_DETAIL_ID | NUMBER | Yes | Primary Key | |
EXCEPTION_ID | NUMBER | Yes | FK to mst_exceptions | |
EXCEPTION_TYPE | NUMBER | Yes | Lookup | |
EXCEPTION_SUB_TYPE | NUMBER | Exception sub type. For eg., consolidating layover and drop trailer exceptions. | ||
PLAN_ID | NUMBER | Yes | FK to mst_plans | |
DELIVERY_DETAIL_ID | NUMBER | FK to mst_delivery_details | ||
DELIVERY_DETAIL_ID2 | NUMBER | FK to MST_DELIVERY_DETAILS. | ||
DELIVERY_ID | NUMBER | FK to mst_deliveries | ||
DELIVERY_LEG_ID | NUMBER | FK to mst_delivery_legs | ||
STATUS | NUMBER | 1 => ACTION TAKEN, 2 => IGNORE, 3 => TO BE REVIEWED | ||
UPDATE_FLAG | NUMBER | Flag to indicate that this exception is due to manual update of the plan | ||
MODE_OF_TRANSPORT | VARCHAR2 | (30) | Lookup | |
CARRIER_ID | NUMBER | FK to wsh_carriers | ||
CARRIER_SERVICE_ID | NUMBER | FK to fte_carrier_services | ||
SERVICE_TYPE | VARCHAR2 | (30) | Service type (TRUCK, LTL, PARCEL, AIR) | |
VEHICLE_TYPE_ID | NUMBER | FK to fte_vehicle_types | ||
CUSTOMER_ID | NUMBER | Customer id | ||
SUPPLIER_ID | NUMBER | Supplier id (FK to po_vendors) | ||
ORGANIZATION_ID | NUMBER | organization id | ||
LOCATION_ID | NUMBER | FK to WSH_LOCATIONS.WSH_LOCATION_ID | ||
FACILITY_ID | NUMBER | FK to fte_location_parameters | ||
COMMODITY_ID1 | NUMBER | Item_category. | ||
COMMODITY_ID2 | NUMBER | Item_category. For some exceptions we need to store two categories eg Incompatible commodities in a containerized package | ||
STOP_ID1 | NUMBER | FK to wsh_trip_stops.vehicle_stop_id | ||
STOP_ID2 | NUMBER | FK to wsh_trip_stops, vehicle_stop_id. For a few exceptions we need two stop ids | ||
LANE_ID | NUMBER | FK to fte_lanes | ||
LANE_SET_ID | NUMBER | FK to fte_lane_sets | ||
OVER_UTILIZATION_NUMBER | NUMBER | Obsolede, not used any more | ||
UNDER_UTILIZATION_NUMBER | NUMBER | Obsolede, not used any more | ||
NUMBER_OF_LOADS | NUMBER | Obsolede, not used any more | ||
CONTINUOUS_MOVE_ID | NUMBER | This column stores the CM ID | ||
TRIP_ID1 | NUMBER | FK to mst_trips | ||
TRIP_ID2 | NUMBER | FK to mst_trips | ||
NUMBER1 | NUMBER | Generic number columns | ||
NUMBER2 | NUMBER | Generic number columns | ||
NUMBER3 | NUMBER | Generic number columns | ||
NUMBER4 | NUMBER | Generic number columns | ||
NUMBER5 | NUMBER | Generic number columns | ||
DATE1 | DATE | Generic date columns | ||
DATE4 | DATE | Generic date columns | ||
DATE5 | DATE | Generic date columns | ||
DATE2 | DATE | Generic date columns | ||
DATE3 | DATE | Generic date columns | ||
CHAR1 | VARCHAR2 | (240) | Generic varchar2 columns | |
CHAR2 | VARCHAR2 | (240) | Generic varchar2 columns | |
CHAR3 | VARCHAR2 | (240) | Generic varchar2 columns | |
CHAR4 | VARCHAR2 | (240) | Generic varchar2 columns | |
CHAR5 | VARCHAR2 | (240) | Generic varchar2 columns | |
CREATED_BY | NUMBER | (15) | Yes | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). |
CREATION_DATE | DATE | Yes | Standard who column - date when this row was created. | |
LAST_UPDATED_BY | NUMBER | (15) | Yes | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
LAST_UPDATE_DATE | DATE | Yes | Standard Who column - date when a user last updated this row. | |
LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). |
Cut, paste (and edit) the following text to query this object:
SELECT EXCEPTION_DETAIL_ID
, EXCEPTION_ID
, EXCEPTION_TYPE
, EXCEPTION_SUB_TYPE
, PLAN_ID
, DELIVERY_DETAIL_ID
, DELIVERY_DETAIL_ID2
, DELIVERY_ID
, DELIVERY_LEG_ID
, STATUS
, UPDATE_FLAG
, MODE_OF_TRANSPORT
, CARRIER_ID
, CARRIER_SERVICE_ID
, SERVICE_TYPE
, VEHICLE_TYPE_ID
, CUSTOMER_ID
, SUPPLIER_ID
, ORGANIZATION_ID
, LOCATION_ID
, FACILITY_ID
, COMMODITY_ID1
, COMMODITY_ID2
, STOP_ID1
, STOP_ID2
, LANE_ID
, LANE_SET_ID
, OVER_UTILIZATION_NUMBER
, UNDER_UTILIZATION_NUMBER
, NUMBER_OF_LOADS
, CONTINUOUS_MOVE_ID
, TRIP_ID1
, TRIP_ID2
, NUMBER1
, NUMBER2
, NUMBER3
, NUMBER4
, NUMBER5
, DATE1
, DATE4
, DATE5
, DATE2
, DATE3
, CHAR1
, CHAR2
, CHAR3
, CHAR4
, CHAR5
, CREATED_BY
, CREATION_DATE
, LAST_UPDATED_BY
, LAST_UPDATE_DATE
, LAST_UPDATE_LOGIN
FROM MST.MST_EXCEPTION_DETAILS;
MST.MST_EXCEPTION_DETAILS does not reference any database object
MST.MST_EXCEPTION_DETAILS is referenced by following:
|
|
|