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: Why was the session "General Ledger Diagnostics Workbench" built?

Any problem noticed and solved before the period closing will reduce the time and pressure during the actual period close itself. So, the General Ledger Administrator can be assisted in his/her daily tasks by viewing and addressing any issues via the "General Ledger Diagnostics Workbench" (tfgld1590m000) session.

The general ledger administrator needs to complete the following tasks during a given fiscal period:

  • Notice, print, and solve erroneous batches that cannot be finalized
  • Notice and solve integration mapping and posting errors
  • Change GL master data for solving posting errors
  • Make sure external (wages, intergroup) and automatic (recurring) documents are posted into the General Ledger
  • Perform technical utility sessions to correct data (e.g. rebuild history, reverse entry) or reset certain statuses (e.g. batch status).
Previous Article Infor LX & BPCS Tip: How to handle “ZERO COST” items
Next Article Are you ready to maximize the benefits of Infor ERP System?
Print
61057 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