Anthony Etzel / Wednesday, May 3, 2017 / Categories: Infor LX & BPCS Tips BPCS/LX Tip of the Week: Purchase Order “In Use” Reset Feature 8.3.5 This new feature provides the ability to resolve or reset a purchase order or requisition that is no longer being processed, but the system still indicates it is ‘in use’. We all remember those situations where we could never figure out how the order got hung up. What we previously had to do was run a behind the scenes script to reset the flag so the order was again accessible. This enhancement provides the ability to resolve the issue and resume processes quickly. This option is now on the PUR menu, and the user can select the Purchase Order/Requisition in Use Maintenance, PUR940D. The user then enters an order or requisition to remove the “In Use” status. Optimize Your Manufacturing Today! Previous Article Baan/LN Tip of the Week: Advantages / Disadvantages of Virtualization Next Article Baan/LN Tip of the Week: Alternative Materials in BOMs: Print 43167 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