Work order
Use this function to create a new work order or select an existing work order for amendment. A work order is an order to make 1 or more products. Conventionally, the work order uses a bill of material (BOM) to create a list of materials to be issued, and a routing to make a list of operations to be performed on work centers.
You can create both planned work orders and firm production works orders for a single, or multiple BOMs. Planned orders cannot be allocated, printed, or tracked. They can, however, be scheduled, and can be respected by Material Requirements Planning (MRP). You assign the production routing needed to produce the goods but have the flexibility to add unexpected operations if necessary.
You can allocate materials to firm planned work orders from this function, and schedule operations directly.
You can also create prototype work orders for "in design" products where the product was created from a product design BOM that's still in design mode.
Prerequisites
Screen management
This function is customized to the needs of your organization and your processes. The transaction you select determines the way in which you enter information, and how information is displayed and printed.
If only 1 transaction has been set up you are not offered a choice, the default entry screen is displayed.
The Work order function contains a home section and 1 section per feature of the requirement:
- Home section. The home section provides key tracking information, including the allocated work order number.
- Header. This is the main section for this function. You use this section to define the product to be manufactured, the production start date, and the routing to be used.
- Components. This section displays the list of materials needed to produce the product.
- Operations. This section displays the operations that are used in the selected routing.
- Documents. This section is for information purposes only. It displays which production folder documents from those defined within the selected transaction code have been printed.
Home
The home section provides key tracking information for the work order.
Block number 1
| Planning site (PLNFCY) |
|
The planning site for the work order. The planning site and production site can be different. The production site defined on the user record is displayed by default but can be amended. |
| Production site (MFGFCY) |
|
The work order production site. The production site defined on the user record is displayed by default but can be amended. |
| Work order (MFGNUM) |
|
The work order reference. You can leave this field blank to generate the next sequential work order number. To amend an existing work order, select the Selection icon then select the work order you need from the displayed list. |
| Prototype (NPIPRO) |
|
Indicates if the work order is for an "in design" product. An "in design" product was created from a product design BOM revision. It has a New product in design mode warning displayed in the home section of the parent product. Note - informationYou cannot create a prototype work order to cover demand for a sales order.
|
Block number 2
Tab Header
You use this section to define the product to manufacture, the production start date, and the routing to use.
Your selected transaction determines if you can manufacture and release multiple products on a single work order.
Using versions: Released products and routings
You need to observe the following rule when using versions: Consistency between the start date of the work order and the version is demanded. This rule applies to the product to be released (BOM) and to the associated routing:
- When a work order is created for a versioned product (BOM), the selected version needs to be valid on the start date of the work order.
This rule applies when you create a work order for a versioned product, and when a BOM with versioned components is deployed from a Material Requirements Planning (MRP) process. - When you create a work order for a versioned BOM, the system automatically proposes the routing. If the routing is also version managed, the system selects the routing version that's valid on the start date of the work order.
If you change the default version, the version selection screen only displays those routing versions that are available for use on the start date. The list includes those versions with an exception date that matches the start date. - Backward or upstream scheduling can result in a change to the start date of the work order. If the scheduling process changes the start date, the system automatically rechecks the selected versions of the BOM then the routing are still consistent, or valid with the new start date.
If there's an inconsistency between the BOM or routing version and the new start date, the work order is created but it is not scheduled.
Where an inconsistency between a BOM or routing version and the start date is indicated, you need to change the version or reschedule the work order.
Grid: Products released
| UPDFLG |
| A line number in the grid. |
| Product (ITMREF) |
|
The code of the product to be released. The product code needs to be valid for the defined production site. Certain criteria apply to the selected product before it can be processed. It needs to be a manufactured product, as defined by the product category, held in stock, as defined by the stock management mode, and be active, as defined by the product status. The bill of material (BOM) defines the materials, the components and ingredients needed to manufacture the product, and whether it's printed on pick lists. To add an unplanned by-product or secondary product to the work order, select the next line in the table then from the Actions icon, select Addition of a by-product. A by-product is a product that will be produced as a secondary result while making the main product. For example, if a component is cut from sheet metal, the offcuts can be returned to stock to be used for smaller components. |
| Description (ITMDES1) |
| The description from the product record. |
| Major version (ECCVALMAJ) |
|
The current version of the product. Major versions might be used where there have been increased or significant changes to the original or previous version. The "form, fit, or function" has changed. You can enter a different version of the product. This field is not available for entry if the product code defined in the Product field is not version managed. |
| Minor version (ECCVALMIN) |
|
The current minor version of the product. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version. You can enter a different version of the product. This field is not available for entry if the product code defined in the Product field is not version managed. |
| Change request (CRID) |
|
This field displays a change request ID if the product, or the specific version or revision of the product is associated with an "active" change request. An active change request is a change request at the planning or implementation stage of the processing cycle. A warning icon is displayed with this field. Note - tipIf a warning icon is displayed, put your work order on hold until the relevant change request has been closed. At that point a change to the product will have either been seen through to its conclusion and the change delivered, or the change request rejected. You’re authorized to progress the work order if you need to.
|
| Line status (ITMSTA) |
| This field tracks the progress and status of the work order line. You cannot modify it. |
| REL (UOM) |
|
The release volume or mass unit of measure for the product for the order. The unit and any applicable unit conversion are defined for the product on the product record. Note - informationYou cannot create a prototype work order to cover demand for a sales order.
|
| Release qty (UOMEXTQTY) |
| The planned quantity. The quantity is expressed in the release unit. The base quantity for the product defined on the bill of material (BOM) record loads by default but can be amended. |
| REL-STK (UOMSTUCOE) |
| The product-specific conversion factor applied between the stock unit and the release unit of measure. This unit conversion is defined for the product on the product record. |
| STK (STU) |
| The unit in which the product is stored. It provides the key to prices, costs, volumes, etc. |
| Expected STK qty (EXTQTY) |
| The planned quantity. The quantity is expressed in the stock unit. |
| BOM code (BOMALT) |
|
Multiple bills of material (BOMs) can be defined for a single product. Each BOM code can be assigned specific management features. For manufactured or subcontracted products this includes restriction of the BOM to a specific site and to specific areas of functionality (for costing or for capacity planning). The first valid BOM code for the product at the production site is displayed by default. |
| Description (TBOSHO) |
| The short description of the bill of material (BOM) code. |
| Project (PJT) |
|
Links production of the product with a specific project. You can enter one of the following:
If the value of this field includes a character such as an exclamation mark "!", this field links to the structure of the project. The character is the separator between a project code and the structure, either the project budget structure or the project operational (task) structure. For example, if a material task code is "USA-P3" and a project code is "USA12345678", this field displays a link to the project operational structure as "USA12345678!USA-P3." Note - informationTo provide a quick and easy visual reference, the link to the project or project structure is distinguishable by the number of separator characters used. If there's no separator, the link is made to the project. A single separator character such as an exclamation mark after the project code, the first code indicates that the link type is a task. The link is to the project operational structure. 2 separators placed after the project code mean that the link corresponds to a budget code. The link is to the project budget structure.
|
| Lot (LOT) |
|
The lot to assign to the released product, based on the product management mode. If the product is managed with automatic lot numbers, the lot number is assigned when the work order is created. |
| Ship-to type (BPCTYPDEN) |
| The destination for the product. This can be a site or a customer. |
| Destination (BPCNUM) |
| The site or customer to ship the product to. The appropriate reference is determined by the value of the Ship-to type field (BPCTYPDEN). |
| Description (BPCDES) |
| The destination site name, or the destination corporate or company name. The appropriate reference is determined by the value of the Ship-to type field (BPCTYPDEN). |
| Original document (VCRNUMORI) |
| The journal number at the origin of the requirement. |
| Origin line (VCRLINORI) |
| The associated line on the source document or order. |
| WO description (MFGDES) |
| A short free-format description or reference for the order. |
| Type (ITMTYP) |
|
The type of product that's on the order line. Product: A manufactured product. An order line is generated for the parent product and for each component in the bill of material (BOM). By-product: A secondary product. An order line is generated for the product. |
| Shrinkage % (SHR) |
| The loss percentage corresponds to the production loss reported with each operation. The quantity to be produced at the next operation is decreased by this reported average loss. |
| Planner (PLANNER) |
| The operator in charge of performing the production planning or product ordering. |
| Production request (XFMI) |
|
Indicates if the work order line was created as a back-to-back order from a sales order. Yes: The work order released product line was created to meet a product line in a demand order. No: The work order released product line was added to the work order manually. |
| CCE1 |
|
The analytical dimensions are initialized in compliance with the Default dimensions setup. Entry or modification of an analytical dimension is determined by the selected entry transaction. When an analytical dimension is used for tracking Project management costs in finance from work orders, the assigned Project code (PJT) determines the Project analytical dimension (CCE(n)). For any subsequent product lines on a work order, project analytical dimensions for the released product are initialized for the assigned project, whereas the components in the bill of material (BOM) and routing operations are initialized for the project assigned to the first released product line on the order. Note - dangerA modification to the Project code (PJT) can result in the Project analytical dimension code (CCE(n)) being reinitialized.
|
Lead time
| Scheduling mode (SCDMOD) |
|
The scheduling method for the work order. Backward: With "backward" or upstream scheduling, the system calculates the production start date (Start date field) from the end or completion date (End date field). Forward: With "forward" or downstream scheduling, the system calculates the completion date (End date field) from the defined production start date (Start date field). These calculations rely on the production lead time, reduction factor, and economic quantity defined on the product-site record. Note - tipThe transaction you select determines if this field is available for entry.
|
| Start date (STRDAT) |
|
The planned production start date. The date is determined by the Scheduling mode:
|
| End date (ENDDAT) |
|
The end or the work order completion date. The date is determined by the Scheduling mode:
|
| Lead-time (+QC) (AVAOFS) |
|
The operation lead-time is used during launch and in the MRP calculations. It’s used to calculate the date of the component or material requirement with respect to the production start date of the parent product. It’s expressed in calendar days. You can enter a negative value. Example
A work order start date is June 26:
|
| % LT reduction (LTIREDCOE) |
|
Based on the selected transaction, increases or decreases the lead times for all the work order operations. By default, the lead time reduction rate suggested is defined by the GPERCOMP—% default LT reduction parameter (GPA chapter, LOA group). The times affected by the reduction are defined by the GTPSCOMP—Lead-time reduction parameter (GPA chapter, LOA group). If the lead time reduction percentage is represented by x, and if x is between 1 and 100 (ranges included), times are decreased by x%. If x is greater than or equal to 101, times are increased by (x - 100)%. |
Block number 3
| Priority (MFGPIO) |
| Assigns a priority to the work order. |
| Planned quantity (MFGEXTQTY) |
| The planned quantity. The quantity is expressed in the stock unit. |
| MFGSTU |
| The release volume or mass unit of measure for the products on the order. The unit and any applicable unit conversion are defined on the product record. |
| Allocation (XALLSTA) |
|
The Allocation (materials), Scheduling, and Status fields display a status for the work order. These fields update automatically. The current status or progress of the work order displays in the Scheduling and Status fields. Selected combinations to note are as follows:
The work order allocation values are defined in the 336 local menu. The scheduling status values are defined in the 335 local menu. The work order status values are defined in the 339 local menu. Note - settingsFor detailed scheduling, the POPS—Production Scheduler activity code activates the Production Scheduler functionality or the generic Finite scheduler interface.
Note - informationProduction Scheduler only applies to on-premises instances of Sage X3. The generic Finite scheduler interface provides an integration connector to any web scheduling solution for either cloud or on-premises solutions.
|
| Scheduling (XSCDFLG) |
|
The Allocation (materials), Scheduling, and Status fields display a status for the work order. These fields update automatically. The current status, or progress of the work order displays in the Scheduling and Status fields. Selected combinations to note are as follows:
The work order allocation values are defined in the 336 local menu. The scheduling status values are defined in the 335 local menu. The work order status values are defined in the 339 local menu. Note - settingsFor detailed scheduling, the POPS—Production Scheduler activity code activates the Production Scheduler functionality or the generic Finite scheduler interface.
Note - informationProduction Scheduler only applies to on-premises instances of Sage X3. The generic Finite scheduler interface provides an integration connector to any web scheduling solution for either cloud or on-premises solutions.
|
| Status (XTRKFLG) |
|
The Allocation (materials), Scheduling, and Status fields display a status for the work order. These fields update automatically. The current status, or progress of the work order displays in the Scheduling and Status fields. Selected combinations to note are as follows:
The work order allocation values are defined in Local menu 336. The scheduling status values are defined in Local menu 335. The work order status values are defined in Local menu 339. Note - settingsFor detailed scheduling, the POPS—Production Scheduler activity code activates the Production Scheduler functionality or the generic Finite scheduler interface.
Note - informationProduction Scheduler only applies to on-premises instances of Sage X3. The generic Finite scheduler interface provides an integration connector to any web scheduling solution for either cloud or on-premises solutions.
|
Routing
| Number (ROUNUM) |
|
The routing code describes the process involved in manufacturing or processing a product. It describes the sequence of operations and tools that are involved in producing or processing a particular product. The routing code matches the product code. The product code can be a manufactured product, a bill of material, or a generic reference to a parent routing that's linked to several products. By default, the system presents the first valid production routing for the released product at the production site unless the product is not linked to a standard routing, in which case this particular routing is submitted. Select the Selection icon to open the list of valid routings for the released products. A control is performed to check consistency between the following:
|
| Code (ROUALT) |
| Multiple routings can be defined for a single product. Each routing code can be assigned specific management features. These include restriction of the routing to a specific site and to specific areas of functionality such as for use in a manufacturing environment, for costing, or for capacity planning. |
| Major version (ROUECCMAJ) |
|
The version of the routing that applies on the scheduled start date (Start date field), if the selected routing is version managed. You can enter a different routing version. Major versions might be used where there have been increased or significant changes to the original or previous version. The "form, fit, or function" has changed. This field is not available for entry if the displayed routing code is not version managed. Note - informationIf you select a different version of this routing, the version selection screen only displays those versions that are available for use on the scheduled start date. The list includes those versions with an exception date that matches the start date. You can, however, use the Routing management (GESROU) function to view all versions of the selected routing. The operations used for the selected version of the routing load automatically if permitted for the release mode defined in the header information. If you change the routing version to comply with a change to the production start date, the routing operations reload accordingly.
|
| Minor version (ROUECCMIN) |
|
The minor version of the routing. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version. This field is not available for entry if the displayed routing code is not version managed. |
| Popup view |
| Select Popup view from the Actions icon to enter the production information for the product using the standard screen display mode. |
| Manufacture detail |
| Select Manufacture detail from the Actions icon to view the product details as planned for the work order. |
| Tracking status |
| Select Tracking status from the Actions icon to view, in summary, the quantities in progress for the work order. |
| Stock - Site |
| Select Stock - Site from the Actions icon to view the inventory levels for the selected product, by site. |
| Management data |
| Select Management data from the Actions icon to view inventory management data for the product. |
| Projected stock |
| Select Projected stock from the Actions icon to view the projected stock movements for the product at 1 or all sites. |
| Available stock |
| Select Available stock from the Actions icon to project the available and available to promise stock for the product at the site in periods of days, weeks, or months. |
| Assignments |
| Select Assignments from the Actions icon to use the assignment workbench to assign the work order to meet demand. |
| Product-site |
| Select Product-site from the Actions icon to view the data associated with the product at the site. |
| Product notes |
|
Select Product notes from the Actions icon to open a window displaying notes associated with the product. This information can relate to product availability, additional or substitute products, or a promotional message. This window could open automatically depending on the setup defined when creating the notes. Note - informationNotes are limited to a screen inquiry. You cannot print them. For further information, see the documentation on Notes.
|
| Addition of a by-product |
|
Select Addition of a by-product from the Actions icon to add an unplanned by-product or secondary product to the work order. A by-product is a product that's produced as a secondary result while making the main product. For example, if a component is cut from sheet metal, the offcuts can be returned to stock to be used for smaller components. Note - warningProduction Scheduler cannot include "by-products" in the scheduling process.
Note - informationProduction Scheduler only applies to on-premises instances of Sage X3.
|
Tab Components
You use this section to add or amend the components needed to produce the product.
The release mode defined in the home section determines if the list of components loads automatically from the bill of material (BOM) record. The default order for the list of components reflects the order of the components in the BOM, but can be amended.
The CUMMAT—Material total mode parameter (GPA chapter, WOM group) defines whether components that appear multiple times are consolidated onto a single line, and at which stage in the process.
The default information for each component is obtained from the BOM record. You can modify selected information, including the following:
- The quantity of the component and the date the component is needed. This adjusts the allocations automatically. You can view updated quantities for the component by selecting Tracking status from the Actions icon.Note - informationYou cannot change the date a component is needed if it's been consumed or partially consumed.
- The percentage of the component that you expect to be scrap. Adding or changing the scrap percentage results in the required quantity (Requirement qty field) being recalculated automatically.
- The assigned operation.
- The operation lead time, and the Materials requisition printing field on the material issue note.
Amendments to the components of a versioned BOM are tightly controlled. You can only change what's considered within the context of amendments to work orders to be critical fields if you’re an authorized user. This includes changing the required quantity of a component or adding a new component. You’re forced to provide a reason for the change if the MFGREV—Revision management parameter (GPA chapter, WOM group) is set.
You can change a component for a different component provided the original component is not allocated.
Component availability
Component availability can directly impact the scheduling of operations needed to manufacture a product.
Many factors affect the availability of a component such as demand and replenishments, free stock, and lead times. Your system suggests an earliest date of first availability for each component. We refer to this suggested earliest date of first availability calculation as the "First Date of Material Availability" (FDMA). The calculation observes the following principles when determining each "first availability" date:
- It recognizes existing assignments.
- It consumes any free (available) stock (where Free stock = Physical stock - Allocated stock - Assigned stock).
- It considers expected receipts.
- It determines if unassigned stock awaiting partial assignment to an order can be used.
- It makes minimal changes to existing assignments.
- Where shortages (calculated as Demand - Allocated stock - Assigned stock > 0) exist, it runs the calculation based on the lead time for the shortage only.
The calculated or suggested First Date of Material Availability is displayed for each component in the First availability field.
| Current date: | May 25 |
| Component requirement (demand): Required date: |
30 units June 15 |
| Current free stock (component) quantity: | 10 units |
| Expected component receipt quantity: Expected component receipt date: |
15 units May 31 |
| Last assignment quantity: Last assignment date: |
5 units June 2 |
| Earliest date of component availability: | June 2 |
Component availability: Rule
An operation should only be scheduled to start on a date when the full quantity of each component needed for the operation is available.
All components not directly linked to a specific operation need to be available at the start of the first operation. Therefore the latest availability of all non-linked components determines the start date of the first operation.
All components directly linked to a specific operation need to be available only at the start of the specific operation. Therefore the availability of the linked component determines the start date of the operation. If multiple components are linked to the same operation, the latest availability of the linked components determines the start date of the operation.
If a work order has multiple components with a combination of linked and non-linked components, the latest availability of all non-linked components determines the start date of the first operation. The availability of linked components determines the start date of that specific operation.
Component availability: Operation scheduling
The Sage X3 scheduling process does not consider component availability when determining operation start dates. Operation start dates are scheduled according to the scheduling rules, as determined by the Scheduling mode and by the Scheduling status fields. However, the calculated component First Date of Material Availability is used to obtain a suggested operation start date following the rules for non-linked/linked components described in Component availability: Rule. The calculated (suggested) operation start date is displayed for each operation in the Earliest start field. If you use Production Scheduler, Sage X3 WebScheduling, or any web scheduling solution developed by an ISV (independent software vendor) for detailed planning, the scheduler can use the dates from the First Date of Material Availability calculation as a constraint when optimizing the operations.
Component availability: First Date of Material Availability calculation purpose
The objective of the First Date of Material Availability calculation is as follows:
- To calculate for each component of a work order, the date when the component availability can cover, in full, the required quantity. This becomes a reference date, which is displayed for each component in the First availability field.
- To calculate for each operation, a start date when the full quantity of each component needed for the operation is available. This becomes a reference date, which is displayed for each operation in the Earliest start field.
- To transfer the earliest operation start date to Production Scheduler, Sage X3 Web Scheduling, or the web scheduling solution. The scheduler can then use the component availability as a constraint when optimizing the operations.
Block number 1
| WO expected quantity (MFGEXTQTY) |
| The planned quantity. The quantity is expressed in the stock unit. |
| Producible quantity (AVAMFGQTY) |
| The maximum quantity in the release unit that can currently be produced with the resources available. It’s only displayed after components are allocated. |
| MFGSTU |
| The unit in which the product will be manufactured. It provides the key to prices, costs, volumes, etc. |
Grid
| Component (ITMREF) |
|
A component that's needed to produce the product. The list of components loads automatically from the bill of material (BOM) record. The default order for the list of components reflects the order of the components in the BOM, but can be amended. The CUMMAT—Material total mode parameter (GPA chapter, WOM group) defines whether components that appear multiple times are consolidated onto a single line, and at which stage in the process. |
| Description 1 (ITMDES1) |
| The description from the product record. |
| Major version (ECCVALMAJ) |
|
Indicates which version of the component applies. Major versions might be used where there have been increased or significant changes to the original or previous version. The "form, fit, or function" has changed. This field is not populated if the component code defined in the Component or Material field is not version managed. |
| Minor version (ECCVALMIN) |
|
Indicates which minor version of the component applies. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version. This field is not populated if the component code defined in the Component or Material field is not version managed. |
| Change request (CRID) |
|
This field displays a change request ID if the component, or the specific version or revision of the component is associated with an "active" change request. An active change request is a change request at the planning or implementation stage of the processing cycle. A warning icon is displayed with this field. Note - informationIf a warning icon is displayed, you should consider delaying the work order until the change request identified is closed. At that point a change to the component will have either been seen through to its conclusion and the change delivered, or the change request rejected. You will not be prevented from progressing the work order if you decide to do so.
|
| Line status (XMATSTA) |
| This field tracks the progress and status of the component. |
| Requirement qty. (RETQTY) |
|
The quantity of the component needed to produce the released product. This figure is calculated from the planned quantity (Release qty field) and the component quantity defined on the bill of material (BOM) record. This value can be modified. Note - settingsYou need to be authorized to change this figure if this is a component of a versioned product (BOM).
|
| First availability (FDMA) |
|
Many factors affect the availability of a component such as demand and replenishments, free stock, and lead times. This date is calculated by your system. It’s the suggested earliest date when the availability of the component can cover, in full, the required quantity. The calculation observes the following principles when determining each "first availability" date:
Note - informationThis date is only a reference date. It’s an indication of the "First Date of Material Availability."
|
| STK (STU) |
| The unit in which the product is stored. It provides the key to prices, costs, volumes, etc. |
| Type (TYPQTY) |
|
Indicates if the component is stored in stock. Physical: This is a physical component. Quantities are stored in stock. Active: This is an active component such as nails or staples. Quantities are not stored in stock. Note - tipActive components have a "potency" percentage defined on the stock record.
|
| Allocated qty. (ALLQTY) |
| The quantity allocated to the order line. |
| Shortage (SHTQTY) |
|
The quantity of the component that's outstanding for the work order to be completed. Note - informationThis quantity is ignored if the Release if shortage checkbox on the Product-site record is selected.
|
| Available qty. (AVAQTY) |
| The available quantity expressed in the stock unit of the components. |
| Consumed qty. (USEQTY) |
| The quantity of the component consumed to produce the bills of material (BOMs) on the work order. |
| Allocation (ALLSTA) |
| Requirement date (RETDAT) |
| The date the component is needed. |
| Op. (BOMOPE) |
|
Assigns the component to a specific operation in a production routing, according to the manufacturing requirements. Note - settingsYou need to be authorized to assign or reassign an operation if this is a component of a versioned product (BOM).
|
| % scrap (SCA) |
|
The percentage of the component that you expect to be scrap or lost during the production process. Inquiries can display the following figures:
|
| Component type (CPNTYP) |
|
The component type. Normal: A component defined on the bill of material. By-product: An unplanned by-product or secondary product. Text: Free-format text. Costing: When a value is calculated for the provisional cost and the production cost price of the parent product. |
| Shrinkage considered (RELSCATIA) |
| This field is used for managing losses incurred during production. It applies to the parent product (BOM). Set to No, any loss percentages defined on the components of the BOM are ignored. |
| BOM sequence (BOMSEQ) |
| Identifies the sequence number of the component in the BOM (bill of material). |
| WO line (MFGLIN) |
| The line number of the released product. |
| Planner (PLANNER) |
| The operator in charge of performing the production planning or product ordering. |
| Total (CUMFLG) |
| Select Yes to display the total available stock. |
| Pick list (PICPRN) |
| Indicates if the component needs to be printed on the material issue slip. |
| Type of supply (SCOFLG) |
| The replenishment source for the component. This might be Internal, made available to a subcontractor, or supplied by a subcontractor. |
| Pick list code (PKC) |
|
Informs warehouse staff of any actions that apply when the component is picked for issue. You can select one of the following actions:
Note - settingsThis field is only available if the MWM—Weighing station activity code is active.
Note - settingsYou need to be authorized to change this statement if this is a component of a versioned product (BOM).
|
| Master container (CTN) |
| Container capacity (CTNCAP) |
| Container weight unit (CTNWEU) |
| Revision reason (REVREASON) |
|
This field supports changes to a component line and changes to the work order header. Changes to the work order header information can result in the products to be released being reloaded with the default information from the BOM record. This results in any previous changes to the components being removed. Changes include editing the work order start date or the planned quantity. Use this field to explain the reason you made the change. This provides traceability by writing details to the Work order-component audit table (MFGMATREV). The audit details include the revision reason from this field, a revision code, and key details from the component line. Note - settings
You need to enter the reason if the product to be released is version-managed and the MFGREV—Revision management parameter (GPA chapter, WOM group) is set. Refer to the documentation on the MFGREV—Revision management and TRACKMATWO—Track a WO component change parameters. Note - tipRefer also to the Revision history action.
|
| CCE1 |
|
The analytical dimensions are initialized in compliance with the Default dimensions setup. Entry or modification of an analytical dimension is determined by the selected entry transaction. When an analytical dimension is used for tracking Project management costs in finance from work orders, the assigned Project code (PJT) determines the Project analytical dimension (CCE(n)). For any subsequent product lines on a work order, project analytical dimensions for the released product are initialized for the assigned project whereas the components in the bill of material (BOM) and routing operations are initialized for the project assigned to the first released product line on the order. Note - dangerA modification to the Project code (PJT) can result in the Project analytical dimension code (CCE(n)) being reinitialized.
|
| Sort by operation / material | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Select Sort by operation / material from the Actions icon to sort the components based on the order of the operations they're attached to. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sort by product / sequence | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Select Sort by product / sequence from the Actions icon to revert the list of components to the default order, as determined by the line sequence of the components in the bill of material (BOM). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Material detail | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Field descriptions
Block number 1
Management
Operation
MiscellaneousRequirement
Select Material detail from the Actions icon to do the following:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exclude line/Reactivate | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Exclude line from the Actions icon to exclude or cancel the component. To reinstate the canceled component, select Reactivate. Note - tip You cannot exclude a component if it’s already allocated.
Note - settings
You need to be authorized to perform these actions if this is a component of a versioned product (BOM). If the MFGREV—Revision management (GPA chapter, WOM group) or TRACKMATWO—Track a WO component change parameter is set to Yes, you can provide a reason for taking the action in the Revision reason field. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Global allocation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Global allocation from the Actions icon to perform a global allocation of the selected component. Global allocation does not specify the details of the stock to be consumed, such as the location or lot. Global allocation simply increments the reserved stock for the component and decreases its available stock. When the materials are consumed, the system changes the global allocation to a detailed allocation. Note - informationSee also the Allocations action.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Manual allocations | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Manual allocations from the Actions icon to manually allocate the selected component. A screen is displayed summarizing all the lines from which allocations can be selected. These include the lot, sublot, version, serial number, and location. If the component is already allocated, the allocated lines are displayed. You can modify the selection or delete the allocations by selecting the Clear action. If the material has not been allocated, or you’ve deleted the allocations, the system can perform the allocation for you. Select the Proposal action. You can specify a preferred lot, location, or status. The system displays the lines selected for allocation. You can modify the selections if needed. Note - informationRefer also to the Allocations action.
Note - warningYou can only allocate individual serial numbers if the Serial number management field on the component record is set to Received/Issued. If it's set to Global Received/Issued, you can only select the lot to allocate the serial numbers from.
Note - informationRequesting a global allocation of all components does not affect manually allocated components.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| View allocation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select View allocation from the Actions icon to view the allocations for the selected component. Note - informationRefer also to the Allocations action.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Projected Stock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Select Projected stock from the Actions icon to view the projected stock movements for the component at 1 or all sites. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Text | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Select Text from the Actions icon to view, enter, or modify text associated with the component. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Tracking status | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Tracking status from the Actions icon to view, in summary, the quantities of the component in progress for the work order. The screen summarizes the line status (pending, in process, completed), the planned and consumed quantities, the material allocation status (global, detailed allocation, with or without shortage), and specifies whether negative stock is authorized for the component or not. If the component is allocated, the system can submit the allocation detail inquiry by quantity, lot, location, and stock status. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Management data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Select Management data from the Actions icon to view inventory management data for the component. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Assignments | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Select Assignments from the Actions icon to use the assignment workbench to assign the component to meet demand. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Product-site | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Select Product-site from the Actions icon to view the inventory levels for the selected component, by site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Revision history | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Revision history from the Actions icon to view a history of key changes to the selected component. This action is only active if the changes were saved. The revision history can include a revision reason, a revision code, and key details from the component line. The current details for the selected component are displayed on the first line of the table. Amended fields are highlighted. Note - settings
The MFGREV—Revision management parameter (GPA chapter, WOM group) needs to be set if the component is a component of a versioned product (BOM). Refer to the documentation on the MFGREV—Revision management and TRACKMATWO—Track a WO component change parameters. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Add unexpected material | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Add unexpected material from the Actions icon to add an unplanned component. If the work order is already allocated, you need to enter the details. Note - settings
You need to be authorized to perform this action and provide a reason in the Revision reason field if the work order is for a versioned product (BOM). Refer to the documentation on the MFGREV—Revision management and TRACKMATWO—Track a WO component change parameters. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Add sub-assembly (phantom) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Add sub-assembly (phantom) from the Actions icon to add a phantom product to the work order. The system explodes the selected product to insert its components. If one of the components is a phantom component, the system checks the availability of stock at the time of release. If sufficient stock exists to at least partially cover the requirement, the system proposes the stock is consumed. The phantom and its components are displayed in the list of components. Note - settings
You need to be authorized to perform this action and provide a reason in the Revision reason field if the work order is for a versioned product (BOM). Refer to the documentation on the MFGREV—Revision management and TRACKMATWO—Track a WO component change parameters. |
Tab Operations
You use this section to add or amend the operations needed to manufacture the product.
The release mode defined in the header information determines if the operations used in the selected routing load automatically.
The scheduling mode is displayed as well as the scheduling status such as order scheduled, to be rescheduled, or not scheduled.
The default information for each operation is obtained from the routing. You can modify selected information, including the following:
-
The planned quantity for an operation.
Note - informationThe operation closes automatically if you reduce the planned quantity. - The assigned work center, provided the operation has not started.
Amendments to the operations are tightly controlled in a work order with both a versioned product and a versioned routing. You can only change what's considered within the context of amendments to work orders to be critical fields if you’re an authorized user. This includes changing machinery running costs or adding a new operation. You’re forced to provide a reason for the change if the MFGREV—Revision management parameter (GPA chapter, WOM group) is set.
A subcontract operation can be planned. Subcontract is the term used to describe the purchase of a service for carrying out an operation for a work order. The subcontract operation time is updated with the reorder lead time planned in the purchase record of the subcontracted product. The work center is replaced by the subcontract work center planned for the operation. You can also enter details for, and then generate, a purchase order for a subcontract operation.
Operation start dates are scheduled according to the scheduling rules.These are determined by the scheduling mode and the scheduling status. The Sage X3 scheduling process does not consider component availability when determining operation start dates. However, an operation should only be scheduled to start on a date when the full quantity of each component needed for the operation is available. Therefore, a First Date of Material Availability (FDMA) calculation calculates for each operation, a start date when the full quantity of each component needed for the operation is available. This becomes a reference date that displays for each operation in the Earliest start field. If you use Production Scheduler, Sage X3 Web Scheduling, or a web scheduling solution for detailed planning, the scheduler can use the calculated earliest operation start date as a constraint when optimizing the operations.
You can set the date and start time for an operation in such a way that the scheduling will not question them. Checks are performed so that the constraints imposed by the scheduling codes of each operation are complied with.
Block number 1
Grid
| No. (OPENUM) |
| The sequence number of the operation. |
| Line status (OPESTA) |
| This field tracks the progress and status of the operation. |
| Work center (EXTWST) |
|
Identifies the production resource to use for the operation. Enter from the Work centers table, the code of the resource to be used for the operation. Note - settingsYou need to be authorized to change this resource if this is an operation in a versioned routing for a versioned product (BOM).
|
| Short description (EXTWSTSHO) |
| The short description defined for the selected work center. |
| Type (XWSTTYP) |
| Identifies the type of operation that's performed on the selected work center. This might be a machine, labor, or a subcontracted operation. Work centers of type Subcontracting are managed externally by subcontract suppliers. |
| Start (OPESTR) |
|
Identifies the date that the operation needs to start. The date is determined by the Scheduling mode and by the Scheduling status fields.
|
| End (OPEEND) |
|
Identifies the date that the operation needs to be completed. The date is determined by the Scheduling mode and by the Scheduling status fields.
|
| Earliest start (FDMA) |
|
Operation start dates are scheduled according to the scheduling rules, as determined by the Scheduling mode and the Scheduling status fields. However, the operation should only be scheduled to start on a date when the full quantity of each component needed for the operation is available. This date is calculated by your system. It’s a suggested earliest date when the full quantity of each component needed for the operation is available. Many factors affect the availability of a component such as demand and replenishments, free stock, and lead times. The calculation observes the following principles when determining each component "first availability" date and therefore the associated operation "earliest start" date:
Note - informationThe scheduling process does not consider component availability when determining operation start dates. This date is only a reference date. It’s an indication of the "First Date of Material Availability."
Note - informationIf you use Production Scheduler, Sage X3 Web Scheduling, or a web scheduler for detailed planning, the scheduler can use the calculated earliest operation start date as a constraint when optimizing the operations.
Note - settingsFor detailed scheduling, the POPS—Production Scheduler activity code activates the Production Scheduler functionality or the generic Finite scheduler interface.
Note - informationProduction Scheduler only applies to on-premises instances of Sage X3. The generic Finite scheduler interface provides an integration connector to any web scheduling solution for either cloud or on-premises solutions.
|
| Forced start (FRCSTRDAT) |
|
Use this field to modify the start date of a scheduled operation, thereby forcing the start date of the operation in the scheduling process. Note - warningIf you force a start date for the operation and you use Production Scheduler, Sage X3 Web Scheduling, or a web scheduler, you’re effectively preventing the scheduler from optimizing its scheduling capabilities. A forced start date on a work order fixes and automatically pins the start date for the operation in the planning schedule. The work order needs to be removed from the scheduling, the date adjusted accordingly (or deleted) then the work order resubmitted for scheduling as "pinned" operations are blocked from manual changes.
Note - settingsFor detailed scheduling, the POPS—Production Scheduler activity code activates the Production Scheduler functionality or the generic Finite scheduler interface.
Note - informationProduction Scheduler only applies to on-premises instances of Sage X3. The generic Finite scheduler interface provides an integration connector to any web scheduling solution for either cloud or on-premises solutions.
|
| Forced time (FRCSTRHOU) |
|
Use this field to modify the start time of a scheduled operation, thereby forcing the end date of the operation in the scheduling process. Note - warningIf you force a start time for the operation and you use Production Scheduler, Sage X3 Web Scheduling, or a web scheduler you’re effectively preventing the scheduler from optimizing its scheduling capabilities. A forced start time on a work order fixes and automatically pins the start time for the operation in the planning schedule. The work order needs to be removed from the scheduling, the time adjusted accordingly (or deleted) then the work order resubmitted for scheduling as "pinned" operations are blocked from manual changes.
Note - settingsFor detailed scheduling, the POPS—Production Scheduler activity code activates the Production Scheduler functionality or the generic Finite scheduler interface.
Note - informationProduction Scheduler only applies to on-premises instances of Sage X3. The generic Finite scheduler interface provides an integration connector to any web scheduling solution for either cloud or on-premises solutions.
|
| Work center group (WCR) |
| Identifies the group of work centers that the work center belongs to. Work center groups are used to review workloads. |
| Description (ROODES) |
| The description defined for the routing operation. |
| Number of resources (EXTWSTNBR) |
|
The number of this particular production resource that's needed for the operation. You can amend this figure. Note - settingsYou need to be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).
|
| Planned quantity (EXTQTY) |
|
The planned quantity expressed in the operation unit. Note - settingsYou need to be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).
|
| Unit (OPEUOM) |
| The unit in which the work order operation quantity is expressed. Work order operation quantities are expressed in the operation unit. |
| Time unit (TIMUOMCOD) |
| The unit of time in which the operation is measured. |
| Setup time (EXTSETTIM) |
|
The time that it takes for the machinery to be set up ready for use. The time is expressed in the defined time unit. The time can be zero. Note - settingsYou need to be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).
|
| Unit time (EXTUNTTIM) |
|
The time that it takes for the machinery to execute the operation. The time is expressed in the defined time unit. Note - settingsYou need to be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).
|
| Run time (EXTOPETIM) |
|
The time it takes to perform the operation for the number of items needed, as defined in the Planned quantity field. Note - settingsYou need to be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).
The operating time:
|
| Nonproductive time (FXDTIM) |
|
The total non-productive time. This is the sum of preparation time, waiting time, and post operation time. Non-productive, or delay time occurs after a process was completed on a machine and until the machine can next be used. It can be either transit time or breakdown time. Non-productive time is not taken into account as workload on the work station. |
| Setup + run time (VARTIM) |
| The sum of the setup time plus the run time for the number of items needed, as defined in the Planned quantity field. This is the time that it takes for the machinery to be set up ready for use plus the time it takes to perform the operation. The time is expressed in the defined time unit. |
| Subcontract (SCOCOD) |
| Indicates if the operation is subcontracted to an outside company. Subcontract is the term used to describe the purchase of a service for carrying out an operation for a work order. |
| Subcontract work center group (SCOWCR) |
| Identifies the group of work centers to which this subcontracted work center belongs. Work center groups are used to review workloads. |
| Subcon w/c (SCOWST) |
|
Identifies the production resource to use for the subcontracted operation. Enter from the Work centers table, the code of the subcontract resource to use for the operation. |
| Subcontract product (SCOITMREF) |
|
Identifies the service to be carried out by the subcontractor to execute the operation. Note - settingsYou need to be authorized to change this service if this is an operation in a versioned routing for a versioned product (BOM).
|
| Subcontract LT (SCOLTI) |
| The number of days for the subcontractor to execute the operation. |
| LT unit (JOUR1) |
| This field displays "Calendar days." This is the unit of time that's used to measure this subcontract operation. |
| Labor center (LABWCR) |
| Identifies the group associated with the labor work center. |
| Labor wk C (EXTLAB) |
|
Associates a labor work center with the machine, such as a labor work center that relates to the crew that operates the machine. Note - settingsYou need to be authorized to change this resource if this is an operation in a versioned routing for a versioned product (BOM).
|
| Short description (EXTLABSHO) |
| The short description defined for the selected work center. |
| No. lab res. (EXTLABNBR) |
|
The number of this particular labor resource that's needed for the operation. Note - settingsYou need to be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).
|
| Revision reason (REVREASON) |
|
This field supports changes to an operation in a versioned routing, and changes to the defined routing or routing version, which results in the operations being reloaded from the new routing record. Use this field to explain the reason you made the change. This provides traceability by writing details to the Work order-component audit table (MFGOPEREV). The audit details include the revision reason from this field, a revision code, and key details from the component line. Note - settings
You need to enter the reason if the product to be released and the defined routing is version-managed and the MFGREV—Revision management parameter (GPA chapter, WOM group) is set. Refer to the documentation on the MFGREV—Revision management and TRACKOPEWO—Track a WO operation change parameters. Note - informationRefer also to the Revision history action.
|
| CCE1 |
|
The analytical dimensions are initialized in compliance with the Default dimensions setup. Entry or modification of an analytical dimension is determined by the selected entry transaction. When an analytical dimension is used for tracking Project management costs in finance from work orders, the assigned Project code (PJT) determines the Project analytical dimension (CCE(n)). For any subsequent product lines on a work order, project analytical dimensions for the released product are initialized for the assigned project, whereas the components in the bill of material (BOM) and routing operations are initialized for the project assigned to the first released product line on the order. Note - dangerA modification to the Project code (PJT) can result in the Project analytical dimension code (CCE(n)) being reinitialized.
|
| LABCCE1 |
| Operation detail | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Field descriptions
Resources
Parameters
Labor factor
Off time charge
Load
Unit
Subcontract
Select Operation detail from the Actions icon to add or amend the details for the operation using the standard screen display mode. The possible operation grouping criteria used by the optimization or scheduling functions is accessed from this screen. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exclude line/Reactivate | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Exclude line from the Actions icon to exclude or cancel the operation. To reinstate the canceled operation, select Reactivate. Note - settings
You need to be authorized to perform these actions and provide a reason in the Revision reason field if the work order is for a versioned product (BOM). Refer to the documentation on the MFGREV—Revision management and TRACKOPEWO—Track a WO operation change parameters. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Tracking status | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Tracking status from the Actions icon to view, in summary, the quantities and operation times for the operation. The screen summarizes the operation status (pending, in process, completed), the planned and actual quantities, and the planned and actual times for subcontract operations, as well as any relevant information related to the subcontract operations. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Text | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Text from the Actions icon to view, enter, or modify text associated with the operation. For example, information describing how to use the workstation, how to merge colors, how to use tools, the torsional movement to fix a screw. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Order | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| This is a subcontracted operation for which a purchase order has not yet been created. Select Order from the Actions icon to enter details for, and then generate a purchase order for the operation. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Subcontracted operation situation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Select Subcontracted operation situation from the Actions icon to view order information for this subcontracted operation. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Revision history | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Select Revision history from the Actions icon to view a history of key changes to the selected operation. This action is only active if the changes were saved. The revision history can include a revision reason, a revision code, and key details from the component line. The current details for the selected component are displayed on the first line of the table. Amended fields are highlighted. Note - settings
The MFGREV—Revision management parameter (GPA chapter, WOM group) needs to be set if the product is versioned and the selected operation is in a versioned routing. Refer to the documentation on the MFGREV—Revision management and TRACKOPEWO—Track a WO operation change parameters. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Additional operation not expected | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Field descriptions
Select Additional operation not expected from the Actions icon to add an unplanned operation. Note - settings
You need to be authorized to perform this action and provide a reason in the Revision reason field if the work order is for a versioned product (BOM) and the routing defined to manufacture the BOM is versioned. Refer to the documentation on the MFGREV—Revision management and TRACKOPEWO—Track a WO operation change parameters. |
Tab Documents
This section is for information purposes only. It displays which production folder documents from those defined within the selected entry transaction were printed.
After all planned documents from the production folder are printed, the work order advances to Printed status.
WO documents
Labeling mode
Reports
By default, the following reports are associated with this function:
DOSFAB: WO documents
BONTRV: Job tickets
BSM: Material issue notes
FICHSUI: Routing sheet
FICHTEC: Technical sheet
RECETTE: Production slip
MFGHEAD: List of WOs
This can be changed using a different setup.
Action panel
|
Allocation |
Select the Allocation action to allocate materials to this firm work order. A WO allocation screen displays a summary of the allocation status for all materials.
To view the details of the allocations, select the View action. You can allocate a specific component from the Actions icon:
Note - informationRequesting a global allocation of all components does not affect manually allocated components.
When the allocation is complete, the Allocation field in the Header section updates. |
|
Scheduling |
Select the Scheduling action to schedule the work order. Scheduling is the process of sequencing the operations in time, according to the durations, slack times, and relationships in the work order, or for suggestions, the routing. A target completion date (Initial objective field) is displayed. This field is initialized by the completion date defined in the End date field in the Header section. This date is for information only. Although it can be amended, it does not affect the scheduling calculations. The number of days to or after the target completion date is also displayed (Advance/delay field). This figure is calculated at the time of display. The scheduling process schedules the operations in the defined routing, and if specified, routing version. It also calculates the production start date (Start date field in the Header section) for the work order if backward scheduling has been defined. You can specify a start date for an operation so that a work order is not scheduled to start before the materials are available, for example. If an operation's start date has been set, scheduling does not change the date, it will, however, reschedule other operations around this date. If scheduling results in the production start date being calculated for a date in the past, a warning displays. The system proposes forward, or downstream scheduling from today's date (Start date field), amending the completion date (End date field in the Header section) accordingly. Note - dangerThe routing version, if defined, needs to be at Available to use status on the production start date (Start date field in the Header section). If scheduling changes the production start date, this might cause an inconsistency with the selected version. The Scheduling field remains at Not scheduled status. You need to either change the routing version or reschedule the work order before you can continue. Refer to the Major version field for further information.
When the scheduling information is correctly set, you can use the planning workbench to reschedule, deschedule, or to mark specific operations to be scheduled. Scheduling sets the start and end dates for the operations according to their productive and non-productive setting and operation times. Note - tipThe sequence of operations follows the defined numbering sequence.
Note - informationYou need to remove the work order from scheduling, deschedule it if you need to modify an operation.
A Graph action is available when the work order is scheduled to view the relationship and duration of the operations in a graphical format. A Load action is available to view the work center load in a graphical format. Field descriptions
Block number 1Block number 2Grid: Schedule data
|
|
Status |
Select the Status action to view summary details for the work order, and for each section. |
|
Tracking |
Select the Tracking action to view the production tracking for the work order. |
|
Submit for scheduling |
Select Submit for scheduling to send the work order to Production Scheduler, Sage X3 Web Scheduling, or your web scheduler for scheduling. While the work order is being scheduled, it remains at Scheduled status and work order status Being optimized. At these statuses you cannot modify the work order. Note - informationYou can submit a range or a set of work orders at a specific status for scheduling using the Submit for scheduling function.
Note - settingsFor detailed scheduling, the POPS—Production Scheduler activity code activates the Production Scheduler functionality. The GFS—Finite scheduler activity code activates the generic Finite scheduler interface.
Note - informationProduction Scheduler only applies to on-premises instances of Sage X3. The generic Finite scheduler interface provides an integration connector to any web scheduling solution for either cloud or on-premises solutions.
|
|
Remove from scheduling |
Select Remove from scheduling to remove the work order from Production Scheduler, Sage X3 Web Scheduling or your web scheduler. The work order changes to the status it was at prior to scheduling, to Pending or In progress status. You can now modify the work order and resubmit it for scheduling if needed. Note - tipYou can remove a range of work orders from scheduling using the Remove from scheduling function.
|
Menu bar
| Select the Header text action view, enter, or modify text associated with the work order. |
| Select the Provisional availability action to view the availability of the components, based on the released quantity. In case of non-availability, the system proposes a first availability date. |
| Select the WO provisional cost calculation action to launch the theoretical provisional cost calculation and the provisional cost calculation for the release. |
| Select the WIP cost inquiry action to view the production costs for the work order and to compare the actual costs with the planned costs. |
| Select the Production cost inquiry action to access the Cost price Inquiry function. |
| Select the Provisional cost inquiry action to access the Provisional cost inquiry function. |
| Select the WO suspension/reactivation action to suspend or place a work order on "hold." Suspended status is displayed in the home section. You cannot track suspended work orders. Reactivate the work order if you need to track it. |
| Select the WO close action to complete and close the work order. |
| Select the Transaction action to view the format of the entry transaction. |
|
This action is available if the order is at Firm status and allocated at least globally. If some materials are in shortage, folder printing is only possible if these materials authorize shortages (the Release if shortage checkbox in the Manufacturing section of the product-site record is selected). Select the WO documents action to start printing the production folder. The documents to be printed are defined in the selected entry transaction. |
| Select the Labels action to print the production labels. |
Error messages
In addition to the generic error messages, the following messages can appear during the entry:
Work order home section
This site is not a production siteThe defined site is not a production site. Select the Selection icon to open the complete list of available production sites.
The site is not in the same legal companyThe planning site and production site need to belong to the same legal company.
Problem at the time of sequence number counter recoveryor
No sequence number has been assigned to this document
This message is displayed where there's a problem in the sequence number counter setup.
Header section: Released products
The entry of at least one product to be released is mandatoryYou need to add a minimum of 1 product to be released by the work order.
Product not manufacturedor
It must be a production BOM
The product to be released needs to be a production BOM, not a commercial BOM.
This is a prototype product. You can only create a prototype work order.This message is displayed when the product is an "in design" product. The product was created from a product design BOM revision. A New product in design mode warning displays in the home section of the parent product. The Prototype checkbox in the home section of the work order is selected automatically.
The product is not linked to this production site!This message is displayed on entry of a released product. The product needs to exist for the selected production site. Select the Selection icon from the field for the product to be released to open the list of products with the product-site defined on the production site.
Caution: non-active BOM (validity dates)This non-blocking warning message can appear following the BOM code validity check. You need to verify the validity dates for the BOM used in the release.
This BOM is being developed (use is not authorized)This message can be displayed following the validity check on the BOM code. The BOM needs to be at Available to use status.
XXXXXXX is the exclusive planner for this productYou can only release products that you’re the planner for, as defined in the Production section of the product-site record, if the GPLNFLT—System entry date parameter (STO chapter, SCH group) sets an exclusive filter on the planner.
Absent lot number sequence number counterThis message can be displayed when entering the released products, if automatic lot numbering is defined for the product.
Capacity of the sequence number counter exceededThis message can be displayed when entering the released products, if automatic lot numbering is defined for the product.
The Stock unit of the released products should be the sameThis message is displayed when releasing multiple products and all released products are not expressed in the same stock unit.
You can only raise a Work order for one project. Select projectThe WOPJMMSG—Block multiple projects on WO parameter (TC chapter, PJM group) is set to Yes, therefore all product lines on a work order need to be assigned to the same project as the first released product line on the work order or left blank (not assigned to a project).
Header section: Lead time
XXXXXXX is not a working day for the production siteThe start or end date entered corresponds to a rest day.
Warning, the date is prior to the current dateThe calculated start date was exceeded.
Header section: Routings
The routing and routing code route must be enteredThe work order is to be completed as "materials only."
You do not have the authorization to use this codeThis message is displayed following the validity check on the BOM and routing codes.
Code not valid for this siteYou need to check the routing and the BOM code belong to the defined production site.
No valid routing found, release not possibleThis message is displayed if the transaction does not authorize entry of the routing, and if no routing can be found automatically.
This routing is under development (use is not authorized)or
The routing is not valid (use not authorized)
or
Code not available for use in production
This message is displayed following the validity check on the routing. The routing needs to be at Available to use status. Additionally, the routing code needs to be available for use in production.
There are inconsistencies between the routing and BOM codesThis message can be displayed after entering the routing code. You need to verify which BOM codes are associated with the selected routing code.
The routing is not active on the production start dateThis message can be displayed following the validity check on the routing.
The stock units are not compatibleThis message is displayed if the routing unit entered is incompatible with the stock unit for the released product.
The routing and product do not share the same version managementThis message is displayed if the work order is for multiple products (Product field) but one of the products is not version-managed. You can either use the standard, non-versioned routing for the work order or create a new work order for the non-versioned product.
The released quantity is less than/greater than the minimum/maximum planned quantity for this routing!This message is displayed following the validity check on the routing. You need to check the minimum release quantity planned for the routing.
No valid routing found, release not possibleThis message is displayed when the transaction entered does not authorize entry of the routing, and when the system cannot find a valid routing.
Components section
The requirement cannot be less than the quantity already consumedThis message is displayed if you attempt to reduce the requirement quantity of a material below the quantity already consumed.
The requirement cannot be later than the WO end dateThis message is displayed if you attempt to postpone a material requirement date beyond the planned end date of the work order.
Incompatible product categoryThis is a contextual warning, for example, a tool needs to belong to the "tool" category.
A phantom component is present. A manual intervention is necessary. Display the list of components concerned?This message is displayed when managing shortages with phantom stock. In this case manual intervention is needed to verify that the quantity taken for the phantom product is actually available. If the quantity is not available, you need to manually add the replacement product and adjust the quantity of the phantom product. You can refer to the displayed list of involved components to identify information on the replaced products and replacement products, such as available to promise stock.
This (unplanned) material has already been addedThis message is displayed if you attempt to add the same planned material more than once.
A product cannot be produced from itselfThis message is displayed if you attempt to add a released product as an unplanned material.
Operations section
Recover the standard operation data?In a similar way to the routing management, the system can recover the standard operation data to add or modify the routing operations.
The planned quantity cannot be less than the produced quantityThis message is displayed if you attempt to reduce the planned quantity for an operation below the quantity already produced.
Unavailable periodThis message is displayed if a date entered falls in an unavailable period for the production site.
XXXXXXX is not a sub-contracting work centerThis message is displayed after the contextual control on the entry of a new work center when the operation is subcontracted.
XXXXXXX is not a labor work centerThis message is displayed after the contextual control on the entry of a new work center. A secondary work center needs to be of labor type.
The labor work center cannot be identical to the main work centerThis message is displayed after the check on the entry of a new secondary work center.
Access not authorized for this productThis message is displayed if the access check fails for the entered product.
If the sub-contracting operations are structural, the principal work center must be of the sub-contracting type.This message is displayed after the entry checks on a new principal work center.
The site attached to the work center must be the same as the site to which the code is attached.This message is displayed after the entry checks on a new work center.
There must be at least one production operationThis message is displayed in the scheduling data if no operation is defined as a "production" operation.
This number is already usedThis message is displayed if you attempt to add an operation number that's already assigned.
Caution: it is necessary to verify that the times (setting, operation or rate) remain coherentThis message is displayed during the modification of data "specific" to an operation, such as the operation unit.
Documents section
A material is out of stock and prohibits the printing of the folderBefore printing the production folder, manually or automatically, the system checks for an out of stock material for which the Release if shortage parameter in the product-site record is set to No. In this case, it is not possible to print the folder.
Work order scheduling/descheduling
Warning, the planned end date has been affected by the schedulingThis message is displayed if, within forward scheduling, the scheduling calculation comes up against the current date and the user has accepted the system proposal to carry out downstream scheduling from the current date. This becomes a constraint, the scheduling is recalculated, and the end date modified.
An error has arisen during scheduling/deschedulingThis is a serious read/write error that has occurred while scheduling/descheduling.
Work order amendments
The work order is scheduled. Do you want to continue?This message is displayed when an attempt is made to modify data that's likely to challenge the scheduling, such as modifications to quantities, dates, times, work centers.
Insufficient stock is available for the phantom product. Do you want to perform a partial substitution?This message is displayed if you edit the planned quantity (Release qty field) for the work order and there's insufficient stock of a phantom product to make the new quantity. You can choose to automatically update the quantity of the phantom product to the available stock quantity and add a replacement product for the remaining quantity needed for the BOM. Select Yes. If you select No you need to add a replacement product and adjust the quantity of the phantom product manually.
You are about to make critical changes to a work order for a versioned productand
You have made a critical change to a work order for a versioned product
Amendments to a work order for a versioned product are tightly controlled. Some, such as the addition of a component, are considered to be a "critical change" within the context of amendments to work orders. This message is displayed to warn you that the work order contains a versioned product and there could be consequences from changing the details.
This message is displayed if a change to a work order for a versioned product results in the components of the product to be released being reloaded. A component reload can occur if the work order start date or the planned quantity (Release qty field) is changed. It will also occur if the version of the product to be released is changed or the product to be released is deleted. When you save your changes, previous key changes to the component information such as the addition of new components or changes to key fields are removed. You need to re-enter this information if it still applies to the updated work order. Alternatively, you can cancel (using the Cancel action) your amendment and keep the previously entered key changes, or close the work order and create a new work order with the new details.
You’ve changed the version of the product to be released. You need to change the start date of the work order if the selected version is not available to use on the scheduled start date. You should also check if the selected version has an exception date that matches the start date.
Production is in process. Do you want to continue?The system requires confirmation that the released quantity is to be modified when the work order is in process.
You can only raise a Work order for one project. Changing the project may cause an inconsistencySage recommends that a work order for a project should only cover demand for a single project. If a work order is created manually, it’s possible to add multiple released products to the order. This is dependent upon the selected entry transaction, which can be set to restrict a work order to 1 released product line (Multiple products allowed checkbox). With multiple products on a single work order it can be difficult to trace inconsistencies in the postings if they occur. Therefore, if the WOPJMMSG—Block multiple projects on WO parameter (TC chapter, PJM group) is set to Yes and a work order has multiple released products, all product lines need to be for the same project as the first released product line or blank (not assigned to a project). If the WOPJMMSG parameter is set to No, this warning is displayed when a project code is entered that does not match the project code assigned to the first released product line but the addition of the product/project to the work order will not be prevented.
Change all lines on the components and operations to the project dimension code?The Project code (PJT field) assigned to the released product line, or the Project analytical dimension (CCE(n) field) has been changed. The Project analytical dimension (CCE(n) field) has been automatically reinitialized with the default dimension for the new project code if the Project code has been changed. Do you want to reinitialize the components in the BOM and the routing operations with the default dimension for the new project code/new Project analytical dimension? Select Yes, No or Yes if same value. For Yes if same value, the Project analytical dimension field is automatically reinitialized with the default dimension for the new project code/project analytical dimension code if the Project analytical dimension field contains the analytical dimension for the original code (the Project analytical dimension field on each component/operation, if changed manually, could potentially be different from the original project analytical dimension).
The scheduling data must be verified. Do you want to do it now?This message is displayed if an action on the operations challenges the coherence of the data scheduling. The system will then suggest opening the scheduling data planning board.
Operations List Update... Unexpected operations and critical field changes will not be kept.This message is displayed if the version-managed routing on the work order header is changed. When you save your changes, the operations are reloaded with the default information from the new routing record. This also results in key changes to the operation information such as the addition of new operations or changes to key fields being removed. You need to re-enter this information if it still applies to the updated work order. Alternatively, you can cancel (using the Cancel action) your amendment and keep the previously entered key changes, or close the work order and create a new work order with the new details.
This message is also displayed if the routing version is changed to comply with a change to the production start date.
This message requests confirmation before accepting the modifications concerning the released product for a work order arising from a direct production order.
Enter a revision reasonAmendments to a work order for a versioned product are tightly controlled. Some, such as the addition of a component, are considered to be a "critical change" within the context of amendments to work orders. This message is displayed if you have not explained the reason you changed the work order details. You need to provide a reason in the Revision reason field for each key change to a work order for a versioned product if the MFGREV—Revision management parameter (GPA chapter, WOM group) is set.
The system requires a confirmation before modifying the production site.
This message is displayed if the reduction of a material quantity triggers automatic closure (linked to the product-site automatic closure percentage).
The operation will be closed. Continue?This message is displayed if the reduction in the operation quantity triggers the automatic closure of the operation as a function of the automatic closure percentage defined at work center level.
Warning, the materials linked to this product have been aggregated and must be manually adjustedThis message is displayed upon aggregation of materials at release. If the materials linked to several released products are aggregated, and some are fixed, this message is displayed upon deletion of 1 of the released products.
The production folder has been printed. Do you want to continue?or
The work order has been printed. Do you want to continue?
This message is displayed if you’re modifying a work order that has previously been printed.
The stock allocations for this WO are going to be deleted. Do you want to continue?The system requires a confirmation to delete an allocated work order.