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

George Moroses

Infor LX & BPCS Tip of the Week: Installing WebTop Over LX

If you plan to use Infor WebTop, the WebTop version 4.7 or above is required when running LX 8.4. Also, acquire and install the latest WebTop 4.7 patches from Infor Xtreme prior to running LX WebTop. WebTop 4.7 can be applied to your existing environments before you install 8.4.0. If this is completed before installing LX 8.4 then the LX install will take care of much of the Webtop server configuration automatically, including installing the LX Webtop metadata, updating WEB_ENV, and including the Webtop Platform library in the INLIBL data area as part of the environment setup. If you choose to install WebTop after the LX 8.4 installation is completed, the “Infor LX 8.4 Webtop 4.7 Configuration Guide” will guide you through all the configuration steps to set up Webtop for your LX environment.

Previous Article LN & Baan Data Collection News – A BUSY 2nd Quarter for Crossroads RMC Data Collection!
Next Article Infor LN & Baan Tip of the Week: What is Included with Infor Operating Service (Infor OS)?
Print
35086 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

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.

Categories