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
16822 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

The Cycle Counting Sub-System Within Inventory Management

The system uses the following information as the basis for cycle counting selection:

  • Cycle Counts/Year: The system calculates the time between cycle counts based on your entry in this Item Master file field for each item (optional).
  • Last Cycle Count Date: This date is in the Location Inventory file, ILI, if you use locations, or in the Warehouse Inventory file, IWI, if you don't.

The system adds the time between cycle counts (calculated as described above) to this date. If the result is less than or equal to today's date, the item is selected for cycle counting. If it is greater than today's date, the item is not selected, it is not due yet for cycle counting.

There is another special condition that causes an item to be selected for cycle counting. If the ILI/IWI record of the item has a Y in the Cycle Flag field, the item is selected automatically. This flag indicates that the item's on-hand balance has gone to a negative value sometime since the last cycle count. That applies even if the value is not negative at selection time. The programs that can set this field are INV500D, INV510, and BIL540.

You can also limit the items selected for counting by specifying limits of the item numbers or warehouses to be searched.

First2526272830323334Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories