My Oracle Support Banner

Data Fix Script To Close CMRO Workorders (Doc ID 2331313.1)

Last updated on MARCH 12, 2021

Applies to:

Oracle Complex Maintenance, Repair, & Overhaul - Version 12.1.3 and later
Information in this document applies to any platform.


Workorder status should always be in sync in CMRO, EAM and WIP side. 

There are chances that CMRO Work orders are supposed to be closed but they are not
(e.g. due to data corruption).

We recommend customer to try to close the Workorders from CMRO UIs first.
Alternatively, customer may run following concurrent programs to Close the
1. Close Discrete Jobs
2. Close Work Order Sync Program

These programs are expected to work as follows;
"Close Discrete Jobs" will update the status (12) and entity type(7) in WIP
tables to close work orders and then concurrent "Close Work Order Sync
Program" will update work order statuses in CMRO tables.

Note: If 'Close Discrete Jobs' is not updating the work order status in
WIP_DISCRETE_JOBS table and entity type in WIP_ENTITIES, "Close Work Order
Sync Program" will not close the work orders in CMRO tables. In that case,
examine parameters entered for "Close Discrete Jobs" concurrent program and
its outputs (View Log and View Output).

We will try the data fix script as last resort, which is used when there
already have been data corruption or in some other special conditions.



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.