Wrong Unit Configuration Displayed After Creating Unassociated Task in Visit (With Defined Sub-Unit Configuration)
Last updated on JANUARY 29, 2018
Applies to:Oracle Complex Maintenance, Repair & Overhaul - Version 12.2.3 and later
Information in this document applies to any platform.
In Visit Work Package, creating a Unit Configuration (UC) with a defined Sub-Unit Configuration.
Now, when Visit was created and added the two unassociated tasks ie. one regards the position “CRH380A” in father unit config as the object and the other regards the position ”CRH380A_M1” which is the head of the sub unit config (see below) :
As shown in the above, Task 09’s Unit Configuration was displayed as CTH380A-A-6002 … but when Task 09 was being created, CHR380A-A-M1-0002 was used (as selected from the LOV). Expecting the value displayed to be CHR380A-A-M1-0002.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms