Kathy Barthelt / Tuesday, September 22, 2015 / Categories: Infor LN & Baan Tips Baan/LN Tip of the Week: Data Sizing Moving to LN The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume. Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB. Previous Article BPCS/LX Tip of the Week: Work Center & Machine Locations Next Article BPCS/LX TIP OF THE DAY: MATERIAL REQUIREMENT DATES AND LEAD TIME OFFSETS IN MRP Print 57315 Rate this article: No rating Kathy BartheltKathy Barthelt Other posts by Kathy Barthelt Contact author Facebook page Twitter Linked In YouTube Website
2Aug2023 Infor LX & BPCS Tip: What prevents tax from being calculated on a purchase order? Wednesday, August 2, 2023 Read more Review the setup and check the following: 1. 2. 3. 4... Read more
17Jul2023 Infor LX & BPCS Tip: What is the purpose of document sequencing? How does it work? Monday, July 17, 2023 Read more Document Sequencing (ACR160) is a feature that allows the BPCS/LX system to assign a unique document number to every document created through ACP, ACR, and BIL. It is required for use with ATP (the general ledger posting engine) for ACR and BIL and is strongly recommended for use with... 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