[Home] [Help]
[Dependency Information]
Object Name: | PV_LEAD_ASSIGNMENTS |
---|---|
Object Type: | TABLE |
Owner: | PV |
FND Design Data: | ![]() |
Subobject Name: | |
Status: | VALID |
PV_LEAD_ASSIGNMENTS stores the lead assignment details. Three types of lead assignments are
handled, single, serial and parallel. If the lead assignment is of serial, the order is derived based on
the partners experties. If the lead assignment is parallel, the lead is offered to all the partners and
is assigned to the partner with a first come first served basis
Tablespace: | ![]() |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
PV_LEAD_ASSIGNMENTS_U1 | NORMAL | UNIQUE |
![]() |
![]() |
PV_LEAD_ASSIGNMENTS_U2 | NORMAL | UNIQUE |
![]() |
![]() ![]() ![]() ![]() |
PV_LEAD_ASSIGNMENTS_N1 | NORMAL | NONUNIQUE |
![]() |
![]() ![]() ![]() |
PV_LEAD_ASSIGNMENTS_N2 | NORMAL | NONUNIQUE |
![]() |
![]() |
PV_LEAD_ASSIGNMENTS_N4 | NORMAL | NONUNIQUE |
![]() |
![]() |
PV_LEAD_ASSIGNMENTS_N6 | NORMAL | NONUNIQUE |
![]() |
![]() |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
LEAD_ASSIGNMENT_ID | NUMBER | (15) | Yes | Lead assignment identifier |
LAST_UPDATE_DATE | DATE | Yes | Standard Who column | |
LAST_UPDATED_BY | NUMBER | (15) | Yes | Standard Who column |
CREATION_DATE | DATE | Yes | Standard Who column | |
CREATED_BY | NUMBER | (15) | Yes | Standard Who column |
LAST_UPDATE_LOGIN | NUMBER | (15) | Yes | Standard Who column |
OBJECT_VERSION_NUMBER | NUMBER | (15) | Yes | Object version number |
PARTNER_ID | NUMBER | Yes | Partner Identifier | |
ASSIGN_SEQUENCE | NUMBER | (15) | Sotes the serial order in which lead is to be assigned to the partners in serial mode | |
CM_ID | NUMBER | (15) | Supplier employee with a channel manager role identifier | |
LEAD_ID | NUMBER | (15) | Yes | Lead identifier |
DURATION | NUMBER | Fixed time duration for a lead with Supplier/Partner for an action to be taken | ||
STATUS | VARCHAR2 | (30) | Yes | Lead assignment status |
STATUS_DATE | DATE | Lead assignment status date | ||
WF_ITEM_TYPE | VARCHAR2 | (30) | Workflow item type, part of workflow unique identifier | |
WF_ITEM_KEY | VARCHAR2 | (30) | Workflow unique identifier | |
WF_PT_USER | VARCHAR2 | (80) | Partner user name | |
WF_CM_USER | VARCHAR2 | (80) | Supplier employee with a role of Channel manager user name | |
ERROR_TXT | VARCHAR2 | (200) | To display workflow error messages | |
SECURITY_GROUP_ID | NUMBER | (15) | Security group identifier | |
REASON_CODE | VARCHAR2 | (30) | Reasons if any | |
SOURCE_TYPE | VARCHAR2 | (30) | Yes | Opportunity source |
RELATED_PARTY_ID | NUMBER | Identifier for indirectly managed partners | ||
PARTNER_ACCESS_CODE | VARCHAR2 | (30) | Controls access to the opportunity for the partner | |
RELATED_PARTY_ACCESS_CODE | VARCHAR2 | (30) | Controls access to the opportunity for the vad |
Cut, paste (and edit) the following text to query this object:
SELECT LEAD_ASSIGNMENT_ID
, LAST_UPDATE_DATE
, LAST_UPDATED_BY
, CREATION_DATE
, CREATED_BY
, LAST_UPDATE_LOGIN
, OBJECT_VERSION_NUMBER
, PARTNER_ID
, ASSIGN_SEQUENCE
, CM_ID
, LEAD_ID
, DURATION
, STATUS
, STATUS_DATE
, WF_ITEM_TYPE
, WF_ITEM_KEY
, WF_PT_USER
, WF_CM_USER
, ERROR_TXT
, SECURITY_GROUP_ID
, REASON_CODE
, SOURCE_TYPE
, RELATED_PARTY_ID
, PARTNER_ACCESS_CODE
, RELATED_PARTY_ACCESS_CODE
FROM PV.PV_LEAD_ASSIGNMENTS;
PV.PV_LEAD_ASSIGNMENTS does not reference any database object
PV.PV_LEAD_ASSIGNMENTS is referenced by following:
|
|
|