APPS.PV_OPPTY_ROUTING_LOG dependencies on PV_LOOKUPS

Line 63: pv_lookups plkp1

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
67: --and ldwf.WF_ITEM_TYPE <> 'PVLEADAS'

Line 137: pv_lookups plkp1,

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
141: logs.oppty_routing_log_id= pc_oppty_routing_log_id

Line 138: pv_lookups plkp2

134:
135: from
136: pv_oppty_routing_logs logs,
137: pv_lookups plkp1,
138: pv_lookups plkp2
139:
140: where
141: logs.oppty_routing_log_id= pc_oppty_routing_log_id
142: and plkp1.lookup_type (+) = 'PV_ASSIGNMENT_STATUS'

Line 157: pv_lookups plkp1,

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
161: logs.oppty_routing_log_id= pc_oppty_routing_log_id

Line 158: pv_lookups plkp2

154:
155: from
156: pv_oppty_routing_logs logs,
157: pv_lookups plkp1,
158: pv_lookups plkp2
159:
160: where
161: logs.oppty_routing_log_id= pc_oppty_routing_log_id
162: and plkp1.lookup_type (+) = 'PV_ASSIGNMENT_STATUS'