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: ERP News, Event / News, IDF

IDF News: default order class for the warehouse customer

In IDF Customers, the default order class for the warehouse customer should be a user-defined order class (base order class = 004). Do not use base order class 002 or 005, to allow for automatic invoicing of warehouse orders (if a separate manual Ship Confirm event is required per the order class, auto invoicing cannot occur from Pick Confirm).
Previous Article Can you afford not to invest in MES?
Next Article Infor OS Webinar: Developing ION API Authorized Applications Webinar – October 2, 2019
Print
21496 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

One way to save space in your general ledger is to compress integration transactions. The transactions are combined into one ledger account number, and the detail is still available in the integration transactions sessions.

The compression is seen after the transactions are finalized. 

Compression is established in the mapping scheme by checking the box under the columns “Compression of Debit/Credit Transactions. This can only be done in a mapping scheme that is not activated. 

First2627282931333435Last

Theme picker

Categories