For either file, you must specify a valid location code as defined in the Location Master File.

If the machine master locations are blank, then the work center locations are used. There are cases where you may want to do a combination between the two in defining the locations.

Let’s say the end item has one operation. The operation is at work center 510 and Machine A is in the work center. You have locations setup in both the Work center file and the Machine master File. You report 100 complete at the work center without specifying the machine.

In this case, the inventory will be processed based on the locations defined in the work center file. If the transaction included the machine number, then the locations in the machine file would be used.

In Infor LX, there are two ways to enter indirect labor. You can use either SFC600 or SFC650.

• If you use SFC600 and enter a reason code for the indirect labor, the reason you entered is written to the Labor Ticket file.
• If you use SFC650 and enter a reason code for the indirect, the reason code is not written to the labor Ticket file.

In either case, the reason code is not validated from the transaction file because there is no indirect transaction code. The indirect code that can be setup is machine downtime. If you need to validate and track indirect by reason and validate the reason code, then you may want to explore an MES solution that works with Infor LX.

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

• Bank Statement Workbench (tfcmg5610m100)
• Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

OPERATIONS: Update, Cancel or Remove Outbound Order Lines

FINANCE: Currency Differences Accounts

TECHNOLOGY: Advantages of Data Replication