MSC_PLAN_MESSAGES
This table stores messages sent from the planning processes when a plan runs to completion
Details
-
Schema: FUSION
-
Object owner: MSC
-
Object type: TABLE
-
Tablespace: Default
Primary Key
| Name | Columns |
|---|---|
|
MSC_PLAN_MESSAGES_PK |
MESSAGE_ID, PLAN_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| MESSAGE_ID | NUMBER | 18 | Yes | An id to uniquely identify the message | |
| PLAN_ID | NUMBER | 18 | Yes | Plan id on which the message is generated | |
| MODULE_CODE | NUMBER | 3 | Yes | The pre-defined module code of the module that generates the message | |
| EXECUTION_ID | NUMBER | 18 | Yes | The execution id of the plan action. It is the same execution id stored in MSC_PLAN_STATUS. | |
| ACTION_CODE | NUMBER | 3 | Yes | The pre-defined plan action code, e.g. 1- Supply paln full refresh; 2 - Supply plan partial refresh, etc. | |
| PROCESS_ID | NUMBER | 18 | Yes | The ID of the process that generated the message. Also displayed in the Scheduled Processes UI. | |
| ITEM_ID | NUMBER | 18 | Inventory item id. If the message is for a particular item, then the item id is populated | ||
| ORGANIZATION_ID | NUMBER | 18 | Organization id. If the message is for a particular organization, then the organization id is populated | ||
| MESSAGE_NAME | VARCHAR2 | 30 | Yes | The name of the message defined in FND Message table, e.g. MSC_PCENG_SOURC_LOOP_BROKEN | |
| MESSAGE_TOKEN1 | VARCHAR2 | 320 | The token value for the message at the format of <TOKEN_NAME>=value, e.g. PLAN_NAME=value | ||
| MESSAGE_TOKEN2 | VARCHAR2 | 320 | The token value for the message at the format of <TOKEN_NAME>=value, e.g. PLAN_NAME=value | ||
| MESSAGE_TOKEN3 | VARCHAR2 | 320 | The token value for the message at the format of <TOKEN_NAME>=value, e.g. PLAN_NAME=value | ||
| MESSAGE_TOKEN4 | VARCHAR2 | 320 | The token value for the message at the format of <TOKEN_NAME>=value, e.g. PLAN_NAME=value | ||
| MESSAGE_TOKEN5 | VARCHAR2 | 320 | The token value for the message at the format of <TOKEN_NAME>=value, e.g. PLAN_NAME=value | ||
| MESSAGE_TOKEN6 | VARCHAR2 | 320 | The token value for the message at the format of <TOKEN_NAME>=value, e.g. PLAN_NAME=value | ||
| MESSAGE_TOKEN7 | VARCHAR2 | 320 | The token value for the message at the format of <TOKEN_NAME>=value, e.g. PLAN_NAME=value | ||
| MESSAGE_TOKEN8 | VARCHAR2 | 320 | The token value for the message at the format of <TOKEN_NAME>=value, e.g. PLAN_NAME=value | ||
| MESSAGE_TOKEN9 | VARCHAR2 | 320 | The token value for the message at the format of <TOKEN_NAME>=value, e.g. PLAN_NAME=value | ||
| MESSAGE_TOKEN10 | VARCHAR2 | 320 | The token value for the message at the format of <TOKEN_NAME>=value, e.g. PLAN_NAME=value | ||
| 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. | |
| 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. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| MSC_PLAN_MESSAGES_U1 | Unique | Default | MESSAGE_ID, PLAN_ID |