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 Tips & Tricks for FINANCE: Set Up and Calculate Currency Differences

Kathy Barthelt 0 3875 Article rating: 5.0

To set up and calculate currency differences for foreign currencies:

  • Use the Company Parameters (tfgld0503m000) session to specify the profit and loss ledger accounts, 12 profit and loss dimensions, and transaction type for a posting exchange rate differences that is calculated using the FIFO method. To specify this data, use the Currency Diff. FIFO tab. The reports printed from the Print Company Parameters (tfgld0404m000) session, include the Currency Differences FIFO fields.
  • Use the Calculate Currency Differences (tfgld5201m000) session to calculate the currency differences resulting from transactions posted on accounts for which the field Currency Analysis in the session Chart of Accounts (tfgld0508m000) is set to Required.

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Using the Data Access Layer (DAL)

Kathy Barthelt 0 4241 Article rating: 5.0

During an Exchange import, you can use all the functionality programmed into the Data Access Layer (DAL). If you use the DAL, Exchange carries out all the constraint checks, integrity checks, and side effects, for example, updates on other tables, that are programmed into the DAL. Database integrity is guaranteed automatically.

Using the DAL reduces the costs of interface development. You can use the DAL to import standard interfaces developed by Infor for partner products, as well as for specific interfaces built by customers, for example, to integrate LN with legacy systems. You can use the DAL in both single site and multisite environments.

The checks or additional actions specified in the DAL are carried out for each row that is imported. Database errors are logged in the same way for DAL and non-DAL import. DAL hook errors are also logged. You can specify whether the DAL property checks are or are not carried out.

If you specify the use of the DAL for a table relation for an import, the dal.new, dal.update, and dal.destroy functions are used instead of db.insert, db.update, and db.delete. You can choose to use DAL for particular tables and not for other tables, therefore, an import batch can contain both types of table relations simultaneously. The import through DAL works for both the import based on audit or indicators (inserts, updates, deletes), and the full import (inserts only).

DAL settings are run time aspects, which means you can change these aspects without having to regenerate the import program. DAL settings are also logged in the log table at batch line level, to enable you to find out what the DAL settings were when the import was run.

Important to realize is that an update through the DAL can result in a number of side effects. Actions performed by the DAL must not be carried out twice. For example, if the DAL updates the available to promise (ATP) quantity for an item when importing order data, the ATP quantity must not be updated in a condition script as well.

For this reason, you must not add any actions in condition scripts, or import additional data, that are already handled in the DAL.

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Add Last Maintained Audit Fields to SYS600

George Moroses 0 8227 Article rating: 5.0

LX has enhanced the SYS600 User Security Maintenance application by adding the ZXUP audit fields:

  • Last Maintained Date

  • Last Maintained Time

  • Last Maintained User

These fields are updated whenever a user or role is revised, deleted, or reactivated.

This enhancement provides standard audit tracking to identify who modified a User Security record and when. The audit fields can be used for ad hoc tracking, reporting, and analysis.

Infor LX/BPCS Tips & Tricks for OPERATIONS: Add Item Description to Inbound Delivery Lines

George Moroses 0 7673 Article rating: 5.0

The Inbound Delivery Line Detail panels have been enhanced to provide clearer item information and improved usability.

Key updates include:

  • Item Description added to the Inbound Delivery Lines Selection screen.

  • Increased number of lines displayed on the selection panel.

  • Multi-language support:

    • Item Description is shown in the user’s language (if available).

    • Defaults to the base language if a translation is not available.

  • On the PO Detail panel, the Item Description also supports multi-language display.

These enhancements give users more detailed item information on inbound deliveries, with Item Descriptions presented in their preferred language and more delivery lines visible at once.

Infor LX/BPCS Tips & Tricks for FINANCE: IDF Ledger Book Journal Line Analysis

George Moroses 0 1447 Article rating: 5.0

This enhancement introduces the IDF Ledger Book Journal Line Analysis business object, which displays reference information on summarized journal lines. To implement this enhancement, request and apply MR 81558.

Key features include:

  • Ledger Book Journal Line Analysis

    • Provides analysis attribute details.

    • Has a 1-to-many relationship with Ledger Book Journal Line Source.

    • Default view: General.

  • Ledger Book Journal Line Source

    • Has a many-to-1 relationship with Ledger Book Journal Line Analysis.

    • Displays the Ledger Book Journal Line Analysis detail card.

This enhancement enables users to access detailed reference information on summarized journal lines, improving analysis and reporting capabilities.

Join Us at inPOWER 2025 – Discover What’s Next for LX/BPCS

Frank Petrasio 0 584 Article rating: 5.0

We’re thrilled to invite you to inPower 2025, taking place September 22 to 25, 2025!

This annual conference is the premier event for the LX/BPCS community, bringing together users, experts, and partners to explore the latest advancements, share best practices, and connect with peers who understand your ERP challenges and goals.

👉 Get all the event details here


Why You Should Attend

inPower 2025 is your chance to:

  • Learn from Infor experts and industry leaders.

  • Explore real-world success stories and new strategies.

  • Connect with peers in the LX/BPCS community.

  • Discover solutions that can transform your business operations.


Stop by the Crossroads RMC Booth!

First2345791011Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Performance improvement by setting the First Free Number Cache (tcmcs0651m000)

Many transactions in all kinds of modules use order numbers or serial numbers. These order numbers are most often automatically generated. In the Number Groups (tcmcs0151m000) session you can define groups of order numbers used for dedicated areas. A Number Group is a group of the first free number series that you can assign to a specific use. All the numbers that Infor LN generates in the number groups that are dedicated to the same purpose are unique.

All the first free numbers are stored in the table tcmcs050.

As many different processes can request a free number from the number groups, we often see delays in the performance, due to locking on the first free number records. This locking issue can have a severe impact on the performance of huge batch-type transactions, but also on the performance perceived by individual users in many areas in LN.

For example:

  • Processing warehouse transactions. Single or in-batch
  • Completing / closing orders
  • Backflushing of production orders
  • Generate Order Planning
  • Cost calculation and warehouse revaluation


How this performance can be improved?

Resolution

In the Number Groups (tcmcs0151m000) session you can open the details of a specific Number Group (tcmcs0651m000) or start the session stand-alone.

In the Number Group, you define the Series with the related First Free Numbers. Per Serie in the First Free Number, you have the option to define the Cache Size.

This Cache size is defaulted on a value of 0 (zero). A cache size of zero means No Cache. How does the First Free Number caching works:

  • When the Cache Size is zero: With this setting a process requests a Free Number from the Serie and the first free number is issued to the process. But the first free number record is not updated yet. At the moment the requesting process is finished, without errors, it reports back that the number is used and the first free number record is updated. All the time that the process is working on the transactions the first free number record is locked. If another process is requesting a free number from the same series, it must wait (retries) until the record is updated and released by the previous process. This is the locking which is causing delays in the other processes.  
  • Setting the Cache Size to a higher value then zero activates the caching. When the Cache Size is set to 1 or higher, the requested free number is sent to the requesting process, the first free number is updated, with the number as defined in the Cache size, and the record is saved. It does not wait until the requesting process has reported back that is finished, with or without errors. In this way the record is immediately released and no locking will occur. If another process is requesting a free number, it does not need to wait until the free number record is released by the earlier process. If the process is ended with errors and therefor the number is not used, this number from the series is lost. This can result in gaps in the numbering. When the cache size is greater than 1, for example it is set to 5, the requesting process receives 5 free numbers. Even if it only needs less than 5. In this way the process only has to request for a new free number after it has used the first 5 numbers from the cache. This will also speedup the process in case of large batch transactions. For ‘warehouse integration users’, like for example Factory Track or WMS users we advise to set the cache size to 5.  

Note that financial documents are not based on number group series / first free numbers. Instead they are based on transaction type series, for which the caching functionality does not exist. Financial documents, like sales invoices, bank transactions, are thus not cached.

The caching is especially important to improve the performance of all logistical processes.

It is strongly recommended (mandatory) to set the Cache Size for all Number Groups to a minimum of 1.

Previous Article Infor LX / BPCS & Infor LN / Baan Tip: A New Wave of Cyber Attacks: Five Actions to Take Now
Next Article ​Infor LN & Baan Tip: Determining What Data to Archive or Delete
Print
30136 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories