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.

This enhancement provides a method to post material, labor, and overhead values on inventory postings to the general ledger to meet financial reporting requirements. The solution provides an optional further breakdown of cost by cost bucket using the new G/L Cost Type.

What would you say to someone if they never went to a doctor for a check-up, or never took their car in for regular maintenance, like an oil change?

You might say that they were asking for problems, right? The point of those check-ups is to catch a problem early, or better yet before it occurs. Going for check-ups gives you the peace of mind that things are running well and if an issue is identified early enough you can reduce overall risk. Regular check-ups can help reduce out-of-pocket expenses over time.

What about Finance, Manufacturing, Supply Chain, and Company-wide Check-Ups for your Infor ERP system? What will happen if you NEVER hit pause?

Here are some questions by department to consider.

Finance:...

There are two options for rework of serialized items. One is to define the serial numbers upfront by defining the as-built serial header before releasing the rework order. The second option is to not define serials in the as-built header and instead, the serials are defined through issuing the material to the rework order. Manually entering the serial number after release of the rework order is not supported.