MSC_API_WD_OPERATION
This Table is used to collect the data from the API for work definition Operation
Details
-
Schema: FUSION
-
Object owner: MSC
-
Object type: TABLE
-
Tablespace: Default
Primary Key
| Name | Columns |
|---|---|
|
MSC_API_WD_OPERATION_PK |
WORK_DEFINITION_ID, OPERATION_SEQ_NUMBER, EFFECTIVE_FROM_DATE, CONFIG_ITEM_ID, ORGANIZATION_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| WD_OPERATION_ID | NUMBER | Yes | Work definition operation identifier specified for the routing. | ||
| WORK_DEFINITION_ID | NUMBER | Yes | This value indicates identifier of the work definition. | ||
| OPERATION_SEQ_NUMBER | NUMBER | Yes | OPERATION_SEQ_NUMBER | ||
| OPERATION_TYPE | NUMBER | OPERATION_TYPE | |||
| OPERATION_DESCRIPTION | VARCHAR2 | 240 | OPERATION_DESCRIPTION | ||
| OPERATION_NAME | VARCHAR2 | 120 | OPERATION_NAME | ||
| WORK_CENTER_ID | NUMBER | Yes | Work centre identifier assigned to the work definition operation. | ||
| WORK_CENTER_NAME | VARCHAR2 | 80 | Work centre name assigned to the work definition operation. | ||
| COUNT_POINT_FLAG | VARCHAR2 | 1 | If an operation is count point then you have to manually complete it and those operations in between the count points are automatically completed i.e. backflushed. | ||
| AUTO_TRANSACT_FLAG | VARCHAR2 | 1 | Indicates whether both resources and material are automatically charged based on the Supply Type or the Charge Type setups for the operation. If the supply type is Operation Pull, the component level issue transactions will happen when the operation is completed. If the supply type is Assembly Pull, the component level issue transactions will happen at the Assembly Completion event. Resource Transaction are automatically done when the Quantity is moved outside the Operation. Valid values are 'Y' and 'N'. | ||
| SERIAL_TRACKING_FLAG | VARCHAR2 | 1 | A serial tracking flag for the work definition operation. | ||
| PLANNING_PERCENT | NUMBER | Planning percentage of the work definition operation. | |||
| OSP_ITEM_ID | NUMBER | Inventory item identifier of the Outside processing item. | |||
| OSP_OPERATION_TYPE | NUMBER | Operation type of the outside processing item. | |||
| SUPPLIER_ID | NUMBER | 18 | This value indicates the Supplier identifier in the planning system. | ||
| SUPPLIER_SITE_ID | NUMBER | 18 | This value indicates the Supplier site identifier. | ||
| LEAD_TIME_UOM | VARCHAR2 | 3 | LEAD_TIME_UOM | ||
| FIXED_LEAD_TIME | NUMBER | Represents the fixed lead time used to calculate the operations start and end date for the supplier operation. | |||
| VARIABLE_LEAD_TIME | NUMBER | Variable lead time used in conjunction with the quantity of the assembly being manufactured. | |||
| EFFECTIVE_FROM_DATE | TIMESTAMP | Yes | Indicate the date from when this operation is effective | ||
| EFFECTIVE_TO_DATE | TIMESTAMP | Indicate the date from which this operation is no longer effective | |||
| WORK_CENTER_CODE | VARCHAR2 | 30 | Work centre code assigned to the work definition operation. | ||
| CONFIG_ITEM_ID | NUMBER | Yes | Unique identifier of the configured item | ||
| ORGANIZATION_ID | NUMBER | Yes | ORGANIZATION_ID | ||
| 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_API_WD_OPERATION_U1 | Unique | Default | WORK_DEFINITION_ID, OPERATION_SEQ_NUMBER, EFFECTIVE_FROM_DATE, CONFIG_ITEM_ID, ORGANIZATION_ID |