Manufacturing > Production tracking > Time tracking plan 

Use this function to record operator time and progress against individual work orders, routings and work centers. This might be recording productive time and the receipt of produced goods for a specific work order, recording activity against a specific operation in a route, or recording time against a work center, usually non-productive time such as maintenance of a machine.

To record, or track production activity, work orders must be at order status 'Firm' (field Order status (field MFGSTA) in the Home section of the Work orders function (GESMFG)) and materials must be available for tracking unless the parameter Release if shortage (field MFGSHTCOD) in the Manufacturing section of the product-site record is selected.

This function is directly linked with the Non-conformance management functionality. If the manufacturing process warrants notification to your Quality management team of a potential non-conformity you can raise a non-conformance incidence directly from this function. For example, if you are aware of a problem, or failure or potential failure in a design or production model, or in a service, or in a process, or in the system.

 Timely notification of a non-conformity can be critical for compliance.

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 Time tracking plan function contains a header information section into which you enter your selection (or filtering) criteria. The operation tracking details will be built from the reference dates you provide. 

Entry screen

Presentation

Filters

Use this section to filter or select records to be tracked:

  • Site. Entry of the production site is mandatory.
  • Employee ID. Entry of an Employee ID is determined by the selected entry transaction. If defined, each record selected defaults to the entered Employee ID code.
  • Tracking dates. You can record operator time over a range of dates.
  • Global time booked. Cumulative time to be apportioned proportionally over the selected records according to the planned times.

Start-end range

A number of ranges are displayed.

  • To include all applicable operations, leave all the fields blank.
  • To include only selected operations, type in the required ranges. Leave the first field blank to include the lowest value or the second field blank to include the highest value.

You can use the Criteria action to enhance the selection criteria applied.

Operation tracking grid

Use the Operation tracking grid or table to enter production times and quantities for operations in the routing used to produce the manufactured product.

The columns displayed in the grid, the order in which they are displayed, the fields available and those that have automated entry of the tracking information is determined by the selected entry transaction.

The default tracking date is today's date. You can enter an earlier date than today but not a later date. Stock issues and receipts corresponding to any material or production tracking are carried out on the entered date. The system will validate that the date falls in a period for which stock updates are authorized.

The types of tracking available – the recording of time against operations for work orders, against operation activity (routing/product tracking) without a work order and against work centers (work center/miscellaneous tracking) – is determined by the selected entry transaction.

You can record progress or completion data against one or all of the selected operations and add an unplanned operation. Production times are adjusted automatically.

  • The quantity you record in the Total completed quantity (field CPLQTY) field should be the total quantity produced by the operation, including any rejected quantities.
  • If you need to record a rejected quantity for an operation, you can assign individual rejection codes to rejection quantities using a Detail entry action. This action is available from the Actions icon in the Actual rejected qty (field REJCPLQTY) and Reject (field SCANUM1) fields.
  • You can record actual setup and run times for an operation over a range of dates and times. An Entry by range action is available from the Actions icon in the Actual setup time (field CPLSETTIM) and Actual run time (field CPLOPETIM) fields. The times are calculated from the entered values.

If this tracking includes progress reporting against the produced goods, the actual quantities are updated from the progress recorded against the selected operations.
 You must adjust the actual quantity of the produced goods if an operation includes a rejected quantity as the total completed quantity of the produced goods reflects the quantity recorded in the Total completed quantity (see above).

If this tracking includes reporting the issue of materials to the work order, the tracked quantities are updated from the progress recorded against the linked operations.

 The Time type provides a useful reference as this function permits progress to be recorded against an operation without a work order.

If this operation tracking is for a scheduled work order, the production load is updated when the tracking is generated.

If the selected entry transaction requires manual confirmation of produced goods quantities or material issues, a Produced goods and/or Material consumption action respectively is available from the Actions icon on each applicable line in the grid. These actions open the appropriate workbench/plan for recording these details. These actions are not available if stock receipts and issues are automated (as determined by the selected entry transaction).

Close

 

Fields

The following fields are present on this tab :

Filters

Type in or select the production site at which operator time is to be recorded. This field is mandatory.

  • Employee ID (field WEMPNUM)

Use this field to identify a specific operator for which time and progress is to be recorded.

  • field EMPDES

This field displays the description from the employee profile and cannot be modified.

  • End date (field ENDDATSTR)

Filter for results within a date range. For a single day, enter the same date in the from/start tracking date and To/End date fields. You can leave the from date field blank to search all records to date.

  • Filter (field FILTOPE)

Use this field to filter the records to be tracked. Select one of the following values:

  • All
  • Closed
  • Not closed

Start - end range

  • Work order (field WMFGNUMD)

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

  • Operation (field WOPENUMD)

Filter for results within a range of operation sequence numbers. For a single operation sequence number, enter the same sequence number in the from/start Operation and to/end Operation fields.

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.

Filter for results within a range of routings. For a single route, enter the same routing code in the from/start Routing and to/end Routing fields.

Filter for results within a range of routing codes. 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).

For a single routing code, enter the same sequence number in the from/start Code and to/end Code fields.

  • Work center (field WWSTD)

Filter for results within a range of actual work centers. For a single work center, enter the same work center code in the from/start Work center and to/end Work center fields.

Block number 2

  • Global time booked (field CPLTIMGLO)

Use this field to define the cumulative time worked between the defined period (dates) if you want the time to be apportioned proportionally over the selected records. Global time is apportioned according to the planned times.

  • field CPLUOMCOD

Use this field to define the time unit in which the defined (global) operator time is expressed. The time unit can be 'hours' or 'minutes'.

  • Warehouse (field WRHE)

The presence of this field is subject to the activity code WRH.

It represents the movement warehouse for all order lines.

  • It can be modified if it is defined as enterable in the entry transaction.
    If it is entered, it serves as a filter for stock detail line selection.
    If it is not entered, the warehouse defined by default for this type of movement in the product-site record will serve as a filter for the selection.
  • It cannot be modified when the entry transaction is set up as single-warehouse managed. The header warehouse is then mandatory.
    To manage multiple warehouses on the lines the entry transaction must be set up so that it can be entered. The selection of a single product line distributed over multiple warehouses is available by clicking Enter detailed quantites from the Actions icon.
    If a single product line is distributed over multiple warehouses, the corresponding fields display the '$' character.

SEEINFOThe warehouse entered on the line has priority over the warehouse entered in the header.

Grid

  • Date (field IPTDAT)

This tracking date defaults to today's date. This date will be used as the posting date for all stock transactions linked to this tracking.
You can enter an earlier date than today but not a later date. The system will validate that the date falls in a period for which stock updates are authorized.

  • Time type (field TIMTYP)

This field displays one of the following values:

  • Work order. The declared time relates to an operation for a work order;
  • Product. The declared time relates to a routing operation;
  • Miscellaneous. The declared time relates to time on a work center such as maintenance of a machine. Miscellaneous time is usually used for recording non-productive time.

  • Order no. (field MFGNUM)

This field displays the work order number (unique ID) progress for this operation is being recorded against.

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.

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

This product code describes what is referred to as a "Bill of Materials" or a "BOM". A BOM contains structured information for making and costing a product. It defines the components that make up a product, and given this, the cost of the product.

The BOM code matches the product code.

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.

  • Operation (field OPENUM)

This field displays the sequence number of this operation.

The operations in a routing used for manufacturing a product are assigned operation numbers. Each operation number corresponds to a task carried out on a given resource, with given times.

  • Ope description (field ROODES)

This field displays the description defined for the routing operation.

  • Standard operation (field STDOPENUM)

This field identifies the standard operation used to create this operation. Standard operations are simply 'template' operations that provide default information to be assembled into routings for producing or processing a particular product.

 Operations based on a standard operation are not updated if the standard operation is changed.

  • Actual work center (field CPLWST)

This field identifies the production resource used for this operation, that is the actual work center used. This work center is the main (principal) work center for this operation. It can be a machine or labor work center. The work center is attached to a work center group.

  • Actual labor W/C (field CPLLAB)

This field identifies the labor work center assigned to this machine. For example, the labor work center that relates to the crew that operates this machine.

The work center site of a 'labor' work center must match the site for the routing code, if defined.

Scheduling is not carried out for labor work centers as they are considered secondary and 'always available' (or available at the same time as the main work center). Their load is managed for information purposes only using the coefficients defined for the main work center.

If the main work center is of type 'subcontracting' there is no associated secondary work center.

  • Labor time set fac (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.

  • Labor r-time fact (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).

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.

  • U-OPE conversion (field OPEWORCOE)

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

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

  • Total completed qty. (field CPLQTY)

Use this field to record the actual completed quantity, in total. This includes the rejected quantity. The quantity is expressed in the operation unit.

  • Actual rejected qty. (field REJCPLQTY)

Use this field to record the actual quantity rejected. This figure cannot exceed the produced quantity. Click Detail entry action from the Actions icon in the field to assign a rejection code to a rejection quantity.

  • Time unit (field TIMUOMCOD)

The time unit defines how time for the operations in this routing is expressed. The time unit can be 'hours' or 'minutes'.

It applies to the setup time, run time and the rate for all operations in the routing.

  • Actual stp. time (field CPLSETTIM)

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

  • Actual unit time (field CPLUNTTIM)

Use this field to record the actual time taken to produce a single unit for this operation. The time is expressed in the defined time unit.

  • Actual run time (field CPLOPETIM)

Use this field to record the actual time taken to perform this operation for the required number of items.

Click the Entry by range action from the Actions icon in the field to record actual setup and run times for an operation over a range of dates and times. The actual operation time is calculated from the entered values.

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.
  • Close (field CLEFLG)

Use this field to specify whether the line must be closed or not ('Yes'/'No').

  • Employee ID (field EMPNUM)

Use this field to identify the operator that performed this operation.

  • Message (field MSGNUM)

Use this field to associate a predefined information message with the information recorded against this operation.

  • Reject (field SCANUM1)

Use this field to associate a predefined rejection message with the rejection quantity recorded against this operation. Click Detail entry action from the Actions icon in the field to assign a rejection code to a rejection quantity.

  • Technical sheet (field TECCRD)

This field displays the code of the quality record or the technical sheet used for quality control.

  • End date (field OPEEND)

This field displays the operation end date.

The setup determines if the analytical dimensions can be modified. They are initialized based on the setup of the default dimension.

In creation mode, if no order line has been entered and the project code is modified, the analytical dimensions are reset based on the setup of default dimensions.

In creation mode, as in modification mode, if an order line is entered and the project code is modified, the analytical dimensions are not reset.

 

  • Non-conformance - process (field NCSPRO)

Click this check box to raise (or report) an incidence of non-conformance against this specific routing operation immediately you validate this tracking record.

Essentially this check box identifies if you are authorized to raise a non-conformance incident requesting an investigation into the 'cause' of a problem. You should report an incidence of non-conformance if you have observed or been informed of a problem, or failure or potential failure in a service, or in a process, or in the system. Typical routing operations within a manufacturing environment that could give rise to a non-conformity might be that the setup and run time are not adapted to the machine, the order of an operation must be changed, additional operations are necessary or a more stable machine must be used. The non-conformance incident forms the details of the non-conformity; it becomes the source of the information to support investigations into the root cause, or failure.

  • Non-conformance - resource (field NCSRES)

Click this check box to raise (or report) an incidence of non-conformance against this specific routing operation immediately you validate this tracking record.

This check box is displayed if you are authorized to raise a non-conformance incident requesting an investigation into the 'effect' of a problem. You should report an incidence of non-conformance if you have observed or been informed of a problem, or failure or potential failure in a resource used for the routing operation. Typical operational resources within a manufacturing environment that could give rise to a non-conformity often occur at run-time such a broken machine or a defective tool. The non-conformance incident forms the details of the non-conformity; it becomes the source of the information to support investigations into the root cause, or failure.

 If you select either of these check boxes (Non-conformance - process (field NCSPRO)/Non-conformance - resource (field NCSRES)) you are indicating that a non-conformance incident should be raised against this routing operation or the resource used for this operation. Essentially you are triggering the creation of a non-conformance incident requesting an investigation into the 'cause' or 'effect' of a problem. Whatever your role within your organization you are only required to provide minimal details for any non-conformance incident. If the Probable cause and/or Non-conformance description fields are displayed you can leave the default values or change them. You do not need to think about a possible or probable cause of the incident, or describe the details of the 'problem'.

 Timely notification of a non-conformity can be critical for compliance.

Leave the default probable or possible cause code, or select a different code. This field is mandatory.

You can support your selected value by adding your suggested reason for raising a non-conformance incident to the free-format Non-conformance probable cause field which is available from the Actions icon on each applicable line in the grid. Providing additional information is optional but it will be used to help establish what the root cause of this incident might be. This action is only displayed if the Non-conformance - process (field NCSPRO) or Non-conformance - resource (field NCSRES) field is selected.

The default code and the list of probable causes is defined in Miscellaneous table 804 - Probable cause.

  • Non-conformance description (field TITLE)

Leave this field blank or type in a short description of this incidence of non-conformance.

Whatever your role within your organization you are only required to provide minimal details for any non-conformance incident. If you leave this field blank it will be set to the default value. So that you do not need to describe the details of the 'problem' the default Non-conformance description will identify that you are raising a non-conformance against this operation. It will include references to the origin of this request and any applicable line or operation numbers. For example, if you are recording time against an operation for a work order and you click the Non-conformance - resource (field NCSRES) field to raise a non-conformance against a resource used for this operation, the default description will reflect this as 'Operation tracking – resource WOTFR0120066 15'.

If you know or understand, or have additional details about the 'problem', you can add this information to the free-format Non-conformance probable cause field which is available from the Actions icon on each applicable line in the grid.

Close

 

Action icon

Popup view

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

Technical sheet

Click Technical sheet from the Actions icon to assign or view the technical sheet linked to this operation if planned in this work order.

Work Order

Click Work order from the Actions icon to view the work order details. 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.

Operation detail

Click Operation detail from the Actions icon to view the details for this operation.

Tracking status

Click Tracking status from the Actions icon to view the current tracking status of this operation. The Operation quantities screen summarizes the planned, actual and remaining quantities and times.

Material consumption

Click Material consumption from the Actions icon to manually record the quantities of materials (components) consumed to produce the products (BOMs) on this work order.

 This action is not available if material issues are automated (as determined by the selected entry transaction).

Produced goods

Click Produced goods from the Actions icon to manually record the quantities of finished goods (BOMs) produced for this work order.

 This action is not available if stock receipts are automated (as determined by the selected entry transaction).

Text

Click Text from the Actions icon to view, enter or modify text associated with progress recorded against this tracking for this operation.

Non-conformance probable cause

Click Non-conformance probable cause from the Actions icon to clarify the probable or possible cause of this incident. The information you provide will be used to help establish what the root cause of this incident might be. You should use this field to provide a clear statement describing the problem in detail. Try to quantify your suggested value for the probable cause and maybe list several reasons why you think the selected value is correct. This will help you ensure you have thought about or described all the possible causes. Your list of reasons will assist the Non-conformance Quality assurance (QA) manager and the approvers when analyzing the problem. If you can, try to explain the potential consequences if the problem is not addressed and provide a clear request for corrective or preventive action. Ultimately, your statement, if you provide one, is critical to the Quality control team for analyzing whether the design or production model complies with the set standard and can be considered 'fit for purpose'. This action is only displayed if the Non-conformance - process (field NCSPRO) or Non-conformance - resource (field NCSRES) field is selected.

 You have selected the Non-conformance - process or Non-conformance - resource field to indicate that a non-conformance incident should be raised against this operation or the resource used for this operation. Essentially these check boxes trigger the creation of a non-conformance incident requesting an investigation into a potential 'problem', where the source of the problem is an operation in a route or a resource used for an operation in a route. Typical routing operations within a manufacturing environment that could cause a problem (a non-conformity) might be that the setup and run time are not adapted to the machine, the order of an operation must be changed, additional operations are necessary or a more stable machine must be used. Operational resources within a manufacturing environment that typically result in a problem (a non-conformity) often occur at setup and run-time. For example, a machine does not comply or is set outside the agreed tolerances, the allocated welding time of 10 seconds does not provide a strong enough join, 15 seconds is required, or a tool is defective.

 

Close

 

Specific actions

Click the Searchaction to load the grid with the operations you can record time and progress against, according to the entered selection criteria.

You can delete selected lines (click Delete from the Actions icon) and add new lines to the grid. The maximum number of lines available is defined in the selected entry transaction.

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

Selection criteria

  • Active memo (field MEMO)

You use a memo code to save the criteria applied to an entry screen. Use this field to find out if a memo code has already been saved for the current screen values.

Use the following buttons to manage memos:

Recall: Recall a previously defined and saved memo.

Memo: Save the current values of the screen in a memo file with a code to be specified.

Del. Memo: Delete a previously saved memo.

If a memo named STD (standard) is associated with the screen, it is loaded when opening the function.

Enter, select or build an Enterprise Management filter calculation expression using the formula editor.

 An error message is displayed if you refer to tables which are not generally used by the configurator, or to unknown variables.

Start - end range

  • Work order (field WMFGNUMD)

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

  • Operation (field WOPENUMD)

Filter for results within a range of operation sequence numbers. For a single operation sequence number, enter the same sequence number in the from/start Operation and to/end Operation fields.

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.

Filter for results within a range of routings. For a single route, enter the same routing code in the from/start Routing and to/end Routing fields.

Filter for results within a range of routing codes. 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).

For a single routing code, enter the same sequence number in the from/start Code and to/end Code fields.

  • Order (field WCDED)

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.

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

  • Work center (field WWSTD)

Filter for results within a range of actual work centers. For a single work center, enter the same work center code in the from/start Work center and to/end Work center fields.

Sort

  • Criteria 1 (field CRIT1)

This field gives the main sort criteria for the table of records to be processed.

  • Criteria 2 (field CRIT2)

This field gives the second sort criteria for the table of records to be processed.

Close

Click the Criteria action to access additional selection criteria. You can filter the products to be processed by order and project, and modify the sort order.

Sort criteria. Use these selection criteria to specify the sort order for the Operation tracking grid.

You can apply a selection formula to filter the results according to specific selection criteria.

You can save one or several sets of criteria using the Memoaction. You can recall these using the Recallaction or delete them using the Delete memo action.

Click the Validation action to validate or confirm the details of each line in the grid. Each line for which validation is successful will create the corresponding work order tracking record. One Work order tracking record will be created per posting date.

If the Non-conformance - process (field NCSPRO) and/or Non-conformance - resource (field NCSRES) check box is selected and the line validation was successful, a non-conformance incidence is immediately raised against the routing operation.

 You can view the details of a reported incident using the Non-conformance (GESNCSH) function. There will be one incident per selected check box, a maximum of two per validated line (operation). The Total completed quantity (field CPLQTY) for the operation is represented in the Non-conformance incident as the Original quantity and the Actual rejected quantity (field REJCPLQTY) as the NC quantity. If you used the Non-conformance probable cause action to provide a detailed description of the problem, your information is written to the Non-conformance to help the Quality assurance (QA) manager and the approvers when analyzing the problem.

If material consumption or production reporting occurs at the same time, the tracking date of the operation is applied to the corresponding stock movement transaction. The system will check that the stock movement date falls in a period in which stock updates are authorized.

The results of the tracking are written to the System log. The log file displays the number for each Non-conformance incident and work order tracking record created.

 If clicking the Validation action returns data to the grid this indicates that there might be an issue with the data or the System log is locked. You should first try to revalidate the data by clicking the Validation action again.

  • If an empty grid is returned after you click the Validation action this confirms that the data has been correctly executed.
  • If data is returned to the grid after clicking the Validation action a second time this indicates that there is an issue with the data on those lines. You must correct the data before you can continue or retry the Validation action in case some records were locked by other transactions. Any lines that have been removed have been saved because the data has been correctly executed.

Menu bar

Option / Transaction

Click the Transactionaction to view the format of this entry transaction.

Limitations

  • An incidence of non-conformance can only be raised (reported) from an operation tracking line where the Time type (field TIMTYP) is set to 'Work order'.

  • The user parameter NCSDOCCRE-Non-conformance creation mode (TC module, NCS group) is not recognized by this function. A non-conformance incident raised from an operation tracking line will be raised in 'basic' mode. The non-conformance will be raised at status 'New' with default values and details from the operation tracking line.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

The messages that arise from the manual tracking of materials or the manual production reporting are listed in the corresponding documentation (Material tracking plan, Production plan).

A material is out of stock and prevents the tracking of this WO (XXXXX)

This message is displayed when creating the tracking for a work order where a material is out of stock, the Release if shortage setup is set to 'No' in the product-site record and the MTKALLMGT general setup Mandatory allocation to the WO is set to 'Yes'.

It is only possible to track a WO with status "FIRM"

This message is displayed if the status of the work order is not set to 'Firm'.

Incomplete allocation. Tracking impossible

This message is displayed if the work order is not at a minimum allocated globally and the MKTALLMGT general setup, Mandatory allocation to the WO, is set to 'Yes'.

The WO is not printed: Tracking impossible

This message is displayed if the production folder has not been printed and this is mandatory for production to start (according to the DOSFAB general setup).

Incomplete Work Order: Tracking impossible

This message is displayed if the work order is not complete (only materials or only operations) and the WO management plans to complete this order before releasing the production.

Previous operation not tracked: operation 999

This message is displayed when an attempt is made to track an operation even though the previous operation has not been tracked. This message can be blocking or not according to the value of the CTLOPEPRE general setup. This message only concerns trackings of type "WO".

Technical sheet not entered

This message is displayed upon tracking creation (as a function of the value of general setup CTLFICTEC) and if an operation with a technical sheet has been tracked and that the technical sheet has not been entered.

Sub-contracting prohibited

This message is displayed when adding a non-planned operation of the sub-contractor type (entry of a standard sub-contractor operation or an actual work centre of the type sub-contractor).

Actual quantity greater than the planned quantity. Continue?

This warning message is displayed during the tracking of an operation if the actual quantity is greater than the planned quantity.

Rejected quantity greater than the actual quantity

This message is displayed during operation tracking if the rejected quantity is greater than the actual quantity.

Recover the standard operation data?

This message is displayed during the addition of a non-planned operation based on a standard operation.

The labor work center must not be identical to the principal work center

This message is displayed during the manual tracking of an operation if the actual labour work centre is identical to the actual principal work centre.

XXXXXX is not a labor work center

This message can be displayed following the validation control on the actual labour work centre.

The site attached to the work center must be the same as the site linked to the routing code

This message can be displayed following the validity control on the actual machine or labour work centre.

Modifying work center of a versioned routing operation

This warning is displayed if this work order uses a routing that is version-managed and you have chosen to modify an existing operation. Click Cancel to abandon your action. To modify the work center, click OK. You will not be prevented from modifying the operation if you need to.

There is an incoherence between the routing and BOM codes!

This message is displayed during the validation of the BOM code in the case of a 'Product'-type tracking.

Tracking unexpected material on a versioned product

This warning is displayed if this work order is for a product (BOM) that is version-managed and you have chosen to add a new component to it. Click Cancel to abandon your action. To add the new component, click OK. You will not be prevented from adding the component if you need to.

You have already carried out the material tracking for this operation!

Information message if a second attempt is made to manually track the materials linked to an operation.

You have already carried out the production reporting for this operation !

Information message if a second attempt is made to manually report the production of products linked to an operation.

Tracking unexpected operation on a versioned routing

This warning is displayed if this work order uses a routing that is version-managed and you have chosen to add a new operation to it. Click Cancel to abandon your action. To add the new operation, click OK. You will not be prevented from adding the operation if you need to.

Operation already present in line 999

This message is displayed if an attempt is made to add an operation that already exists on another line.

Excluded line

Work center does not exist for this site.

Operation not tracked

This message is displayed if an attempt is made to track an operation for which the tracking stage field (no, normal, range) is set to no.

Tables used

SEEREFERTTO Refer to documentation Implementation