MSC_CLUSTER_DATA

Table msc_cluster_data holds the clusters used in each plan for inventory rebalancing, partitioned by plan_id.

Details

• Schema: FUSION

• Object owner: MSC

• Object type: TABLE

• Tablespace: Default

Primary Key

Name	Columns
MSC_CLUSTER_DATA_PK	PLAN_ID, CLUSTER_ID, LOCATION_ID

Columns

Name	Datatype	Length	Precision	Not-null	Comments
PLAN_ID	NUMBER		18	Yes	Plan Id is the foreign key to the msc_plan_definitions table.
CLUSTER_ID	NUMBER		18	Yes	Cluster id is the foreign key to the msc_clusters_b table.
LOCATION_ID	NUMBER		18	Yes	Location_id is the foreign key to the msc_organizations table and the id of org or sub-inventory used in the specified cluster.
CLUSTER_SEQUENCE	NUMBER			Yes	Sequence is the order in which the clusters will be processed in inventory rebalancing engine calculations.
LOCATION_SEQUENCE	NUMBER				Sequence is the order in which the location will be processed within the cluster during inventory rebalancing engine calculations.
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.
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_CLUSTER_DATA_U1	Unique	Default	PLAN_ID, CLUSTER_ID, LOCATION_ID