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 LN & Baan Tip: Considerations for Release to Warehousing for a Cost Item

Kathy Barthelt 0 52591 Article rating: 5.0

When there are two Cost Items, one with Release to Warehousing applied and the other with Release to Warehousing not applied, upon approval of the Sales Order, the Cost Item that is released to Warehousing will go straight to Staged status, pending Shipment confirmation, while the Cost Item that is not released to Warehousing will be up for Sales Deliveries.

Apart from this main difference in functionality between having and not having this option to release to Warehousing checked, there are other impacts to consider...

Reskilling and Upskilling Your Staff – Why You Shouldn’t Ignore This

Crossroads RMC 0 12917 Article rating: 5.0

According to the World Economic Forum, half of all employees will require significant reskilling or upskilling by 2025.

For many of you, your Infor ERP system was implemented 5, 10, 15, or 20+ years ago, and now there are only a handful of people left from that implementation if any at all. Since most of your "how and why" walked out the door, how much longer can you get by on “tribal knowledge”? While many companies understand the importance of employee training, implementing that training remains a challenge. What’s the best way to proceed you ask?

Infor LN & Baan Tip: What conditions must exist before changing an item's inventory unit?

Kathy Barthelt 0 55070 Article rating: 5.0

Is there a procedure for changing an item’s inventory unit? What conditions must exist before it can be done?

Once inventory transactions (receipts or issues) have occurred for an item, the inventory unit cannot be changed. If only orders have been placed against the item (sales or purchase), the inventory unit can be changed if these...

Infor LX & BPCS Tip: 4 Approaches to Customizing LX / BPCS - Preparing for a Future Upgrade

George Moroses 0 21660 Article rating: 5.0

How do I modify BPCS/LX to allow for the ease of upgrading in the future?

  1. Exit Points...

Is it time to get more out of your ERP?

Crossroads RMC 0 12469 Article rating: 5.0

As crazy as it sounds, we’re about to enter the 2nd half of 2023. How are you doing on your 2023 goals? Planning for 2024 projects?
Maybe it's time to get more out of your Infor ERP system.

OFF SUPPORT AND MAINTENANCE WITH INFOR AND FEEL STUCK?

⇒⇒ TIME TO UPGRADE?

⇒⇒ NOT UPGRADING?

Infor LX & BPCS Tip: Support for IBM i 7.3 and Infor LX Products

George Moroses 0 19690 Article rating: 5.0

On September 30, 2022, IBM® announced the end of support of IBM i operating system 7.3 effective September 30, 2023. In line with IBM’s support policy, Infor will no longer support LX and related products on IBM i 7.3 after May 31, 2024. All Infor LX releases, patches, and related solutions are...

First2021222325272829Last

Tips:  LX | BPCS | M3

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.

Last

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for 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.

Previous Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Cash Flow Statements (tfgld 0123m100)
Print
32963 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories