My Oracle Support Banner

E1 13: 17: Creating a PM Work Order with a Future Projected Start Date Populates the F1307 WO History Status Start Date with the Future Date, Not the System Date (P12071, R12807) (Doc ID 2710749.1)

Last updated on NOVEMBER 16, 2020

Applies to:

JD Edwards EnterpriseOne Capital Asset Management - Version 9.2 to 9.2 [Release 9.2]
JD Edwards EnterpriseOne Service Management - Version 9.2 to 9.2 [Release 9.2]
Information in this document applies to any platform.

Symptoms

When creating an assigned PM work order from R12807, the work order status history (F1307) file has the projected date and time, not the system date and time, as expected.  If the work order history start date is written with a projected work order start date, when system date is expected, then if the projected WM order has any needed status changes, prior to the projected start date, these will be out of (system) date sequence.

Steps:  

  1. Enter named version of P17714 to use actual date for status change.
  2. Enter named version of P48201 to use named version of P17714.  
  3. Enter a future dated WM work order and then change the status, such as M to MA.  
  4. Review the status history and note that the status history record for M status shows system date as the from date.  OK so far.  
  5. Enter a asset record and assign a PM service that is date based, such a 28 day interval.
  6. Create an asset specific maintenance rule and run R12807 to create a future dated assigned work order.  
  7. Optionally advance the assigned work order status as of a date prior to the projected start date.
  8. Review the work order status history, making note of the history record start date.

Changes

 

Cause

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

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


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