Wrong Unit Configuration Displayed After Creating Unassociated Task in Visit (With Defined Sub-Unit Configuration) (Doc ID 2017260.1)

Last updated on SEPTEMBER 06, 2016

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) :


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 hundreds of Community platforms