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

If you setup the “From” and “To” Location fields in the Work Center file, this will determine the locations for material issue transactions and production reporting transactions.

The reporting of the transactions happen through production reporting, JIT600, or using the Shop Floor labor posting, SFC600, or Shop Floor Posting from SFC650.

Remember, any location used in the work center file must first be set up in the location master file. Using an MES solution by-passes the need to key any of the data to Infor LX.

Ok… so you want to know the status of a specific shop order that was released two days ago.

What do you do?

It’s a sure bet that you have a manager, supervisor, or planner who can walk the floor and find the order at whatever work center it happens to be at. He/she can then answer “what operations have been completed and how many were completed?” All this requires leg work, and of course, a fair amount of time.

Now, if you have set up your BPCS master files properly, and you report transaction activity, you should be able to get those shop order statuses much faster using the SFC300 Shop Order Inquiry Screen.

At your fingertips you can see:

  • Release date & due date
  • How many hours remain in total and at each operation
  • The quantity required, what was finished, and the remaining quantity
  • What components (materials) have been issued

Pretty basic information, right? Are you getting what you need to know? If not, then you may want to reexamine how your BPCS files are set up and what transactions along with their frequency are captured.

FirstLast

Tips: LN | Baan

Categories