FND_SAVED_SEARCH_USER_PREFS
Table to store the user customizations (preferences) for a particular saved search.
Details
-
Schema: SEARCH
-
Object owner: FND
-
Object type: TABLE
-
Tablespace: Default
Primary Key
Name | Columns |
---|---|
FND_SAVED_SEARCH_USER_P_PK |
USER_NAME, SAVED_SEARCH_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
USER_NAME | VARCHAR2 | 2000 | Yes | USER_NAME - The user associated to the saved searches preferences | |
SAVED_SEARCH_ID | NUMBER | 18 | Yes | SAVED_SEARCH_ID - unique id for saved search | |
ENABLED_FLAG | VARCHAR2 | 1 | ENABLED_FLAG - Is this saved search enabled (Y/N). Only enabled saved searches will be seen by the end-user. | ||
VISIBLE_FLAG | VARCHAR2 | 1 | VISIBLE_FLAG - Is the Saved Search shown in UI to users? | ||
AUTO_RUN_FLAG | VARCHAR2 | 1 | AUTO_RUN_FLAG - Is the Saved Search automatically executed? Some saved searches should not be run blind and require users to provide keywords before execution. | ||
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. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
FND_SAVED_SEARCH_U_P_U1 | Unique | Default | USER_NAME, SAVED_SEARCH_ID |