Manufacturing >  Production tracking >  Time tracking plan  

Display all Hide all

The objective of this function is to collect the production times and the actual quantities for a given operator.

Unlike the WO tracking function, different types of times can be tracked via an operation workbench: production times spent on an operation for a released work order, production time spent on a routing operation without WO, miscellaneous times.

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 what 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

Header information

This section is used to enter the different criteria designed to be used to select all the operations that should be tracked:

Production site: the site for which the tracking is carried out, this field is initialized with the production site associated with the operator.

 Personnel ID number: this is the personnel ID number of the operator who enters their times (or for whom the time passed is entered): according to the setup of the transaction, the entry of this personnel ID number is mandatory, optional or forbidden). The personnel ID number entered in the header loads by default the personnel ID number of each line of the operation workbench.

 End date range: this is used to select the WO operations where the planned end date falls within the range of the dates entered.

 Filter: this is used to select the operations to be tracked depending on their closure flag (closed, not closed, all). According to the transaction setup, the filter is pre-loaded by default and can be entered, displayed or invisible.

 Global time: If a global time is entered here, it will be broken down over the different operations of the selection pro rata with the planned times.

 WO number ranges: used to set a filter on the work orders to be processed in the operation workbench. This filter is only accessible if the tracking type "WO" is planned by the transaction.

 Operation number range : this is used to set a filter on the WO operations to be processed.

 Routing/Routing code range: If the user wishes to work without WO and the transaction setup allows it, these fields are used to filter the routings to be processed. In the case where a range of WOs have already been entered in the selection criteria, it is not possible to carryout a selection based on the routes.

 Work center: These fields are used to filter the operations (WO or routing) to be processed as a function of their principal work center.

The information shown above makes up the principal selection criteria available to the operator.

Operation grid

This grid is loaded with routing operations or work order operations, according to the selection criteria entered.

All the columns displayed in this grid and their display order depend on the setup of the chosen transaction.

The columns available are a function of the tracking type that it is possible to use with this transaction.

The pre-loading of the production time and actual quantity fields with the planned times and quantities depends on the setup of the chosen transaction.

"WO" tracking

A WO to be tracked operation can come from the selection criteria or added manually in the grid. The corresponding tracking type is the "WO" tracking.

It is possible to modify the actual work center and the actual labor work center.

According to the transaction setup, it is possible to choose, or not to choose, the tracking unit (amongst which the stock unit for the released product and the operation unit).

The information that can be entered for an operation is as follows:

   The posting date: by default the current date is proposed, also it is possible to enter an earlier date than the current date but not a later date.

   The actual principal work center and the secondary labor work center

   Completed quantity: it is the total quantity completed for the operation, it includes the rejected quantity or the quantity under control coming from the operation. In order to minimize the entry and if the transaction setup allows it, the completed quantity field for each operation is loaded by default with the remaining quantity for the WO and by default the operation closure is proposed.

   The rejected quantity

   The actual setting time and actual operation time

   The ID number (as a function of the transaction setup)

   The messages: it is possible to assign a message to an operation tracking, the creation of new messages during the tracking is also possible.

  The scrap messages : if a reject quantity is entered on the operation line, it is possible to associate the entry with up to 15 different reject messages, each associated with a part of the total rejected quantity.

Finally, it is possible to add a non-planned WO operation booking by simple entry of the operation in the grid: the system detects that the operation entered is not planned in the referenced WO and a warning message is displayed for user confirmation.

If a tracking range operation is present in the grid, the operations tracked by this range will not be displayed in the grid: their actual quantities and times are automatically adjusted according to the range tracking.

"Product" tracking

According to the setup chosen for the time tracking plan transaction, it is also possible to enter the time on the basis of a route without WO.

A routing to be tracked operation can come from the selection criteria or be added manually in the grid. This type of tracking corresponds to the "Product" tracking.

The line is then re-loaded with the information coming from the routing operation.

It is possible to associate a BOM and BOM alternative to each operation in the route for which a tracking entry will be made. The system then checks that the routing being tracked is actually a parent routing associated with the selected BOM.

It is possible to add the tracking of a non-planned routing operation by simple entry in the grid of this operation: the system detects that the operation entered is not planned in the referenced routing and warns the user for confirmation.

"Miscellaneous" tracking

According to the setup chosen for the operation workbench transaction, it is also possible to enter the production times on the basis of the work centers without either WO or routing.

Such a tracking line is of type "Miscellaneous tracking" and is used to total in a specific work center all the non-productive times of the same nature, for instance.

Automatic material consumption /Automatic production reporting

According to the setup chosen for the operation workbench transaction, it is possible to plan the material consumptions and the stock receipts of finished products automatically and without user intervention.

Only the materials attached (in the BOM) to the tracked operation are consumed.

The materials not attached to any operation are consumed at the time of tracking of the productive operation.

The receipt into stock is performed at the time of the productive operation tracking.

Manual production reporting

According to the setup chosen for the operation workbench transaction, it is possible to access a manual production reporting.

In this case, the Produced goods action is available on the productive operations. This action provides access to a preloaded production workbench (for which the transaction is then chosen) of the product/products (in the case of a multi-product release or sub-product management) to be received to stock. The receipt to stock is then carried out according to the setup planned by the production workbench that has been activated (see the Production workbench documentation).

After validation of the entries in the Production Workbench, the tracking(s) corresponding to the stock receipt is/are created.

Exiting the production workbench automatically returns the user to the operation workbench as it was before unbranching.

Validating the operation workbench entries creates the corresponding tracking(s), the manual entries already carried out are no longer relevant.

Manual material consumption

According to the setup chosen for the operation workbench, it is possible to access a manual material consumption.

In this case, the Material consumption action is available on those operations to which materials are attached. This action gives access to a pre-loaded operation workbench (for which the transaction is then chosen) with the materials to be issued from stock. The material issues then take place according to the setup of the selected consumption workbench (see the Material Issue Workbench documentation).

Exiting the material issue workbench automatically returns the user to the operation workbench such as it was before debranching.

Validating the operation workbench entries creates the corresponding tracking(s), the manual entries already carried out are no longer relevant.

Close

 

Fields

The following fields are present on this tab :

Filters

The production site associated with the user is proposed by default. It can be modified by another site authorized for the operator, depending on its authorizations.
  • Employee ID (field WEMPNUM)

This field corresponds to the Labor operator.
  • field EMPDES

 
  • End date (field ENDDATSTR)

This field makes it possible to filter the data to be processed.
It is only taken into account when pre-loading a WO.
Mind the loading time.
  • field ENDDATEND

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

Entering these fields is not mandatory. Use them to limit the display of allocations to one document or a range of documents.
  • field WMFGNUMF

Enter the selection end entry number.
  • Operation (field WOPENUMD)

Enter the selection start operation number.
  • field WOPENUMF

Enter the selection end operation number.

Enter the selection start product number. The product ranges limit the adjustment to these products only.

Enter the selection end product number.

Enter the selection start routing.

Enter the selection end routing.

Enter the start selection routing code.

Enter the end selection routing code.
  • Work center (field WWSTD)

Enter the name of the initial work center of the selection.

  • field WWSTF

Enter the name of the final work center of the selection.

Block number 2

  • Global time booked (field CPLTIMGLO)

If a global time is entered here, it will be broken down over the different operations of the selection pro rata with the planned times.
  • field CPLUOMCOD

The time unit makes it possible to express the time in hours and minutes.
  • Warehouse (field WRHE)

 

Grid

  • Date (field IPTDAT)

This is the date which is used when posting the movement. It defaults to today's date but can be changed to an earlier date, if the selected date is in an open period in the accounting calendar.

SEEINFO You cannot enter a date later than today's date.
  • Time type (field TIMTYP)

This field can take the following values:

  • WO: the declared time concerns a WO operation,
  • product: the declared time concerns a routing operation,
  • miscellaneous: the declared time concerns time on a work center.
 
 
  • Order no. (field MFGNUM)

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

The routing is used to describe the product manufacturing process.
The routing identifier is a product reference which can be the reference of a manufactured product, or a generic reference (mother routing) linked to several 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 field contains the BOM (Bill of Materials) code for the product.

    Several BOMs can be defined for the same product reference.
    They can be distinguished via the code, entered on two numbers.

    The various BOM codes can be used to manage different product structures according to their use context such as:

    • MRP calculation,
    • Sales order entry
    • Manufacturing/production

    This field can be left empty (value = 0) to enable manual entry of the components. In this case, only the component is loaded.
    • Operation (field OPENUM)

    The production routing is described by means of operation numbers.
    Each operation corresponds to a task carried out on a given resource, with given times.
    • Ope description (field ROODES)

    This field indicates the routing 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.
    • Actual work center (field CPLWST)

    This field indicates the actual work center.
    The work center is attached to a work center group. It corresponds to a production resource on which a routing operation has been carried out.  
     
    • Actual labor W/C (field CPLLAB)

    A labor work center can be associated with the machine-type principal work center.

    The labor work center times are calculated using two coefficients:
    • 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).

    The operation unit expresses the operating time in another unit than that of the product described by the routing.

    Example :


    A product managed by unit can be subject to three operations, without any intermediate stock. It is not necessary to create semi-finished products for each production phase:

    • Mixing: time is expressed for a lot with the kilogram as the unit,
    • Extrusion: time is a rate in meters per hour,
    • Cutting: time is expressed in hours per unit.

    This unit is associated with a conversion coefficient for the stock unit of the product for which the routing has been set up and the operation unit.

    The quantities of the work order operations are expressed in the operation unit.
    • U-OPE conversion (field OPEWORCOE)

     

     
    • Total completed qty. (field CPLQTY)

    This field displays the total completed quantity, including the rejected quantity, expressed in the operation unit.
    • Actual rejected qty. (field REJCPLQTY)

    This field displays the actual rejected quantity.

    The sum of the "quantity produced under quality control" plus the "rejected quantity" cannot exceed the Total completed 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 of all operations in the routing.
    • Actual stp. time (field CPLSETTIM)

    This is the actual setting time.
    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.
    • Actual unit time (field CPLUNTTIM)

     
    • Actual run time (field CPLOPETIM)

    This is the actual operation time.
    It is possible via a contextual button to enter start and end times.
    In that case, the system automatically calculates the actual operation time.

    The operating time:

    • in hours or minutes (see the 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 based on the operating time type.
      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 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)

    This field corresponds to the Labor operator.
    • Message (field MSGNUM)

    This field displays the information message linked to the operation tracking.
    It belongs to the TABMSG table.
    It is possible to enter an information message, whether the time unit is entered or not.
    • Reject (field SCANUM1)

    It is the information message concerning the rejected quantity.
    It belongs to the TABSCA table of the scrap messages.
    • Technical sheet (field TECCRD)

     
    • End date (field OPEEND)

     

    The setup determines whether the analytical dimensions can be modified. These are initialized in compliance with the default dimension setup.

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

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

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

    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.

    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 view the material consumption for this work order.

    Produced goods

    Click Produced goods from the Actions icon to view the production details including the material consumption for this work order.

    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.

     

    Close

     

    Specific actions

    Click the Search action to load the grid with the operations to be tracked 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.

    This button is used to refine the selection by filtering the operations to be processed by Order and / or Project, to modify the sort criteria planned by default by the transaction and to save a set of selection criteria by saving one or more Memo codes.

    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 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 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 Transaction action to view or amend the format of this entry transaction.

    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