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

Kathy Barthelt
/ Categories: Partner News, Infor

Infor News You Can Use | The Cloud: Even More Strategic Value

Cloud increasingly tied to better business outcomes

Infor cloud infographic

Previous Article Infor LN & Baan Tip: Propagating Unused Sub-Accounts
Next Article Infor LX / BPCS Tips & Tricks for OPERATIONS: Outside Operation Purchase Order Include Vendor Item Number
Print
4722 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

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

Here are some issues that you might run into if you stay on an old porting set too long:

  • Incompatibility because of operating system patches
  • Printing issues because of out-of-date libraries
  • Potential performance issues if binaries are not updated
  • Updating third party products may not be possible because of dependencies
  • Limited support from Infor
  • Issues with updating database software/patches because of dependencies (if database is also running on same server as application)

Need help getting on a newer porting set? Let us know! We’d be happy to help.

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error.

It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Still have GRINYA questions you need answered?
Contact us. We’d be happy to help.

Optimize Your Manufacturing Today!
 
First9394959698100101102Last

Theme picker

Categories