WIE_WORK_ORDERS_B_GT
This is a global temporary table that is to capture shadow records of work order's header records
Details
-
Schema: FUSION
-
Object owner: WIE
-
Object type: TABLE
-
Tablespace: Default
Primary Key
Name | Columns |
---|---|
WIE_WORK_ORDERS_B_GT_PK |
TEMPORARY_ROW_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
TEMPORARY_ROW_ID | NUMBER | Yes | Unique id of work order shadow record | ||
WORK_ORDER_ID | NUMBER | 18 | This is the internal Work Order identifier | ||
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. | |
ORGANIZATION_ID | NUMBER | 18 | Refers to the organization that owns the Work Order | ||
WORK_ORDER_NUMBER | VARCHAR2 | 120 | Work Order Number. The uniqueness of which will be controlled by user setups at the work method or at the plant. | ||
WORK_METHOD_ID | NUMBER | 18 | Work Order is created for a specific manufacturing method. Manufacturing methods are pre-seeded. | ||
WORK_ORDER_TYPE | VARCHAR2 | 30 | Indicates the type of this work order. Values are contained within the ORA_WIE_WO_TYPE lookup if this work order is a manufacturing work order. If this is a maintenance work order, valid values are contained within the ORA_MNT_WO_TYPE lookup. | ||
WORK_ORDER_SUB_TYPE | VARCHAR2 | 30 | The subtype specifically will be populated for non-standard work. This is used to derive the appropriate costing account for non-standard work. Values are contained in the ORA_WIE_WO_SUB_TYPE lookup if this work order is a manufacturing work order. If this is a maintenance work order, valid values are contained within the ORA_MNT_WO_SUB_TYPE lookup. | ||
INVENTORY_ITEM_ID | NUMBER | 18 | Refers to the top level, final assembly, subassembly, or model item which belongs to the given organization. | ||
ITEM_REVISION | VARCHAR2 | 18 | If the primary product is revision controlled, this will have a value. | ||
ITEM_VERSION | NUMBER | 18 | If the item is version controlled, this value will be populated. At the time of work order creation, the work definition selection API returns the valid item version based on the work definition as of date. And that value will be persisted here. | ||
ITEM_STRUCTURE_NAME | VARCHAR2 | 80 | Item Structure Name (aka alternate_bom_designator). This is how it used to be called in EBS. In Fusion PIM it is called as Item Structure Name. This will be populated programmatically and will not be captured by the end user. | ||
TRANSFORM_FROM_ITEM_ID | NUMBER | 18 | Refers to the assembly item that is being transformed to a new assembly item on a Transform work order. | ||
WORK_DEFINITION_AS_OF_DATE | TIMESTAMP | The As-Of-Date is used to figure out the proper version of the work definition when the Org + Product + As-Of-Date is provided as the filter criteria in narrowing down the work order. | |||
WORK_DEFINITION_ID | NUMBER | 18 | The foreign key reference to the work definition. | ||
WORK_DEFINITION_VERSION_ID | NUMBER | 18 | The version of the work definition. | ||
WORK_ORDER_PRIORITY | NUMBER | Work Order Priority. A supervisor will be able to set the priority of the work order depending on the demand that needed to be prioritized. | |||
WORK_ORDER_STATUS_ID | NUMBER | 18 | User defined status of the work order. | ||
SCHEDULING_METHOD | VARCHAR2 | 30 | Whether the work order is scheduled based on the Work Definition data or Manual. | ||
PLANNED_START_QUANTITY | NUMBER | Refers to the planned Work Order Quantity which should be greater than zero for standard work orders, and can be equal to or greater than zero for non standard work orders. Note: Post R12, the planned Quantity needs to be based on the item shrinkage rate and operation yield. | |||
NETTABLE_SUPPLY_QTY_OVERRIDE | NUMBER | This is a user entered override of the completion quantity intended to indicate if there are work order specific variances compared to the calculated Completion Quantity | |||
UOM_CODE | VARCHAR2 | 3 | UOM Code. The assembly quantity will be produced in this uom. The transactions that moves the assembly from operation to operation and also eventually the completions will be performed in this UOM. | ||
PRIMARY_PRODUCT_QUANTITY | NUMBER | Represents the output quantity of the primary product used to create the work order. | |||
PRIMARY_PRODUCT_UOM_CODE | VARCHAR2 | 3 | Represents the unit of measure code of the primary product used to create the work order. | ||
FIRM_PLANNED_FLAG | VARCHAR2 | 1 | Flag to allow or prevent Planning from suggesting rescheduling and re-planning recommendations with respect to the Work Order. When the flag is on, this work order will not be considered by MRP to reschedule or re-plan. | ||
PLANNED_START_DATE | TIMESTAMP | Planned start date of the work order. | |||
PLANNED_COMPLETION_DATE | TIMESTAMP | Planned completion date of the work order. | |||
ACTUAL_START_DATE | TIMESTAMP | Actual start date of the work order. | |||
ACTUAL_COMPLETION_DATE | TIMESTAMP | Actual completion date of the work order. | |||
RELEASED_DATE | TIMESTAMP | Date when the work order is released. | |||
CLOSED_DATE | TIMESTAMP | Date when the work order is closed. | |||
CANCELED_DATE | TIMESTAMP | Date when the work order is canceled. | |||
CANCELED_REASON | VARCHAR2 | 240 | Reason for which the work order is canceled. This is a free format text. | ||
NEED_BY_DATE | TIMESTAMP | Date when the supply created by the work order will be used to fulfill a demand. | |||
STATUS_CHANGE_REASON | VARCHAR2 | 240 | The reason which is a free format capture of why the status is changed. The most current status change reason will be persisted in this column. | ||
COMPLETED_QUANTITY | NUMBER | Primary Product Quantity completed so far in the work order. This is a summary column. | |||
SCRAPPED_QUANTITY | NUMBER | Primary Product Quantity that is scrapped in the work order. This is a summary column. | |||
REJECTED_QUANTITY | NUMBER | Primary Product Quantity that is rejected in the work order. This is a summary column. | |||
OVERCOMPL_TOLERANCE_TYPE | VARCHAR2 | 30 | The tolerance type for over completions. Valid values exist in the lookup with lookup_type = EGP_OVER_TOLTYPE. | ||
OVERCOMPL_TOLERANCE_VALUE | NUMBER | The percent or amount value that is allowed over the scheduled completion work order quantity. | |||
UNDERCOMPL_TOLERANCE_TYPE | VARCHAR2 | 30 | The tolerance type for under completions. Valid values exist in the lookup with lookup type = ORA_EGP_UNDER_COMP_TOL. | ||
UNDERCOMPL_TOLERANCE_VALUE | NUMBER | The percent or amount value that is allowed under the scheduled completion work order quantity. | |||
UNDER_COMPLETED_FLAG | VARCHAR2 | 1 | Flag to indicate that the work order is marked as under-completed. | ||
SUPPLY_TYPE | VARCHAR2 | 30 | References the Material Supply Type. | ||
COMPL_SUBINVENTORY_CODE | VARCHAR2 | 10 | The default completion subinventory for the primary product. | ||
COMPL_LOCATOR_ID | NUMBER | 18 | The default completion locator for the primary product, if the subinventory is locator controlled. | ||
SERIAL_TRACKING_FLAG | VARCHAR2 | 1 | Indicates that the end item (eg assembly in discrete manufacturing) is tracked by serial numbers during work execution. The partially finished assembly starts its serialization during the lifecycle of the work order. This again depends on the serial control policies of the primary product and the enablement of the serialization at a particular operation within the work order. | ||
BACK_TO_BACK_FLAG | VARCHAR2 | 1 | Flag to indicate that the work order is created as a result of a back-to-back flow. | ||
ORCHESTRATION_CODE | VARCHAR2 | 30 | Attribute made available for integrating stakeholders to retain and persist a handle in the work orders schema to filter out events that make only sense to them. Stakeholders include SCO and Planning. | ||
INTERFACE_SOURCE_CODE | VARCHAR2 | 30 | Attribute made available for integrating stakeholders to retain and persist a handle in the work orders schema to filter out events that make only sense to them. Stakeholders include SCO and Planning. | ||
SCO_SUPPLY_ORDER_ID | NUMBER | 18 | When SCO creates the Work Order, This column will be populated by the SCO process. This is nothing but a sco order reference. For manually created CM Orders, or when Planning creates the CM Order in Manufacturing directly, this reference will not be there. SCO then reads these SCO Unaware CM work orders via an ESS program and creates them in SCO repository. | ||
CONTRACT_MFG_FLAG | VARCHAR2 | 1 | Flag to indicate that the work order is a contract manufacturing work order. | ||
CM_PO_HEADER_ID | NUMBER | 18 | Contract Manufacturer's purchase order identifier. | ||
CM_PO_LINE_ID | NUMBER | 18 | The reference to the contract manufacturers PO Line ID. In R11, The PO Line will have the item that is identified as a CM Service Item (or also called as the CM FG Server in the examples) in the PO Line. It is not the Primary Product on the work order. | ||
CM_PO_LINE_LOC_ID | NUMBER | 18 | The reference to the contract manufacturers PO Schedule Line Reference. This will be populated only when the WO is created in the CM Org. | ||
ORDER_LESS_FLAG | VARCHAR2 | 1 | Flag to indicate if the work order represents an 'orderless' order. | ||
SOURCE_SYSTEM_TYPE | VARCHAR2 | 30 | Source system type that interfaces the data to manufacturing. It could either come from a Fusion application in that case the source system type value will be "INTERNAL". When interfaced from a third party system the source system type will be "EXTERNAL". Valid values exist in the lookup with lookup_type = ORA_WIE_SOURCE_SYSTEM_TYPE. | ||
SOURCE_SYSTEM_ID | NUMBER | 18 | Source system identifier. When the source_system_type = "INTERNAL" it will be the application_id. When the source_system_type = "EXTERNAL", it will be the system id defined in the source system's table. | ||
SOURCE_HEADER_REF | VARCHAR2 | 240 | Represents the source system's user-facing header reference identifier. | ||
SOURCE_HEADER_REF_ID | NUMBER | 18 | Represents the source system's internal header reference identifier. | ||
SOURCE_LINE_REF | VARCHAR2 | 240 | Represents the source system's user-facing line reference identifier. | ||
SOURCE_LINE_REF_ID | NUMBER | 18 | Represents the source system's internal line reference identifier. | ||
MNT_FORECAST_ID | NUMBER | 18 | Reference to the maintenance forecast that created the work order. Foreign key to MNT_FORECASTS.FORECAST_ID. | ||
PJC_CONTEXT_CATEGORY | VARCHAR2 | 40 | Segment used to identify the descriptive flexfield application context for project-related standardized cost collection. | ||
PJC_PROJECT_ID | NUMBER | 18 | Identifier of the project used to build the transaction descriptive flexfield for project-related transaction distributions. Foreign key to PJF_PROJECTS_ALL_B.PROJECT_ID. | ||
PJC_PROJECT_NUMBER | VARCHAR2 | 25 | The number assigned to a project. | ||
PJC_TASK_ID | NUMBER | 18 | Identifier of the task used to build the transaction descriptive flexfield for project-related transaction distributions. Foreign key to PJF_PROJ_ELEMENTS_B.PROJ_ELEMENT_ID (however uses an alias of TASK_ID). | ||
PJC_TASK_NUMBER | VARCHAR2 | 100 | The identifying number for a task which is a subdivision of project work. | ||
PJC_EXPENDITURE_TYPE_ID | NUMBER | 18 | Expenditure type used to build the transaction descriptive flexfield for project-related transaction distributions. | ||
PJC_EXPENDITURE_ITEM_DATE | DATE | Date on which a project-related transaction is incurred. | |||
PJC_ORGANIZATION_ID | NUMBER | 18 | Identifier for expenditure organization used to build the transaction descriptive flexfield for project-related transaction distributions. | ||
PJC_BILLABLE_FLAG | VARCHAR2 | 1 | Flag that indicates if a project-related item is available to be billed to customers. Valid values are Y or N. | ||
PJC_CAPITALIZABLE_FLAG | VARCHAR2 | 1 | Flag that indicates if a project-related item is eligible for capitalization. Valid values are Y or N. | ||
PJC_WORK_TYPE_ID | NUMBER | 18 | Identifier for project-related classification of the worked performed. | ||
PJC_CONTRACT_ID | NUMBER | 18 | Identifier of contract. This attribute is used when Oracle Contract Billing or Oracle Grants Accounting is installed. | ||
PJC_CONTRACT_LINE_ID | NUMBER | 18 | Tracks contract line information. This attribute is used when Oracle Contract Billing or Oracle Grants Accounting is installed. | ||
PJC_FUNDING_ALLOCATION_ID | NUMBER | 18 | Specifies the name of the project funding override. This attribute is used when Oracle Contract Billing or Oracle Grants Accounting is installed. | ||
PJC_RESERVED_ATTRIBUTE1 | VARCHAR2 | 150 | Reserved for project-related functionality. | ||
PJC_RESERVED_ATTRIBUTE2 | VARCHAR2 | 150 | Reserved for future project-related functionality. | ||
PJC_RESERVED_ATTRIBUTE3 | VARCHAR2 | 150 | Reserved for future project-related functionality. | ||
PJC_RESERVED_ATTRIBUTE4 | VARCHAR2 | 150 | Reserved for future project-related functionality. | ||
PJC_RESERVED_ATTRIBUTE5 | VARCHAR2 | 150 | Reserved for future project-related functionality. | ||
PJC_RESERVED_ATTRIBUTE6 | VARCHAR2 | 150 | Reserved for future project-related functionality. | ||
PJC_RESERVED_ATTRIBUTE7 | VARCHAR2 | 150 | Reserved for future project-related functionality. | ||
PJC_RESERVED_ATTRIBUTE8 | VARCHAR2 | 150 | Reserved for future project-related functionality. | ||
PJC_RESERVED_ATTRIBUTE9 | VARCHAR2 | 150 | Reserved for future project-related functionality. | ||
PJC_RESERVED_ATTRIBUTE10 | VARCHAR2 | 150 | Reserved for future project-related functionality. | ||
PJC_USER_DEF_ATTRIBUTE1 | VARCHAR2 | 150 | Reserved for user-definable project information. | ||
PJC_USER_DEF_ATTRIBUTE2 | VARCHAR2 | 150 | Reserved for user-definable project information. | ||
PJC_USER_DEF_ATTRIBUTE3 | VARCHAR2 | 150 | Reserved for user-definable project information. | ||
PJC_USER_DEF_ATTRIBUTE4 | VARCHAR2 | 150 | Reserved for user-definable project information. | ||
PJC_USER_DEF_ATTRIBUTE5 | VARCHAR2 | 150 | Reserved for user-definable project information. | ||
PJC_USER_DEF_ATTRIBUTE6 | VARCHAR2 | 150 | Reserved for user-definable project information. | ||
PJC_USER_DEF_ATTRIBUTE7 | VARCHAR2 | 150 | Reserved for user-definable project information. | ||
PJC_USER_DEF_ATTRIBUTE8 | VARCHAR2 | 150 | Reserved for user-definable project information. | ||
PJC_USER_DEF_ATTRIBUTE9 | VARCHAR2 | 150 | Reserved for user-definable project information. | ||
PJC_USER_DEF_ATTRIBUTE10 | VARCHAR2 | 150 | Reserved for user-definable project information. | ||
IOT_SYNC_STATUS | VARCHAR2 | 30 | This column tracks the status of the data synchronization of the work order object to IoT Production Monitoring Cloud. Valid values exist in the lookup with lookup type = ORA_WIE_IOT_SYNC_STATUS. | ||
PREASSIGN_LOT_FLAG | VARCHAR2 | 1 | Flag used to indicate that the lots for primary product and outputs can be pre-assigned in the work order. | ||
RESEQUENCE_FLAG | VARCHAR2 | 1 | Flag used to indicate if the work order has operations which can be re-sequenced while executing the operation. Valid values are Y or N. |
Indexes
Index | Uniqueness | Columns |
---|---|---|
WIE_WORK_ORDERS_B_GT_U1 | Unique | TEMPORARY_ROW_ID |