Background: Labor Import

Use the Labor Import (LEI) program to import hours worked from an ASCII file. See Road Map for work flow.

This topic has these subtopics:

Comparison with Labor Entry (LLE)

Importing labor data can save you time. Labor Import allows you to quickly import regular and overtime hours worked by employee and manufacturing order operation sequence, pieces completed and scrapped, and vacation, sick, and holiday hours.

If you set up component picking by operation sequence, the system picks components when you import labor for a sequence. However, if you need to scrap components of a manufacturing order, you need to use Labor Entry (LLE).

Non-standard routing sequences cannot be imported; you must use LLE because it requires entry of fields that are not in the import file (i.e., operation code, work center and machine).

Why Use a Native Disc

The file you import data from can reside on your PC (or network) or on a native disc.

• Importing from a native disc is much faster since it the data does not have to be read on the PC and then transferred

• Import files residing on your PC (or network) are limited to 512-characters

Import Process

The program reads data from an ASCII file on your PC or network. You can use any program to generate the data (for example, a spreadsheet or database program) as long as it is capable of outputting an ASCII file.

The import process consists of these steps:

1. Run the Labor Import program to read the ASCII file. The program validates the file's format and displays the records read.

2. Click Import validation to validate the data in these records. If the program encounters an error, it writes the Labor Import Exception Report.

3. Select records with Error in the Validated column and correct the errors. Check your default output device for the exception report that contains the error messages.
   
   Note
   You cannot correct records with errors. You have two options: Fix the import file and re-import, or click Add and enter the data manually.
   
   After you fix all errors, click Import validation again.

4. Click Labor update to write the good records. You can display now this data with the Labor Inquiry By Manufacturing Order (MLI) or Labor Entry (LLE) programs. The imported data is included when you run the Labor Entry Register (LPR), Daily Production Report (LPD), and Weekly Production Report (LPW) programs. Clicking Labor update also updates the accumulated good and scrap, quantity remaining, and percent complete for each operation sequence, which you display with the WIP Order Inquiry (WIQ) program.

5. After the update, the Labor Import Transfer Log prints a log of labor hours imported. See Background: Labor Import Transfer Log for what prints on the log.

Machine Entries for Unattended Operations

This program supports machine entries (employee type of X) for unattended operations. If the employee type for the imported record is X and the imported work center and machine are blank, the values from the employee master are used. If the employee master also has blank values, the work center and machine from the WIPF file are used (as seen in Work Order Inquiry [WIQ]).

Labor Import Listing

The listing includes this information:

• Manufacturing branch

• Date worked

• Employee number

• Manufacturing order number

• Operation sequence number

• Labor code:
  D: Direct labor
  H: Holiday time
  I: Indirect labor
  O: Other labor
  R: Rework labor
  S: Sick time
  U: Setup labor
  V: Vacation hours

• Labor entry sequence

• Reported regular hours

• Reported overtime hours at level 1 rate

• Reported overtime hours at level 1 rate

• Validated: Good or Error

Labor Import Exception Report

Any validation errors are sent to your default output device. The report includes this information:

• Branch

• Date worked

• Employee number

• Manufacturing order number

• Operation sequence

• Labor code

• Labor entry sequence

• Error message that indicates the problem; for example: invalid employee number, invalid date, manufacturing order number not found, etc.

ASCII File Format

For a delimited file, you can use a standard delimiter (for example, a semicolon, comma, or tab). If a delimiter appears as data in an alphanumeric field, the entire field value must be enclosed in double quotation marks ("  "). If a double quotation mark appears in a field, it must itself be preceded by a double quote.

If one employee has entries for fields at the end of the file (for example, overtime hours or lunch time out and lunch time in), subsequent employee entries must either have these same fields or delimiters for these fields. For example, employee 15 has 2 hours of level 1 overtime and employee 7 has no overtime.

20221012;15;CA-100002142;1;D;8;10;0;1;STK;;;2
20221012;7;CA-100002142;2;D;8;8;1;;ASSY1;;;;

If you reverse the order, final delimiters are not required:

20221012;7;CA-100002149;2;D;8;8;1;;ASSY1
20221012;15;CA-100002149;1;D;8;8;0;8;STK;;;2

A carriage return must be placed after the last record in the file.

The ASCII file must contain these variables in this sequence:

Audit Trail

To activate an audit trail, select one of the files listed below in the Audit Trail Maintenance (XAT) program. The system records all transactions. You can then run the Audit Trails (ATR) program and select that file to print a report of these transactions.

• LS7: Labor Entry

Copyright © Qantel Technologies, Inc. 2025