PSC_COM_ATTN_TILE_QUERY_TBL
This table contains the SQL’s that are used while processing all attention tiles.
Details
-
Schema: FUSION
-
Object owner: PSC_CC
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
| Name | Columns |
|---|---|
|
PSC_COM_ATTN_TILE_QUERY_PK |
SEQUENCE_NUMBER, TILE_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| SEQUENCE_NUMBER | NUMBER | 22 | Yes | The criteria for executing the attention tile query sql can be achieved using this sequence number. | |
| TILE_ID | VARCHAR2 | 50 | Yes | Indicates the tile id information. | |
| ACTIVE_USER_FLAG | VARCHAR2 | 1 | Yes | This indicates whether the attention tile processing should be triggered for all registered public users in the system or only for active registered public users at a given moment. | |
| SQL_QUERY | CLOB | Indicates the SQL’s that are used for processing attention tiles. | |||
| 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. | |
| 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. | ||
| MODULE_ID | VARCHAR2 | 32 | Seed Data Framework: indicates the module that owns the row. A module is an entry in Application Taxonomy such as a Logical Business Area. When the MODULE_ID column exists and the owner of the row is not specified, then the Seed Data Framework will not extract the row as seed data. | ||
| SEED_DATA_LOCK | NUMBER | 1 | Yes | Indicates wheher the row is a seed data. Valid values are 0 for data that is for customer data, 1 for data that can not be modified , and 2 indicates that the seed data can be modified. | |
| DELETED_FLAG | VARCHAR2 | 1 | Yes | Indicates whether the record is logically deleted (Y or N). Valid values are Y for deleted record, and N for active record. Default value is N. | |
| SEED_DATA_SOURCE | VARCHAR2 | 512 | Source of seed data record. A value of 'BULK_SEED_DATA_SCRIPT' indicates that record was bulk loaded. Otherwise, specifies the name of the seed data file. | ||
| ORA_SEED_SET1 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET1. Context values are Y or N. | |
| ORA_SEED_SET2 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET2. Context values are Y or N. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| PSC_COM_ATTN_TILE_QUERY_PK | Unique | Default | SEQUENCE_NUMBER, TILE_ID, ORA_SEED_SET1 |
| PSC_COM_ATTN_TILE_QUERY_PK1 | Unique | Default | SEQUENCE_NUMBER, TILE_ID, ORA_SEED_SET2 |