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: LN Report Archive

LN Report Archive Solution Overview

The LN Report Archive solution allows you to archive printed reports for long-term access and reprinting, even years after their original print date.

This is especially valuable for external documents such as invoices, purchase orders, and other reports sent to customers or suppliers. In some countries, the ability to reprint these documents for up to 10 years is a legal requirement.

Key Features:

  • Report Archiving:
    Define which reports should be archived. Once printed, they are automatically saved to a designated archive folder.

  • Reprinting Capability:
    Access and reprint archived reports whenever needed.

  • Archive Management:
    Easily maintain the archive by moving reports to another folder or transferring them to a CD-R(W) or DVD.


Note: Reports printed using Business Objects are archived like other reports, but cannot be reprinted on a Business Objects device.

Previous Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Next Article Infor LN & Baan Tips & Tricks for OPERATIONS: Revisions and approval
Print
3134 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