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
54380 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

Get ahead of the curve with a seamless, comprehensive integration strategy that surpasses other competitive solutions. In part two of this webinar, join our discussion of best practice integration tricks and solutions from a fellow customer’s office of finance. Understand what makes their integration approach effective and review best practices in integrating your IBM i solution to other office of finance solutions (F9/EPM/Birst/GRC).

Hosted by Peg Tuttle from the IBM i podcast, “The Incredible i Show”. 

  • How version upgrades have tightened internal control loopholes.
  • Structural IBM i advancements designed to safeguard your organization.
  • IBM i ecosystem solutions that strengthen both data and access vulnerabilities.

Don't miss this fourth fireside chat, Eight Ways to Modernize your IBM i product – Topic #3 of 8: Best practices in integration for the office of finance (Part 2). Register today!

Register today!

Did you know that you can set up one-time vendors in LX? One Time Vendor (1,A): Specify Y to indicate that this vendor is a one-time vendor. Otherwise, could you specify N. The system removes a one-time vendor's information from the Vendor Master file after all transactions are reconciled. If this vendor already exists as a one-time vendor, you can specify N to change the vendor to a regular vendor.

FirstLast

Tips: LN | Baan

Categories