APPS.QA_TCA_PKG dependencies on FND_API

Line 39: -- fnd_api.g_ret_sts_success if operation successfully completed.

35: --
36: -- p_batch_party_id is an internal TCA ID, unused in this procedure.
37: --
38: -- x_return_status will be
39: -- fnd_api.g_ret_sts_success if operation successfully completed.
40: -- fnd_api.g_ret_sts_unexp_error if there is any exception.
41: --
42:
43: CURSOR c IS

Line 40: -- fnd_api.g_ret_sts_unexp_error if there is any exception.

36: -- p_batch_party_id is an internal TCA ID, unused in this procedure.
37: --
38: -- x_return_status will be
39: -- fnd_api.g_ret_sts_success if operation successfully completed.
40: -- fnd_api.g_ret_sts_unexp_error if there is any exception.
41: --
42:
43: CURSOR c IS
44: SELECT qpc.plan_id

Line 54: x_return_status := fnd_api.g_ret_sts_success;

50:
51: BEGIN
52:
53: x_to_id := p_from_id;
54: x_return_status := fnd_api.g_ret_sts_success;
55:
56: --
57: -- We shall handle only HZ_PARTIES in QA_RESULTS.
58: --

Line 102: x_return_status := fnd_api.g_ret_sts_unexp_error;

98: WHEN OTHERS THEN
99: fnd_message.set_name('AR', 'HZ_MERGE_SQL_ERROR');
100: fnd_message.set_token('ERROR', sqlerrm);
101: fnd_msg_pub.add;
102: x_return_status := fnd_api.g_ret_sts_unexp_error;
103:
104: END party_merge;
105:
106: