Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Infor will no longer support LX or BPCS on IBM i 7.2 after April 30, 2021

George Moroses 0 47253 Article rating: 5.0

On September 10, 2019, IBM® announced the end of support of IBM i 7.2 effective April 30, 2021. In line with IBM’s support policy, Infor will no longer support LX, BPCS, SSAEAM, PRMS, BOSS and related products on IBM i 7.2 after April 30, 2021.

All releases, patches, and solutions are expected to be delivered and compiled for IBM i 7.3 effective May 1, 2021. These deliverables should install and function on version 7 release 3 (IBM i 7.3) and above. This will require that your operating system be at a minimum release level of IBM i 7.3.

This policy extends to other Infor LX related technologies including WebTop, System i Workspace (SIW), and Infor Development Framework (IDF).

If you have not done so already, we recommend you start planning and completing your upgrade to IBM i 7.3 or above prior to April 30, 2021. After this date, if you register a support call with Infor Support, and your application still runs on IBM i 7.2, you may be requested to upgrade to a supported version of the IBM i operating system.

In addition, we invite you to log on to Infor Concierge to view and download important information regarding Infor LX, BPCS, and Infor SSAEAM. General KB Articles have been created to proactively provide you with information regarding this Announcement (1397381) and the Infor BPCS/LX Product Lifecycle Policy (1947086).

Read more

Infor LX & BPCS Tip of the Week: Journal Upload – EGLi

George Moroses 0 49509 Article rating: 5.0

EGLi users who maintain journal entries in a Microsoft Excel spreadsheet can use this utility to upload journal entries to EGLi. The Journal Upload installation program adds an Add-Ins tab to Microsoft Excel. This tab includes options to connect to the server where EGLi is installed and to open a spreadsheet template to use for manual journal entry. When the spreadsheet is complete, the Add-Ins tab is used to upload the spreadsheet.

To install Journal Upload:

  1.  The Power-Link Installation page has links to the Client installation programs and a link to download and install the Journal Upload utility. To access this page, use this link with your own values for system and NetLinkport: http://system:NetLinkport/Installs/ClientInstall/Install.html  where system is the server where IDF is installed and NetLinkport is the Net-Link port, typically 36001
     
  2. On the Power-Link Installation page, click the link provided to download and install EGLi Journal Upload.
     
  3. Follow the screen prompts to complete the installation on your PC.
     
  4. To verify the installation, open an Excel spreadsheet. Confirm that the Add-Ins tab is on the spreadsheet. 


See the Infor Enterprise General Ledger for System i Journal Upload Installation and Infor LX Configuration Guide.

Read more

Infor LN & Baan Tip: Open Transactions Check – LN 10.7

Kathy Barthelt 0 39401 Article rating: 5.0

When closing a project, users were informed about open transactions blocking the closure process. To proactively check on open transactions, the Show Open Transactions option has been introduced in the Project Status (tppdm6107s000) session. With this option, issues can be resolved before changing the status.

Read more

Infor LX & BPCS Tip of the Week: LX 8.4 Enhancement – Company Security for ACR510

George Moroses 0 14218 Article rating: 5.0

This enhancement provides LX Company Security to Invoice Maintenance, ACR510. Only users authorized to the invoice company can view or maintain invoices.

User must be authorized to ACR as a product or ACR510 as an individual program in Security Master Maintenance, SYS600. Additionally, ACR510-01, displays all records, but if the user tries to revise or display a transaction record for a company the user is not authorized to, this error message is displayed: “User is not authorized to the transaction company.”

Read more

Infor LX & BPCS Tip of the Week: Item Deletion Option in IDF Enterprise Items

George Moroses 0 17353 Article rating: 5.0

Previously, users were unable to delete items in IDF Enterprise Items when they have inventory balances or the item is connected to ancillary records, such as sales history records. This feature added in LX 8.4 provides the ability to delete an item when sales history records are found but all sales history activity is zero.

When the user attempts to delete an item in IDF Enterprise Items that is tied to a sales history record, the panel displays a message that the item cannot be deleted. The user can then run the Delete Validation Report to determine which records are tied to this item that prevents the validation. If the item no longer has manufacturing activity but had old sales history, the item can be deleted.

Read more
First4546474850525354Last

Tips:  LX | BPCS | M3

Item Facility Master has a new attribute to define the override inspection days lead time CICP.ICINSD.

  • When an item facility has a defined override inspection days lead time, that value will be used instead of the system parameter inspection days lead time.

MRP exception report, MRP200B
Purchase planning report, PUR285B
Purchase order / Requisition maintenance, PUR500D3
Purchase order consolidation / release, PUR640B1
Vendor splits, PUR653B

Read more

This enhancement improved the subfile utilized in MRP320D Master Schedule Detail Inquiry -SCR001 by expanding the subfile with data rather than clearing the subfile as user pages. This change provides full support for the WebTop 4.8 Grid decorator.

This enhancement updated the approach used to populate the subfile to allow a deployed Webtop Grid to function correctly. There is no visible or user-impacted change to the way the program functions.

This enhancement provides improved functionality and full support of a Webtop grid applied to the subfile.

Read more
Last

Tips: LN | Baan

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.

Read more
  • 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.
Read more

Categories