Warranty Active And Warranty Expiration Date Inconsistent Functionality
(Doc ID 1543796.1)
Last updated on FEBRUARY 24, 2019
Applies to:Oracle Enterprise Asset Management - Version 12.1.3 and later
Information in this document applies to any platform.
***Checked for relevance on 02-March-2015***
On Application Release 12.1.3, under Maintenance Super User responsibility:
It was found that there is an inconsistent behavior when creating work orders from either Work orders page or from Asset : Capital page, with reference to how Warranty Active flag is being set.
Relevant example is provided for work orders created for asset number , which has an warranty expiration date in the future (i.e. 31-DEC-2013);
- for work order 1, created from the Work Orders tab, the Warranty Active is set to YES and Warranty Expiration Date = 31-DEC-2013;
- for work order 2, created from Asset: Capital tab, the Warranty Active is set to NO and Warranty Expiration Date = 31-DEC-2013;
Expected to have the same behavior for work order creation process, regardless the method/source of creating the work order.
More specifically, for given case, the Warranty Active flag should also be set to YES whenever work order is created from Asset:Capital page.
The issue can be reproduced at will with the following steps:
1. Under Maintenance Super User responsibility:
2.1. Create a new work order for asset number from Work Orders tab
2.2. Create a new work order for asset number from Asset Capital tab.
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