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
60772 Rate this article:
5.0

Contact

Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories