Kathy Barthelt / Wednesday, November 4, 2015 / Categories: Infor LN & Baan Tips Baan/LN Tip of the Week: GRINYA Reconciliation – What Could Go Wrong? One common GRINYA issue would be incorrectly entered Integration Setups. Check the Baan or Infor 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. To ensure, it’s recommended that the Integrations Setup tables should be audited either through Baan/LN or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined. Previous Article BPCS/LX Tip of the Week: Inventory Control Next Article Baan/LN Tip of the Week: Month End – Miscellaneous To-Do’s Print 56710 Rate this article: No rating Kathy BartheltKathy Barthelt Other posts by Kathy Barthelt Contact author Facebook page Twitter Linked In YouTube Website
14Jan2025 Infor LX/BPCS Tips & Tricks for EXECUTIVES Tuesday, January 14, 2025 Read more Technology: Reset Purchase Order In Use - Operations: Retain Lot Status on Shipped Resupply Orders - Finance: Inventory Period Balance Freeze - Read more
10Dec2024 Infor LX/BPCS Tips & Tricks: Infor's Product Lifecycle Policy Tuesday, December 10, 2024 Read more Are you up to speed on Infor’s Product Lifecycle Policy for your version of BPCS/LX? Review this document from Infor, and contact Frank Petrasio at Crossroads RMC with any questions about how this may impact your organization. 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