EGO_ITEM_PUB.process_items API When Updating Existing Items Does Not Return All Errors
(Doc ID 2617953.1)
Last updated on AUGUST 15, 2021
Applies to:Oracle Product Hub - Version 12.2.8 and later
Information in this document applies to any platform.
On : 12.2.8 version, Catalog items
When using the EGO_ITEM_PUB.process_items API to update existing items, some failed master/child org imports do not display any errors.
When this problem occurs, the call to EGO_ITEM_PUB.process_items correctly returns an "E" for x_return_status, and it returns a positive value for x_msg_count. BUT, the call to error_handler.get_message_count(), which should contain the error itself, returns 0 - and there are no errors to return from error_handler.get_message.
However - note that if we query mtl_interface_errors before rolling back, we can see the errors that should've been returned. But, because there's no direct tie between the ego_item_pub.process_items call and mtl_interface_errors rows, there's no way to directly get the true errors in this case. This is a serious problem because the user who is trying to send item data into EBS has no idea what the real error was and cannot correct it.
(No errors) , though expect correct errors to be returned if there are any.
The issue can be reproduced at will with the following steps:
1. Update two items using API , See that first one errors, second one passes. User expects errors to be returned for the failed item, but sees none.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document