Time tracking plan
Use this function to customize the Time tracking plan (FUNBENCHO) function to the needs of your organization and your processes.
Your system is provided with a standard or master Time tracking plan entry format. You can modify the master or create new entry definitions to suit your processes, your users or just to make your system more convenient to use. Each entry definition affects the way in which information is entered, and what information is displayed and printed.
You create each entry definition as a 'Transaction'. Each transaction you define is available for selection when the Time tracking plan function is loaded, either from the menu or from an action in a linked function. The default entry screen will be displayed and a choice will not be offered if you do not define additional transactions to the standard or master Time tracking plan entry format.
Prerequisites
Refer to documentation Implementation
Screen management
The Time tracking plan Entry transactions function contains a Home section and one section per feature of the functionality:
- Home section. The Home section contains the code and name for this entry transaction, and the user access code.
- Parameters. Use this section to describe the functional characteristics of this entry transaction.
- Input. Use this section to control entry of selected fields, and to provide default entry fields and values.
- Filters/sort. Use this section to provide default filters (selections) and sort orders.
- Display. Use this section to define the entry and display fields, and the layout.
- Analytical. Use this section to define the default analytical dimensions applicable to this entry transaction.
Header
The Home section provides key tracking and access information. You can pin this section so that it does not scroll off the page.
Each transaction code you define is available for selection when the Time tracking plan function is loaded, either from the menu or an action that accesses the Time tracking plan function.
Time tracking plan
Transaction (field BTSNUM) |
Use this field to assign a code to this entry transaction. |
field DESAXX |
Use this field to identify this transaction. |
Active (field ENAFLG) |
Use this check box to activate (field Active=selected) or deactivate (field Active=clear) this record. Inactive records are not available for selection. |
Access code (field ACSCOD) |
This access code is used to restrict access to data by user or group of users. |
Group (field GFY) |
Use this field to restrict access to this transaction to a specific site/company group. |
Tab Parameters
You use this section to define functional characteristics for this entry transaction. This includes the following information:
- The types of tracking to be available to the user – the recording of time against operations for work orders, against operation activity (routing tracking) without a work order and against work centers (work center tracking);
- Whether operation tracking is linked to material consumption;
- Whether operation tracking is linked to the associated production reporting.
Tracking type
Block number 2
Mobile Automation
Unplanned operations (field UNPOPE) |
Materials
Manufacturing
Non-conformance
Non-conformance - process (field NCSPRO) |
Use this field to identify, for this entry transaction, if a non-conformance can be raised against an operational process in a routing. An operational process in this context is defined as a specific numbered operation in a routing, or an operation in a routing specifically related to a previous operation, that is the operation has a successor. This check box is only displayed if the NCS-Non-conformance activity code is active. Note:
Before setting the value of this check box you are advised to consider the role of users that have access to this entry transaction. Essentially this check box identifies if the user of this entry transaction can raise a non-conformance incident requesting an investigation into a potential 'problem', where the source of the problem is 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. Employees with the experience to raise a non-conformity against a perceived fault in an operational process are typically, therefore, the more senior or skilled workers such as a foreman, shop floor manager and design engineer. In many organizations, an employee might not have the skills to determine a non-conformity for a process but they might have the skills to determine a non-conformity on a resource such as reporting a broken machine or a defective tool. If this entry transaction applies to that group or those types of employees you should consider setting the Non-conformance - resource flag (field NCSRES) instead. Note:
If you click this check box you must add the Non-conformance fields to the list of fields displayed in the Time tracking plan (FUNBENCHO) function. Note:
This field is only available if this entry transaction can be used for recording time against an operation for a work order (the WO tracking |
Non-conformance - resource (field NCSRES) |
Use this field to identify, for this entry transaction, if a non-conformance can be raised against a resource used for a routing operation. A resource in this context is defined as a single machine (a work center), or a work center group, or a labor resource, or both a machine and a labor resource. This check box is only displayed if the NCS-Non-conformance activity code is active. Note:
Note:
If you click this check box you must add the Non-conformance fields to the list of fields displayed in the Time tracking plan (FUNBENCHO) function. Note:
This field is only available if this entry transaction can be used for recording time against an operation for a work order (the WO tracking |
Tab Input
You use this section to provide default entry fields and values.
- The Stock receipt fields are available for entry if operation tracking is linked to production reporting automatically (as defined on the Parameters tab).
- The Stock issue fields are available for entry if operation tracking is linked to material consumption automatically (as defined on the Parameters tab).
Input
Stock receipt
Transaction group (field TRSFAM) |
Movement group, initialized by the movement group of the transaction being used. Statistical information used in the stock transactions associated with the shipment. This value is fixed if the original document does not reference a movement group. Otherwise, the movement group of the document at the origin of the quality control is suggested in priority. |
Auto journal code (field ENTCOD) |
This field is used for this transaction to specify the code of the accounting automatic journal used to generate, via the stock accounting interface, the accounting entries with respect to the stock movements created with this transaction. |
Movement code (field TRSCOD) |
A stock transaction code is used to specify rules within a similar transaction type. Note:
These codes must be created in the miscellaneous table number 14. The movement code is used to define specific stock receipt and issue rules for some transactions. For example, a dedicated transaction associated with experienced users can authorize the receipt to stock of goods in A status while the other users may be associated with a transaction authorizing the receipt to stock of goods in Q status. |
Print labels (field PRNCOD) |
Use this field to specify if stock label printing is authorized for this entry transaction. Stock label printing is launched automatically upon completion of the tracking record if you authorize stock label printing. |
No. prints (field PRNNBRFLG) |
Parameter used to define, for this entry transaction, if the number of documents to be printed can be entered or not. |
Stock issue
Transaction group (field TRSFAMS) |
Movement group, initialized by the movement group of the transaction being used. Statistical information used in the stock transactions associated with the shipment. This value is fixed if the original document does not reference a movement group. Otherwise, the movement group of the document at the origin of the quality control is suggested in priority. |
Auto journal code (field ENTCODS) |
This field is used for this transaction to specify the code of the accounting automatic journal used to generate, via the stock accounting interface, the accounting entries with respect to the stock movements created with this transaction. |
Movement code (field TRSCODS) |
A stock transaction code is used to specify rules within a similar transaction type. Note:
These codes must be created in the miscellaneous table number 14. The movement code is used to define specific stock receipt and issue rules for some transactions. For example, a dedicated transaction associated with experienced users can authorize the receipt to stock of goods in A status while the other users may be associated with a transaction authorizing the receipt to stock of goods in Q status. |
Tab Filters/sort
You use this section to provide default filters (selections) and sort orders.
Filter
Default value (field FILTDEF) |
Use this field to set, for this entry transaction, the default value for the Filter field (field FILTOPE). |
Filter (field FILTFLG) |
Use this field to define, for this entry transaction, if the Filter field (field FILTOPE) should be:
|
Sort
Tab Display
You use this section to define which fields to display and the order in which they are to be displayed.
Block number 1
Preload completed (field CPLUPDFLG) |
Preload of times/quantities carried out. |
Block number 2
Grid List of fields
Field (field INTIT) |
This column lists the fields that are available for display. Note:
The Operation field is mandatory. You cannot clear the Input value for this field however you can reposition it in the order of display. Note:
The Non-conformance - process field is mandatory if you have clicked the Non-conformance - process (field NCSPRO) check box in the Non-conformance block (Parameters section); the Non-conformance - resource field is mandatory if you have clicked the Non-conformance - resource (field NCSRES) check box. Note:
Displaying the Non-conformance description field and/or the Probable cause field in the Time tracking plan (FUNBENCHO) function is optional. Whatever the role of users that have access to this entry transaction, the Time tracking plan functionality only requires the user to provide a quick non-conformance incident with minimal details. If you choose not to display these fields the user does not need think about a possible or probable cause of the incident and they are not expected to describe the details of the 'problem'. The default Non-conformance description will identify that they are raising a non-conformance against the operation. It will include references to the origin of the request and any applicable line or operation numbers. For example, if whilst recording time against an operation for a work order they raise a non-conformance against a resource used for an operation, the default description will reflect this as 'Operation tracking – resource WOTFR0120066 15'. They can leave the default Non-conformance description and Probable cause |
Input (field DAC) |
Use this column to define which fields are to be displayed and the order in which those fields are displayed. Note:
|
Include/Exclude |
Click Include/Exclude from the Actions icon to select (include) or clear (exclude) this field. Note:
A newly included field is positioned last. Check the Order |
Classification |
Click Classification from the Actions icon to sort the fields into ascending order. |
Renumber |
Click Renumber from the Actions icon to sort the fields into ascending order and renumber them in increments of 5. |
Tab Analytical
You use this section to define the default analytical dimensions applicable to this entry transaction.
Block number 1
Entry
field CCESCR |
Grid Dimension line
Dimension type (field DIE) |
You can enter an analytical dimension type code on each table line. |
Method (field CCECOD) |
Parameter used to define, for this entry transaction, if the analytical dimension must be:
|
Preload dimensions |
Click Preload dimensions from the Actions menu to load all dimension types defined for a given group of sites or companies. |
Menu Bar
Copy
Click the Copy action to copy this entry transaction to a different folder. Block number 1
Block number 2
|