This function allows you to post labor activities (labor validation), which creates the production tracking record. 

The Labor validation process:

  • Uses core labor posting routines to create work order tracking records.
  • Updates the Shop floor tracking transaction (SFTTXN) entries as posted and moves them to the Shop floor tracking transaction history (SFTTXNH). 
  • Can be run interactively or as a scheduled batch request.

Before posting activities, you need to complete the following steps:

  1. Create Shop floor transaction records. This can be done through the Shop floor tracking (SFT) workbench or manually using the Employee activity function (FUNSFTEAC).
  2. Review the activity record and modify as needed using the Employee activity function (FUNSFTEAC).

Criteria

You can filter activities to post using a variety of criteria including:

Team and/or Employee - Filter by team, employee, or both. (See field help for details).

Entry transaction – Entry must be a valid transaction code that is setup to support time tracking via the Time tracking plan function (GESMOL).

Site – Optional. If specified it must be a valid production site.

Define ranges – employee, shift dates, work centers, work orders, and operation.

Activity – Clock in/out, Indirect reference, Setup, and Run.

Log file

Validating labor activities generates a log file that contains details about processed records and tracking activity. It includes successful and failed activity postings.

The log file contains the following information:

  • Work order number
  • Setup time completed
  • Run time completed
  • Completed qty.
  • Rejected qty.
  • Tracking number
  • Error message (when applicable)

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Criteria

The fields below allow you to filter activities to post.

Batch task

This function can be run in batch mode. The standard task FUNSFTVAL is provided for that purpose.

Error messages

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

Record skipped due to break or exclusive indirect.

Tables used

SEEREFERTTO Refer to documentation Implementation