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 FINANCE: Rebuild History for Account Matching (tfgld1218m000)

Use this session to rebuild the ledger account history for account matching. This is particularly useful if you’ve recently defined a ledger account, on which transactions already exist, as a matchable account.

You can specify the fiscal year and period for which you want to rebuild the account matching history.

Note: This session can also be used to remove unmatched transactions if you decide to stop performing account matching for a specific ledger account.

Field Information

Selection Range

  • Use Job Reference Date
    If selected, Infor LN uses the Job Reference Date as the basis for rebuilding history data.

  • Job Reference Date
    Specifies the date and time used for the rebuild process.
    Enabled only if "Use Job Reference Date" is selected.

  • Financial Company
    The financial company for which you want to rebuild a ledger account history.

  • Ledger Account
    The specific ledger account to rebuild.

  • Fiscal Year
    The fiscal year for which you want to rebuild the ledger account matching history.


     

Previous Article Infor LX/BPCS Tips for EXECUTIVES
Next Article Infor LN & Baan Tips & Tricks for OPERATIONS: Copy Customized Product Structure to Standard Structure (tipcs2232m000)
Print
3616 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