Kathy Barthelt / Wednesday, September 24, 2014 / Categories: Infor LN & Baan Tips Baan/LN Tip of the Week: Aborted Finalization Run When a finalization run is aborted and in the batches selected for this finalization run are transaction types having the update mode finalization, you must use the Restart Finalization Run session. This session can be found in the Transaction Processing menu of the General Ledger Module of the Finance Package. Previous Article BPCS/LX Tip of the Week: SFC600 Next Article BPCS/LX Tip of the Week: The Machine Master Part 1 Print 75182 Rate this article: No rating Kathy BartheltKathy Barthelt Other posts by Kathy Barthelt 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 TECHNOLOGY:Â Authorization and Security - LN REST APIs Tuesday, June 10, 2025 Read more In typical LN REST API integrations, permissions and authorizations are not implemented or rarely used. To ensure smooth data exchange and avoid errors, it is recommended to disable the authorization and security settings. Recommendation: In the Authorization and Security Parameters session (tcsec0100m000): Clear the Authorization and Security Enabled check box. Clear all check boxes under Authorization Enable for on the Enabling tab. Why This Matters: Enabling authorization and security without proper setup can lead to errors and blocked transactions during integration. For example, work center permissions may interfere with: Creating new shifts Booking machine hours Read more