Technology: Reset Purchase Order In Use -

Operations: Retain Lot Status on Shipped Resupply Orders -

Finance: Inventory Period Balance Freeze -

Are you up to speed on Infor’s Product Lifecycle Policy for your version of BPCS/LX? Review this document from Infor, and contact Frank Petrasio at Crossroads RMC with any questions about how this may impact your organization.

Users can personalize sessions and apply special formatting to the data displayed in sessions. The personalizations and formatting settings that are specified by the users are stored on the LN server. Administrators can maintain these settings.

• Session personalizations

  Users can personalize sessions in various ways. users can, for example, hide fields, change labels, customize the toolbar, and move fields to another tab. Administrators can maintain the personalizations defined by the users. For example, an administrator can export personalizations to an XML file, import personalizations from an XML file, and copy personalizations to another user, to a DEM role, or to a company number.

• Report personalizations

  You can use the Report Designer (ttstppersrep) to personalize the layouts and style of reports, without modifying the standard reports or using an external reporting solution. The changes are stored as personalizations.

  You can also generate new reports that are based on a selection of fields from the application data model. These reports are generated in the extensibility package. You can personalize these reports in the Report Designer (ttstppersrep), or modify them in Infor LN Studio.

  For details, see the Infor LN Report Designer Development Guide
   

• Conditional formatting

  users can define conditions to apply special formatting to the data displayed in LN sessions. The users can define multiple conditions per session and different types of formatting, such as a specific color for particular fields or rows, and a warning symbol for particular rows. Administrators can maintain the formatting settings specified by the users and can define system-wide formatting settings.

• If Finances 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.

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 is linked to the purchase order line, and for which an internal invoice must be sent from the purchase 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.