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

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip of the Week: LX 8.4 Database

The database in LX 8.4 has undergone a significant change from previous versions. The database has been created using SQL DDL language instead of the old DDS language. The newer format allows for LX to take better advantage of advances in IBM database technologies as they move forward. Additionally, LX will be better able to make changes to tables (aka files) in the future without causing very large MR explosions to replace all programs that use a specific table. To ease the impact of this significant change, the LX tables (aka physical files) have new names that are the same as the previous version file names but with a “P” at the end, for example IIM is now IIMP. The old file names now belong to SQL views that looks just like the tables. This change made it easier to upgrade all the LX programs without changing every reference to every file. Many of the logical files remain although some have been replaced by SQL indexes to improve performance.
Previous Article Crossroads RMC is Proud to Announce Product Certification for Baan IV to Avalara!
Next Article A/P Payment Update in LX 8.3.4
Print
32572 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Exit Points is a new feature in Infor LX Version 8 that allows users to customize, without changing the original LX source code. Exit points provide a way for you to call an external program and pass a set of parameters to implement any needed custom logic. By using Exit Points, LX customers are able to modify the software, and still take advantage of new releases from Infor. Exit points are available in many LX programs. A complete list is available on the Infor support website.

Optimize Your Manufacturing Today!

Poor performance indicators make for poor outcomes.

Companies today continue to tolerate and accept how labor and production information is recorded, and the reliability on that information is questionable. In addition to collecting labor and production information, there are many other pieces of information manually recorded from the shop floor.

A critical element of information for productivity throughput would be to examine how much time the work center or machine was actually up and running. Downtime is another critical element of data that is usually manually recorded along with a reason identifying what caused production to stop. If this information is not provided on a timely and accurate basis, then what good is it anyway? Forms are filled out, data may or may not be keyed to a spreadsheet, the forms are sorted and filed, but is anybody really looking at the information that was recorded? Think about the amount of time it takes to manage the manual collection of information from your shop floor. 

What would real time access to data mean to your organization?
The benefits:

  1. Real Time Production Visibility
  2. Reduced Paperwork Load
  3. Downtime and Scrap Visibility
  4. WIP Inventory Visibility
  5. Improve Efficiency, Capacity Utilization

Optimize Your Manufacturing Today!

First101102103104106108109110Last

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