DBA Data[Home] [Help]

APPS.OKL_DRA_PVT dependencies on FND_MSG_PUB

Line 11: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;

7: PROCEDURE load_error_tbl (
8: px_error_rec IN OUT NOCOPY OKL_API.ERROR_REC_TYPE,
9: px_error_tbl IN OUT NOCOPY OKL_API.ERROR_TBL_TYPE) IS
10: j INTEGER := NVL(px_error_tbl.LAST, 0) + 1;
11: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;
12: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
13:
14: BEGIN
15:

Line 12: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;

8: px_error_rec IN OUT NOCOPY OKL_API.ERROR_REC_TYPE,
9: px_error_tbl IN OUT NOCOPY OKL_API.ERROR_TBL_TYPE) IS
10: j INTEGER := NVL(px_error_tbl.LAST, 0) + 1;
11: last_msg_idx INTEGER := FND_MSG_PUB.COUNT_MSG;
12: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
13:
14: BEGIN
15:
16: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before

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

12: l_msg_idx INTEGER := FND_MSG_PUB.G_NEXT;
13:
14: BEGIN
15:
16: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
17:
18: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the
19:
20: -- message stack gets set to 1. This makes sense until we call FND_MSG_PUB.GET which

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

14: BEGIN
15:
16: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
17:
18: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the
19:
20: -- message stack gets set to 1. This makes sense until we call FND_MSG_PUB.GET which
21:
22: -- automatically increments the index by 1, (making it 2), however, when the GET function

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

16: -- FND_MSG_PUB has a small error in it. If we call FND_MSG_PUB.COUNT_AND_GET before
17:
18: -- we call FND_MSG_PUB.GET, the variable FND_MSG_PUB uses to control the index of the
19:
20: -- message stack gets set to 1. This makes sense until we call FND_MSG_PUB.GET which
21:
22: -- automatically increments the index by 1, (making it 2), however, when the GET function
23:
24: -- attempts to pull message 2, we get a NO_DATA_FOUND exception because there isn't any

Line 34: l_msg_idx := FND_MSG_PUB.G_FIRST;

30: -- will only update the index variable when 1 and only 1 message is on the stack.
31:
32: IF (last_msg_idx = 1) THEN
33:
34: l_msg_idx := FND_MSG_PUB.G_FIRST;
35:
36: END IF;
37:
38: LOOP

Line 40: fnd_msg_pub.get(

36: END IF;
37:
38: LOOP
39:
40: fnd_msg_pub.get(
41:
42: p_msg_index => l_msg_idx,
43:
44: p_encoded => fnd_api.g_false,