APPS.OKC_RLD_PVT dependencies on FND_MSG_PUB

Line 20: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;

16: px_error_rec IN OUT NOCOPY OKC_API.ERROR_REC_TYPE,
17: px_error_tbl IN OUT NOCOPY OKC_API.ERROR_TBL_TYPE) IS
18:
19: j INTEGER := NVL(px_error_tbl.LAST, 0) + 1;
20: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;
21: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
22: BEGIN
23: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
24: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the

Line 21: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;

17: px_error_tbl IN OUT NOCOPY OKC_API.ERROR_TBL_TYPE) IS
18:
19: j INTEGER := NVL(px_error_tbl.LAST, 0) + 1;
20: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;
21: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
22: BEGIN
23: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
24: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the
25: -- message stack gets set to 1. This makes sense until we call FND_MSG_PUB.GET which

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

19: j INTEGER := NVL(px_error_tbl.LAST, 0) + 1;
20: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;
21: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
22: BEGIN
23: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
24: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the
25: -- message stack gets set to 1. This makes sense until we call FND_MSG_PUB.GET which
26: -- automatically increments the index by 1, (making it 2), however, when the GET function
27: -- attempts to pull message 2, we get a NO_DATA_FOUND exception because there isn't any

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

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

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

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

Line 32: l_msg_idx := FND_MSG_PUB.G_FIRST;

28: -- message 2. To circumvent this problem, check the amount of messages and compensate.
29: -- Again, this error only occurs when 1 message is on the stack because COUNT_AND_GET
30: -- will only update the index variable when 1 and only 1 message is on the stack.
31: IF (last_msg_idx = 1) THEN
32: l_msg_idx := FND_MSG_PUB.G_FIRST;
33: END IF;
34: LOOP
35: fnd_msg_pub.get(
36: p_msg_index => l_msg_idx,

Line 35: fnd_msg_pub.get(

31: IF (last_msg_idx = 1) THEN
32: l_msg_idx := FND_MSG_PUB.G_FIRST;
33: END IF;
34: LOOP
35: fnd_msg_pub.get(
36: p_msg_index => l_msg_idx,
37: p_encoded => fnd_api.g_false,
38: p_data => px_error_rec.msg_data,
39: p_msg_index_out => px_error_rec.msg_count);