Import EAM Asset Number (EAMANIMP) Not Importing Asset Numbers And Attribute Values
Last updated on AUGUST 21, 2017
Applies to:Oracle Enterprise Asset Management - Version 12.1.3 and later
Information in this document applies to any platform.
The Import EAM Asset Number (EAMANIMP) process does not import asset numbers and attribute values. The following error is seen in mtl_eam_asset_num_interface and mtl_eam_attr_val_interface tables.
Asset numbers and attribute values can be added using the "Define Asset Number" form. So, there issue only occurs when using the Import process.
PROCESS_FLAG = E
ERROR_CODE = 300
ERROR_MESSAGE = Failed because Extensible Attributes import failed
ERROR_NUMBER = 9999
ERROR_MESSAGE = Program error. Please inform your support representative that the descriptive flexfields server validation function has been called incorrectly. The segment ids for column C_ATTRIBUTE3 of type V were not initialized using FND_FLEX_DESCVAL.SET_COLUMN_VALUE() prior to calling FND_FLEX_DESCVAL.VALIDATE_DESCCOLS(). The error is either in a form, or in a server-side package that calls the descriptive flexfields validation routine.
The issue can be reproduced at will with the following steps:
1. Responsibility: Enterprise Asset Management
2. Run Import EAM Asset Number (EAMANIMP)
3. Find errors in both mtl_eam_asset_num_interface & mtl_eam_attr_val_interface tables
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