APPS.OKL_KRP_PVT dependencies on FND_MSG_PUB

Line 57: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;

53: px_error_rec IN OUT NOCOPY OKC_API.ERROR_REC_TYPE,
54: px_error_tbl IN OUT NOCOPY OKC_API.ERROR_TBL_TYPE) IS
55:
56: j INTEGER := NVL(px_error_tbl.LAST, 0) + 1;
57: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;
58: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
59: BEGIN
60: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
61: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the

Line 58: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;

54: px_error_tbl IN OUT NOCOPY OKC_API.ERROR_TBL_TYPE) IS
55:
56: j INTEGER := NVL(px_error_tbl.LAST, 0) + 1;
57: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;
58: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
59: BEGIN
60: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
61: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the
62: -- message stack gets set to 1. This makes sense until we call FND_MSG_PUB.GET which

Line 60: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before

56: j INTEGER := NVL(px_error_tbl.LAST, 0) + 1;
57: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;
58: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
59: BEGIN
60: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
61: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the
62: -- message stack gets set to 1. This makes sense until we call FND_MSG_PUB.GET which
63: -- automatically increments the index by 1, (making it 2), however, when the GET function
64: -- attempts to pull message 2, we get a NO_DATA_FOUND exception because there isn't any

Line 61: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the

57: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;
58: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
59: BEGIN
60: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
61: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the
62: -- message stack gets set to 1. This makes sense until we call FND_MSG_PUB.GET which
63: -- automatically increments the index by 1, (making it 2), however, when the GET function
64: -- attempts to pull message 2, we get a NO_DATA_FOUND exception because there isn't any
65: -- message 2. To circumvent this problem, check the amount of messages and compensate.

Line 62: -- message stack gets set to 1. This makes sense until we call FND_MSG_PUB.GET which

58: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
59: BEGIN
60: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
61: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the
62: -- message stack gets set to 1. This makes sense until we call FND_MSG_PUB.GET which
63: -- automatically increments the index by 1, (making it 2), however, when the GET function
64: -- attempts to pull message 2, we get a NO_DATA_FOUND exception because there isn't any
65: -- message 2. To circumvent this problem, check the amount of messages and compensate.
66: -- Again, this error only occurs when 1 message is on the stack because COUNT_AND_GET

Line 69: l_msg_idx := FND_MSG_PUB.G_FIRST;

65: -- message 2. To circumvent this problem, check the amount of messages and compensate.
66: -- Again, this error only occurs when 1 message is on the stack because COUNT_AND_GET
67: -- will only update the index variable when 1 and only 1 message is on the stack.
68: IF (last_msg_idx = 1) THEN
69: l_msg_idx := FND_MSG_PUB.G_FIRST;
70: END IF;
71: LOOP
72: fnd_msg_pub.get(
73: p_msg_index => l_msg_idx,

Line 72: fnd_msg_pub.get(

68: IF (last_msg_idx = 1) THEN
69: l_msg_idx := FND_MSG_PUB.G_FIRST;
70: END IF;
71: LOOP
72: fnd_msg_pub.get(
73: p_msg_index => l_msg_idx,
74: p_encoded => fnd_api.g_false,
75: p_data => px_error_rec.msg_data,
76: p_msg_index_out => px_error_rec.msg_count);