MSC_PLAN_CLUSTER_DMD_SUP
Table msc_plan_cluster_dmd_sup holds the demand and supply types to use for inventory rebalancing calculation for the plan
Details
-
Schema: FUSION
-
Object owner: MSC
-
Object type: TABLE
-
Tablespace: Default
Primary Key
| Name | Columns |
|---|---|
|
MSC_PLAN_CLUSTER_DMD_SUP_PK |
PLAN_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. | |
| INTRANSIT_SHIPMENTS | NUMBER | 1 | Indicates whether intransit shipments are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| MOVEMENT_REQUESTS | NUMBER | 1 | Indicates whether movement requests are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| ON_HAND | NUMBER | 1 | Indicates whether on hand quantity is considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| PLANNED_INBOUND_SHIPMENTS | NUMBER | 1 | Indicates whether planned inbound shipments are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| PURCHASE_ORDER | NUMBER | 1 | Indicates whether purchase orders are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| PURCHASE_REQUISITION | NUMBER | 1 | Indicates whether purchase requisitions are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| SHIPMENT_IN_RECEIVING | NUMBER | 1 | Indicates whether shipments in receiving are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| TRANSFER_ORDER | NUMBER | 1 | Indicates whether transfer orders are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| GROSS_FORECAST | NUMBER | 1 | Indicates whether gross forecasts are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| MANUAL_DEMAND | NUMBER | 1 | Indicates whether manual demands are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| MOVEMENT_REQUEST_DEMAND | NUMBER | 1 | Indicates whether movement request demands are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| NET_FORECAST | NUMBER | 1 | Indicates whether net forecasts are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| PLANNED_OUTBOUND_SHIPMENTS | NUMBER | 1 | Indicates whether planned outbound shipments are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| SALES_ORDER | NUMBER | 1 | Indicates whether sales orders are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| TRANSFER_ORDER_DEMAND | NUMBER | 1 | Indicates whether transfer order demands are considered in inventory rebalance calculations, 1 = Yes, 2 = No. | ||
| 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_PLAN_CLUSTER_DMD_SUP_U1 | Unique | Default | PLAN_ID |