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

The final step in Cycle Count processing is to maintain the (ICY) Cycle Count file. This history file increases in size with each posting session. It is up to users to purge the historical data that you no longer need. Previously, INV015 Cycle Count Purge by date only allowed users to purge the cycle count file by date. Now, additional selection criteria have been added that allows users improved ways to control records they may want to purge.

In addition to assigning lot numbers in Shop Order Entry/Maintenance (SFC500) after the shop orders have been released, users can now pre-assign lot numbers during the Multi-level Shop Order Release process (SFC530) and the Multi-Level Backflush process (LMP600) for sub-assemblies that are lot controlled items. The user has the choice of using the parent lot ID, the next sequential generated lot ID, or not pre-assigning lot IDs. Multiple items per lot must be installed to use the parent lot number option.

First6263646567697071Last

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