Baan/LN Tip of the Week: Product Configurator - Part 2 Baan Tips Kathy Barthelt / Wednesday, December 10, 2014 0 107217 Article rating: 3.0 Who gets involved? Most commonly Engineering is involved in writing the rules, creating the bills and routings. Sales or Customer Service determines the questions and the order they are asked in. Sales or Customer Service determines the rules for the pricing. Sales, or Customer Service, and Engineering work together in determining the part number, description and text. What are the steps? 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. 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. 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. 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. 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. 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. Read more
10Jun2025 Infor LX/BPCS Tips for EXECUTIVES Tuesday, June 10, 2025 Read more FINANCE: Override Warning in Invoice Entry PO Costing OPERATIONS: Auto Calculate Vendor Delivery Date TECHNOLOGY: User Provisioning Read more
10Jun2025 Infor LX/BPCS Tips & Tricks for FINANCE: Override Warning in Invoice Entry PO Costing Tuesday, June 10, 2025 Read more 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. Read more
10Jun2025 Infor LN & Baan Tips & Tricks for EXECUTIVES Tuesday, June 10, 2025 Read more FINANCE: Rebuild History for Account Matching (tfgld1218m000) OPERATIONS: Copy Customized Product Structure to Standard Structure (tipcs2232m000) TECHNOLOGY: Authorization and Security: LN REST APIs Read more