Kathy Barthelt / Tuesday, June 11, 2024 / Categories: Infor LN & Baan Tips, Operations Infor LN & Baan Tip & Tricks for OPERATIONS: Best Practices for Purchase Order Archiving / Deleting Here are some best practices to follow if you are considering archiving or deleting purchase order data: If Financials is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data. When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived. Purchase contracts must be archived before purchase orders can be archived. You cannot delete a purchase order (line) if: The linked warehouse order is closed but cannot be removed. The purchase order is linked to a PCS project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order. A consignment replenishment order is not yet consumed completely. The invoice is yet to be completely matched and approved. The invoice amount is not yet inserted as turnover history. The sales order or service order that's linked to the purchase order line, and for which an internal invoice must be sent from the purchas office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced. Previous Article Infor LN & Baan Tip & Tricks for TECHNOLOGY: Using Table Boosters to Speed Up Sessions & Processes Next Article Infor LN / Baan Tips & Tricks for EXECUTIVES Print 21973 Rate this article: 5.0 Kathy BartheltKathy Barthelt Other posts by Kathy Barthelt Contact author Facebook page Twitter Linked In YouTube Website
10Jun2025 Infor LX / BPCS Tips & Tricks for OPERATIONS: Auto Calculate Vendor Delivery Date Tuesday, June 10, 2025 Read more Enhances purchase order efficiency by automatically calculating the Vendor Delivery Date based on user input. When a purchase order line is created, the user enters the item, order quantity, and Due Date. LX automatically calculates the Vendor Delivery Date, adding buffer time for quality control, testing, and inspection activities. If the Due Date is revised, an informational message prompts the user to review and potentially update the Vendor Delivery Date. Enhancements: A new PUR820 system parameter enables automatic recalculation of the Vendor Delivery Date. Instead of a manual reminder, PUR500 now issues a message: “Vendor Delivery Date recalculated,” showing the updated date. Benefits: Eliminates the need to manually review and update the Vendor Delivery Date. Removes the need to delete and recreate PO lines to trigger automatic date calculation. Read more
10Jun2025 Infor LX/BPCS Tips & Tricks for TECHNOLOGY: User Provisioning Tuesday, June 10, 2025 Read more Enables integration between LX and Infor OS Federation Services (IFS) to automate user provisioning. Bi-directional user synchronization between Infor OS and LX: Infor OS user creation or changes automatically create or update users in LX. IBM i user profiles can be created if needed. Updates to SYS600 user data are reflected in Infor OS. Security Role Integration: LX Security Roles and Units are published as IFS Security Roles via SyncSecurityRoleMaster BODs. LX receives inbound SyncSecurityUserMaster BODs from IFS to create or update user records in SYS600. SYS600 Exit Points trigger ProcessSecurityUserMaster BODs to request user creation or updates in IFS on behalf of LX. Available Versions: 8.3.5, 8.4.1, 8.4.2 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