FNDLOAD is not Replacing the Existing Lookup Type and is Creating a New Record
Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Application Object Library - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
When trying to modify a Lookup Type using FNDLOAD with CUSTOM_MODE=FORCE, it is not replacing
the existing Lookup Type and is creating a new record with the modified Lookup Type information,
ending up with two records.
For example, there is a record in Application Object Library Lookups form (FNDLVMLU) as below:
There will have a new record created in Application Object Library Lookups (FNDLVMLU) form,
ending up with Lookup Type=XXTEST1 and Lookup Type=XXTEST1_NEW records.
How to correct this?
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