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

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Audit Fields by Table (ttaud3125m000)

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.

Previous Article Infor LN & Baan Tips & Tricks for OPERATIONS: Sales Contract Linked Documents (tdsls3506m000)
Next Article CASE STUDY: Navigating an ERP Upgrade with Outdated Knowledge
Print
10742 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

Industry Insight: Why ERP Data Stays Siloed, and What to Do About It

Most manufacturers don't have a data problem. They have a connection problem.

Production data lives in one system. Sales and customer data lives in another. Finance runs somewhere else entirely. Each system does its job well on its own, but without a way to connect them, the organization never gets the full picture, and neither do the people trying to run the business.

Why This Happens
ERP systems are often the core of a manufacturer's operations, but they rarely operate alone. Over time, businesses add third-party software for CRM, e-commerce, warehouse management, EDI, and more. Each addition solves an immediate need, but without integration, it also creates another silo.

The result is familiar across manufacturing: teams end up manually re-entering data between systems, waiting on reports that should be immediate, and making decisions without visibility into what's happening elsewhere in the business.

Integration vs. Enhancement
There are two ways to close this gap, and they solve different problems:

  1. ERP Integration connects your ERP to the third-party software you use every day, creating a single source of data instead of several disconnected ones. Whether it's a one-way, two-way, or complex systems integration, the goal is the same: eliminate errors, reduce manual entry, and give everyone access to the same real-time information.
  2. ERP Enhancement goes a step further, creating new functionality or modifying existing functionality within the ERP itself, so the system matches how your business actually operates rather than forcing your business to adapt to the system's limitations. Done right, enhancements use parameter-co

Categories