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: Role-Based Security

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, 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.

Optimize Your Manufacturing Today!

Previous Article Baan/LN Tip of the Week: Strategies to Issue Materials – LN
Next Article December Lunch & Learn Webinar for BPCS & LX!
Print
26837 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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

In Baan IV, if a link with Financials exists for commissions and rebates, invoices are created directly in the Commission Control System (CMS) module and posted to Financials. As a result, users must specify the ledger accounts that are used for posting commissions and rebates in the Maintain Commission/Rebate Transaction Accounts (tdcms2101m000) session.

In LN, the Maintain Commission/Rebate Transaction Accounts (tdcms2101m000) session is removed from the Commission Control System (CMS) module, because invoices are no longer created directly in the Commission Control System module.

Project templates are useful because you can specify all of the information that you would normally want to include when creating a new project such as project structure, budget and so on.

In Baan IV/V, project templates do not exist, but you can set up a project template by creating a regular project, and setting the status to simulated or free. This is done so that the project does not create plans. Under this scenario, you can easily copy one project to another.

In LN, when you create a new project, a template can be used as the starting point. This is similar to copying a normal project, but unlike normal projects, no costs or revenues can be posted on a template.

First122123124125127129130131Last

Theme picker

Categories