MSC_ROUTING_OPERATIONS
This tables stores the operations composing each routing.
Details
-
Schema: FUSION
-
Object owner: MSC
-
Object type: TABLE
-
Tablespace: TRANSACTION_TABLES
Primary Key
Name | Columns |
---|---|
MSC_ROUTING_OPERATIONS_PK |
PLAN_ID, ORGANIZATION_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, NEW_PLAN_ID, SIMULATION_SET_ID, PART_KEY1 |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
PLAN_ID | NUMBER | Yes | This value indicates the plan identifier for the record. | ||
OPERATION_SEQUENCE_ID | NUMBER | 18 | Yes | Reference to the operation to which this routing is assigned. | |
ROUTING_SEQUENCE_ID | NUMBER | Yes | Routing sequence identifier for the routing/work definition. | ||
OPERATION_SEQ_NUM | NUMBER | 18 | Yes | Operation sequence number of the operation associated with the routing. | |
PART_KEY1 | NUMBER | 18 | Yes | Source application instance identifier | |
OPERATION_DESCRIPTION | VARCHAR2 | 960 | Operation description (use for UI and reports) | ||
EFFECTIVITY_DATE | DATE | Yes | Indicate the date from when this operation is effective | ||
DISABLE_DATE | DATE | Date indicating End of effectivity | |||
FROM_UNIT_NUMBER | VARCHAR2 | 30 | Effective from this unit number | ||
TO_UNIT_NUMBER | VARCHAR2 | 30 | Effective up to this unit number | ||
OPTION_DEPENDENT_FLAG | NUMBER | Yes | Flag to indicate whether this operation option dependent | ||
OPERATION_TYPE | NUMBER | Indicate operation type: Process, Line, or Event. Events are not used here | |||
MINIMUM_TRANSFER_QUANTITY | NUMBER | Minimum operation transfer quantity | |||
YIELD | NUMBER | Process yield at this operation | |||
DEPARTMENT_ID | NUMBER | 18 | Yes | Department identifier (source application identifier) in which the operation takes place | |
DEPARTMENT_CODE | VARCHAR2 | 120 | Department code (for reporting) | ||
OPERATION_LEAD_TIME_PERCENT | NUMBER | Indicates the amount of overlape its lead time has with the parent lead time | |||
CUMULATIVE_YIELD | NUMBER | Cummulative process yield from the beginning of routing to this operation | |||
REVERSE_CUMULATIVE_YIELD | NUMBER | Cummulative process yield from the end of routing to comparable operation | |||
NET_PLANNING_PERCENT | NUMBER | Cummulative planning percents derived from the operation network | |||
SETUP_DURATION | NUMBER | Duration of the set-up for the routing/work definition operation. | |||
TEAR_DOWN_DURATION | NUMBER | Duration of the tear down for this operation | |||
UOM_CODE | VARCHAR2 | 3 | Unit of measure code of the routing operation. | ||
STANDARD_OPERATION_CODE | VARCHAR2 | 4 | Code of the standard operation on which this operation is based. Operations having the same code are identical | ||
REFRESH_NUMBER | NUMBER | Refresh number populated by the collection program | |||
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. | |
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_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
USE_IN_PLAN | NUMBER | This column is used for Routing Effectivity Timestamp | |||
ORGANIZATION_ID | NUMBER | 18 | Yes | This column indicates the organization identifier. | |
STEP_QUANTITY | NUMBER | Quantity associated with an operation. Populated for opm jobs | |||
STEP_QUANTITY_UOM | VARCHAR2 | 3 | Unit of measure of the step quantity of the routing or work definition operation. | ||
NEW_PLAN_ID | NUMBER | 18 | Yes | This indicates the new plan identifier if the base plan exists for this record. | |
SIMULATION_SET_ID | NUMBER | 18 | Yes | Simulation set to which the current record is added. | |
NEW_PLAN_LIST | VARCHAR2 | 256 | List indicates the new plan identifiers for the record. | ||
APPLIED | NUMBER | Flag used for online replanning | |||
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. | |
ASSEMBLY_ITEM_ID | NUMBER | 18 | Item identifier of the assembly. | ||
SUPPLIER_ID | NUMBER | 18 | This value indicates the Supplier identifier in the planning system. | ||
SUPPLIER_SITE_ID | NUMBER | 18 | Supplier Site ID for OSP operation | ||
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. | |||
OPERATION_COST | NUMBER | This value indicates OSP Operation Cost. | |||
OSP_OPERATION_TYPE | NUMBER | Indicate operation type: InHouse(1) or Supplier(2) | |||
SIM_EDIT_FLAGS | NUMBER | Indicates which columns are edited in simulation set records | |||
LINE_OP_SEQ_NUMBER | NUMBER | Indicates the production line operation sequence number. | |||
AUTO_TRANSACT_FLAG | NUMBER | 1 | Indicates whether both resources and materials 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 transactions are automatically done when the quantity is moved outside the operation. Valid values are 1 and 2. |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
MSC_ROUTING_OPERATIONS | msc_routings | PLAN_ID, ORGANIZATION_ID, ROUTING_SEQUENCE_ID, NEW_PLAN_ID, SIMULATION_SET_ID, PART_KEY1 |
msc_operation_resource_seqs | msc_routing_operations | PLAN_ID, ORGANIZATION_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, NEW_PLAN_ID, SIMULATION_SET_ID, PART_KEY1 |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
MSC_ROUTING_OPERATIONS_N1 | Non Unique | Default | PLAN_ID, OPERATION_SEQUENCE_ID |
MSC_ROUTING_OPERATIONS_N2 | Non Unique | Default | PLAN_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQ_NUM |
MSC_ROUTING_OPERATIONS_U1 | Unique | Default | PLAN_ID, ORGANIZATION_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, NEW_PLAN_ID, SIMULATION_SET_ID, PART_KEY1 |
MSC_ROUTING_OPERATIONS_U2 | Unique | Default | PLAN_ID, ORGANIZATION_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQ_NUM, EFFECTIVITY_DATE, NEW_PLAN_ID, SIMULATION_SET_ID, PART_KEY1 |