1. Tables and Views for Sales, Fusion Service, and Field Service
  2. MOO_OPTY_SRC

MOO_OPTY_SRC

A Source of an Opportunity. Each Opportunity may be initiated through multiple sources -- a source is either a Marketing Campaign, Referral or other source. Marketing Campaigns may be decomposed into sub-campaigns each of which may be the source of an opportunity.

Details

  • Schema: FUSION

  • Object owner: MOO

  • Object type: TABLE

  • Tablespace: Default

Primary Key

Name Columns

MOO_OPTY_SRC_PK

OPTY_SRC_ID

Columns

Name Datatype Length Precision Not-null Comments Status
OPTY_SRC_ID NUMBER 18 Yes Unique ID for opportunity source. Active
OPTY_ID NUMBER 18 Yes Opportunity Id Active
SOURCE_CODE VARCHAR2 100 Yes The source of the marketing event. For example, a campaign, new product line, a marketing seminar, and so on. This is a required attribute. Active
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). Active
CREATION_DATE TIMESTAMP Yes Who column: indicates the date and time of the creation of the row. Active
CREATED_BY VARCHAR2 64 Yes Who column: indicates the user who created the row. Active
LAST_UPDATE_DATE TIMESTAMP Yes Who column: indicates the date and time of the last update of the row. Active
LAST_UPDATED_BY VARCHAR2 64 Yes Who column: indicates the user who last updated the row. Active
LAST_UPDATE_LOGIN VARCHAR2 32 Who column: indicates the session login associated to the user who last updated the row. Active
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. Active
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). Active

Foreign Keys

Table Foreign Table Foreign Key Column
MOO_OPTY_SRC moo_opty OPTY_ID

Indexes

Index Uniqueness Tablespace Columns
MOO_OPTY_SRC_F1 Non Unique Default SOURCE_CODE
MOO_OPTY_SRC_PK1 Unique Default OPTY_SRC_ID
MOO_OPTY_SRC_U1 Unique Default OPTY_ID, SOURCE_CODE, CONFLICT_ID
MOO_OPTY_SRC_U2 Unique Default LAST_UPDATE_DATE, OPTY_SRC_ID