Please Wait a Moment
X

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

Crossroads Connections

Infor ERP Tips & News from the Experts

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

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

George Moroses 0 47493 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).

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

George Moroses 0 49945 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.

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

Kathy Barthelt 0 40992 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.

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

George Moroses 0 14479 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.”

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

George Moroses 0 17696 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.

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

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.

Last

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES

TECHNOLOGY: Data Sharing Methods (Advantages and Disadvantages)

Depending on the multicompany scenario you choose, an implementation team must decide whether or not tables must be logically linked or if data must be synchronized in another way to achieve availability of data across various companies. 

There are 3 ways in which data may be shared among companies. Here are some advantages and disadvantages of each:

  1. Logical Table Linking - If two companies use the same physical data, the physical table exists, or is used, in only one company: the physical company. Each piece occurs only once: one instance of the same data. If the term logical table linking is used, users from multiple companies use a single physical instance of the data. If the company tables are on the same server, this can be accomplished by logical table linking. Access to specific data can be restricted, if required.

    • Advantages: Logical Table Linking takes place in real time; therefore, the moment a record is created or modified in one company, a record becomes available in all other linked companies as well. The setup and maintenance of logical table linking is easier than the setup and maintenance of data replication. Logical table linking is extremely reliable because this type of linking is independent of network connections and user interventions. 

    • Disadvantages: Table sharing implies that all attributes for a record are the same in all companies. Therefore, suppose you share the item table and, for a particular item in a company, the product class is XXX. In this case, in all other companies, the product class for this item must be XXX as well.

  2. Data Replication - In this situation, each company has exactly the same data, but each company has a unique copy of the data. The same piece of data exists in multiple (physical) places: multiple instances of the same data. The process to copy the data is called data replication.

    • Advantages: Rather than using table sharing by means of the logical linking of tables, you can replicate the content of tables between companies. The advantage is that, on company level, some (non-key) attributes of a record can differ by company. For example, if the bills of materials are replicated instead of shared, for each company, you can link a different warehouse to the bill of material. As a result, the bills of materials can be the same across all companies and only the warehouses differ. Using replication, you can also make only a subset of the records available in other companies. For example, if you replicate items between companies, in a sales company, for example, by means of the item group, you can only make end items available. In addition, you can replicate only a subset of items, for example, depending on the item group. Note that replication also requires that the referenced tables are replicated or shared.

    • Disadvantages: Replication is not in real time, and therefore, for processes that require real-time integrated data as the financial integration processes, replication is not an option. For replication, you also must take into account the sequence in which you replicate. First, you must replicate the child tables and then the parent tables, and therefore first the business partners and then the purchase contracts. During the replication process, the data must be frozen. This point is of particular importance if the replication process takes a lot of time.

  3. Manual Syncronization - If only a small number of records are the same between some companies, you can enter, maintain, and keep the records synchronized manually. Note that the more dynamic data is, the more difficult this process is. This solution is strictly procedural. Therefore, depending on the discipline of the users, the solution is error sensitive: data can be forgotten, updated too late, or typing errors may occur.

  • Advantages - The main advantage is the flexibility so that only the data that really must be shared can be kept synchronized. By manually keeping data synchronized, not all attributes of a record need to have the same value.

  • Disadvantages - The main disadvantage is that this method depends on user interaction. Therefore, the method depends on the user’s time - because the method is not a real time procedure and the user may forget to update the data - and users can make mistakes.

OPERATIONS: Creating a Purchase Order with Subcontracting

To create a purchase order (with subcontracting) third party outsourcing from purchase order, execute these steps:

  1. Create a purchase order using the same data set defined in the Subcontracting Models (tisub1100m000) session.
  2. In the Purchase Order Intake Workbench (tdpur4601m200) session, click New. The Purchase Order (tdpur4100m900) session is displayed.
  3. Select the business partner in the Business Partner field, Press Tab. Note: Infor LN populates the default data for the selected business partner in the other fields of the purchase order header.
  4. Select the order type for subcontracting in the Order Type field, purchase office in the Purchase Office field, and the related order series in the Order field.
  5. Click New on the Order Lines tab and select your subcontracted price item in the second segment of the Item field.
  6. Specify the required quantity in the Ordered Quantity field, price of the item in the Price field and click Save.
  7. Click the Approve button to approve the purchase order. The purchase order Status is updated to Approved.
  8. Verify that the material to be sent to the subcontractor is updated on the Material Supply Lines tab.
  9. Select the material line on the Material Supply Lines tab and click Actions > Generate Supply Order.
  10. Select the generated supply order line updated in the Supply Order Line field on the Material Supply Lines tab and click References > Supply Lines. The Warehousing Order (whinh2100m100) session is displayed.
  11. Select the outbound order line on the Outbound Lines tab and click References > Status Overview. The Outbound Line Status Overview (whinh2129m000) session is displayed.
  12. In the Outbound Line Status Overview (whinh2129m000) session, ensure that the Generate Outbound Advice and the Release Outbound Advice activities are automatically executed.
  13. On the specific menu, click Freeze/Confirm. The Shipment Lines (whinh4131m000) session is displayed.
  14. Select the shipment line and click Confirm. The shipment line Status is updated to Confirmed on the Status tab.
  15. Verify that the Line Status is Shipped for the outbound order line on the Outbound Lines tab in the Warehousing Order (whinh2100m100) session.

FINANCE: Cash Flow Statements (tfgld 0123m100)

Use this session to define or maintain cash flow statements and hierarchical structures of cash flow reasons for cash flow statement reports. 

On the Cash Flow Reasons by Statement tab, you can select cash flow reason groups and cash flow reasons to build a hierarchical structure of cash flow reasons for the cash flow statement report.

To link a child cash flow reason group to a parent cash flow reason group:

  1. In the Parent Cash Flow Reason Group field, select the parent cash flow reason group.
  2. In the Child Cash Flow Reason Group field, select the child cash flow reason group.
  3. Leave the Child Cash Flow Reason field empty.

To link a cash flow reason to a cash flow reason group:

  1. in the Parent Cash Flow Reason Group field, select the cash flow reason group
  2. Make the Child Cash Flow Reason Group field empty.
  3. In the Child Cash Flow Reason field, select the cash flow reason.

Note: To link cash flow reasons to a child cash flow reason group, you must select the child cash flow reason group in the Parent Cash Flow Reason Group field.

Previous Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Next Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Data Sharing Methods (Advantages and Disadvantages)
Print
18791 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories