Kathy Barthelt / Thursday, October 30, 2014 / Categories: Infor LN & Baan Tips Baan/LN Tip of the Week: What could go wrong with GRINYA? One common GRINYA issue would be incorrectly entered Integration Setups. Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error. It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined. Previous Article Baan/LN Tip of the Week: Differentiating An Item By Supplier - LN Next Article BPCS/LX Tip of the Week: Work Center & Machine Locations Print 77362 Rate this article: No rating Kathy BartheltKathy Barthelt Other posts by Kathy Barthelt Contact author Facebook page Twitter Linked In YouTube Website
7May2025 Infor LX/BPCS Tips & Tricks for FINANCE: IDF Ledger Book Journal Line Analysis Wednesday, May 7, 2025 Read more This enhancement added the IDF Ledger Book Journal Line Analysis business object for displaying reference information on summarized journal lines. This enhancement provided Ledger Book Journal Line Analysis business object and a bi-directional relationship to Ledger Book Journal Line Source. This enhancement provides the user with detailed reference information on summarized journal lines for analysis purposes. Read more
6May2025 Infor LX/BPCS Tips & Tricks for EXECUTIVES: Tuesday, May 6, 2025 Read more FINANCE TIP: IDF Ledger Book Journal Line Analysis TECHNOLOGY TIP: Improve WebTop Grid Support for MRP320D Master Schedule Detail Inquiry OPERATIONS: Override inspection days lead time at the item-facility 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