Logon/Logoff rules

Administration > System Initialization > Configuration Wizard > Production > FDC > Logon/Logoff rules

Top  Previous  Next
Expand/Collapse Toggles

PATH: Administration > System Initialization > Configuration wizard > Production > FDC.

 

Parameter

Description

Work order must be set to planned

Logon via pool report or terminal logon only if production has been set to planned.

Operation may not be closed

Per default a time receipt on completed work sequences is blocked. If you deactivate this option, it has the following effects: Work Orders - Expand, right mouse-click on a work sequence (green line): Selection "Time Receipt" also is displayed if the work sequence is completed.

Production Time Administration - new Message: No Time Receipt but a blocking message appears at selection of a completed work sequence.

Time receipt through "new receipt > barcode"or by Production Time Administration – Quick Input: The Input is possible without a further error message. Through Logon/Logoff Open Work Order: It is generally not possible to register completed work  sequences.

Material Inventory Test at Login

Info: If the inventory is insufficient, a message is displayed.
Required: If the inventory is insufficient, the operation cannot be logged on.

No (default): No inventory check is performed.

For setup reporting, no inventory check is normally performed.

Time receipt only during presence

Enabled: It is only possible to log on and off when attendant (does not apply for activity tracking). As long as work orders are logged on, the employee cannot leave.

See App "Leaving"
Variable: bde_nur_anwesend, Default=N

Attendance logoff: automatic logoff Work order

After attendance logoff from terminal, all work orders of the current user will automatically logged off as well.

Previous op.sequ. must be completed

Note:

Only the preceding reportable operation is checked

Affected: App "Logon order" and all extensions using this logon-object.

Not affected: function "Report time receipt"

Previous routing position with quantity confirmation

Enabled: Logon is only possible if a quantity was reported in the preceding routing position.        

Previous QC must be OK

If the previous reportable position has a QC plan, the following is checked:

1. Does the inspection plan exist for this position?

2. Are all samples okay?

If the answer to both is not Yes, you cannot log on to the subsequent position.

See

Configuration wizard – QC-create new

Quality control Concept

Routing

Confirm at least previous quantity

The rule takes effect only from the second operation sequence.

 

Example 1: Operation sequence 1: reported 10 yield, 5 scrap.

Confirmation on the second operation with option enabled.

Report 5 yield-> blocked. At least 10 need to be confirmed.

Report 5 yield,  5 scrap -> : OK, minimum quantity of 10 is reached.

 

Example 2: Operation sequence 1: report 5 yield, 0 scrap.

operation sequence 2: report yield 4, 1 scrap -> OK.

operation sequence 1: another 3 reported, 0 scrap.

Confirmation on the second operation with option enabled:

 

Minimum quantity according to operation sequence: 8.

Already posted to 2.nd operation: 5 (4 yield, 1 scrap).

Minimum quantity for the next posting to the operation sequence 2 : 3 pieces.

 

It makes sense to combine this option with "maximum previous quantity reportable".

Confirm at most previous quantity

If nothing has yet been reported in the previous position or if the corresponding quantity was already reported in this position, the yield quantity input field is blocked.

This check does not refer to the first confirm able operation sequence, but only to the subsequent one. It determines, whether not more than the quantity of previous operation sequence may be confirmed.
Yield and scrap quantity is taken into account.
Example:
Operation sequence 1:  confirmed 10 yield, 3 scrap.
Operation sequence 2: confirmed 5 yield, 3 scrap.

For operation sequence 2 only 2 remaining pieces may be confirmed.

 

Affected: work order time registration and external operation - collective purchase.

Note: If the maximum quantity is exceeded, an error message is issued: "(maxqty0243) Maximum purchase quantity exceeded! (Max. quantity due to time receipt of preceding operation)"

Max. planned quantity reportable

This refers only to the first confirm able operation and determines whether as maximum only the planned quantity may be produced. Scrap is not taken into account.

Example: planned operation sequence of 10 pieces.
1st confirmation:  8 yield, 2 scrap.

2nd confirmation: only 2 additional pieces are permitted.

 
This check is only performed when creating a new order-related time receipt, not when changing an existing receipt. It takes place at the moment the time receipt is saved.

 

Important: The rules only apply to time reports, not to purchase orders on external operations.


Help URL: https://help.beascloud.com/beas202102/index.html?anmelderegeln2.htm