[Home] [Help] [Dependency Information]
Object Name: | PV_OPPTY_ROUTING_LOGS |
---|---|
Object Type: | TABLE |
Owner: | PV |
FND Design Data: | PV.PV_OPPTY_ROUTING_LOGS |
Subobject Name: | |
Status: | VALID |
This table is used to store the opportunity routing history. Thsi is consolidated table where we store the entire opportuniy assignment/routing logging history.
Tablespace: | APPS_TS_TX_DATA |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
PV_OPPTY_ROUTING_LOGS_N1 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX | LEAD_ASSIGNMENT_ID |
PV_OPPTY_ROUTING_LOGS_N2 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX | LEAD_ID |
PV_OPPTY_ROUTING_LOGS_N3 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX | LEAD_WORKFLOW_ID |
PV_OPPTY_ROUTING_LOGS_U1 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX | OPPTY_ROUTING_LOG_ID |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
OPPTY_ROUTING_LOG_ID | NUMBER | Yes | primary kay of the table | |
EVENT | VARCHAR2 | (15) | Yes | The opportunity routing/assignment event |
LEAD_ID | NUMBER | Yes | Opportunity Id | |
LEAD_WORKFLOW_ID | NUMBER | Yes | lead_workflow_id from pv_lead_workflows table | |
ROUTING_TYPE | VARCHAR2 | (30) | Type of the routing done for the opportunity | |
LATEST_ROUTING_FLAG | VARCHAR2 | (1) | Yes | Latest routing flag which describes if it is latest routing log row or not incase of multiple routings done on opportunity |
BYPASS_CM_FLAG | VARCHAR2 | (1) | This flag describes if the routing is done by-passing Channel Manager or not. | |
LEAD_ASSIGNMENT_ID | NUMBER | Lead Assignment Id from pv_lead_assignments table | ||
EVENT_DATE | DATE | Yes | Routing Event Date | |
VENDOR_USER_ID | NUMBER | User Id of the Vendor who involves in the routing/assignment action | ||
PT_CONTACT_USER_ID | NUMBER | User Id of the Partner Contact who involves in the routing action from partner side | ||
USER_RESPONSE | VARCHAR2 | (30) | User Response of the Partner Contact who involves in the routing action from partner side | |
REASON_CODE | VARCHAR2 | (30) | A reason for the partner user Response if the routing action is from partner side | |
USER_TYPE | VARCHAR2 | (60) | Type of the user who is responsible for routing/assignment action | |
VENDOR_BUSINESS_UNIT_ID | NUMBER | Vendor Business Unit |
Cut, paste (and edit) the following text to query this object:
SELECT OPPTY_ROUTING_LOG_ID
, EVENT
, LEAD_ID
, LEAD_WORKFLOW_ID
, ROUTING_TYPE
, LATEST_ROUTING_FLAG
, BYPASS_CM_FLAG
, LEAD_ASSIGNMENT_ID
, EVENT_DATE
, VENDOR_USER_ID
, PT_CONTACT_USER_ID
, USER_RESPONSE
, REASON_CODE
, USER_TYPE
, VENDOR_BUSINESS_UNIT_ID
FROM PV.PV_OPPTY_ROUTING_LOGS;
PV.PV_OPPTY_ROUTING_LOGS does not reference any database object
PV.PV_OPPTY_ROUTING_LOGS is referenced by following:
|
|
|