Anthony Etzel / Wednesday, April 12, 2017 / Categories: Infor LX & BPCS Tips BPCS/LX Tip of the Week: Transactions If you opt to summarize transactions, do so after a period of testing so that you can be certain that all models and aliases are working to your satisfaction. When you summarize, consider ‘Summary with Detail’ because this retains the detail transactions in GLH. Previous Article Baan/LN Tip of the Week: Creating Product Variants Next Article Baan/LN Tip of the Week: Vendor Evaluation Print 47492 Rate this article: No rating Anthony EtzelAnthony Etzel Other posts by Anthony Etzel 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