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

1. If you use SFC600 and enter a reason code for the indirect labor, the reason you entered is written to the Labor Ticket file.
2. 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.

Certain industries require lot control, where others may find it an option based on how they want to trace the material used in a product in the event of a defect, or recall.

LX provides tight lot controls and flexibility with lot number assignments. Shop orders can have a pre-assigned lot number, or a lot number can be automatically assigned when the item is produced. You can also assign a specific lot number for the entire shop order, or for each item/quantity reported against a shop order.

In typical LN REST API integrations, permissions and authorizations are not implemented or rarely used. To ensure smooth data exchange and avoid errors, it is recommended to disable the authorization and security settings.

Recommendation:

• In the Authorization and Security Parameters session (tcsec0100m000):

  • Clear the Authorization and Security Enabled check box.

  • Clear all check boxes under Authorization Enable for on the Enabling tab.

Why This Matters:

• Enabling authorization and security without proper setup can lead to errors and blocked transactions during integration.

• For example, work center permissions may interfere with:

  • Creating new shifts

  • Booking machine hours

  • Read more