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

Understanding: What Was Issued to the Shop Order

The shop order inquiry program provides several function keys. By using the function key for the material, the display will present what components have been issued under the issued quantity column. You are also presented with the required quantity. While viewing the quantities you may see that more was issued than what was required. Possibly there was scrap and more material was required to be issued. Perhaps there was an over issue and the balance of the material is slated to be returned to stock.

A red flag should go up if the Shop Order quantity finished is equal to the required quantity for the end item and all the components have not been issued. You may want to investigate why.

Understanding: The quantities required, finished and remaining at the operation and in total for the Shop Order

The shop order may require 1,000 pieces but only 950 are reported as finished in total for the shop order. The quantity required is what is planned on the SO and it may be a higher number than what is finished, factoring in that there can be scrap. If a 1,000 pieces are required to be produced, and there is always is scrap of 10 pieces, then plan for scheduling a quantity of 1,010.

The quantity finished for the end item is what is reported in the inventory application with a production order receipt transaction. At the operation level, if the quantity is reported at the operation, there will be a value in the PCS Complete field on the operation detail screen showing the pieces completed through that operation.

If you want to get a handle on the difference between the required quantity and the finished quantity, you may want to look into reporting quantities at the operation level as well as examining how scrap is controlled and reported.

FirstLast

Tips: LN | Baan

Categories