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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

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

What is it?
The configurator consists of a set of features (questions). The options (answers) to these questions then are used to generate the custom bill of material and routing. These questions may be answered at the time of order entry, prior to order entry (in a project or quote) or after order entry (in the project). The order of the questions need not have any relationship to the bill of materials. The configurator may also calculate the selling price, create a unique “smart” item number, custom description and text. Simple rules are used to interpret the answers.

Who uses the configurator?
Companies whose products have options. The configurator eliminates the need for part numbers for all combinations of options. The configurator ensures that the pricing and bills are correct. The configurator also keeps statistics on the frequency the options are selected.
Previous Article BPCS/LX Tip of the Week: Uses for LX Bill of Material
Next Article BPCS/LX Tip of the Week: Configuration Management
Print
80089 Rate this article:
No rating

Contact

Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories