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: Determining What Data to Archive or Delete

Ensuring access to historical logistical and financial transaction information for your employees is crucial. However, before proceeding with archiving or deletion, it's essential to evaluate the necessity of retaining this data. Baan and Infor LN (ERP LN) offer standard archiving sessions within major modules that typically handle a significant volume of historical transactions. These sessions are designed to transfer historical data to an archive company before deleting it from the operational company.

When it comes to archiving sessions, you have three primary options:

  1. Archiving and Deleting: Data is transferred to the archive company and then deleted from the operational company.
  2. Deleting: Data is directly removed from the operational company without archiving.
  3. Archiving Only: Data is moved to the archive company without deletion from the operational company.

It's important to note that options 1 and 2 result in irreversible actions. However, with option 3, where Archiving Only is selected, multiple archiving processes can be executed for previewing results.

Additionally, during archiving sessions, you can typically specify:

  • The cutoff date for the data to be archived.
  • Whether accompanying texts should also be archived.
  • Whether existing texts in the archive company should be replaced.

For more detailed information on archiving procedures, you can refer to the Baan IV and Infor LN documents provided.

Previous Article Infor LX & BPCS Tip: MPS Planned vs. MRP Planned
Next Article Infor LN & Baan: Customizing Shipping Labels for All Customers
Print
30656 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

When to use a user defined inventory transaction

ERP LX (BPCS) provides you with the flexibility to create inventory transactions without program modifications. The typical transaction types are defined with effects set on how the transaction will impact inventory balances.

Perhaps you want to process a customer return and don’t want to the inventory to be impacted. You can create a user define transaction effect to allow the customer receipt and not update the inventory balance.

The shop order release date is the date that the shop order is scheduled to be released for production.

If you want to use the backward schedule method, make sure the release date is blank and the due date is maintained.

If you maintain the quantity on the shop order and the due date is prior to the system date, the due date and the release date are the same.

FirstLast

Tips: LN | Baan

Categories