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.

TECHNOLOGY: Using the Data Access Layer (DAL)

FINANCE: Set Up and Calculate Currency Differences

OPERATIONS: Subcontracting Overview

Disconnected data—information stored outside your core ERP system—creates inefficiencies and blind spots across every level of your organization. While spreadsheets, email orders, and external reporting tools may serve a purpose, the lack of integration between these systems leads to far-reaching consequences.

Operations Impact

• Inventory levels and supplier shipments are tracked in spreadsheets, disconnected from your ERP.
• Dealer portal email orders require manual entry into the system, slowing fulfillment.

Finance Impact

• Budgeting data lives in isolated spreadsheets, unlinked to ERP sales or quoting information.
• Open purchase orders and invoices must be manually matched and approved, consuming valuable time.

Technology Impact

• Countless reports are generated outside the ERP just to keep teams “up to date.”
• Significant time is wasted exporting ERP data into external data cubes for analysis.

Executive Impact

• Leaders struggle to compile an accurate view of inventory and financial health when data comes from multiple sources.
• A lack of real-time visibility into shortages causes lost sales and customer dissatisfaction.

Disconnected data isn’t just an inconvenience—it drains productivity and delays critical business outcomes.

The Business Costs of Disconnected Data...

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.

LN Report Archive Solution Overview

The LN Report Archive solution allows you to archive printed reports for long-term access and reprinting, even years after their original print date.

This is especially valuable for external documents such as invoices, purchase orders, and other reports sent to customers or suppliers. In some countries, the ability to reprint these documents for up to 10 years is a legal requirement.

Key Features:

• Report Archiving:...

New IDF Inquiries 

Infor LX has a long history of providing IDF inquiries over most critical business areas, but there are still some areas that lack this capability.
The following IDF inquiries are now available in 8.4.2:

• Customer Quote
• Customer Quote Line
• RMA (Return Material Authorization)
• RMA Line

Benefits

• Ability to sort, subset, filter, and view information in a modern and intuitive way
• Point and click navigation to related information – 360 views
  • Exceptional personalization and extensibility capabilities

In typical LN REST API integrations, permissions and authorizations are not implemented or rarely used. To ensure smooth data exchange and avoid errors, it is recommended to disable the authorization and security settings.

Recommendation:

• In the Authorization and Security Parameters session (tcsec0100m000):

  • Clear the Authorization and Security Enabled check box.

  • Clear all check boxes under Authorization Enable for on the Enabling tab.

Why This Matters:

• Enabling authorization and security without proper setup can lead to errors and blocked transactions during integration.

• For example, work center permissions may interfere with:

  • Creating new shifts

  • Booking machine hours

  • Read more

Enables integration between LX and Infor OS Federation Services (IFS) to automate user provisioning.

• Bi-directional user synchronization between Infor OS and LX:

  • Infor OS user creation or changes automatically create or update users in LX.

  • IBM i user profiles can be created if needed.

  • Updates to SYS600 user data are reflected in Infor OS.

• Security Role Integration:

  • LX Security Roles and Units are published as IFS Security Roles via SyncSecurityRoleMaster BODs.

  • LX receives inbound SyncSecurityUserMaster BODs from IFS to create or update user records in SYS600.

  • SYS600 Exit Points trigger ProcessSecurityUserMaster BODs to request user creation or updates in IFS on behalf of LX.

Available Versions: 8.3.5, 8.4.1, 8.4.2