Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Frank Petrasio

Consulting News: Planning for your LX Upgrade

Here are some steps that you can start NOW to plan for your LX upgrade:

To discuss your upgrade to the latest version of Infor LX, contact Frank Petrasio.

Previous Article Infor LX & BPCS Tip of the Week: Control Number, POCNO, added to CEA502B1
Next Article On Time Orders: OTTO - The Right Tools!
Print
44072 Rate this article:
5.0
Frank Petrasio

Frank PetrasioFrank Petrasio

Other posts by Frank Petrasio

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

BPCS/LX Tip of the Week: SFC600

In addition to SFC650, this ERPLX program is also used to capture and post shop floor information.

The key difference between the two is that SFC600 only captures Labor (run time) reporting, machine time, downtime and indirect time.

If you use SFC600, then all shop order material receipts and issues would be captured using INV500.

Both Inventory and Shop Floor Transaction entry is keyboard dependent, unless you incorporate an automated method like an MES solution to capture the data.

Using SFC600 to enter downtime.

You are tracking downtime and using SFC600 to enter the downtime, but you don’t know where to go to setup downtime reasons. You can set up the downtime reason codes in the INV application by selecting the reason code maintenance program INV140D1.

Once you are in the reason code maintenance program, position to the transaction effect code “D”. Using the transaction effect code “D” you can now setup as many downtime reason codes as needed. The reason code field is alpha numeric, so be creative with your reason code assignments.

FirstLast

Tips: LN | Baan

Categories