MSC_USER_ACTIONS

This table stores the user changes as user action in planning.

Details

  • Schema: FUSION

  • Object owner: MSC

  • Object type: TABLE

  • Tablespace: Default

Primary Key

Name Columns

MSC_USER_ACTIONS_PK

ACTION_ID

Columns

Name Datatype Length Precision Not-null Comments
ACTION_ID NUMBER 18 Yes Id of the user action row, the primary key of the table
PLAN_ID NUMBER 18 The plan_id of the plan in which the user actions takes place
BASE_PLAN_ID NUMBER 18 The base_plan_id of the plan in which the user actions takes place
ACTION_TYPE NUMBER 18 The input entity type of the user action. Values are 102-UPDATE, 105-CREATE, 106-DELETE.
TABLE_NAME VARCHAR2 256 The table name of the input entity that the user action is generated for.
ACTION CLOB The clob stores the user edit/create/delete action, one user action clob per one input entity row.
EDIT_VERSION NUMBER 18 The number sequence of the user ction
PLAN_VERSION NUMBER 18 The number sequence of the plan that Engine set at the end of each Run Plan
RECALCULATED NUMBER Whether the action data gets processed by UI interactive recalculate. 1 - Yes; 2 (or Null) - No.
LAST_UPDATE_DATE TIMESTAMP Yes Who column: indicates the date and time of the last update of the row.
LAST_UPDATED_BY VARCHAR2 64 Yes Who column: indicates the user who last updated the row.
CREATION_DATE TIMESTAMP Yes Who column: indicates the date and time of the creation of the row.
CREATED_BY VARCHAR2 64 Yes Who column: indicates the user who created 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.

Indexes

Index Uniqueness Tablespace Columns
MSC_USER_ACTIONS_N1 Non Unique Default PLAN_ID
MSC_USER_ACTIONS_U1 Unique Default ACTION_ID