eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.WIP_EAM_WORKREQUEST_PUB dependencies on WIP_EAM_WORK_REQUESTS

Line 50: * @param p_work_request_rec This is a PL QL record type, it is a ROWTYPE of WIP_EAM_WORK_REQUESTS table

46: * @param x_return_status Return status of the procedure call
47: * @param x_msg_count Count of the return messages that API returns
48: * @param x_msg_data The collection of the messages.
49: * @param p_mode The flag indicating the operation is CREATE or UPDATE
50: * @param p_work_request_rec This is a PL QL record type, it is a ROWTYPE of WIP_EAM_WORK_REQUESTS table
51: * @param p_request_log This is a reqest log for the current work request, if this is null, it is same as the work request description
52: * @param p_user_id The user who creates / updates the work request
53: * @param x_work_request_id This is the unique identifier of newly created work request record.
54: * @scope public

Line 65: p_work_request_rec in WIP_EAM_WORK_REQUESTS%ROWTYPE,

61: p_init_msg_list in VARCHAR2 := FND_API.G_FALSE,
62: p_commit in VARCHAR2 := FND_API.G_TRUE,
63: p_validation_level in NUMBER := FND_API.G_VALID_LEVEL_FULL,
64: p_mode in VARCHAR2,
65: p_work_request_rec in WIP_EAM_WORK_REQUESTS%ROWTYPE,
66: p_request_log in VARCHAR2,
67: p_user_id in NUMBER,
68: x_work_request_id out NOCOPY NUMBER,
69: x_return_status out NOCOPY VARCHAR2,