Create Equipment Move API Incorrectly Assigns Task To User Who Runs Job (Doc ID 2177214.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Yard Management - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

When creating an equipment move via API YMS_TRANSACTION_PUB.CREATE_EQUIPMENT_MOVE the user who runs the job becomes the person assigned to the move task:

The API does not contain an input variable for the assigned user.

during the course of processing, the procedure API YMS_TRANSACTION_PUB.CREATE_EQUIPMENT_MOVE calls YMS_MOVE_TASK_PVT.CREATE_EQUIPMENT_MOVE. When doing so, the parameter p_user_id => fnd_global.user_id is passed.


YMS_MOVE_TASK_PVT.CREATE_EQUIPMENT_MOVE uses p_user_id as an IN parameter. The default for this parameter is NULL. During the course of processing, the procedure checks to see if p_user_id is null. if not null, then the procedure assigns the task to the passed p_user_id, which in this case is the person who ran the original API. This causes an incorrect assignment of the task.


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