MNT_WORK_REQUIREMENTS_B
This table stores the detailed work requirements specifiec to the maintenance program business object. Maintenance program is a preventive maintenance plan that is to be executed at a regular periodic schdeuld or based on the usage of the asset or when a condition of the asset is detected for one or more maintainable assets. Work requirement details the assets to be used in the realization of the forecast based on schedules, usages, or conditions.
Details
-
Schema: FUSION
-
Object owner: MNT
-
Object type: TABLE
-
Tablespace: Default
Primary Key
Name | Columns |
---|---|
MNT_WORK_REQUIREMENTS_B_PK |
REQUIREMENT_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
REQUIREMENT_ID | NUMBER | 18 | Yes | The unique system generated identifier for the work requirement. | |
OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
ORGANIZATION_ID | NUMBER | 18 | Yes | The organization identifier. This is the maintenance organization in which the maintenance program is authored. | |
PROGRAM_ID | NUMBER | 18 | Yes | Foreign key to the maintenance program identifier. | |
REQUIREMENT_TYPE_CODE | VARCHAR2 | 30 | Yes | This requirement is done at the asset level or at the item level is designated by this value. The valid values are 'Asset' or 'Item'. | |
ITEM_ID | NUMBER | 18 | Yes | Foreign key to the inventory item. | |
ASSET_ID | NUMBER | 18 | Foreign key reference to the Asset business object. | ||
STATUS_CODE | VARCHAR2 | 30 | The status of the maintenance work requirements. The valid statuses are Draft and Active. | ||
FORECAST_USING_CYCLE_FLAG | VARCHAR2 | 1 | Yes | Flag indicating whether the requirement is to be forecasted using a cycle of patterns either for the schedule or meter based requirement. | |
INTERVALS_IN_THE_CYCLE | NUMBER | Intervals in the cycle of patterns. How many intervals are to be considered in the cycle. And varying work definitions can be specified to be picked up in the nth interval. | |||
CALENDAR_BASED_FLAG | VARCHAR2 | 1 | Yes | Flag indicating whether this requirement is going to be used for a periodic calendar based forecasting. | |
METER_BASED_FLAG | VARCHAR2 | 1 | Yes | Flag indicating whether this requirement is going to be used for a usage based forecasting. Usage is drawn from the readings on the meter tied to the asset. | |
CONDITION_BASED_FLAG | VARCHAR2 | 1 | Yes | Flag indicating whether this requirement is going to be used for a condition based work order creation. A condition of the asset will be used in driving the work definition to be picked up for the creation of the adhoc work. | |
DAY_BASED_FLAG | VARCHAR2 | 1 | Indicates the method to forecast is a Day Interval. | ||
NUMBER_OF_DAYS | NUMBER | Indicates the number of days between cycle intervals in the forecast. This is used in the day based forecast. | |||
NEXT_FORECAST_DUE_BY_CODE | VARCHAR2 | 30 | Indicates if next due uses the Base Interval or the Last Service of a work order. | ||
ASSET_HISTORY_SERVICE_DATE | DATE | Used for Asset based work requirements to indicate the last date in which the work was accomplished from an external system. This is just captured one time at the setting up of the program for the first time for this asset. | |||
ASSET_HISTORY_SERVICE_INTERVAL | NUMBER | Used for Asset based work requirements to indicate the last interval in a cycle which the work was accomplished from an external system. | |||
ASSET_INCLUSION_TYPE_CODE | VARCHAR2 | 30 | Indicates if the Assets are Implicitly or Explicitly covered by the work requirement. Values are Automatically or Manually. | ||
SCHEDULE_PATTERN_ID | NUMBER | 18 | The foreign key reference to the schedule pattern. | ||
ACTIVE_START_DATE | DATE | The effectivity start date of the work requirement. | |||
ACTIVE_END_DATE | DATE | The effectivity end date of the work requirement. | |||
SUPPRESS_MERGE_CODE | VARCHAR2 | 30 | The attribute indicates whether the work definitions are suppressed or merged when forecasts are generated on the same scheduled date. | ||
SUPPRESS_MERGE_OVERRIDE_FLAG | VARCHAR2 | 1 | Yes | This flag indicates whether the program level concurrent requirements are overriden at the work requirement level. | |
LAST_FORECAST_DATE | DATE | The date when the forecast was run last for this maintenance program. | |||
MODIFIED_FLAG | VARCHAR2 | 1 | Yes | The flag indicating whether the Maintenance Program has become dirty after a forecast generation was already run. | |
NEXT_WORK_ORDER_ONLY_FLAG | VARCHAR2 | 1 | Yes | Flag indicating that the work order generation program only generates the very next work order to the already forecasted and completed work order in the work order creation horizon. The other occurances of forecasts that are to be converted as work orders will be ignored. | |
REQUIREMENT_REFERENCE | VARCHAR2 | 120 | A reference captured from another third party application. | ||
REQUIREMENT_REFERENCE_ID | NUMBER | 18 | A reference identifier captured from another third party application. | ||
FORECAST_WINDOW_IN_DAYS | NUMBER | 9 | The number of days to be considered for the forecast window. | ||
WORK_ORDER_WINDOW_IN_DAYS | NUMBER | 9 | The number of days to be considered for the work order window. | ||
CREATE_WORK_ORDER_OPTION_CODE | VARCHAR2 | 30 | The mode in which the work order is created from the forecast. Is it automatically or via a manual process. | ||
WORK_ORDER_STATUS_ID | NUMBER | 18 | Represents the internal identifier of the user-defined status of the work order. | ||
WORK_ORDER_PRIORITY | NUMBER | The priority of the work order that is to be created from this requirement. | |||
FIRM_PLANNED_FLAG | VARCHAR2 | 1 | Flag to allow or prevent Planning from suggesting rescheduling and re-planning recommendations with respect to the Work Order. When the flag is on, this work order will not be considered by MRP to reschedule or re-plan. | ||
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
REQUEST_ID | NUMBER | 18 | Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row. | ||
JOB_DEFINITION_NAME | VARCHAR2 | 100 | Enterprise Service Scheduler: indicates the name of the job that created or last updated the row. | ||
JOB_DEFINITION_PACKAGE | VARCHAR2 | 900 | Enterprise Service Scheduler: indicates the package name of the job that created or last updated the row. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
MNT_WORK_REQUIREMENTS_B_N01 | Non Unique | Default | PROGRAM_ID |
MNT_WORK_REQUIREMENTS_B_N02 | Non Unique | Default | ORGANIZATION_ID |
MNT_WORK_REQUIREMENTS_B_N03 | Non Unique | Default | REQUIREMENT_REFERENCE_ID, REQUIREMENT_REFERENCE |
MNT_WORK_REQUIREMENTS_B_U01 | Unique | Default | REQUIREMENT_ID |