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

Analytics Dashboard Pre-configured views for Infor LX | BPCS | Infor LN | Baan | Infor M3

ERP Reports: Get EXACTLY what you need when you need it for as little as $125/user/month

Crossroads RMC 0 31628 Article rating: 5.0

Everyone understands the importance of ERP reporting, but what if you’re relying on the wrong reports?

Having access to ERP data in a usable format allows for a common understanding and the ability to take action based on what the data is telling you. What do you do if the way your data is presented is not useful, or flat out wrong?

How can your reports be wrong? That would mean that the data is wrong, wouldn’t it?
Not necessarily. Reports are wrong because they are stagnant. They represent the truth ONLY at the moment they are run. If that data is shared with others within your organization, the information the report(s) is trying to convey has already changed. Decisions are then made on bad information.

What is preventing you from upgrading your Infor LX or BPCS ERP System?

George Moroses 0 38929 Article rating: 5.0

Your answer to this question is likely customizations… customizations that were once the best thing since sliced bread but now have become the bane of your existence.

There is something you can do about it! 

Crossroads RMC has many options for LX & BPCS when dealing with customizations:

What is preventing you from upgrading your Infor LN or Baan ERP System?

Kathy Barthelt 0 70302 Article rating: 5.0

Your answer to this question is likely customizations… customizations that were once the best thing since sliced bread but now have become the bane of your existence.

There is something you can do about it! 

Crossroads RMC has many options for dealing with customizations:

The Importance of an Integrated System

Crossroads RMC 0 42484 Article rating: 5.0

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…

First4243444547495051Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Last

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Product Configurator - Part 2

Baan Tips

Who gets involved?
  1. Most commonly Engineering is involved in writing the rules, creating the bills and routings.
  2. Sales or Customer Service determines the questions and the order they are asked in.
  3. Sales or Customer Service determines the rules for the pricing.
  4. Sales, or Customer Service, and Engineering work together in determining the part number, description and text.

What are the steps?

  1. You must start by defining the features and options (questions and answers) and the order in which these are asked. We work this out first using sticky notes and large easel paper. Normally during the process we find that we want to move these questions around. Setting them down on paper makes the process of getting the data into Baan much more efficient. We also then have a record of what decisions were made prior to entering the data. This is normally a joint effort of Engineering and Sales. This is required and must be the first step.
  2. Constraints for features and options. These are the rules for determining what questions are asked and which options are allowed. This is generally done by Engineering or whoever is responsible for the configurator. This is required.
  3. Generic Bill of Material. All possible bill options are entered here and constraints are written to determine which options are selected based on the answers to the questions. This is generally done by Engineering or whoever is responsible for the configurator. This is a required step.
  4. Generic Routing. Similar to the bill of material, but used for generation of the routing steps. This is generally done by Engineering or whoever is responsible for the configurator. This is optional.
  5. Generic Item Data. This consists of creating custom item numbers, descriptions, text, material, size or standard fields in the custom item master. This is generally done by Engineering or whoever is responsible for the configurator though Sales may have some involvement. This is optional.
  6. Generic Pricing. This is used to calculate the selling price based on the answers to the questions. This is normally a responsibility of Sales or whoever determines the pricing. This group is also trained on writing the constraints for this section only. This is optional.

What other modules will be affected?
  1. Quotes, sales orders and projects.
  2. PRP planning for the configured items.
  3. Managing changes to the configuration. Who, what and when?
  4. Variant statistics.
  5. MPS and generic items.
Previous Article Baan/LN Tip of the Week: Product Configurator - Part 1
Next Article Baan/LN Tip of the Week: Printing Pick Lists
Print
108081 Rate this article:
3.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories