Import Non Visible Multilist Value Ends in Fatal Exception Occured Error (Doc ID 2163438.1)

Last updated on FEBRUARY 16, 2017

Applies to:

Oracle Agile PLM Framework - Version 9.3.3.0 to 9.3.5.0 [Release 9.3]
Information in this document applies to any platform.

Symptoms

Actual Behavior
When some subclass Page Two Multilist attribute visible flag is set to Yes while other subclass have Page Two Multilist attribute visible flag set to No,
when and source import file(excel file) has subclass (Page Two Multilist attribute visible flag set to No) with Page Two Multilist attribute set, import ends with the following error.

Error
Fatal Exception occured

Step to Reproduce

  1. Login to Java Client and set Parts class Page 2 Multilist01 visible flag set to Yes.
    For Subclass under Parts class, Subclass : Part set Page 2 Multilist01 visible flag set to Yes. For Subclass : Part2 set Page 2 Multilist01 visible flag set to No.

    Item
       +---- Parts
                      +---- Part
                      +---  Part2

  2. Login to Web Client
  3. Tools and Settings > Import
  4. Specify excel file as import source file. Following data is set to excel sheet.

    Number Part Type MultiList01
    YO0608 Part2 1;2
  5. Press Preferences button and set Default Types

    Default Part Type : Part2

  6. Save
  7. Set the following

    Item Only : check
    Define attribute mapping in next step  : check
    No transformations are necessary  : check
    Updates do not require redlining  : check

  8. Map Number ,Part Type, MultiList01
  9. Run import and confirm the error

    Fatal Exception occured -1




Cause

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