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 DAY: MATERIAL REQUIREMENT DATES AND LEAD TIME OFFSETS IN MRP

The system automatically performs offsets for requirements dates for components in the MPS/MRP calculations. It also performs offsets for calculation of material need dates at the time that shop orders are released.

To calculate the offset, the system takes the parent lead time from the Item Master and adjusts it by the bill of materials offset (plus or minus) for the component. This gives the lead time days for that specific component. The system starts with the due date of the parent and backs up and skips all non-workdays in the shop calendar.

Note that the offset calculation uses only calendar records that have a blank work center (the calendar record applies to all work centers). See the information for the Shop Calendar Maintenance program, SFC140, in your Shop Floor Control documentation for shop calendar details.

Previous Article Infor LN 10.4.1 Release Notes
Next Article Key Solution Strengths For Process Manufacturers
Print
39709 Rate this article:
No rating
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

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories