Manufacturing > Planning > 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 one or more products. Conventionally, the work order uses a bill of materials (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 required 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, that is, the product has been created from a product design BOM that is still in design mode.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

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 one 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 one 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 required 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.

Header

Presentation

The home section provides key tracking information for this work order.

Close

 

Fields

The following fields are present on this tab :

Block number 1

Type in or select the planning site for this 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.

Type in or select the production site at which this work order is to be processed.

The production site defined on the user record is displayed by default but can be amended.

  • Work order (field MFGNUM)

Type in a reference for this work order, or leave this field blank to generate the next work order number (unique ID) on file.

To amend an existing work order click the Selection icon then choose the required work order from the displayed list.

  • Prototype (field NPIPRO)

This check box is selected if this work order is for an "in design" product, that is, the product has been created from a product design BOM revision and has a New product in design mode warning displayed in the home section of the parent product.

This prototype work order cannot be raised to cover demand for a sales order.

Block number 2

  • Order status (field MFGSTA)

Use this field to set the initial status for this work order as 'Firm' or 'Planned'. Planned orders can not be allocated, printed, or tracked. They can, however be scheduled, and can be respected by the Material Requirements Planning (MRP) process.

  • Release mode (field MFGMOD)

Use this field to define the release mode for this work order. The transaction you select determines which of the following values are available for selection and what controls are applied to your selected value:

  • Complete. Both components and routing operations are mandatory for this work order. The list of components from the bill of materials (BOM) record and the operations in the routing will be loaded automatically. The default order for the list of components reflects the order of the components in the BOM, but can be amended.
  • Materials only. Initially, only components are mandatory for this work order. If the selected transaction is set to 'To be completed' you must define a routing number before you can start tracking this work order; you can release this work order without routing information if the selected transaction is set to 'Complete'.
  • Operations only. Initially, only routing operations are mandatory for this work order. If the selected transaction is set to 'To be completed' you must define material (component) requirements before you can start tracking this work order; you can release this work order without material requirements if the selected transaction is set to 'Complete'.

Close

 

Tab Header

Presentation

You use this section to define the product to be manufactured, the production start date and the routing to be used.

Your selected transaction determines if you can manufacture and release multiple products on a single work order.

 Production Scheduler cannot include "by-products" in the scheduling process.

 Production Scheduler only applies to on-premises instances of Sage X3.

Using versions: Released products and routings

You must 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 raised for a versioned product (BOM) the selected version must 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 raise 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 which is 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 (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 (BOM then routing) are still consistent (valid) at the new start date.
    If there is an inconsistency between the BOM or routing version and the new start date the work order will be created but it will not be scheduled.

Where an inconsistency between a version (BOM or routing) and the start date is flagged you must change the version or reschedule the work order.

Close

 

Fields

The following fields are present on this tab :

Grid Products released

  • field UPDFLG

This field displays a line number in this particular table/grid/block.

Type in or select the code of the product to be released. The product code must be valid for the defined production site.

Certain criteria apply to the selected product before it can be processed. It must be a manufactured product (product category), held in stock (stock management mode) and be active (product status). The bill of material (BOM) will define the materials (components, ingredients) required to manufacture this product, and whether it is printed on Pick lists.

To add an unplanned by-product or secondary product to this work order, select the next line in the table then click Addition of a by-product from the Actions icon. A by-product is a product that will be produced as a secondary result whilst 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 (field ITMDES1)

This is the description from the product record.

  • Major version (field ECCVALMAJ)

The current version of this product is displayed:

  • Major versions might be used where there have been increased or significant changes to the original or previous version, that is the 'form, fit or function' has changed.
  • 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 type in, or select a different version of this product, if required. This field is not available for entry if the product code defined in the Product field is not version managed.

  • Minor version (field ECCVALMIN)

 

  • Change request (field CRID)

This field displays a change request ID if this product, or the specific version or revision of this 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 adjacent this field.

If 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 this product will have either been seen through to its conclusion and the change delivered, or the change request rejected. You are always authorized to progress this work order should you decide to do so.

  • Line status (field ITMSTA)

This field tracks the progress and status of this work order line. You cannot modify it.

This field displays the release unit of measure (volume or mass) for this product for this order. This unit and any applicable unit conversion are defined for this product on the product record.

 If you are adding multiple products to be released, all products must have the same release unit.

  • Release qty (field UOMEXTQTY)

This field displays the planned quantity. The quantity is expressed in the release unit. The base quantity for this product defined on the bill of materials (BOM) record is loaded by default but can be amended.

  • REL-STK (field UOMSTUCOE)

This field displays the product-specific conversion factor applied between the stock unit and the release unit of measure. This unit conversion is defined for this product on the product record.

This field displays the unit in which the product is stored. It provides the key to prices, costs, volumes etc.

  • Expected STK qty (field EXTQTY)

This field displays the planned quantity. The quantity is expressed in the stock unit.

  • BOM code (field BOMALT)

Multiple bills of materials (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 this product at this production site is displayed by default.

  • Description (field TBOSHO)

This field displays the short description of the bill of material (BOM) code.

Use this field to link production of this product with a specific project.

Type in, or select from the Projects table, one of the following:

  • A project code;
  • A project code and a project budget code;
  • A project code and a project task code, that is a material task code, a labor task code (sales only), or a combined (mixed) labor and material task code.

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'.

To 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 is 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 the link type is a task (the link is to the project operational structure). Two separators placed after the project code mean that the link corresponds to a budget code (link to the project budget structure).

  • Lot (field LOT)

This is the lot to be assigned to the released product, based on the product management mode.

If the product is managed with automatic lot numbers, the lot number is assigned by the system when the work order is created.

  • Ship-to type (field BPCTYPDEN)

Use this field to identify the destination for this product. This can be a site or a customer.

  • Destination (field BPCNUM)

Use this field to define the site or customer to ship this product to. The appropriate reference is determined by the value of the Ship-to type field (field BPCTYPDEN).

  • Description (field BPCDES)

This field displays 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 (field BPCTYPDEN).

  • Original document (field VCRNUMORI)

This is the journal number at the origin of the requirement.

  • Origin line (field VCRLINORI)

 

  • WO description (field MFGDES)

Use this field to type in a short free-format description/reference for this order.

  • Type (field ITMTYP)

This field displays the type of product that is on this order line, as follows:

  • Product. A manufactured product. An order line will be generated for the parent product and for each component in the bill of materials (BOM).
  • By-product. A secondary product. An order line will be generated for the product.
  • Shrinkage % (field 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.

Operator in charge of performing the production planning or product ordering.

  • Production request (field XFMI)

 

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 Projectcode (field PJT) determines the Project analytical dimension (field 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 materials (BOM) and routing operations are initialized for the project assigned to the first released product line on the order.

 A modification to the Project code (field PJT) can result in the Project analytical dimension code (field CCE(n)) being reinitialized.

Lead time

  • Scheduling mode (field SCDMOD)

Use this field to define the scheduling method for this work order. Select one of the following:

  • Backward. With 'backward', or upstream scheduling the system calculates the production start date (field Start date) from the end or required completion date (field End date).
  • Forward. With 'forward', or downstream scheduling the system calculates the required completion date (field End date) from the defined production start date (field Start date).

These calculations rely on the production lead time, reduction factor and economic quantity defined on the product-site record.

The transaction you select determines if this field is available for entry.

  • Start date (field STRDAT)

This field identifies the planned production start date for this work order. The date is determined by the Scheduling mode :

  • 'Forward' scheduling respects this date. You must, therefore, define this date manually.
  • 'Backward' scheduling respects the defined End date. Leave this field blank. The system will calculate the date from the production lead time, reduction factor and economic quantity defined on the product-site record.
  • End date (field ENDDAT)

This field identifies the end or required completion date for this work order. The date is determined by the Scheduling mode :

  • 'Backward' scheduling respects this date. You must, therefore, define this date manually.
  • 'Forward' scheduling respects the defined Start date. Leave this field blank. The system will calculate the date from the production lead time, reduction factor and economic quantity defined on the product-site record.
  • Lead-time (+QC) (field AVAOFS)

The operation lead-time is used during launch and in the MRP calculations. It is used to calculate the date of the component (material) requirement with respect to the production start date of the parent product.

It is expressed in calendar days. You can enter a negative value.

Example: A work order has a start date of the 26/06:

  • If the operation lead-time is 7 days, the material requirement date will be calculated on the 03/07 (26/06 + 7);
  • If the operation lead-time is -7 days, the material requirement date will be calculated on the 19/06 (26/06 - 7).

  • % LT reduction (field LTIREDCOE)

Based on the chosen transaction, use this field to increase or decrease the lead-times for all the WO operations.

By default, the lead-time reduction rate suggested is the one defined by the general parameter GPERCOMP - % default LT reduction (GPA chapter, LOA group).
The times affected by this reduction are those defined by the general parameter GTPSCOMP - Lead-time reduction (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 (field MFGPIO)

Use this field to assign a priority to this work order.

  • Planned quantity (field MFGEXTQTY)

This field displays the planned quantity. The quantity is expressed in the stock unit.

This field displays the release unit of measure (volume or mass) for the product(s) on this order. This unit and any applicable unit conversion are defined on the product record(s).

  • Allocation (field XALLSTA)

The Allocation (materials), Scheduling and Status fields display a status for this work order. These fields are updated automatically by the system.

The current status, or progress of this work order is displayed in the Scheduling and Status fields. Selected combinations to note are as follows:

  • 'Not scheduled' and 'Pending'. The work order is awaiting scheduling. It cannot be submitted for scheduling in Production Scheduler, Sage X3 Web Scheduling or in any web scheduling solution developed by an ISV (independent software vendor).
  • 'Scheduled' and 'Pending'. The work order is scheduled but has not actually been submitted for scheduling.
  • 'Scheduled' and 'Being optimized'. The work order is being scheduled (has been submitted for scheduling). At these statuses you cannot modify the work order.
  • 'Optimized' and 'Pending'. The work order operations have been optimized by the scheduler.

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.

 For detailed scheduling, Activity code POPS activates the Production Scheduler functionality or the Generic finite scheduler interface.

 Production 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 (field XSCDFLG)

The Allocation (materials), Scheduling and Status fields display a status for this work order. These fields are updated automatically by the system.

The current status, or progress of this work order is displayed in the Scheduling and Status fields. Selected combinations to note are as follows:

  • 'Not scheduled' and 'Pending'. The work order is awaiting scheduling. It cannot be submitted for scheduling in Production Scheduler, Sage X3 Web Scheduling or in any web scheduling solution developed by an ISV (independent software vendor).
  • 'Scheduled' and 'Pending'. The work order is scheduled but has not actually been submitted for scheduling.
  • 'Scheduled' and 'Being optimized'. The work order is being scheduled (has been submitted for scheduling). At these statuses you cannot modify the work order.
  • 'Optimized' and 'Pending'. The work order operations have been optimized by the scheduler.

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.

 For detailed scheduling, Activity code POPS activates the Production Scheduler functionality or the Generic finite scheduler interface.

 Production 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 (field XTRKFLG)

The Allocation (materials), Scheduling and Status fields display a status for this work order. These fields are updated automatically by the system.

The current status, or progress of this work order is displayed in the Scheduling and Status fields. Selected combinations to note are as follows:

  • 'Not scheduled' and 'Pending'. The work order is awaiting scheduling. It cannot be submitted for scheduling in Production Scheduler, Sage X3 Web Scheduling or in any web scheduling solution developed by an ISV (independent software vendor).
  • 'Scheduled' and 'Pending'. The work order is scheduled but has not actually been submitted for scheduling.
  • 'Scheduled' and 'Being optimized'. The work order is being scheduled (has been submitted for scheduling). At these statuses you cannot modify the work order.
  • 'Optimized' and 'Pending'. The work order operations have been optimized by the scheduler.

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.

 For detailed scheduling, Activity code POPS activates the Production Scheduler functionality or the Generic finite scheduler interface.

 Production 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

This routing code describes the process involved in manufacturing (producing) or processing a product. That is, 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 materials), or a generic reference to a parent routing which is 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 will be submitted.
Click the Selectionicon to open the list of valid routings for the released products.
A control is performed so as to check the consistency:

  • between the routing and BOM codes,
  • between operations of material assignment and routing operations: a warning encourages the user to perform the required modifications manually.

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 (for use in a manufacturing environment, for costing or for capacity planning).

  • Major version (field ROUECCMAJ)

The version of this routing that applies on the scheduled start date (field Start date) for this work order is displayed, if the selected routing is version managed.

You can type in, or select a different version of this routing, if required.

  • Major versions might be used where there have been increased or significant changes to the original or previous version, that is the 'form, fit or function' has changed.
  • 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.

If you choose to 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, view all versions of the selected routing via the Routing Management (GESROU) function. The operations used for the selected version of the routing are loaded 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 are reloaded accordingly.

  • Minor version (field ROUECCMIN)

 

Close

 

Action icon

Popup view

Click Popup view from the Actions icon to enter the production information for this product using the standard screen display mode.

Manufacture detail

Click Manufacture detail from the Actions icon to view the product details as planned for this work order.

Tracking status

Click Tracking status from the Actions icon to view, in summary, the quantities in progress for this work order.

Stock - Site

Click Stock - Site from the Actions icon to view the inventory levels for the selected product, by site.

Management data

Click Management data from the Actions icon to view inventory management data for this product.

Projected stock

Click Projected stock from the Actions icon to view the projected stock movements for this product at one or all sites.

Available stock

Click Available stock from the Actions icon to project the available and available to promise stock for this product at this site in periods of days, weeks or months.

Assignments

Click Assignments from the Actions icon to use the assignment workbench to assign this work order to meet demand.

Product-site

Click Product-site from the Actions icon to view the data associated with this product at this site.

Product notes

Click this action in order to open a window displaying the note(s) associated with this 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.

Notes are limited to a screen inquiry and cannot be printed.

For further information, see the documentation on Notes.

Addition of a by-product

Click Addition of a by-product from the Actions icon to add an unplanned by-product or secondary product to this work order. A by-product is a product that will be produced as a secondary result whilst 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.

 Production Scheduler cannot include "by-products" in the scheduling process.

 Production Scheduler only applies to on-premises instances of Sage X3.

 

Close

 

Tab Components

Presentation

You use this section to add or amend the components (materials) required to produce the product.

The release mode defined in the home section determines if the required list of components is loaded automatically from the bill of materials (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, however, modify selected information, including the following:

  • The required quantity of the component, and date the component is required. This adjusts the allocations automatically. You can view updated quantities for the component by clicking Tracking status from the Actions icon.
     You cannot change the date a component is required if it has 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 is considered within the context of amendments to work orders, to be critical fields if you are an authorized user. This includes changing the required quantity of a component or adding a new component. You will be 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 has not been allocated.

Component availability

Component availability can directly impact the scheduling of operations required 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". 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.

These principles can be observed in the following example:

Current date:25 May      
Component requirement (demand):
Required date:
30 units      
15 June
Current free stock (component) quantity:     10 units  
Expected component receipt quantity:
Expected component receipt date:
15 units
31 May
Last assignment quantity:
Last assignment date:
5 units
2 June
Earliest date of component availability:          2 June          

The calculated (suggested) First Date of Material Availability is displayed for each component in the First availability field.

Component availability: Rule

An operation should only be scheduled to start on a date when the full quantity of each component required for the operation is available.

All components not directly linked to a specific operation must 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 must 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 above (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 Web Scheduling 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 in the optimization of 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 required 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 in the optimization of the operations.

 For 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.

 Production 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.

 

Fields

The following fields are present on this tab :

Block number 1

  • WO expected quantity (field MFGEXTQTY)

This field displays the planned quantity. The quantity is expressed in the stock unit.

  • Producible quantity (field AVAMFGQTY)

This field indicates the maximum quantity (in the release unit) that can currently be produced with the resources available. It is only displayed after components have been allocated.

This field displays the unit in which the product will be manufactured. It provides the key to prices, costs, volumes etc.

Grid

Use this field to add a component (material) required to produce the product. The required list of components is loaded automatically from the bill of materials (BOM) record. The default order for the list of components reflects the order of the components in the BOM, but can be amended.

Parameter CUMMAT - Material total mode (chapter GPA, group WOM) defines whether components that appear multiple times are consolidated onto a single line, and at which stage in the process.

  • Description 1 (field ITMDES1)

This is the description from the product record.

  • Major version (field ECCVALMAJ)

This field indicates which version of this component (material) applies. Major versions might be used where there have been increased or significant changes to the original or previous version, that is 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 (field ECCVALMIN)

This field indicates which minor version of this component (material) 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 (field CRID)

This field displays a change request ID if this component, or the specific version or revision of this 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 adjacent this field.

If a warning icon is displayed you should consider delaying this work order until the change request identified is closed. At that point a change to this component will have either been seen through to its conclusion and the change delivered, or the change request rejected. You will not, however, be prevented from progressing this work order should you decide to do so.

  • Line status (field XMATSTA)

This field tracks the progress and status of this component.

  • Requirement qty. (field RETQTY)

This field displays the quantity of this component required to produce the released product. This figure is calculated from the planned quantity (field Release qty) and the component quantity defined on the bill of materials (BOM) record. This value can be modified.

 You must be authorized to change this figure if this is a component of a versioned product (BOM).

  • First availability (field 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 is the suggested earliest date when the availability of this component can cover, in full, the required quantity. 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.

 This date is only a reference date. It is an indication of the 'First Date of Material Availability'.

This field displays the unit in which the product is stored. It provides the key to prices, costs, volumes etc.

  • Type (field TYPQTY)

This field indicates if this component is stored in stock. This field can be set to one of the following values:

  • Physical. This is a physical component for which quantities are stored in stock.
  • Active. This is an active component such as nails or staples for which quantities are not stored in stock.
     Active components have a "potency" percentage defined on their stock record.

  • Allocated qty. (field ALLQTY)

This field displays the quantity allocated to the order line.

  • Shortage (field SHTQTY)

This field displays the quantity of this component that is outstanding for this work order to be completed.

This quantity is ignored if the Release if shortage check box on the Product-site record is selected.

  • Available qty. (field AVAQTY)

This field displays the available quantity expressed in the stock unit of the components.

  • Consumed qty. (field USEQTY)

This field displays the quantity of this component consumed to produce the bills of materials (BOMs) on this work order.

  • Allocation (field ALLSTA)

 

  • Requirement date (field RETDAT)

This field displays the date on which the requirement arises.

  • Op. (field BOMOPE)

Use this field to assign this component to a specific operation in a production route, according to the manufacturing requirements.

 You must be authorized to assign or reassign an operation if this is a component of a versioned product (BOM).

  • % scrap (field SCA)

Type in the percentage of the component that you expect to be scrap (lost during the production process).

Inquiries can display the following figures:

  • Net quantities. The loss (scrap) percentage is not included in calculations of the quantity required to produce a parent product.
  • Gross quantities. The loss percentage is included in calculations of the quantity required to produce a parent product.

  • Component type (field CPNTYP)

This field displays the component type. It will be set to one of the following values:

  • Normal: A component defined on the bill of materials.
  • 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 (field 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 (field BOMSEQ)

This field identifies the sequence number of this component in the BOM (bill of materials).

  • WO line (field MFGLIN)

This field displays the line number of the released product.

Operator in charge of performing the production planning or product ordering.

  • Total (field CUMFLG)

Select 'Yes' to display the total available stock at the bottom of the page.

  • Pick list (field PICPRN)

Use this field to specify if this component must be printed on the Material issue slip for this work order.

  • Type of supply (field SCOFLG)

This field displays the replenishment source for this component. This might be 'Internal', made available to a subcontractor or supplied by a subcontractor.

  • Pick list code (field PKC)

Use this field to inform warehouse staff of any actions that apply when this component is picked for issue. You can select one of the following actions:

  • Component not weighed at station — Setup level and weighing tolerance fields are disabled.
  • Component weighed at station
  • Component weighed in production
  • Excipient phase at station
  • Excipient phase in manufacturing
  • Final work order excipient phase at station
  • Final work order excipient phase in manufacturing
  • Material correction at station — Blank option available for Setup level.
  • Material correction in manufacturing — Blank option available for Setup level.
  • QFS at end of manufacture

 This field is only available if the MWM-Weighing station activity code is active.

 You must be authorized to change this statement if this is a component of a versioned product (BOM).

 

  • Container capacity (field CTNCAP)

 

 

  • Revision reason (field REVREASON)

This field supports the following changes to a work order for a versioned product:

  • Critical changes made by an authorized user to a component line;
  • Changes to key information in the work order header.

Critical changes to a component line are defined as the following:

  • Addition of a component using the Add unexpected material or Add sub-assembly (phantom) action (from the Actions icon);
  • Exclusion (or cancelling) of a component, or reinstatement of a (cancelled) component using the Exclude line or Reactivate actions respectively (from the Actions icon);
  • Changes to the required quantity of a component (field Requirement qty);
  • Changes to a pick list component issue statement (field Pick list code);
  • Assigning, or changing, a specific manufacturing operation for a component (field Op. (Operation)).

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 to key information in the work order header are therefore defined as the following:

  • Changes to the work order start date;
  • Changes to the planned quantity;
  • Deletion of a product to be released.

Use this field (maximum 50 characters) to explain the reason you made the change. This field is mandatory for a change listed above when the product to be released is version-managed and parameter MFGREV - Revision management (chapter GPA, group WOM) is set. It provides traceability of these changes by writing details of each change to the Work order - component audit table (table MFGMATREV). Details written to this table include the revision reason from this field, a revision code and key details from the component line.

Changes to key information in the work order header update this field automatically.

 Parameter MFGREV (Revision management)

 Revision history action

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 Projectcode (field PJT) determines the Project analytical dimension (field 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 materials (BOM) and routing operations are initialized for the project assigned to the first released product line on the order.

 A modification to the Project code (field PJT) can result in the Project analytical dimension code (field CCE(n)) being reinitialized.

 

Action icon

Sort by operation / material

Click Sort by operation / material from the Actions icon to sort (order or reorder) the components based on the order of the operations to which they are attached.

Sort by product / sequence

Click 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 materials (BOM).

Material detail

Fields

The following fields are included in this window :

Block number 1

  • Component (field ITMREF)

Component product reference.

  • field ITMDES1

This is the description from the product record.

  • Major version (field ECCVALMAJ)

Use this field to indicate which major version of this component applies. Major versions might be used where there have been increased or significant changes to the original or previous version, that is the 'form, fit or function' has changed.

Type in, or select a version code from the list of version codes displayed. This field is not available for entry if the component code defined in the Component field is not version managed.

  • Minor version (field ECCVALMIN)

Use this field to indicate which minor version of this 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.

Type in, or select a version code from the list of version codes displayed. This field is not available for entry if the component code defined in the Component field is not version managed.

  • Change request (field CRID)

This field displays a change request ID if this component, or the specific version or revision of this 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 adjacent this field.

If a warning icon is displayed you should consider delaying this work order until the change request identified is closed. At that point a change to this component will have either been seen through to its conclusion and the change delivered, or the change request rejected. You will not, however, be prevented from progressing this work order should you decide to do so.

This field displays the unit in which the product is stored. It provides the key to prices, costs, volumes etc.

  • Component type (field CPNTYP)

This field displays the component type. It will be set to one of the following values:

  • Normal: A component defined on the bill of materials.
  • 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.

  • Default potency % (field DEFPOT)

This field indicates the average potency in percentage to be defined for the active products. It is used for receipt to stock as a default value, before the quality control measures the real potency. This field is accessible if the Stock management mode field (STOMGTCOD) is set to Potency managed.

  • Pick list code (field PKC)

This field informs warehouse staff of any actions that apply when this component is picked for issue.

  • Link type (field MFGLINK)

This field is used when releasing the product. An unplanned material can be associated with the complete work order or with a specific released product.

  • field MFGLIN

This field displays the line number of the released product.

Management

  • Management unit (field QTYCOD)

The management unit defines the quantity of the BOM links using a basis other than the product unit.
A BOM can therefore be entered for 1 product unit, 100 product units, 1,000 product units, using a percentage or specifying the size of a "lot".
In the percentage definition, the total link quantities must be equal to 100.
The management unit selected determines if the Base quantity field (BASQTY) is initialized or available for entry.

 
  • Base quantity (field BASQTY)

The base quantity is determined by the management unit, as follows:

  • The management unit is equal to 1, 100, 1000 or is expressed as a percentage. The base quantity is the value 1, 100, 1000 or 100 respectively.
  • Unit management is 'by lot'. You can enter the base quantity.
    If the BOM code is assigned to a specific site, it is initialized to the lot size of the product at the site.

This field displays the unit of measure (volume or mass).

  • UOM-STK factor (field BOMSTUCOE)

This is the conversion coefficient between the operation unit of the component and the storage unit.
It is initialized from the value specified at BOM level.

  • UOM link quantity (field BOMQTY)

The link quantity specifies the number of components required for the basic quantity of the parent product.
It is entered in a variable format (fluctuating number of decimals).
For a management unit of Percentage, the sum of the link quantities must be equal to 100.

  • STK link quantity (field LIKQTY)

 

  • Link quantity code (field LIKQTYCOD)

The code of the link quantity can be:

  • Proportional: the quantity is multiplied by the required quantity for the parent product used in the processing,
  • Fixed: the quantity is fixed regardless of the quantity required for the parent product.
  • Quantity rounding (field QTYRND)

The quantity of BOM links is entered with a maximum accuracy, which is not always useful for the stock management.
This code is used to manage the quantity rounding mode, based on the stock unit decimal, in the processes using the BOM.
The rounding can be to the nearest, highest or lowest.

  • Scrap factor % (field SCA)

The loss percentage is used to increase the required quantity in order to take into account losses incurred during the production process.

  • Shrinkage considered (field 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.

Operation

  • Operation (field BOMOPE)

Use this field to assign this component to a specific operation in a production route, according to the manufacturing requirements.

 You must be authorized to assign or reassign an operation if this is a component of a versioned product (BOM).

  • Lead time (field BOMOFS)

The operation lead-time is used during launch and in the MRP calculations. It is used to calculate the date of the component (material) requirement with respect to the production start date of the parent product.

It is expressed in calendar days. You can enter a negative value.

Example: A work order has a start date of the 26/06:

  • If the operation lead-time is 7 days, the material requirement date will be calculated on the 03/07 (26/06 + 7);
  • If the operation lead-time is -7 days, the material requirement date will be calculated on the 19/06 (26/06 - 7).

  • Type of supply (field SCOFLG)

This field displays the replenishment source for this component. This might be 'Internal', made available to a subcontractor or supplied by a subcontractor.

Miscellaneous

  • Link description (field BOMSHO)

This field displays the short description of the bill of material (BOM).


    • Valuation (field CSTFLG)

    This check box is only available if this order line is for a by-product. Click this check box if the value of this by-product must be taken into account when calculating the standard cost of the product; leave clear if the value of this by-product must not be included in the standard cost.

    • Print pick list (field PICPRN)

    Use this field to specify if this component must be printed on the Material issue slip for this work order.

    • Cumulated links (field CUMFLG)

    Select 'Yes' to display the total available stock at the bottom of the page.

    • Of which total (field CUMFXDQTY)

    If the aggregation of materials at release is active, a material line can be the merge between a material whose link quantity is proportional and a material whose link quantity is contractual. In such a context, a contractual part of the cumulated requirement quantity must be saved.


    Requirement

    • Quantity (field RETQTY)

    This field displays the quantity of this component required to produce the released product. This figure is calculated from the planned quantity (field Release qty) and the component quantity defined on the bill of materials (BOM) record. This value can be modified.

     You must be authorized to change this figure if this is a component of a versioned product (BOM).

    • field XTYPQTY

    This field indicates if this component is stored in stock. This field can be set to one of the following values:

    • Physical. This is a physical component for which quantities are stored in stock.
    • Active. This is an active component such as nails or staples for which quantities are not stored in stock.
       Active components have a "potency" percentage defined on their stock record.

    • Date (field RETDAT)

    This field displays the date on which the requirement arises.

    • field RETQTY2

    This field displays the required quantity and cannot be modified.

    • field XTYPQTY2

     

    • Revision reason (field REVREASON)

    This field supports the following changes to a work order for a versioned product:

    • Critical changes made by an authorized user to a component line;
    • Changes to key information in the work order header.

    Critical changes to a component line are defined as the following:

    • Addition of a component using the Add unexpected material or Add sub-assembly (phantom) action (from the Actions icon);
    • Exclusion (or cancelling) of a component, or reinstatement of a (cancelled) component using the Exclude line or Reactivate actions respectively (from the Actions icon);
    • Changes to the required quantity of a component (field Requirement qty);
    • Changes to a pick list component issue statement (field Pick list code);
    • Assigning, or changing, a specific manufacturing operation for a component (field Op. (Operation)).

    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 to key information in the work order header are therefore defined as the following:

    • Changes to the work order start date;
    • Changes to the planned quantity;
    • Deletion of a product to be released.

    Use this field (maximum 50 characters) to explain the reason you made the change. This field is mandatory for a change listed above when the product to be released is version-managed and parameter MFGREV - Revision management (chapter GPA, group WOM) is set. It provides traceability of these changes by writing details of each change to the Work order - component audit table (table MFGMATREV). Details written to this table include the revision reason from this field, a revision code and key details from the component line.

    Changes to key information in the work order header update this field automatically.

     Parameter MFGREV (Revision management)

     Revision history action

    Close

    Click Material detail from the Actionsicon to do the following:

    • Add or amend selected details for this component using the standard screen display mode.
    • Change this component to a different component. Click the Replaceaction, select the required component, then update the component details accordingly.
    Exclude line/Reactivate

    Click Exclude line from the Actions icon to exclude (or cancel) this component. To reinstate this (cancelled) component, click Reactivate.

    You cannot exclude a component if it is already allocated.

     You must be authorized to perform these actions if this is a component of a versioned product (BOM). If parameter MFGREV - Revision management (GPA chapter, WOM group) is set to Yes you must provide a reason (maximum 50 characters) for taking this action (Revision reason field).

    Global allocation

    Click 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 (location, lot) to be consumed. Global allocation simply increments the reserved stock for the component and decreases its available stock. At the time of the effective consumption of the materials, the system transforms the global allocation into a detailed allocation.

     Allocations action

    Manual allocations

    Click Manual allocations from the Actions icon to manually allocate the selected component. A screen is displayed summarizing all the lines from which allocations (lot, sublot, version, serial number, location) can be selected.

    If the component is already allocated, the allocated lines are displayed. You can modify this selection or delete the allocations by clicking the Clear action.

    If the material has not been allocated, or you have deleted the allocations, the system can perform the allocation for you. Click the Proposal action. You can specify a preferred lot, location or status. The system displays the lines selected for allocation. You can modify these selections if required.

     Allocations action

     You can only allocate individual serial numbers if the Serial number management field on the component record is set to Received/Issued. If the Serial number management field on the component record is set to Global Received/Issued you can only select the lot from which the serial numbers are to be allocated.

     Requesting a global allocation of all components does not affect manually allocated components.

    View allocation

    Click View allocation from the Actions icon to view the allocations for the selected component.

     Allocations action

    Projected Stock

    Click Projected stock from the Actions icon to view the projected stock movements for this component at one or all sites.

    Text

    Click Text from the Actions icon to view, enter or modify text associated with this component.

    Tracking status

    Click Tracking status from the Actions icon to view, in summary, the quantities of this component in progress for this 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 this material or not. If this component is allocated, the system can submit the allocation detail inquiry (by quantity, lot, location and stock status).

    Management data

    Click Management data from the Actions icon to view inventory management data for this component.

    Assignments

    Click Assignments from the Actions icon to use the assignment workbench to assign this component to meet demand. 

    Product-site

    Click Product-site from the Actions icon to view the inventory levels for the selected component, by site.

    Revision history

    Click 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, parameter MFGREV - Revision management (GPA chapter, WOM group) is set and the selected component is a component of a versioned product (BOM). The revision history includes 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 (top) line of the table. Amended fields are highlighted.

    Add unexpected material

    Click Add unexpected material from the Actions icon to add an unplanned component. If this work order is already allocated you must enter the details manually.

     You must be authorized to perform this action if this work order is for a versioned product (BOM). If parameter MFGREV - Revision management (GPA chapter, WOM group) is set to Yes you must provide a reason (maximum 50 characters) for taking this action (Revision reason field).

    Add sub-assembly (phantom)

    Click Add sub-assembly (phantom) from the Actions icon to add a phantom product to this 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.

     You must be authorized to perform this action if this work order is for a versioned product (BOM). If parameter MFGREV - Revision management (GPA chapter, WOM group) is set to Yes you must provide a reason (maximum 50 characters) for taking this action (Revision reason field).

     

    Close

     

    Tab Operations

    Presentation

    You use this section to add or amend the operations required to manufacture the product.

    The release mode defined in the header information determines if the operations used in the selected routing are loaded automatically.

    The scheduling mode is displayed as well as the scheduling status (order scheduled, to be rescheduled or not scheduled).

    The default information for each operation is obtained from the routing. You can, however, modify selected information, including the following:

    • The planned quantity for an operation.
       If you reduce the planned quantity for an operation the operation is closed automatically.
    • 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 is considered within the context of amendments to work orders to be critical fields, if you are an authorized user. This includes, for example, changing machinery running costs or adding a new operation. You will be 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 (as 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 required for the operation is available. Therefore, a First Date of Material Availability calculation calculates for each operation, a start date when the full quantity of each component required for the operation is available. This becomes a reference date which is displayed 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 in the optimization of the operations.

     Components section > Component availability

    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.

     For 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.

     Production 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.

    Close

     

    Fields

    The following fields are present on this tab :

    Block number 1

    • Scheduling mode (field SCDMOD)

    This field displays the scheduling mode defined on the Header. 'Backward' scheduling respects the defined End date; 'Forward' scheduling respects the defined Start date.

    • Scheduling status (field SCDFLG)

    This field indicates the current stage of this work order in the scheduling process.

    The lead time of an unscheduled work order can be changed manually by modifying one of the start or end dates.

    Grid

    • No. (field OPENUM)

    This field displays the sequence number of this operation.

    • Line status (field OPESTA)

    This field tracks the progress and status of this operation.

    • Work center (field EXTWST)

    Use this field to identify the production resource that is to be used for this operation.

    Type in, or select from the Work Centers table the code of the resource to be used for this operation.

     You must be authorized to change this resource if this is an operation in a versioned routing for a versioned product (BOM).

    • Short description (field EXTWSTSHO)

    This field displays the short description defined for the selected work center.

    • Type (field XWSTTYP)

    This field identifies the type of operation that is 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 (field OPESTR)

    This field identifies the date this operation must be started. The date is determined by the Scheduling mode and by the Scheduling status fields, as follows:

    • If this work order is 'Not scheduled', this operation's start date matches the start date for this work order (as defined on the Header).
    • If this work order is 'Scheduled', this operation's start date will be the earliest date this operation can start according to the scheduling process. That is, this date will be determined by the sequence of operations in time according to the durations, slack times and relationships in the routing.
    • End (field OPEEND)

    This field identifies the date this operation must be completed. The date is determined by the Scheduling mode and by the Scheduling status fields, as follows:

    • If this work order is 'Not scheduled', this operation's end date matches the end date for this work order (as defined on the Headertab)
    • If this work order is 'Scheduled', this operation's end date will be the latest date this operation can be completed according to the scheduling process. That is, this date will be determined by the sequence of operations in time according to the durations, slack times and relationships in the routing.
    • Earliest start (field FDMA)

    Operation start dates are scheduled according to the scheduling rules (as determined by the Scheduling mode and the Scheduling status fields). However, this operation should only be scheduled to start on a date when the full quantity of each component required for this operation is available. This date is calculated by your system. It is a suggested earliest date when the full quantity of each component required for this 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:

    • 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 scheduling process does not consider component availability when determining operation start dates. This date is only a reference date. It is an indication of the 'First Date of Material Availability'.

     If 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 in the optimization of the operations.

     For detailed scheduling, Activity code POPS activates the Production Scheduler functionality or the Generic finite scheduler interface.

     Production 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 (field 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.

     If you force a start date for this operation and you use Production Scheduler, Sage X3 Web Scheduling or a web scheduler you are 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 must 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.

     For detailed scheduling, Activity code POPS activates the Production Scheduler functionality or the Generic finite scheduler interface.

     Production 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 (field 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.

     If you force a start time for this operation and you use Production Scheduler, Sage X3 Web Scheduling or a web scheduler you are 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 must 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.

     For detailed scheduling, Activity code POPS activates the Production Scheduler functionality or the Generic finite scheduler interface.

     Production 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.

    This field identifies the group of work centers to which this work center belongs. Work center groups are used to review workloads.

    • Description (field ROODES)

    This field displays the description defined for the routing operation.

    • Number of resources (field EXTWSTNBR)

    This field displays the number of this particular production resource that are required for this operation. You can amend this figure, if required.

     You must be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).

    • Planned quantity (field EXTQTY)

    This field displays the planned quantity expressed in the operation unit.

     You must be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).

    This field displays the unit in which this work order operation quantity is expressed. Work order operation quantities are expressed in the operation unit.

    • Time unit (field TIMUOMCOD)

    This field displays the unit of time in which this operation is measured.

    • Setup time (field EXTSETTIM)

    Use this field to define the time that it takes for this machinery to be set up ready for use. The time is expressed in the defined time unit. The time can be zero (0).

     You must be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).

    • Unit time (field EXTUNTTIM)

    This field displays the time that it takes for this machinery to execute the operation. The time is expressed in the defined time unit.

     You must be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).

    • Run time (field EXTOPETIM)

    This field displays the time it takes to perform this operation for the required number of items (as defined in the field Planned quantity).

     You must be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).

    The operating time:

    • Is defined in hours or minutes (field Time unit).
    • Is expressed for 1, 100, 1000 or a lot of units of the operation based on the management unit,
    • Can be proportional or fixed based on the operating time type.
      For example:
      Time unit = Hours
      Time type = proportional
      Management unit = Time for 100
      Operating time = 2
      Operating unit = Kg
      Finished product unit = Un
      REL-OPE conversion coefficient = 0.5
      The operation time is equal to 2 hours for 100 Kg. If the Work order is launched for 1000 units of the finished product, the time necessary to produce this operation is 10 hours to obtain 500 Kg.
    • Nonproductive time (field FXDTIM)

    This field displays the total non-productive time, that is, the sum of preparation time, waiting time and post operation time. Non-productive, or delay time occurs after a process has been 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 (field VARTIM)

    This field displays the sum of the setup time plus the run time for the required number of items (as defined in the field Planned quantity). That is, the time that it takes for this machinery to be set up ready for use plus the time it takes to perform this operation. The time is expressed in the defined time unit.

    • Subcontract (field SCOCOD)

    This field indicates if this 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.

    This field identifies the group of work centers to which this subcontracted work center belongs. Work center groups are used to review workloads.

    • Subcon w/c (field SCOWST)

    Use this field to identify the production resource that is to be used for this subcontracted operation.

    Type in, or select from the Work Centers table the code of the subcontract resource to be used for this operation.

    Use this field to identify the service to be carried out by the subcontractor to execute this operation.

     You must be authorized to change this service if this is an operation in a versioned routing for a versioned product (BOM).

    • Subcontract LT (field SCOLTI)

    This field displays the number of days for the subcontractor to execute the operation.

    • LT unit (field JOUR1)

    This field displays 'Calendar days'. This is the unit of time that is used to measure this subcontract operation.

    This field identifies the group associated with the labor work center.

     
    • Labor wk C (field EXTLAB)

    Use this field to associate a labor work center with this machine. For example, a labor work center that relates to the crew that operates this machine.

     You must be authorized to change this resource if this is an operation in a versioned routing for a versioned product (BOM).

    • Short description (field EXTLABSHO)

    This field displays the short description defined for the selected work center.

    • No. lab res. (field EXTLABNBR)

    Use this field to define the number of this particular labor resource that are required for this operation.

     You must be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).

    • Revision reason (field REVREASON)

    This field supports the following changes to a work order for a versioned product:

    • Critical changes made by an authorized user to an operation in a versioned routing;
    • Changes to the defined routing or routing version in the work order header which result in the operations being reloaded from the new routing record.

    Critical changes to an operation in a versioned routing are defined as the following:

    • Addition of an operation using the Additional operation not expected action (from the Actions icon);
    • Exclusion (or cancelling) of an operation, or reinstatement of a (cancelled) operation using the Exclude line or Reactivate actions respectively (from the Actions icon);
    • Changes to the production resource that is to be used for an operation (fields Work center or Number of resources);
    • Changes to the planned quantity for an operation (field Planned quantity);
    • Changes to machinery running costs (fields Setup timeUnit time or Run time);
    • Changes to labor costs (fields Labor wk CNo. lab res. or Subcontract product).

    Use this field (maximum 50 characters) to explain the reason you made the change. This field is mandatory for a change listed above when the product to be released and the defined routing is version-managed, and parameter MFGREV - Revision management (chapter GPA, group WOM) is set. It provides traceability of these changes by writing details of each change to the Work order - operations audit table (table MFGOPEREV). Details written to this table include the revision reason from this field, a revision code and key details from the operation line.

    Changes to the defined routing or routing version update this field automatically.

     Parameter MFGREV (Revision management)

     Revision history action

    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 Projectcode (field PJT) determines the Project analytical dimension (field 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 materials (BOM) and routing operations are initialized for the project assigned to the first released product line on the order.

     A modification to the Project code (field PJT) can result in the Project analytical dimension code (field CCE(n)) being reinitialized.

     

    Close

     

    Action icon

    Operation detail

    Fields

    The following fields are included in this window :

    Resources

    • Work center (field XWSTTYP)

    This field identifies the type of operation that is 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.

    • field EXTWST

    Use this field to identify the production resource that is to be used for this operation.

    Type in, or select from the Work Centers table the code of the resource to be used for this operation.

     You must be authorized to change this resource if this is an operation in a versioned routing for a versioned product (BOM).

    • field WSTDES

    This field displays the short description defined for the selected work center.

    • Number (field EXTWSTNBR)

    This field displays the number of this particular production resource that are required for this operation. You can amend this figure, if required.

     You must be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).

    • Labor wk C (field XLABWSTTYP)

    This field identifies the type of operation that is 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.

    • field EXTLAB

    Use this field to associate a labor work center with this machine. For example, a labor work center that relates to the crew that operates this machine.

     You must be authorized to change this resource if this is an operation in a versioned routing for a versioned product (BOM).

    • field LABWSTDES

    This field displays the short description defined for the selected work center.

    • Number (field EXTLABNBR)

    Use this field to define the number of this particular labor resource that are required for this operation.

     You must be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).

    Parameters

    • Time type (field ROOTIMCOD)

    The operation time type conditions the production time entry.
    The following values are possible:

    • Proportional: the production time is proportional to the released quantity. It is expressed in hours and minutes (based on the time unit) for a given number of units (based on the management unit and basic quantity).
      With a proportional time type, the production time is entered in the operation time section and the rate section cannot be assigned.
    • Rate: the production time is proportional to the released quantity. The rate is used to express the time in number of units per hour or minute, depending on the time unit.
      With a rate time type, the production time is entered in the rate section and the operating times, management unit and basic quantity cannot be entered.
    • Fixed: the production time is independent of the released quantity. This time is expressed in hours or in minutes depending on the management unit.
      With a fixed time type, the production time is entered in the operating time section and the management unit, basic quantity and rate cannot be entered.
    • Management unit (field TIMCOD)

    Depending on the resource being used, the number of decimals of the operation time can be insufficient to express the production time.
    The management unit makes it possible to express the operation time for 1, 100, 1000 or a lot of units of parts to be produced.
    If the management unit is chosen by lot, the size of the lot can be entered in the basic quantity.

    • Base quantity (field BASQTY)

    The basis quantity entry depends on the management unit.
    In effect, if the time is expressed for 1 unit, for 100 units or for 1,000 units, the basis quantity is forced, respectively to 1, 100 or 1,000 units.
    However, if the time is expressed for a lot, the basis quantity can be entered. If the processed routing code is dedicated to a site, it is initialized by the lot size of the product-routing for this site.
    The basis quantity entry format depends on the operation unit.

    • Rate (field CAD)

    The rate is a number of units produced by minute or by hour according to the time unit specified in the routing header (for an operation), or in the standard operation itself.
    The number of units is expressed according to the time unit.
    It can only be entered if the operation time type is the "rate".

    • field TIMUOM3

    This field displays the unit of time in which this operation is measured.

    Labor factor

    • Setup time (field SETLABCOE)

    This is the planned setting time to obtain the setting time allocated to the labor work center linked to the main work center.

    This coefficient applied to the planned setting time to obtain the setting time allocated to the labor work center linked to the main work center.
    This field is only available for entry if the labor work center is entered.

    • Run time (field OPELABCOE)

    This is the coefficient applied to the planned operation time. It is used to obtain the operation time for the labor work center linked to the principal work center. This field is only available for entry if the labor work center is defined.

    Operation times are subdivided as follows:

    Proportional times are expressed for the production of an operation unit (and not in the stock unit of the finished product using the routing).

    Off time charge

    • Coefficient (field HCTIMCOE)

    This coefficient helps with data entry. It is used to multiply the load times (preparation time, waiting time and post run time) for a standard operation, if the 'recovery of the operation data' has been confirmed.

    This coefficient is not recorded in the tables. It is set to 0 (zero) when loading a routing operation. If a standard operation specified for a routing operation is modified, it is set to 1. The coefficient can be entered on the operation detail line for a new routing operation, or in the Routing operation detail screen (available from the Actions icon) when set to 1.

    • Preparation (field PRPTIM)

    Preparation time is 'waiting time' set at the start of an operation.

     Preparation time is always expressed in hours. It does not use the time unit defined in the routing header (field Time unit). Preparation time is not applied to the work center load.

    Although preparation time is waiting time it can be used for the time it takes to prepare for an operation on a work center. This might be time for settling liquids or cleaning a machine. For this type of scenario, that is when preparation time is used for setting time at the start of an operation, the resource must be available.

    When scheduling preparation time the calendar for the defined resource is applied. This means that if, for example, a work center (machine or labor) runs from 08:00-12:00 and 13:00-17:00 with a break for one hour between 12:00-13:00, preparation time will be interrupted by the one hour break.

    If the operation requires an 'emergency release', a reduction coefficient can be assigned that makes it possible to completely remove any preparation time.

    • field TIMUOM4

    This field displays the unit of time in which this operation is measured.

    • Wait time (field WAITIM)

    Waiting time is 'delay time' that occurs after an operation. It is non-productive time such as drying time or cooling time that occurs after a process has been completed on a machine and until the machine can next be used.

     Waiting time is always expressed in hours. It does not use the time unit defined in the routing header (field Time unit). Waiting time is not applied to the work center load.

    If machine time is required for an operation during the allowed waiting time you should add a new operation to this routing. A machine might be required for example, for drying or cooling components at a work center. The additional operation must be for the appropriate resource type, such as 'cooler'.

    When scheduling time for these resources if, for example, a work center (machine or labor) runs from 08:00-12:00 and 13:00-17:00 with a break for one hour between 12:00-13:00:

    • When scheduling waiting time the calendar for the defined resource is applied. Waiting time will be interrupted by the one hour break.
    • When scheduling time for the additional resource the calendar for the defined resource is applied. Time will be interrupted by the one hour break.
    • field TIMUOM5

     

    • Post op time (field PSPTIM)

    Post operation, or post run time is a 'deadline' that occurs after waiting time. It is non-productive time, typically 'transfer time', or a transition period from one work center to the next work center that occurs after a process has been completed on a machine and until the machine can next be used.

     Waiting time is always expressed in hours. It does not use the time unit defined in the routing header (field Time unit). Waiting time is not applied to the work center load.

    If operator time is required for an operation during the allowed post run time you should add a new operation to this routing. An operator might be required for example, for the transportation or carriage, or the transition between two work centers. The additional operation must be for the appropriate resource type, such as 'carrier'.

    When scheduling time for these resources if, for example, a work center (machine or labor) runs from 08:00-12:00 and 13:00-17:00 with a break for one hour between 12:00-13:00:

    • When scheduling post run time a neutral 24 hour calendar for the defined resource is applied. Post run time is not, therefore, interrupted by the one hour break.
    • When scheduling time for the additional resource the calendar for the defined resource is applied. Time will be interrupted by the one hour break.

    If the operation requires an 'emergency release', a reduction coefficient can be assigned that makes it possible to completely remove any post run time.

     When scheduling time for these resources, if both waiting time and post run (post operation) time has been declared for the operation only the largest of the two values is used.

    • field TIMUOM6

     

    Load

    • Coefficient (field CTIMCOE)

    This coefficient helps with data entry. It is used to multiply the load times (setup time and run time) for a standard operation, if the 'recovery of the operation data' has been confirmed.

    This coefficient is not recorded in the tables. It is set to 0 (zero) when loading a routing operation. If a standard operation specified for a routing operation is modified, it is set to 1. The coefficient can be entered on the operation detail line for a new routing operation, or in the Routing operation detail screen (available from the Actions icon) when set to 1.

    • Setup time (field EXTSETTIM)

    The setting time is a fixed amount of time necessary to prepare the work center.
    It is part of the work center load.
    It is expressed in the time unit specified in the routing.

    • field TIMUOM1

    This field displays the unit of time in which this operation is measured.

    • Unit times (field EXTUNTTIM)

    Planned unitary time.
    The unitary time is the planned operating time necessary for the production of a unit.

    • field TIMUOM8

     

    • Planned quantity (field EXTQTY)

    This field displays the planned quantity expressed in the operation unit.

     You must be authorized to change this figure if this is an operation in a versioned routing for a versioned product (BOM).

    • Run time (field EXTOPETIM)

    The operation time is the time necessary to manufacture the product described in the routing.

    The operating time:

    • in hours or minutes (see the time unit),
    • is expressed for 1, 100, 1,000 or a lot of units of the operation based on the management unit,
    • can be proportional or fixed, based on the type of operation times.
      Example:
      Time unit = Hours
      Time type = Proportional
      Management unit = Time for 100
      Operating time = 2
      Operation unit = Kg
      Finished product unit = One
      Conversion coefficient DU-OU = 0.5
      The operating time equals 2 hours for 100 Kg. If the Work Order is launched for 1,000 units of finished product, the time necessary to produce this operation is 10 hours to obtain 500 Kg.
    • field TIMUOM2

     

    • % efficiency (field EFF)

    Efficiency is a way to measure compliance to the preset standards. It can be calculated over a given period by work center: Standard hours calculated for a given production divided by the actual hours worked.
    Efficiency makes it possible to correct the standard times of the routing (multiplying factor) according to the used resource.

    Two efficiency rates are managed depending on the following:

    • Work center: The rate is applied to all the routing operations that will take place at the work center.
    • Routing operation: The rate only applies to the considered operation.

    If both factors are entered, they add up.
    The calculated operating time is corrected in the following way: work center efficiency * operation efficiency * time.

    The WSTEFFINH - Work center efficiency history parameter (GPA chapter, MIS group) is used to specify whether the efficiency defined at work center level should be used on the routing operation.

    • If WSTEFFINH is set to Yes, the efficiency entered in the work center is suggested by default when creating the routing operation with this work center. The calculated runtime = runtime entered * 1 / operation efficiency.
    • If WSTEFFINH is set to No, the efficiency entered in the work center is combined with that entered in the routing operation. The calculated runtime = runtime entered * 1 / work center efficiency * 1 / operation efficiency.


    • Shrinkage in % (field SHR)

    This percentage is used to balance the quantities on the production operations based on the released quantity.

    It is possible to introduce a shrinkage percentage on the work center, which is used to weight the planned runtimes for an operation using this work center by a loss or gain on the quantity produced for the work center.

    Unit

    Work order operation quantities are expressed in the operation unit. Use this operation unit to express operating time in a different unit to that of the product being produced by the routing.

    For example, a product managed by unit is subject to three different operations, none of which produce intermediate stock:

    • Mixing time (operation 1) is expressed for a lot with Kilogram as the unit;
    • Extrusion time (operation 2) is a rate in meters per hour;
    • Cutting time (operation 3) is expressed in hours per unit.

    There is no need to create semi-finished products for each production phase.

    The operation unit is associated with a conversion coefficient for the stock unit of the product being produced by the routing and the operation unit.

    • STK-OPE factor (field OPESTUCOE)

    The Stock unit-Operation unit conversion coefficient is used to convert the released quantity of finished product into the quantity of the operation according to its unit.
    It belongs to the coefficient table.

    Subcontract

    • Lead time (field SCOLTI)

    This field displays the number of days for the subcontractor to execute the operation.

    • field XJOUR1

     

    Close

    Click Operation detail from the Actions icon to add or amend the details for this operation using the standard screen display mode.

    The possible operation grouping criteria used by the Optimization/Scheduling functions is accessed from this screen.

    Exclude line/Reactivate

    Click Exclude line from the Actions icon to exclude (or cancel) this operation. To reinstate this (cancelled) operation, click Reactivate.

     You must be authorized to perform these actions if this work order is for a versioned product (BOM) and the routing defined to manufacture the BOM is versioned. If parameter MFGREV - Revision management (GPA chapter, WOM group) is set to Yes you must provide a reason (maximum 50 characters) for taking this action (Revision reason field).

    Tracking status

    Click Tracking status from the Actions icon to view, in summary, the quantities and operation times for this 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

    Click Text from the Actions icon to view, enter or modify text associated with this 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 raised. Click Order from the Actionsicon to enter details for, and then generate a Purchase order for this operation.

    Subcontracted operation situation

    Click Subcontracted operation situation from the Actionsicon to view order information for this subcontracted operation.

    Revision history

    Click 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, parameter MFGREV - Revision management (GPA chapter, WOM group) is set, the product is versioned and the selected operation is in a versioned routing. The revision history includes a revision reason, a revision code and key details from the operation line. The current details for the selected operation are displayed on the first (top) line of the table. Amended fields are highlighted.

    Additional operation not expected

    Fields

    The following fields are included in this window :

    • Operation (field OPENUM)

    Type in the sequence number of this operation.

    • field OPESPLNUM

     

    • Line status (field XOPESTA)

    This field tracks the progress and status of this operation.

    • Standard operation (field STDOPENUM)

    The standard operation is a "template" operation used to create or modify the routing operations.
    The definition of the fields of a standard operation is very similar to that of a routing operation.

    Recover the standard operation data:

    • if the operation unit is mentioned in the standard operation, it is used again, otherwise, the stock unit of the product in the routing is used.
      If not entered, the conversion coefficient is extracted from the coefficient table
    • The times (rate, setting time and operating time) are converted if the time unit of the routing header is different from that of the standard operation.
      The standard operation is referenced in the operation that called it as a template.

    SEEWARNING When modifying a standard operation, the modifications are not passed on to the associated operations.

    • Description (field ROODES)

    This field displays the description defined for the routing operation.

    Close

    Click Additional operation not expected from the Actions icon to add an unplanned operation.

     You must be authorized to perform this action if this work order is for a versioned product (BOM) and the routing defined to manufacture the BOM is versioned. If parameter MFGREV - Revision management (GPA chapter, WOM group) is set to Yes you must provide a reason (maximum 50 characters) for taking this action (Revision reason field).

     

    Close

     

    Tab Documents

    Presentation

    This section is for information purposes only. It displays which production folder documents from those defined within the selected Entry transaction have been printed.

    Once all planned documents from the production folder have been printed the work order advances to status Printed.

    Close

     

    Fields

    The following fields are present on this tab :

    WO documents

    • Material issue slip (field PICLISFLG)

    If selected, a Material issue note (BSM) is printed. If clear, a Material issue note is not required.

    • Routing sheet (field ROUSHEFLG)

    If selected, the Routing sheet (FICHSUI) is printed. If clear, the Routing sheet is not required.

    • Job ticket (field LABTIKFLG)

    If selected, a Job ticket (BONTRV) is printed. If clear, a Job ticket is not required.

    • Production slip (field MFGTIKFLG)

    If selected, a Production slip (RECETTE) is printed. If clear, a Production slip is not required.

    • Technical sheet (field TECCRDFLG)

    If selected, the Technical sheets (FICHTEC) are printed. If clear, the Technical sheets are not required.

    Labeling mode

    • Manual (field LBEMAN)

    This field controls the printing of labels. Set to 'Manual' labels are printed on demand using the Labels action. If set to 'Automatic', labels are printed when progress is recorded using the Production tracking function (GESMTK).

     This field is ignored when production reporting is made via subcontract receipts, the production tracking plans or imports.

    • Automatic (field LBEAUT)

    This field controls the printing of labels. Set to 'Manual' labels are printed on demand using the Labels action. If set to 'Automatic', labels are printed when progress is recorded using the Production tracking function (GESMTK).

     This field is ignored when production reporting is made via subcontract receipts, the production tracking plans or imports.

    Close

     

    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

    Click 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.

    • If the work order is not allocated (field Allocation status= Not allocated), choose the allocation type (global or detailed allocation) and click Allocate. The system will allocate all the components in the work order simultaneously.

      • Global allocation does not specify the details of the material stock (location, lot) to be consumed. It increments the reserved stock for the component and decreases its available stock. At the time of the effective consumption of the materials, the system will itself transform the global allocation into a detailed allocation.

      • Detailed allocation specifies the location from which the material will be consumed. The allocated stock for the material is increased and its available stock is decreased. The determination of these locations is performed based on the allocation rule set up at product category level.

    Once the allocation has been performed, the Allocate action remains active and the summary data for the allocation status is updated.

    • If the components are allocated (field Allocation status= Complete), the Deallocate action is active. You can choose to deallocate all the materials which were allocated globally or in detail (complete deallocation), or to deallocate the materials by allocation type (deallocation by type). Once the materials have been deallocated the summary data is updated.
       You must deallocate the materials if you need to modify an allocated component.

    • If your selected entry transaction is set to automatically allocate materials when a work order is created, a global allocation is performed simultaneously for all components. As described above, you can view the summary data in the WO allocation screen and deallocate materials or reallocate materials using the Deallocate and Allocate actions respectively.

    To view the details of the allocations, click the View action.


    You can allocate a specific component from the Actions icon:

    • Click the Global allocation action to perform a global allocation of the selected material.
    • Click the Manual allocations action to manually allocate the selected material. A screen is displayed summarizing all the lines from which allocations (lot, sublot, version, serial number, location) can be selected.
     Components sectionAction icon

     Requesting a global allocation of all components does not affect manually allocated components.


    Once the allocation is complete, the Allocation field in the Header section is updated.

    The following fields are included on the window opened through this button :

    Block number 1

    • Work order (field MFGNUM)

    This field displays the work order number (unique ID).
    This number is automatically or manually generated upon each creation.
    Click the Selectionicon to open the list of work orders (which only includes 'Firm' or 'Closed' work orders) and select a work order.

    • Scheduling mode (field SCDMOD)

    This field displays the scheduling mode defined on the Header. 'Backward' scheduling respects the defined End date; 'Forward' scheduling respects the defined Start date.

    • Scheduling status (field SCDFLG)

    This field indicates the current stage of this work order in the scheduling process. This status can be Scheduled or Optimized.

    Block number 2

    • Initial objective (field OBJDAT)

    This field displays the end date of this work order. It represents a target production delivery date. It is calculated when a work order is created and scheduled for the first time.

    If your objectives, requirements or target completion date for this work order have changed you can change this date.

     This work order will be marked as 'late' in your production report if this work order cannot be completed on time and you have not changed this date.

    • Advance/Delay (field ELFLG)

    The number of Early or Late days is calculated by the system depending on the initial objective date and the current date.
    If the difference is positive, the order is early. If the difference is negative, the order is late.

    • field JOUR1

     

    Grid Schedule data

    • No. (field OPENUM)

    This field displays the sequence number of this operation.

    • Type (field WSTTYP)

    This field identifies the type of operation that is 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.

    • Work center (field WST)

    This field identifies the production resource that is to be used for this operation. This work center is the main (principal) work center for this operation. It can be a machine, labor or subcontract work center. The scheduling of the operations looks at the availability of this work center.

    Work centers of type 'subcontracting' are managed using the lead time defined in the subcontract product record. Subcontract operation times are not used by the scheduling.

    • No. (field EXTWSTNBR)

    The number of work centers makes it possible to set up all or part of the resources of a work center with a view to performing an operation.

    • Operation start (field OPESTRDAT)

    This field identifies the date this operation must be started. The date is determined by the Scheduling mode and by the Scheduling status fields, as follows:

    • If this work order is 'Not scheduled', this operation's start date matches the start date for this work order (as defined on the Header).
    • If this work order is 'Scheduled', this operation's start date will be the earliest date this operation can start according to the scheduling process. That is, this date will be determined by the sequence of operations in time according to the durations, slack times and relationships in the routing.
    • Operation end (field OPEENDDAT)

    This field identifies the date this operation must be completed. The date is determined by the Scheduling mode and by the Scheduling status fields, as follows:

    • If this work order is 'Not scheduled', this operation's end date matches the end date for this work order (as defined on the Headertab)
    • If this work order is 'Scheduled', this operation's end date will be the latest date this operation can be completed according to the scheduling process. That is, this date will be determined by the sequence of operations in time according to the durations, slack times and relationships in the routing.
    • Beginning load (field INFCAPSTR)

     

    • Ending load (field INFCAPEND)

     

    • Next operation (field NEXOPENUM)

    The next operation is used to link the routing operation in a logical order for the operational process.
    This operation does not necessarily start at the end of the previous operation in the operational process as the scheduling describes the sequencing mode of the operations.

    The next operation must be different from the processed operation, and must be part of the operations of the processed routing.
    The last operation in the routing must have available a next operation set to zero.

    • Scheduling (field SCDCOD)

    Scheduling determines the way in which routing operations follow each other. It can take the following values:

    • Absolute successor. Position is at the end of the longest operation in the routing.
    • Overlapping wait = lots. The following operation can start after a period of time corresponding to the number of lots manufactured during the processed operation.
    • Overlapping wait = time. The next operation can start after a period of time equal to a given overlapping time.
    • Overlapping wait = quantity. The next operation can start when a given quantity over the processed operation has been produced.
    • Start synchronization. The next operation is synchronized to start at the same time as the processed operation.
    • End synchronization. The next operation is synchronized to end at the same time as the processed operation.
    • All order operations parallel. The next operation is synchronized to start at the same time as the first operation.
    • Subcontract synchronization. Code used automatically when a subcontracted operation is distributed over several supplier orders. In this situation the operation is split up and this code is used to link the various components to a single operation.
    • Simple successor. Position is just after the previous operation.
    • Overlapping time (field SCDTIM)

    Overlapping time is only accessible if the Scheduling field (SCDCOD) is set to Overlapping wait = time.

    Overlapping time is always expressed in the routing Time unit (TIMUOMCOD field).

    • Overlap qty (field SCDQTY)

    Overlapping quantity is only accessible if the Scheduling field (field SCDCOD) is set to 'Overlapping wait = quantity'.

    An overlapping quantity is always expressed in the operation unit (field OPEUOM).

    • No. of overlap lots (field SCDLOT)

    The number of overlapping lots is only accessible if the automatic scheduling is set to "overlapping with waiting time = number of lots".

    • Lot quantity (field LOTQTY)

    Lot size
    The lot size is used in the MRP (Materials Requirements Planning) calculation. According to the reorder policy, the lot size lets you perform the following actions:

    • Split a global suggestion into several lots (manufacturing constraint: vat size, etc.)
    • Round up the requirement to the minimum quantity when the lot size is fixed (purchase constraint such as boxes of n units).
      For example:
    • Production suggestion of 500 units, to be divided into 5 suggestions of 100 units
    • Purchasing suggestion of 52 units with a lot size of 12: it is necessary to order 60 units.

    This field identifies the group of work centers to which this work center belongs. Work center groups are used to review workloads.

    • Milestone (field DACMST)

    This field defines the type of production tracking that applies to this operation, as follows:

    • No. This operation is not tracked manually.
    • Normal tracking. This operation is tracked normally.
    • Range. This operation and all the previous non-tracked operations are tracked automatically until the first operation is found that is set to Normal trackingor is itself included in a range of operations.
    • Production step (field MFGMST)

    When the "production step" code is set to "yes" for an operation, the production reporting (receipt to stock of the finished product) can follow the end of the time entry.
    For a given routing, the scheduling is only correct (and the routing validated) if there is a least one production step.

    Close

    Click the Schedulingaction to schedule this 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 routing for suggestions).

    A target completion date (Initial objectivefield) is displayed. This field is initialized by the required 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 since the target completion date is also displayed (Advance/delayfield). 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 this 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 is displayed. The system proposes forward (downstream) scheduling from today's date (Start date field), amending the required completion date (End date field in the Header section) accordingly.

    The routing version, if defined, must be at status Available to use 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 Schedulingfield will remain at status Not scheduled. You must either change the routing version or reschedule this work order before you can continue. Please refer to the Major version field for further information.

    Once 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.

    The sequence of operations follows the defined numbering sequence.

     You must remove this work order from scheduling (deschedule) if you need to modify an operation.

    A Graphaction is available when this work order is scheduled to view the relationship and duration of the operations in a graphical format.

    A Loadaction is available to view the work center load in a graphical format.

    Click the Status action to view summary details for this work order, and for each section.

    Click the Tracking action to view the production tracking for this work order.

    Click Submit for scheduling to send this work order to Production Scheduler, Sage X3 Web Scheduling or your web scheduler for scheduling.

    Whilst this work order is being scheduled (has been submitted for scheduling) it remains at scheduling status Scheduled and work order status Being optimized. At these statuses you cannot modify this work order.

     You can submit a range or a set of work orders at a specific status for scheduling using the Submit for scheduling function.

     For detailed scheduling, thePOPS - Production Scheduer activity code activates theProduction Scheduler functionality; theGFS - Finite scheduler activity code activates the generic Finite scheduler interface.

     Production 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.

    Click Remove from scheduling to remove this work order from Production Scheduler, Sage X3 Web Scheduling or your web scheduler.

    This work order changes to the status it was at prior to scheduling, that is, status Pending or In progress. You can now modify this work order and resubmit it for scheduling if necessary.

     You can remove a range of work orders from scheduling using the Remove from scheduling function.

    Menu bar

    Texts / Header text

    Click the Header text action to view, enter or modify text associated with this work order.

    Option / Provisional availability

    Use this option, based on the released quantity, to view the availability of the required components. In case of non-availability, the system proposes a first availability date.

    Option / WO provisional cost calculation

    Use this option to launch the theoretical provisional cost calculation and the provisional cost calculation for the release.

    Option / WIP cost inquiry

    Click the WIP cost inquiry action to view the production costs for this work order and to compare the actual costs with the planned costs.

    Option / Production cost inquiry

    Use this option to access the Cost price Inquiry function.

    Option / Provisional cost inquiry

    Use this option to access the Provisional cost inquiry function.

    Option / Sub-con situation

    Option / WO suspension/reactivation

    Use this option to suspend or place a work order on "hold". Suspended status is displayed in the home section. You cannot track suspended work orders. Reactivate this work order if you need to track it.

    Option / WO close

    Click the WO close action to complete and close this work order.

    Option / Transaction

    Click the Transaction action to view the format of this Entry transaction.

    Report / WO documents

    This action is available if this order is at Firm status and allocated at least globally. If some materials are in shortage, folder printing will only be possible if these materials authorize shortages (the Release if shortage check box in the Manufacturing section of the product-site record is selected).
    Click the WO documents action to start printing the production folder (the documents to be printed are defined in the selected Entry transaction).

    Report / Labels

    Click 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 site

    The defined site is not a production site. Click the Selectionicon to open the complete list of available production sites.

    The site is not in the same legal company

    The planning site and production site must belong to the same legal company.

    Problem at the time of sequence number counter recovery
    or
    No sequence number has been assigned to this document

    This message is displayed where there is a problem in the sequence number counter setup.

    Header section: Released products

    The entry of at least one product to be released is mandatory

    You must add a minimum of one product to be released by this work order.

    Product not manufactured
    or
    It must be a production BOM

    The product to be released must 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, that is, the product has been created from a product design BOM revision and has a New product in design mode warning displayed in the home section of the parent product. The Prototype check box in the home section of this 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 must exist for the chosen production site. Click the Selectionicon from the field of the product to be released in order to open the list of products for which the product-site has been 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 must be at status Available to use.

    XXXXXXX is the exclusive planner for this product

    You can only release products for which you are the planner (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 counter

    This message can be displayed when entering the released products, only if an automatic lot numbering is defined for the product.

    Capacity of the sequence number counter exceeded

    This message can be displayed when entering the released products, only if an automatic lot numbering is defined for the product.

    The Stock unit of the released products should be the same

    This 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 project

    The WOPJMMSG - Block multiple projects on WO parameter (TC chapter, PJM group) is set to Yes therefore all product lines on a work order must 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 site

    This message appears if the start or end date entered corresponds to a rest day.

    Warning, the date is prior to the current date

    This information message is displayed if the calculated start date is exceeded.

    Header section: Routings

    The routing and routing code route must be entered

    This message is displayed when the work order is to be completed as "materials only".

    You do not have the authorization to use this code

    This message is displayed following the validity check on the BOM and routing codes.

    Code not valid for this site

    You must check the routing and the BOM code belong to the defined production site.

    No valid routing found, release not possible

    This 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 must be at status Available to use. Additionally, the routing code must be available for use in production.

    There are inconsistencies between the routing and BOM codes

    This message can be displayed after entering the routing code. You need to verify which BOM codes are associated with the chosen routing code.

    The routing is not active on the production start date

    This message can be displayed following the validity check on the routing.

    The stock units are not compatible

    This 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 management

    This message is displayed if this 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 this work order or raise 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 possible

    This 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 consumed

    This 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 date

    This message is displayed if you attempt to postpone a material requirement date beyond the planned end date of this work order.

    Incompatible product category

    This is a contextual warning, for example, a tool must 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 required to verify that the quantity taken for the phantom product is actually available. If the quantity is not available you must 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 added

    This message is displayed if you attempt to add the same planned material more than once.

    A product cannot be produced from itself

    This 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 quantity

    This message is displayed if you attempt to reduce the planned quantity for an operation below the quantity already produced.

    Unavailable period

    This message is displayed if a date entered falls in an unavailable period for the production site.

    XXXXXXX is not a sub-contracting work center

    This 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 center

    This message is displayed after the contextual control on the entry of a new work center. A secondary work center must be of labor type.

    The labor work center cannot be identical to the main work center

    This message is displayed after the check on the entry of a new secondary work center.

    Access not authorized for this product

    This 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 operation

    This message is displayed in the scheduling data if no operation is defined as a "production" operation.

    This number is already used

    This message is displayed if you attempt to add an operation carrying a number that is already assigned.

    Caution: it is necessary to verify that the times (setting, operation or rate) remain coherent

    This 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 folder

    Before 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 scheduling

    This 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 required end date modified.

    An error has arisen during scheduling/descheduling

    This is a serious read/write error that has occurred whilst 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 is likely to challenge the scheduling, such as modifications to quantities, dates, times, work centers.

    You are about to make critical changes to a work order for a versioned product
    and
    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 only displayed to an authorized user when they attempt to make what is considered to be a critical change to the work order. It will not be redisplayed for subsequent changes until the Saveaction is selected.

    Unexpected or excluded materials or critical changes on this WO will also be removed.

    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 quantity 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 must 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 raise a new work order with the new details.
     This message is only displayed if there are existing critical changes to the components or operations.

    Products error on line n

    You have changed the version of the product to be released. You must 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 inconsistency

    Sage recommends a work order for a project should only cover demand for a single project. If a work order is raised manually it is 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 one released product line (Multiple products allowed check box). 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 must 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 must 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 raise 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 is only displayed if there are existing critical changes to the operations in a version-managed routing for a work order for a versioned product (BOM).

    Direct order: continue the modification?

    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 reason

    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 if you have not explained the reason you changed the work order details. Providing a "revision reason" is mandatory for each key change to a work order for a versioned product if the MFGREV - Revision management parameter (GPA chapter, WOM group) is set.
     MFGREV - Revision management parameter

    The WO will be allocated to a new production site. Do you want to continue?

    The system requires a confirmation before modifying the production site.
     You can only modify the production site if the work order has not been allocated or scheduled.

    The requirement will be closed. Continue?

    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 adjusted

    This 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 one 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 are 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.

    Tables used

    SEEREFERTTO Refer to documentation Implementation