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 Tips & Tricks for TECHNOLOGY: Update User Security in IDF

Automatically synchronize security changes from LX to IDF, replacing CPYSECIDF. This new process synchronizes users in IDF with those in core LX security whenever a user’s security settings are changed. When a user is deleted from an LX environment, they can also be automatically removed from the IDF environment. Changes to a user’s access to programs in LX are mirrored in IDF. Access to Companies, Facilities, and Warehouses are also synchronized. Additionally, when Business Roles or Business Units access is changed, all users assigned to those roles or units are updated in IDF security.

Previous Article Infor LX/BPCS Tips & Tricks for OPERATIONS: Copy Shop Order
Next Article Infor LX/BPCS Tips & Tricks for FINANCE: Prevent Voiding of Selected Invoices
Print
4512 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

If you do not wish to define a detailed mapping to various ledger accounts for specific integration transactions, you can map the corresponding integration document type to a default account. All the transactions of the integration document type for which an account cannot be determined based on the mapping scheme details, are posted to the default account.

 

The mapping of an integration document type to a default account is direct, without the need for element groups and mapping elements. No distinction is made on any of the transaction details.

 

Default accounts can be used in two ways:

  • Instead of a detailed mapping to various ledger accounts. All the transactions are posted to the same account. For example, all warehouse receipts are posted to the Inventory ledger account, without any distinction.
  • In addition to a detailed mapping. If a transaction cannot be mapped based on the detailed mapping scheme, it is posted to the default account.

A cluster is a group of one or more warehouses in a particular geographical area. You can plan an item by cluster (geographical area).

To enable this, you can set up multiple plan items for one item. You always define one plan item without a cluster indication and multiple plan items with a cluster indication. A plan item with a cluster is called a clustered plan item, and a plan item without cluster is called the non-clustered plan item.

The plan items in the clusters can be supplied not only by distribution, but also through purchase and production. In this way, you can, for example, plan local purchasing in a cluster (geographical area). You can also plan supply from multiple sources.

 

Optimize Your Manufacturing Today!

First9899100101103105106107Last

Theme picker

Categories