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: What Data Can Be Archived or Deleted?

From time to time, your employees need access to information related to logistical and financial transactions that have occurred in the past. Before you archive or delete this information, you must understand the need for this information. Baan and LN contain standard archiving sessions in the major modules that tend to have a high volume of historical transactions. These sessions are designed to copy historical data to the archive company, and then delete the data from the operational company.

You have three options in archiving sessions:

  1. Archiving and deleting: Data is transferred to the archive company and then deleted in the operational company.
  2. Deleting: Data is deleted in the operational company, but not archived.
  3. Archiving: Data is transferred to the archive company, but not deleted in the operational company.

Using option 1 or 2 makes archiving irreversible. If you archive only, option 3, because you want to preview the results, the archiving can be done a number of times. Usually, in archiving sessions, you can also specify:

  • The date up to which the data must be archived.
  • If texts must also be archived.
  • If texts that already exist in the archive company must be replaced.
     

Want more detail about archiving?

Previous Article Infor LX & BPCS Tip: Can’t Select Orders for Pick Release or Pick Confirm?
Next Article Staff Augmentation: Knowledgeable ERP Staff Quickly
Print
51555 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Last

Tips: LN | Baan

Categories