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 Demand-Driven Manufacturing Metrics that Drive Action - White Paper
Print
27744 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

I recently came across an article from CIO Magazine that talked about the various ways that your ERP system could be hurting your business. The single most important item on that list referenced ERP systems that weren’t integrated with other systems that housed mission-critical business data.

Having data in two (or more) systems that don’t talk to one another is like baking a pizza crust in one oven and the toppings in another. Once baked, you may have some good food to snack on, but it sure isn’t pizza! Pizza requires the cheese and sauce and spices to bake with the crust. One takes on the flavor of the other and when you take a bite, you get a complete representation of the flavors.   

That’s the value of an integrated ERP system. When you take a bite, you get a complete representation of the flavors…meaning, you get one version of the truth. Everything comes together to allow you to analyze critical business data in an efficient way with no disconnects.

Crossroads consultants have spent years developing integration expertise to tie countless different systems to Infor ERPs.

Here are some examples…

First4849505153555657Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories