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 77375 Rate this article: No rating Kathy BartheltKathy Barthelt Other posts by Kathy Barthelt Contact author Facebook page Twitter Linked In YouTube Website
8Apr2025 Infor LX/BPCS Tips & Tricks for FINANCE: Increase A/P Retention Days Tuesday, April 8, 2025 Read more This enhancement allows reconciled payables and payments to be retained in the system for over 200 years. It extends the retention period in A/P Application Control Maintenance (ACP180) to support up to five digits. This gives LX customers the ability to retain data online for significantly longer durations. Read more
8Apr2025 Infor LX / BPCS Tips & Tricks for EXECUTIVES: Tuesday, April 8, 2025 Read more FINANCE: Increase A/P Retention Day TECHNOLOGY: Search by Description in Segment Value List OPERATIONS: IDF Customer Order Inquiry Enhancements 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