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

Infor M3 Tip: Personalization Tools in M3: Setting a field to be mandatory
Frank Petrasio

Infor M3 Tip: Personalization Tools in M3: Setting a field to be mandatory

This procedure describes how to make a field mandatory. A mandatory field must be completed by specifying a value. If this field is left blank, the user cannot proceed to the next panel or form.

  1. Go to the detail panel of a program.
  2. Choose the input field that you want to be mandatory. Right-click the field and select Personalize > Enable Mandatory.

Note: An asterisk (*) beside the field indicates that the field is mandatory. To disable the feature, right-click the field and select Personalize > Disable Mandatory.

Previous Article Infor LN & Baan Tip of the Week: What Am I Able to “Extend” in Infor LN?
Next Article Infor LX & BPCS Tip of the Week: Production History Purge
Print
42598 Rate this article:
5.0
Frank Petrasio

Frank PetrasioFrank Petrasio

Other posts by Frank Petrasio

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