Enable the My Maintenance Work Page

Oracle Fusion Cloud Maintenance lets you execute work orders in the Maintenance Dispatch List and My Maintenance Work pages.

In general, work orders can only be executed after they are created, edited, and released for work execution. Both the Maintenance Dispatch List and My Maintenance Work pages provide slightly different capabilities. Analyze your business processes before choosing the page you plan to use for work order reporting and completion. Additional details, including a comparison of functionality is covered in the Execute My Maintenance Work chapter of the Using Maintenance guide.

Note: Maintenance Dispatch List does not support repairing multiple assets in a single item-based work order. The return to inventory capability and the ability to complete all work order operations out-of-sequence are also not supported. These capabilities are only available in the My Maintenance Work page.

To enable the My Maintenance Work page:

• Set the profile option ORA_MNT_DISPATCH_LIST_REDWOOD_ENABLED to Y at the site level. This disables the task Maintenance Dispatch List and enables the task My Maintenance Work in the Maintenance Management landing page.

• Ensure that users have the existing dispatch list privileges:
  • Review Maintenance Dispatch List
  • MNT_REVIEW_MAINTENANCE_DISPATCH_LIST_PRI

• Ensure that users have security access to each maintenance organization for which they need to report maintenance.

• Run the initial bulk ingestion of work orders and schedule routine bulk ingestion updates, as described in the rest of this section.

After you enable the profile option, you need to enable the Oracle Search Extension Framework to create indexes, ingest predefined indexes, and manage search capabilities:

• Set the Enable/Disable Search Ext Framework (ORA_FND_SEARCH_EXT_ENABLED) profile option to Yes.

• Make sure that you have the Manage Scheduled Job Definition (FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV) privilege to run scheduled processes.

• Submit the scheduled process to create the index definition and perform initial ingest to the OSCS process for creating indexes and ingesting predefined indexes.
  • Job Name: ESS job to create index definition and perform initial ingest to OSCS.
  • Index Name to Reingest: fa-alm-work-order-asset

Note: If you don't specify any index names when submitting the process, the process runs for all predefined indexes.

Tips and Considerations

The following tips and considerations apply when enabling the My Maintenance Work page:

• Make sure to submit the scheduled process to create index definition and perform initial ingest to OSCS before using this feature. You can also submit the process if the index is already created, and you want to ingest it again. This process clears the index and reingests the data.
  • Program name: ESS job to create index definition and perform initial ingest to OSCS.
  • Index Name to Reingest: fa-alm-work-order-asset.

• Work orders can be created using the Manage Maintenance Work Orders page in the Maintenance Management work area, using REST APIs, from maintenance programs, and created or updated using File-Based Data Import (FBDI). Not all modes of work order creation trigger the near real-time ingest of the index. Therefore, you will need to update the index by running a separate scheduled process. This scheduled process doesn't clear the index, but only updates the existing index with the changes from these transactions. We recommend that you ingest these updates at least once a day, or as often as your business requires, to keep the index current.
  • Program Name to Run Bulk Ingest: ESS job to run Bulk ingest to OSCS.
  • Index Name to Reingest: MNT_WO_BULK_INGEST.

Note: If you are a US Government customer, don't enable this Oracle Search Extension Framework and don't enable the opt-in for this feature. You must use the Maintenance Dispatch List page instead.