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

OTTO Q&A from the Director of Planning & Technology at Champion Industries

1.  How difficult is it to initially install OTTO?

Dead easy is the straight answer. We relied on you to install, and you installed in the predicted 1 hour.  

2.  Would you install it on a test system or on the production system?

Production system is another easy answer. I use OTTO as the ideal prototype when talking to business contacts about “add-on” products. It is non-invasive; it only reads data from our ERP files. I know the implementation is 100% safe because no ERP files are ever updated (read corrupted) by OTTO.

3.  How difficult was it to implement OTTO? Was there a negative impact on daily operations?

There is a learning curve involved in using any new tool that has value to add. OTTO implementation is very low on the impact scale, but I would strongly recommend that a prospective client plan on investing in education and practice. OTTO implementation is low impact. No valuable tool is “no impact”.

Click here to learn more about OTTO

Previous Article Is the Crossroads Analytics Dashboard Product Better than Spreadsheets?
Next Article What do you get with IDF?
Print
30337 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

To utilize the Security Rules Optimization feature, a system administrator can assign security codes to 100 pre-defined user groups. User groups are created in the Group Security Maintenance (SYS603) program. All users assigned to this group possess the same level of security.   

A system administrator can assign security codes for up to 100 of the user groups. All user groups over 100 are still administered by all security reject/allow rules assigned to them but are not able to utilize the optimized process. 

Each of the security codes and access levels are assigned to user groups and are mapped to the account strings and stored in the Account Cross Reference (CEA106D1) file.   

Once security codes have been assigned, the system administrator must: 

  • Determine which level each group is allowed access.

  • Determine which segment values/account strings are assigned to which user groups.

  • Create security rules for specific segment values/account strings and assign these groups to the created rules.

  • Select the rules to be processed.  Processing can be done in either batch mode or interactively.

  • The Security Rules flag must be on in the CEA Control Parameters program before any rules are effective. 

This feature provides a parameter that allows the user to enter expiration dates on the Inventory Transaction Posting screen, INV500, and Purchase Order Receipts screen, PUR5505, when they have received a lot controlled item that is not QMS controlled. This new field allows an expiration date to be entered and not overridden. A system parameter was added to Advanced Process Industries Parameters, API820D. When the parameter is set to Yes, a new lot expiration date is available in the Inventory Transaction Posting, INV500D2, and Purchase Order Receipts, PUR550D2, screens.

FirstLast

Tips: LN | Baan

Categories