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: Multi-level Shop Order Release Due Dates

Previously, Material Requirements Planning (MRP) preferred practices meant that the component’s due date was the same as the parent’s shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The user is now able change how the due date is determined for multi-level shop orders. If the Due Date of Children parameter is set to 1=Yes, the due date of the child components is the same as the release date of the parent. If the parameter is set to 0=No, the due date is the day before the release date of the parent.

Optimize Your Manufacturing Today!

Previous Article Baan/LN Tip of the Week: How is Your Productivity?
Next Article Baan/LN Tip of the Week: 5 Ways to Motivate Your Employees
Print
54320 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

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