MSC_NOTE_OBJECT_MAPPINGS

This table is the mapping table between object_uid of the planning note with the numeric object_id of hrt_notes.

Details

• Schema: FUSION

• Object owner: MSC

• Object type: TABLE

• Tablespace: Default

Primary Key

Name	Columns
MSC_NOTE_OBJECT_MAPPINGS_PK	OBJECT_ID

Columns

Name	Datatype	Length	Precision	Not-null	Comments
OBJECT_ID	NUMBER		18	Yes	This column is used to store object unique identifier.
OBJECT_TYPE	NUMBER		2	Yes	This column is used to store different type of note objects such as 1 forCustomer,2 for Exception,3 for Item,4 for Level Member etc.
OBJECT_UID	VARCHAR2	64		Yes	This column stores uid which is currently used in zmm_notes.source_object_uid column.
DETAIL	CLOB				This column stores detail description of json based source object.
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_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.
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.
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
MSC_NOTE_OBJECT_MAPPINGS_U1	Unique	Default	OBJECT_ID
MSC_NOTE_OBJECT_MAPPINGS_U2	Unique	Default	OBJECT_UID