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

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: Revisit The Last Brilliant Idea

Sometimes the best ideas have to be tabled due to competing priorities. That doesn’t mean that the idea was bad. Revisit previously suggested cost savings ideas, or ideas to make a manual process more efficient. Now could be the right time to do something great!

Optimize Your Manufacturing Today!

Previous Article Baan/LN Tip of the Week: Difference Between a Serialized Item and Unit Effective Item
Next Article Baan/LN Tip of the Week: Order Series Full – Switching to a Different Series
Print
19110 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

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