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

George Moroses

DON'T MISS - 8 Ways to Modernize your IBM i Product– Topic #3 of 8: Best practices in integration for the office of finance (Part 2)

Thursday, May 30, 2024 - 10am EST | 9am CST | Duration: 30 minutes

Get ahead of the curve with a seamless, comprehensive integration strategy that surpasses other competitive solutions. In part two of this webinar, join our discussion of best practice integration tricks and solutions from a fellow customer’s office of finance. Understand what makes their integration approach effective and review best practices in integrating your IBM i solution to other office of finance solutions (F9/EPM/Birst/GRC).

Hosted by Peg Tuttle from the IBM i podcast, “The Incredible i Show”. 

  • How version upgrades have tightened internal control loopholes.
  • Structural IBM i advancements designed to safeguard your organization.
  • IBM i ecosystem solutions that strengthen both data and access vulnerabilities.

Don't miss this fourth fireside chat, Eight Ways to Modernize your IBM i product – Topic #3 of 8: Best practices in integration for the office of finance (Part 2). Register today!

Register today!

Previous Article Customer Appreciation Day Giveaway
Next Article inPower 2024 - Join Gold Sponsor Crossroads RMC
Print
17052 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