My Oracle Support Banner

Apps.wip_eam_workrequest_pub.work_request_import API Does Not Work After Patch Implemention (Doc ID 2712394.1)

Last updated on SEPTEMBER 21, 2020

Applies to:

Oracle Enterprise Asset Management - Version 12.2.3 and later
Information in this document applies to any platform.

Symptoms


ACTUAL BEHAVIOR

After EAM Patch 24498252 was applied in a test environment. The API apps.wip_eam_workrequest_pub.work_request_import was tested and it did not work, when trying to submit it manually.
The thing is that the API generates the notification of the Work Request, but it does not generate the actual Work Request. We can see and open the notification, but when we open the details, it gives an error window (because non Work Request was created, the WR does not exist in WR table).

On the other hand, we tested other APIs, and they work.

The same API (apps.wip_eam_workrequest_pub.work_request_import) works in another test environment.


EXPECTED BEHAVIOR

Expect that the Work Request is generated along with the Notification

STEPS

The issue can be reproduced at will with the following steps:

1. After applying Patch 24498252 run the API apps.wip_eam_workrequest_pub.work_request_import
2. Notification is generated but actual Work Request is not

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.