MSC_ST_ROUTINGS
The staging table used by the collection program to validate and process data for table MSC_ROUTINGS.
Details
-
Schema: FUSION
-
Object owner: MSC
-
Object type: TABLE
-
Tablespace: INTERFACE
Columns
Name | Datatype | Length | Not-null | Comments |
---|---|---|---|---|
ROUTING_SEQUENCE_ID | NUMBER | Routing sequence identifier for the routing/work definition. | ||
ASSEMBLY_ITEM_ID | NUMBER | Item identifier of the assembly. | ||
ROUTING_TYPE | NUMBER | This value indicates the routing type of the wd/routing record. | ||
ROUTING_COMMENT | VARCHAR2 | 960 | Comment for the routing or a work definition record. | |
PRIORITY | NUMBER | Routing priority collected from the source system. | ||
ALTERNATE_ROUTING_DESIGNATOR | VARCHAR2 | 30 | Name of the alternate routing. Null for primary routing | |
PROJECT_ID | NUMBER | This column stores the value of Project identifier. | ||
TASK_ID | NUMBER | This value indicates the Task identifier. | ||
LINE_ID | NUMBER | This column indicates the manufacturing line identifier. | ||
UOM_CODE | VARCHAR2 | 50 | Unit of measure code of the routing or a work definition. | |
CFM_ROUTING_FLAG | NUMBER | Flag to indicate whether the routing is continuos flow or traditional routing | ||
CTP_FLAG | NUMBER | Flag to indicate whether capacity must be checked when item is ordered | ||
ROUTING_QUANTITY | NUMBER | Quantity of the work definition or a routing. | ||
COMPLETION_SUBINVENTORY | VARCHAR2 | 10 | Name of the subinventory that stores the completed quantity of the wip job. | |
COMPLETION_LOCATOR_ID | NUMBER | Indicates the completion locator identifier for the work definition obtained. | ||
COMMON_ROUTING_SEQUENCE_ID | NUMBER | Common routing sequence identifier | ||
MIXED_MODEL_MAP_FLAG | NUMBER | This value indicates the Mix model map flag. | ||
TOTAL_PRODUCT_CYCLE_TIME | NUMBER | This value indicates the Total product cycle time. | ||
ORGANIZATION_ID | NUMBER | This column indicates the organization identifer. | ||
DELETED_FLAG | NUMBER | Yes/No flag indicates whether corresponding record in ODS will be deleted | ||
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. | |
SR_INSTANCE_ID | NUMBER | Source application instance identifier | ||
REFRESH_NUMBER | NUMBER | Refresh identifier populated by the collection progam | ||
FIRST_OP_SEQ_NUM | NUMBER | First operation sequence number | ||
LAST_OP_SEQ_NUM | NUMBER | Last operation sequence number of the work definition or routing. | ||
COMPANY_ID | NUMBER | Unique id assigned to the company | ||
COMPANY_NAME | VARCHAR2 | 255 | Party name with which the company is registered. | |
BOM_NAME | VARCHAR2 | 250 | BOM Name. If this is empty during uploads then it would be replaced by ASSEMBLY_NAME | |
ROUTING_NAME | VARCHAR2 | 250 | Name of the routing or a work definition. | |
BILL_SEQUENCE_ID | NUMBER | Bill of material unique identifier | ||
ORGANIZATION_CODE | VARCHAR2 | 18 | This column indicates the organization code. | |
ASSEMBLY_NAME | VARCHAR2 | 300 | Name assigned to the assembly item | |
SR_INSTANCE_CODE | VARCHAR2 | 30 | Source Instance code from which data is being populated. | |
LINE_CODE | VARCHAR2 | 10 | This value indicates the Routing line defined for a Routing or work definition. | |
PROJECT_NUMBER | VARCHAR2 | 25 | This column stores the value of Project Number. | |
TASK_NUMBER | VARCHAR2 | 25 | This value indicates the Task number. | |
ALTERNATE_BOM_DESIGNATOR | VARCHAR2 | 80 | Name of the bill for alternate bills (null for the primary bill) . | |
MESSAGE_ID | NUMBER | This is a foreign key reference to ECX_DOCLOGS.INTERNAL_CONTROL_NUMBER for records got via XML | ||
PROCESS_FLAG | NUMBER | Processing Flag indicating the status of records during pre-processing. 1- New Record, 2- In-Process, 3- Error, 4- Propagated Error, 5- Successfully Processed | ||
ERROR_TEXT | VARCHAR2 | 2000 | This will describe the reason for the error if any. | |
DATA_SOURCE_TYPE | VARCHAR2 | 15 | Source Type indicating the source of the records[ | |
ST_TRANSACTION_ID | NUMBER | Transaction ID generated during pre-processing to uniquely identify a record in the staging table | ||
BATCH_ID | NUMBER | Batch identifier generated during pre-processing | ||
FIRST_OPERATION_SEQ_CODE | VARCHAR2 | 10 | First operation sequence code of the network | |
LAST_OPERATION_SEQ_CODE | VARCHAR2 | 10 | Last operation sequence code of the network | |
COMMON_ROUTING_NAME | VARCHAR2 | 250 | Name of the Routing or the Work definition that is common between parent and child | |
ITEM_PROCESS_COST | NUMBER | Identifies the inventory item process cost | ||
PREFERENCE | NUMBER | This value indicates the preference of the routing. | ||
SOURCE_ORGANIZATION_ID | NUMBER | This is the Organization ID for the Organization in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_ASSEMBLY_ITEM_ID | NUMBER | This is the Assembly Item ID for the Assembly Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_ROUTING_SEQUENCE_ID | NUMBER | This is the Routing Sequence ID for the Routing Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_TASK_ID | NUMBER | This is the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_PROJECT_ID | NUMBER | This is the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_BILL_SEQUENCE_ID | NUMBER | This is the Bill Sequence ID for the Bill Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_COMMON_ROUTING_SEQ_ID | NUMBER | This is the Common Routing Sequence ID for the Common Routing Sequence in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_LINE_ID | NUMBER | This is the Line ID for the Line in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
AUTO_STEP_QTY_FLAG | NUMBER | 1 Yes, 2 No1 yes => Calculate the Step Quantity fieldbased on the amount of ingredients per step as defined in the StepMaterial Association.2=> step quantities are calculated fromthe default routing steps, | ||
RETRY_COUNT | NUMBER | Number of retries to process failed records. | ||
ERROR_CODE | VARCHAR2 | 150 | Error code for functional validation errors in the record | |
LOAD_REQUEST_ID | NUMBER | It Stores the Request ID of Job that loaded the data. | ||
PROCESS_NAME | VARCHAR2 | 120 | Indicates the unique name for the work definition. In the case of process manufacturing, this represents the process name. | |
QUANTITY | NUMBER | Represents the quantity produced for the work definition. In process manufacturing, this is the batch quantity. | ||
WORK_METHOD_CODE | NUMBER | A code that represents the user key to the work method. Valid values are 1=DISCRETE_MANUFACTURING, 2=PROCESS_MANUFACTURING | ||
EFFECTIVITY_DATE | DATE | Indicates the date from when this Routing is effective. |