MSC_BM_ALLOCATION_RULES
This table describes the allocation rules
Details
-
Schema: FUSION
-
Object owner: MSC
-
Object type: TABLE
-
Tablespace: Default
Primary Key
Name | Columns |
---|---|
MSC_BM_ALLOCATION_RULES_PK |
ALLOCATION_RULE_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
ALLOCATION_RULE_ID | NUMBER | 18 | Yes | Identifier to the allocation rule | |
ALLOCATION_RULE_NAME | VARCHAR2 | 30 | Yes | Unique name for the allocation rule | |
DESCRIPTION | VARCHAR2 | 80 | Description of the allocation rule | ||
ALLOCATION_SPECIFICATION | NUMBER | Yes | Allocation specification can be either 1 - Number 2 - Ratio 3 - Percentage | ||
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_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. | |
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. | |
REFRESH_NUMBER | NUMBER | 18 | Refresh identifier populated by the collection program. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
MSC_BM_ALLOCATION_RULES_U1 | Unique | Default | ALLOCATION_RULE_ID |
MSC_BM_ALLOCATION_RULES_U2 | Unique | Default | ALLOCATION_RULE_NAME |