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
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip of the Week: What is EGLi?

EGLi provides Infor LX Configurable Enterprise Accounting (CEA) functionality including Advanced Transaction Processing (ATP), a configurable ledger, and batch transaction processing in the IDF architecture.

EGLi is a complete replacement for CEA. Infor LX applications integrate with EGLi, and subsystem transactions generated in Infor LX are used to create journal entries in EGLi. The Infor LX integration system parameters allow you to specify whether CEA or EGLi is your primary financial product.

We recommend that you select CEA while you test the integration. The primary financial product flag and the CEA migration programs are designed to assist existing CEA clients with their implementation of EGLi. Journals are produced in both GL systems so you can verify that the data in both GL systems are the same. This integration includes migration programs that copy your existing CEA files to corresponding EGLi files. After you run the migration programs, EGLi should be configured and ready to use. If you are already running IDF via Ming.le or SiW, before you install EGLi, you will need to see the Ming.le integration guide for instructions on how to export EGLi tasks from IDF to SiW/Ming.le.

Learn More > Infor LX Integration Guide for Enterprise General Ledger

Previous Article Analytics Dashboard: Up-to-Date Reports Help You Make Good Decisions For Your Business
Next Article Learn how MES can benefit your company in 2020 by simply doing all of these things...
Print
32005 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

In previous releases of LN, the Assembly Control Bill of Material (BOM) offered limited flexibility. For each end item configuration, users were required to create unique Engineering Modules, which are used to determine the assembly parts that are consumed in a specific Line Station during a specific operation.

If LN is integrated with Design Studio, previously called Infor CPQ, BOM structures can be maintained in Design Studio for Assembly Control. These structures can include non-configurable parts that are directly linked to configurable items. When communicating these structures to LN using the Assembly Control, Product Variant Structure (tiapl3510m000) session, the structures were rejected because non-configurable parts were not supported by the session logic.

In this release, BOM structures that include non-configurable parts can now be accepted in LN. Consequently, if LN is integrated with Design Studio, it is no longer required to use the Engineering Module. Using the Engineering Module has become optional.

First4950515254565758Last

Theme picker

Categories