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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Porting Set Issues

Are you on the latest porting set for your version of Baan or Infor LN?

Here are some issues you might run into if you stay on an old porting set too long:

  • Incompatibility because of operating system patches
  • Printing issues because of out-of-date libraries
  • Potential performance issues if binaries are not updated
  • Updating third-party products may not be possible because of dependencies
  • Limited support from Infor
  • Issues with updating database software/patches because of dependencies (if the database is also running on the same server as the application)


To check the latest porting set available for your version of Baan or Infor LN:

  • For the last Infor LN, Infor Baan5 and Infor Baan4 porting set see KB 22923520
  • For the last BaanIVc 6.1c porting set see KB 22923521 
  • No fixes are made based on the 6.1c porting set, support continues for BaanIVc with the LN porting set, see KB 22923520
  • For the last Worktop set see KB 22881488
  • For the last BW set see KB 22881483
  • For the last EME set see KB 22866552
  • For the last Office integration set see KB 22867312
  • For the last Dynamic Form Editor see KB 22881485


Learn more about Infor LN & Baan Software & Infor LN Consulting & Baan Consulting Services.

Contact us today at: solutions@crossroadsrmc.com  | 800.762.2077

Previous Article It’s mid-January and IT’S GO TIME!
Next Article What you missed: Infor’s vision for the IBM i teams’ future alignment and focus – Register today!
Print
59515 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

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