To define activity types:Lookup codes must be decided upon and defined during the implementation process. Lookup codes fall within three categories:
Extensible: Existing lookup codes cannot be modified, but you can add new codes to the table.
User-defined: All codes may be modified.
System-defined: Existing codes cannot be modified, and new codes cannot be added to the table.
You must define Asset Lookups, Work Request Lookups, and Work Order Lookups.
This section includes the following topics:
Activity types are used to describe the type of maintenance work that is performed on an asset (See: Defining Activities). For example, Inspections, Lubrications, Overhauls, Calibration, and Repetitive work. Activity types are extensible (See: Defining Lookups).
To define activity types:Navigate to the Oracle Manufacturing Lookups window.
Click the Find icon.
Select MTL_EAM_ACTIVITY_TYPE from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning of the code, for example, Lubrication.
Enter a Description for the code.
Optionally enter a Tag to categorize lookup values. This field is for informational purposes.
The Effective From Date defaults as the system date, but you can update this. Optionally enter a Effective To Date to indicate an expiration of the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Activity cause codes are reasons for an asset failure. For example, Preventive, Normal Wear, Rework, and Breakdown. This information enables you to understand the dynamics that affect an asset's ability to perform. They establish critical data that is used for reporting and analysis of asset failure causes and the frequency of such conditions. Asset cause codes are referenced when setting up an activity (See: Defining Activities). Activity cause codes are extensible (See: Defining Lookups).
To define activity cause codes:Navigate to the Oracle Manufacturing Lookups window.
Select MTL_EAM_ACTIVITY_CAUSE from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning of the code, for example, Breakdown.
Enter a Description for the code.
Optionally enter a Tag to categorize lookup values. This field is for information purposes.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date of the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Activity source codes are the reasons why activities are executed. For example, warranty compliance, OSHA compliance, or military specification requirements. Activity source codes are referenced when setting up an activity (See: Defining Activities). Activity source codes are extensible (See: Defining Lookups).
To define activity source codes:Navigate to the Oracle Manufacturing Lookups window.
Select MTL_EAM_ACTIVITY_SOURCE from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering of alpha codes causes database errors in the application.
Enter the Meaning of the code, for example, Breakdown.
Enter a Description for the code.
Optionally enter a Tag to categorize lookup values.
This field is for informational purposes.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration of the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Activity priority codes indicate asset activity priority levels, for example, Low, Medium, and High. Activity priorities are extensible (See: Defining Lookups).
To define activity priorities:Navigate to the Oracle Manufacturing Lookups window.
Select WIP_EAM_ACTIVITY_PRIORITY from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering of alpha codes causes database errors in the application.
Enter the Meaning of the code, for example, High.
Enter a Description.
Optionally enter a Tag to categorize lookup values. This field is for information purposes.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Failure is reported on a work order. Each work order represents one single failure occurrence (event) for the asset specified on the work order (See: Failure Analysis Overview). You can optionally add more codes, specifying different source types. For example, you may specify different types of work orders with different source types. Asset failure source types are user-defined (See: Defining Lookups).
To define asset failure source types:Navigate to the Oracle Manufacturing Lookups window.
Select EAM_ASSET_FAIL_SRC_TYPE from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning, for example, Preventive Maintenance Work Order.
Enter a Description.
Optionally enter a Tag to categorize lookup values.
This field is for informational purposes.
The Effective From Date defaults as the system date, but you can update this. Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
The eAM Asset Number Open Interface enables you to import asset numbers into eAM, using a batch process. You can optionally import asset number attributes. You can create new asset numbers and attributes, or update existing asset numbers and attributes. See eAM Asset Number Open Interface. Define the process' parameter scope codes. Asset import scope codes are user-defined (See: Defining Lookups).
To define asset import scope codes:Navigate to the Oracle Manufacturing Lookups window.
Select EAM_ASSET_IMPORT_SCOPE from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning, for example, With Attributes.
Enter a Description.
Optionally enter a Tag to categorize lookup values.
This field is for informational purposes.
The Effective From Date defaults as the system date, but you can update this field.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
The eAM Asset Number Open Interface enables you to import asset numbers into eAM, using a batch process. You can optionally import asset number attributes. You can create new asset numbers and attributes, or update existing asset numbers and attributes. See eAM Asset Number Open Interface. Define the process' import statuses. Asset import statuses are user defined (See: Defining Lookups).
To define asset import statuses:Navigate to the Oracle Manufacturing Lookups window.
Select EAM_ASSET_IMPORT_STATUS from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning, for example, Success.
Enter a Description.
Optionally enter a Tag to categorize lookup values.
This field is for informational purposes.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
You can define events, and associate them to work order statuses. A work order might require approvals or notifications at different stages of its lifecycle. Workflow automates this process. You can initiate Workflow to generate notifications, approvals, transactions, and update a work order status. These statuses are used within your customized workflow (See: Setting Up Oracle Workflow and Setting Up the Business Event System). Asset log user-defined events are user-defined (See: Defining Lookups).
To define asset log user-defined events:Navigate to the Oracle Manufacturing Lookups window.
Select EAM_USER_EVENTS from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning of the code.
Enter a Description.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
You can set up contact preferences. Contact preferences are extensible (See: Defining Lookups).
To define contact preferences codes:Navigate to the Oracle Manufacturing Lookups window.
Select WIP_EAM_CONTACT_PREFERENCE from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning of the code.
Enter a Description.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Cost category codes are used as the default for departments that do not have a cost category defined. Department costs are then posted to the appropriate cost elements. Valid values are Maintenance, Operations, Contract, and any other values that you might add within this extensible lookup table. See: Overview of eAM Cost Management.
To define cost category codes:Navigate to the Oracle Manufacturing Lookups window.
Select BOM_EAM_COST_CATEGORY from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning of the code, for example, High.
Enter a Description for the code.
Optionally enter a Tag to categorize lookup values.
This field is for informational purposes.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Criticality codes suggest the importance of an asset to an organization, for example, High and Low. An asset that has a direct impact on production or that is difficult to replace may be considered a critical asset. Asset criticality codes help you to determine the urgency of requested work. Asset criticality codes are referenced when defining an asset (See: Defining Asset Numbers). Asset Criticality Codes are extensible (See: Defining Lookups).
To define asset criticality codes:Navigate to the Oracle Manufacturing Lookups window.
Select MTL_EAM_ASSET_CRITICALITY from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Warning: Oracle recommends that you do not create more than 250 asset criticality codes in order to avoid performance issues.
Enter the Meaning of the code, for example, High.
Enter a Description for the code.
Optionally enter a Tag to categorize lookup values.
This field is for informational purposes.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Failure, cause, and resolution codes are organized into multiple tree structures called failure code sets, which are then assigned to asset groups. Each set provides asset group-specific information on the possible failures of an asset group, the possible causes of each failure, and the possible resolutions for each cause. Assets within an asset group inherit the assigned failure code set. At the work order level, failure tracking codes are entered to report a failure, its cause, and resolution. (See: Failure Analysis Overview). You can optionally update the meaning for the failure code types.
To define failure code types:Navigate to the Oracle Manufacturing Lookups window.
Select EAM_FAILURE_CODE_TYPE from the Type list of values.
Optionally update the Meaning, for example, Failure Code.
Enter a Description.
Optionally enter a Tag to categorize lookup values.
This field is for informational purposes.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
The Work Request Approval is the process of changing a work request status from Open to Awaiting Work Order. Maintenance work orders are linked to work requests with a status of Awaiting Work Order. If the Auto Approve check box is selected on the eAM Parameters page (See: Defining eAM Parameters) then work requests for that organization are created with an automatic status of Awaiting Work Order. If the check box is not selected, work requests are created with a status of Open. Any user who receives the notification (See: Defining Department Approvers) can change the work request status to Awaiting Work Order.
A plant or facility may need to include additional statuses. Currently, the workflow cannot be customized to work with user-defined work request statuses. However, work request approval statuses are extensible (See: Defining Lookups).
To define work request statuses:Navigate to the Oracle Manufacturing Lookups window.
Select WIP_EAM_WORK_REQ_STATUS from the Type list of values.
Optionally add codes to the pre-existing list of codes. The codes that are pre-existing cannot be deleted; however the meaning can be modified.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning of the code, for example, Open.
Enter a Description for the code.
Optionally enter a Tag to categorize lookup values. This field is for information purposes.
Optionally enter Effective From and To Dates to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Work request types describe and categorize work requests, for example, Manual, System, Routine, Capital, and Furniture. Work request types are extensible (See: Defining Lookups).
To define a work request type:Navigate to the Oracle Manufacturing Lookups window.
Select WIP_EAM_WORK_REQ_TYPE from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning of the code, for example, Manual.
Enter a Description for the code.
Optionally enter a Tag to categorize lookup values. This field is for informational purposes only.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Work order priority codes contribute to the organization and execution of work orders. For example, High, Medium, and Low, or 1,2, and 3, respectively. Typically, a priority is assigned by the people entering work requests and work orders. The planner or supervisor compares this priority to the asset criticality (See: Asset Criticality Codes). These codes are entered when creating activity associations, work orders, and work requests. Typically, a priority is assigned by the person that enters the work request and its related work order. Priority specified during activity association becomes the work order priority when a work order is created, using the activity association (See: Routine Work Orders and Work Requests). Work order priority codes are extensible (See: Defining Lookups).
To create work order priority codes:Navigate to the Oracle Manufacturing Lookups window.
Select WIP_EAM_ACTIVITY_PRIORITY from the Type list of values.
Optionally add additional codes to the pre-existing list of codes.
The codes that are pre-existing cannot be deleted; however, the Meaning can be modified.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning of the code, for example, High.
Enter a Description for the code.
Optionally enter a Tag to categorize lookup values. This field is for informational purposes only.
The Effective From Date defaults as the system date, but you can update this value.
Optionally enter a Effective To Date to indicate an expiration code for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Reconciliation codes detail how work orders and operations were completed. These codes usually fall within two categories: Completed as Planned or Partial Completion. You can further define the condition within these two types of completion statuses. These codes enable you to evaluate work orders by percentage completed or delayed, and if they were delayed, the reason for the delay. Reconciliation codes are extensible (See: Defining Lookups).
To define Work Order reconciliation codes:Navigate to the window.
Select WIP_EAM_RECONCILIATION_CODE from the Type list of values.
Enter a numeric Code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning of the code, for example, Fixed Completely.
Enter a Description for the code.
Optionally enter a Tag to categorize lookup values.
This field is for informational purposes.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.
Work order types enable you to differentiate work orders. For example, Routine, and Rebuild. Maintenance management can use this information to sort and monitor work activity for reporting and budgeting. Work order types are referenced in the activity and work order.
Work order types are created manually or automatically. For example, rebuildable work orders are created automatically or manually (See: Rebuild Work Orders). Preventive maintenance work orders are created automatically, based on meter readings (See: Preventive Maintenance Work Orders).
Work order types are extensible (See: Defining Lookups).
To define work order types:Navigate to the Oracle Manufacturing Lookups window.
Select WIP_EAM_WORK_ORDER_TYPE from the Type list of values.
Enter a numeric code.
Oracle recommends that you enter values in increments of 10, enabling you to easily add codes later.
Warning: Do not use alpha codes. Entering alpha codes causes database errors in the application.
Enter the Meaning of the code, for example, Routine.
Enter a Description for the code.
Optionally enter a Tag to categorize lookup values.
This field is for informational purposes.
The Effective From Date defaults as the system date, but you can update this.
Optionally enter a Effective To Date to indicate an expiration date for the code.
Select the Enabled check box to enable this code for Enterprise Asset Management.
Save your work.