[Home] [Help]
2363: * of Trips upgraded successfully and the number of Trips failed to be upgraded
2364: * because of possible overlap with existing trips. Note that this message is
2365: * not put in the Message Stack. So API users should not rely on the value of
2366: * x_msg_data to determine whether the API failed or not. Rather they should
2367: * rely only on standard way of checking x_return_status.
2368: *
2369: * @param p_api_version API Version (1.0)
2370: * @param p_init_msg_list Initialize Message List
2371: * @param p_commit Commits the Database
3832: , p_resource_tbl => l_resources_tbl
3833: , x_request_id => l_sched_request_id
3834: );
3835:
3836: -- Standard check of the return status for the API call
3837: IF x_return_status = fnd_api.g_ret_sts_error THEN
3838: RAISE fnd_api.g_exc_error;
3839: ELSIF x_return_status = fnd_api.g_ret_sts_unexp_error THEN
3840: RAISE fnd_api.g_exc_unexpected_error;
4813: x_msg_data Varchar2(2000);
4814: BEGIN
4815:
4816:
4817: -- Standard call to check for call compatibility.
4818: IF NOT FND_API.Compatible_API_Call (l_api_version ,
4819: p_api_version ,
4820: l_api_name ,
4821: G_PKG_NAME )
4885: X_RETURN_STATUS Varchar2(10);
4886:
4887: BEGIN
4888:
4889: -- Standard call to check for call compatibility.
4890: IF NOT FND_API.Compatible_API_Call (l_api_version ,
4891: p_api_version ,
4892: l_api_name ,
4893: G_PKG_NAME )