APPS.PV_OPPTY_ROUTING_LOG dependencies on PV_OPPTY_ROUTING_LOG

Line 1: PACKAGE BODY PV_OPPTY_ROUTING_LOG as

1: PACKAGE BODY PV_OPPTY_ROUTING_LOG as
2: /* $Header: pvxvorlb.pls 120.1 2006/03/10 15:02:31 amaram noship $ */
3: -- ===============================================================
4: -- Start of Comments
5: -- Package name

Line 6: -- PV_OPPTY_ROUTING_LOG

2: /* $Header: pvxvorlb.pls 120.1 2006/03/10 15:02:31 amaram noship $ */
3: -- ===============================================================
4: -- Start of Comments
5: -- Package name
6: -- PV_OPPTY_ROUTING_LOG
7: -- Purpose
8: --
9: -- History
10: --

Line 17: G_PKG_NAME CONSTANT VARCHAR2(30):= 'PV_OPPTY_ROUTING_LOG';

13: -- End of Comments
14: -- ===============================================================
15:
16:
17: G_PKG_NAME CONSTANT VARCHAR2(30):= 'PV_OPPTY_ROUTING_LOG';
18: G_FILE_NAME CONSTANT VARCHAR2(12) := 'pvxvorlb.pls';
19:
20: G_USER_ID CONSTANT NUMBER := NVL(FND_GLOBAL.USER_ID, -1);
21: G_LOGIN_ID CONSTANT NUMBER := NVL(FND_GLOBAL.CONC_LOGIN_ID, -1);

Line 62: pv_oppty_routing_logs logs,

58: pv_lead_assignments assgn,
59: pv_lead_workflows ldwf,
60: pv_partner_profiles partprof,
61: hz_parties party,
62: pv_oppty_routing_logs logs,
63: pv_lookups plkp1
64: WHERE
65: logs.oppty_routing_log_id= pc_oppty_routing_log_id
66: and ldwf.lead_workflow_id= logs.lead_workflow_id

Line 136: pv_oppty_routing_logs logs,

132: plkp1.meaning response_meaning,
133: plkp2.meaning reason_meaning
134:
135: from
136: pv_oppty_routing_logs logs,
137: pv_lookups plkp1,
138: pv_lookups plkp2
139:
140: where

Line 156: pv_oppty_routing_logs logs,

152: plkp1.meaning response_meaning,
153: plkp2.meaning reason_meaning
154:
155: from
156: pv_oppty_routing_logs logs,
157: pv_lookups plkp1,
158: pv_lookups plkp2
159:
160: where

Line 316: END PV_OPPTY_ROUTING_LOG;

312:
313:
314:
315:
316: END PV_OPPTY_ROUTING_LOG;