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 21971 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 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 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