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
30539 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

Define Inventory transactions for issuing components to the shop and receiving finished items. See the Inventory help text for examples of transactions.

  • Transaction type I - Single Issue to Shop Order. Use this transaction type to issue one component at a time. Use this for high-value items that are marked as Must Single Issue on the Item Master file.
  • Transaction type M - Multiple Issue to Shop Order. Use this transaction type to issue all the components as listed in the Shop Order, in one transaction. Note that this transaction type does not issue Must Single Issue items.
  • Transaction type S - Receipt from shop. Use this transaction type to receive the finished item into stock and update the shop order accordingly. 

The Shop Order Lot/Location Allocation program is an alternative to using the above Inventory transactions. Use this when the item is finished, and you want to review exactly what was used to make it. You can review the components as allocated, make any changes, and finally accept the finished order.

The system allows you to manipulate and maintain a simulated MPS and MRP. You can copy the simulation from the existing first cut, or you can create a totally new schedule. You can also perform a simulation of the rough-cut capacity plan. This allows a quick visual inspection by inquiry or menu of needed work center

loads for the proposed MPS. After you choose a suitable MPS and rough-cut capacity, the system allows you to transfer the simulated MPS to the live Master Production Schedule.

FirstLast

Tips: LN | Baan

Categories