Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

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 BPCS/LX Tip of the Week: How To Capture Re-Work Time (Part 1)
Next Article Huf North America Goes Lives With Next Phase of RMC3 Data Collection
Print
122296 Rate this article:
3.0
Tags: Baan TipsERP LN TipsInfor LN TipsLN Tips

Contact

Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Note: The Blocked Operations (tisfc0540m000) session displays the blocked operations.

Introduction

Sometimes a problem occurs that must be solved before an operation proceeds. Examples of such situations are:

  • The quality of an intermediate product must first be inspected.
  • A machine is in repair.
  • A supplier cannot deliver an essential component in time.
  • A customer is late with its payments.

In these situations the operation can get the operation status Blocked.

An operation can be blocked:

  • Manually.
  • Automatically by Quality.

Blocking reasons

Every blocked operation must have a blocking reason. The blocking reason of a blocked operation has two purposes:

  • To indicate why the operation is blocked.
  • To determine which actions you can no longer perform on the operation.

Types of blocking

The following actions can be blocked by means of a blocking reason:

  • Reporting a quantity completed.
  • Reporting a quantity rejected.
  • Reporting a quantity to be inspected.
  • Reporting an operation completed.

You normally carry out these actions in the Report Operations Completed (tisfc0130m000) session.

You can define blocking reasons in the Blocking Reasons (tisfc2100m000) session.

Manual blocking

Use the Report Operations Completed (tisfc0130m000) session to block an operation. When you block an operation, you must also enter a blocking reason. If Quality has already blocked the operation, you can only enter a blocking reason, which is more restrictive than the blocking reason of Quality.

Blocking by Quality Managem

Read more

Categories