Anthony Etzel / Tuesday, July 9, 2019 / 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 57424 Rate this article: 5.0 Anthony EtzelAnthony Etzel Other posts by Anthony Etzel Contact author Facebook page Twitter Linked In YouTube Website
10Jun2025 Infor LX/BPCS Tips for EXECUTIVES Tuesday, June 10, 2025 Read more FINANCE: Override Warning in Invoice Entry PO Costing OPERATIONS: Auto Calculate Vendor Delivery Date TECHNOLOGY: User Provisioning Read more
10Jun2025 Infor LX/BPCS Tips & Tricks for FINANCE: Override Warning in Invoice Entry PO Costing Tuesday, June 10, 2025 Read more Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action. In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed. A new “F14 to Override” warning message replaces the old message: “Details have changed. Press enter again to accept data.” This ensures users acknowledge and confirm significant changes explicitly. New System Parameter: “Apply GRN Costing Tolerance for PO Costing” (optional): Within tolerance: Displays the original message — “Details have changed. Press enter again to accept data.” Outside tolerance: Triggers the new override requirement — “F14 to Override” Benefits: Enhances oversight and reduces unintentional cost acceptance. Enables better control of PO costs when invoice details differ from expectations. Read more
10Jun2025 Infor LN & Baan Tips & Tricks for EXECUTIVES Tuesday, June 10, 2025 Read more FINANCE: Rebuild History for Account Matching (tfgld1218m000) OPERATIONS: Copy Customized Product Structure to Standard Structure (tipcs2232m000) TECHNOLOGY: Authorization and Security: LN REST APIs Read more