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

What is preventing you from upgrading your Infor LX or BPCS ERP System?
George Moroses

What is preventing you from upgrading your Infor LX or BPCS ERP System?


Your answer to this question is likely customizations… customizations that were once the best thing since sliced bread but now have become the bane of your existence.

There is something you can do about it! 

Crossroads RMC has many options for LX & BPCS dealing with customizations: 

  • Customizations can be written using Exit Points or the User Extension File so that custom functionality can be achieved without modifying the core of the LX application.
  • Analytics Dashboard allows for an endless variation of Infor LX or BPCS views to be created all without touching your ERP system
  • Using ION / Infor OS, customizations can be re-written to call standard Infor LX functions via APIs, libraries, and BOD messages.
  • IDF can be used to create your own custom-designed report output and display of data.
  • New functionality in the latest version of the ERP software may allow you to eliminate many of your customizations. 

It all starts with an assessment of your custom components. This is something that can be done internally by you, or with the assistance of Crossroads RMC consultants.

Why continue to live with the elephant in the room who insists on blocking the doorway to progress? Start the process today to get rid of the customizations that are preventing you from taking your ERP system to the next level. Contact us today to learn more: 800.762.2077, solutions@crossroadsrmc.com, or request a phone consultation.

Previous Article What is preventing you from upgrading your Infor LN or Baan ERP System?
Next Article What is preventing you from upgrading your Infor M3 ERP System?
Print
39614 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

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