MKL_LEAD_TERRITORIES
This table stores reference to the sales territory which is associated with a lead. When a lead is assigned for followup, it can be assigned to resources associated with different sales territories. For reference,a sales territory is a segment of the market for which one or more salespeople are responsible.
Details
-
Schema: FUSION
-
Object owner: MKL
-
Object type: TABLE
-
Tablespace: Default
Primary Key
Name | Columns |
---|---|
MKL_LEAD_TERRITORIES_PK |
LEAD_TERRITORY_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
LEAD_TERRITORY_ID | NUMBER | 18 | Yes | Primary Key | |
LEAD_ID | NUMBER | 18 | Yes | Lead Id | |
TERRITORY_ID | NUMBER | 18 | Yes | Territory Id | |
TERRITORY_VERSION_ID | NUMBER | 18 | Yes | Territory Version Id | |
ACCESS_LEVEL_CODE | VARCHAR2 | 30 | Yes | Access level code | |
LEAD_EFFECTIVE_DATE | TIMESTAMP | Lead Effective Date. Denorm column storing the lead header creation date i.e MKL_LM_LEADS.CREATION_DATE | |||
LEAD_STATUS_CD | VARCHAR2 | 30 | Lead Status Code. Denorm column storing the lead header status code i.e MKL_LM_LEADS.STATUS_CD | ||
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
CONFLICT_ID | NUMBER | 18 | Yes | Disconnected Mobile: this value is used to guarantee the uniqueness of the row when duplicates are created in different databases (i.e. mobile databases or the server). | |
USER_LAST_UPDATE_DATE | TIMESTAMP | Disconnected Mobile: indicates the date and time of the last update of the row. This value is different from LAST_UPDATE_DATE if the update originally happened in a different database (i.e. a different mobile database or the server). |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
MKL_LEAD_TERRITORIES | mkl_lm_leads | LEAD_ID |
Indexes
Index | Uniqueness | Tablespace | Columns | Status |
---|---|---|---|---|
MKL_LEAD_TERRITORIES_FK1 | Non Unique | Default | LEAD_ID | Obsolete |
MKL_LEAD_TERRITORIES_FK2 | Non Unique | Default | TERRITORY_ID | |
MKL_LEAD_TERRITORIES_N1 | Non Unique | Default | CREATION_DATE | |
MKL_LEAD_TERRITORIES_N2 | Non Unique | Default | LEAD_ID, TERRITORY_ID, LEAD_EFFECTIVE_DATE | |
MKL_LEAD_TERRITORIES_PK | Unique | Default | LEAD_TERRITORY_ID | |
MKL_LEAD_TERRITORIES_U1 | Unique | Default | LEAD_ID, TERRITORY_VERSION_ID, TERRITORY_ID | |
MKL_LEAD_TERRITORIES_U2 | Unique | Default | LEAD_ID, TERRITORY_ID, LEAD_STATUS_CD, LEAD_EFFECTIVE_DATE | Obsolete |
MKL_LEAD_TERRITORIES_U3 | Unique | Default | LEAD_ID, LEAD_EFFECTIVE_DATE, TERRITORY_VERSION_ID, TERRITORY_ID | |
MKL_LEAD_TERRITORIES_U4 | Unique | Default | LEAD_EFFECTIVE_DATE, LEAD_STATUS_CD, TERRITORY_VERSION_ID, LEAD_ID |