CST_WORK_ORDERS
This is the persistent table that stores work order information transferred from source manufacturing systems. This table will be source of truth for work order information within costing. Preprocessing program will generate a unique identifier for every external_system_reference + external_system_ref_id and the surrogate will be used to identify these work orders in downstream costing tables.
Details
-
Schema: FUSION
-
Object owner: CST
-
Object type: TABLE
-
Tablespace: Default
Primary Key
| Name | Columns |
|---|---|
|
CST_WORK_ORDERS_PK |
CST_WORK_ORDER_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| CST_WORK_ORDER_ID | NUMBER | 18 | Yes | Surrogate identifying a work order uniquely in costing. | |
| EXTERNAL_SYSTEM_REFERENCE | VARCHAR2 | 60 | Yes | Code identifying the external system owning this work order definition. | |
| EXTERNAL_SYSTEM_REF_ID | VARCHAR2 | 30 | Yes | Surrogate ID identifying the work order in the source system. Manufacturing work order ID. | |
| WORK_ORDER_NUMBER | VARCHAR2 | 120 | Yes | Work Order Number in manufacturing. The uniqueness of which will be controlled by user at the work method level or at the plant level. | |
| INVENTORY_ORGANIZATION_ID | NUMBER | 18 | Yes | Manufacturing Organization in which the work order is created. | |
| WORK_METHOD_ID | NUMBER | 18 | Yes | The work method that will be used to execute the work order. The Master table for which is WIS_WORK_METHODS_B/TL. | |
| WORK_ORDER_TYPE | VARCHAR2 | 30 | Yes | Based on the Work Method, this attribute further classifies the Work Order to indicate whether it is meant for either Standard or Non Standard Production. The value for which comes from a lookup_type = 'WIE_WO_TYPE'. This lookup is system defined and not alterable by the user. | |
| WORK_ORDER_SUB_TYPE | VARCHAR2 | 30 | For a specific Work Order Type, this attribute represents the specific nature of work being performed such as Standard Production, Prototyping, or Repair. The value for which comes from a lookup_type = 'WIE_WO_SUB_TYPE'. This is a user extensible lookup. | ||
| RESEQUENCE_FLAG | VARCHAR2 | 1 | Flag used to indicate if the operation can be re-sequenced while executing the operation. Valid values are Y or N. | ||
| INVENTORY_ITEM_ID | NUMBER | 18 | Yes | This refers to the primary product that needs to be manufactured, and can be any active item that has the "Build in WIP" flag checked at the Item Organization (Plant) level | |
| WORK_DEFINITION_ID | NUMBER | 18 | Surrogate ID identifying the work definition associated to the work order. | ||
| WORK_DEFINITION_VERSION_ID | NUMBER | 18 | Surrogate ID identifying the work definition version. | ||
| WORK_DEFINITION_AS_OF_DATE | TIMESTAMP | The "As-Of-Date" is used to figure out the proper version of the work order when the Org + Product + "As-Of-Date" is provided as the filter criteria in narrowing down the work order. | |||
| WORK_ORDER_STATUS_ID | NUMBER | 18 | Yes | Work Order Status Identifier. Statuses are defined in a flexible user defined table. The user defined statuses will have to be defined on top of some seeded system statuses. The user defined status table is 'WIE_WO_STATUSES_B/TL'. The system statuses are seeded in the lookup type = 'WIE_WO_SYSTEM_STATUS'. | |
| RELEASED_DATE | TIMESTAMP | Date when the work order is released. | |||
| CLOSED_DATE | TIMESTAMP | Date when the work order is closed. This value is available only when the work order is currently in closed status. If a closed work order is reopened then this value would be updated accordingly. | |||
| COMPLETION_DATE | TIMESTAMP | Date when the work order is completed. This value is available only when the work order is currently in closed/completed status. If a closed work order is reopened this value is updated accordingly. | |||
| CONTRACT_MFG_FLAG | VARCHAR2 | 1 | Yes | Indicates if this work order is meant for contract manufacturing. | |
| CONTRACT_MFG_PO_LINE_LOC_ID | NUMBER | 18 | The reference to the purchase order schedule that is created for the contract manufacturing flow. | ||
| WORK_ORDER_LESS_FLAG | VARCHAR2 | 1 | When products have well defined product definitions, They can be produced by means of something called work order less completions. Such completion transaction can trigger the creation of a work order and marks that with the ORDER_LESS_FLAG = "Y". | ||
| INVENTORY_ASSET_FLAG | VARCHAR2 | 1 | Internal column. Indicates whether the end item on the work order is asset or expense. | ||
| 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_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_ORGANIZATION_ID | NUMBER | 18 | Identifier for expenditure organization 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_EXPENDITURE_TYPE_ID | NUMBER | 18 | Expenditure type used to build the transaction descriptive flexfield for project-related transaction distributions. | ||
| 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_WORK_TYPE_ID | NUMBER | 18 | Identifier for project-related classification of the worked performed. | ||
| PJC_CAPITALIZABLE_FLAG | VARCHAR2 | 1 | Flag that indicates if a project-related item is eligible for capitalization. Valid values are Y or N. | ||
| 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_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. | ||
| COUNTRY_OF_ORIGIN_CODE | VARCHAR2 | 2 | Code for the country of manufacture used to stripe Inventory transactions | ||
| 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. | ||
| REQUEST_ID | NUMBER | 18 | Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row. | ||
| JOB_DEFINITION_NAME | VARCHAR2 | 100 | Enterprise Service Scheduler: indicates the name of the job that created or last updated the row. | ||
| JOB_DEFINITION_PACKAGE | VARCHAR2 | 900 | Enterprise Service Scheduler: indicates the package name of the job that created or last updated the row. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| CST_WORK_ORDERS_N1 | Non Unique | Default | UPPER("WORK_ORDER_NUMBER") |
| CST_WORK_ORDERS_N2 | Non Unique | Default | TRUNC("RELEASED_DATE") |
| CST_WORK_ORDERS_PK | Unique | Default | CST_WORK_ORDER_ID |
| CST_WORK_ORDERS_U1 | Unique | Default | EXTERNAL_SYSTEM_REFERENCE, EXTERNAL_SYSTEM_REF_ID |
| CST_WORK_ORDERS_U2 | Unique | Default | EXTERNAL_SYSTEM_REFERENCE, WORK_ORDER_NUMBER, INVENTORY_ORGANIZATION_ID |