Modify objectives

• Production site (field MFGFCY)

Type in or select the production site from which the work orders are to be selected. This field is mandatory.

• Firm work orders (field WOFFLG)

Select this check box if firm work orders are to be processed. If firm work orders are to be excluded from the run, leave this check box clear.

• Planned work orders (field WOPFLG)

Select this check box if planned work orders are to be processed. If planned work orders are to be excluded from the run, leave this check box clear.

• Include optimized orders (field OPTFLG)

Click this check box if optimized work orders are to be processed. If optimized work orders are to be excluded from the run, leave this check box clear.

• Order no. (field MFGNUMDEB)

Filter for results within a range of work orders. For a single work order, enter the same work order number in the from/start Order no. (Work order number) and to/end Order no. fields.

• Project (field PJTDEB)

Filter for results within a range of project codes. For a single project, enter the same project code in the From/start project and To/end project fields.

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

• Destination (field BPCNUMDEB)

Filter for results within a range of "ship-to" customers and/or sites. For a single customer or site, enter the same code in the from/start Destination and to/end Destination fields.

• Order no. (field VCRNUMDEB)

Filter for results within a range of source sales orders. For a single sales order, enter the same code in the from/start Order no. (Order number) and to/end Order no. fields.

• Released product (field ITMREFDEB)

Filter for results within a range of finished products (BOMs). For a single bill of materials (BOM), enter the same product code in the from/start Released product and to/end Released product fields.

• Start date (field STRDATDEB)

Filter for results within a range of dates. For a single day, enter the same date in the Start date and End date fields. You can leave the Start date field blank to search all records to date.

• field TRI

Use this field to modify the sort order.

• Production site (field MFGFCY)

The production site from which the work orders are to be processed.

• field FCYDES

The name (title) of the production site.

• No. W.O. (field MFGNUM)

This field displays the work order number.

• Order status (field MFGSTA)

This field indicates the current status of the work order to be generated. This status can be 'Firm' or 'Planned'. You cannot modify it.

• Status (field MFGTRKFLG)

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 (field ROUNUM)

This routing code describes a particular sequence of shop floor processes for a particular product. That is, the sequence of operations and tools that are used in a particular routing.

The routing code is a product code which can be the reference for a manufactured product or a generic reference (parent routing) linked to multiple products.

• Routing code (field ROUALT)

Multiple routings can be defined for a single product. Each routing code can be assigned specific management features. These include restriction of the routing to a specific site and to specific areas of functionality (for use in a manufacturing environment, for costing or for capacity planning).

• STK (field STU)

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

• Remaining quantity (field RMNEXTQTY)

This field displays the remaining (outstanding) quantity required to complete the order.

• 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 can change this date if your objectives or production start date for this work order have changed.
• 'Backward' scheduling respects the defined End date. The system calculates the date from the production lead time, reduction factor and economic quantity defined on the product-site record. It will adjust this date accordingly if you change the Start date.

 You cannot change this date if you use Production Scheduler, that is Activity code POPS-Production Scheduler is 'Active', if the operations on this work order have been optimized by the scheduler.

 Production Scheduler only applies to on-premises instances of Enterprise Management.

• 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 can change this date if your objectives or required completion date for this work order have changed.
• 'Forward' scheduling respects the defined Start date. The system calculates the date from the production lead time, reduction factor and economic quantity defined on the product-site record. It will adjust this date accordingly if you change the End date.

 You cannot change this date if you use Production Scheduler, that is Activity code POPS-Production Scheduler is 'Active', if the operations on this work order have been optimized by the scheduler.

 Production Scheduler only applies to on-premises instances of Enterprise Management.

• Objective date (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.

• Early/Late (field AVRT)

This field measures the number of days between the target production delivery date of this work order (field Objective date) and the end or required completion date for this work order (field End date). It shows a positive figure if the work order will be completed early and a negative figure if the work order is overdue or will be late, according to the scheduling or your planning.

• Priority (field MFGPIO)

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

• Scheduling (field SCDFLG)

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.

• Allocation (field ALLSTA)

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

• Project (field PJT)

This field displays the associated project code. The content can be 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 content 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 cost structure or the project operational 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).

• Destination (field BPCNUM)

This field displays the 'ship-to' customer or site.

• Source document number (field VCRNUM)

This field identifies the number of the source document or order.