Kathy Barthelt / Wednesday, December 10, 2014 / Categories: Infor LN & Baan Tips Baan/LN Tip of the Week: Product Configurator - Part 2 Baan Tips 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. What other modules will be affected? Quotes, sales orders and projects. PRP planning for the configured items. Managing changes to the configuration. Who, what and when? Variant statistics. 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 107217 Rate this article: 3.0 Tags: Baan TipsERP LN TipsInfor LN TipsLN Tips Kathy BartheltKathy Barthelt Other posts by Kathy Barthelt Contact author Facebook page Twitter Linked In YouTube Website
10Jun2025 Infor LX / BPCS Tips & Tricks for OPERATIONS: Auto Calculate Vendor Delivery Date Tuesday, June 10, 2025 Read more Enhances purchase order efficiency by automatically calculating the Vendor Delivery Date based on user input. When a purchase order line is created, the user enters the item, order quantity, and Due Date. LX automatically calculates the Vendor Delivery Date, adding buffer time for quality control, testing, and inspection activities. If the Due Date is revised, an informational message prompts the user to review and potentially update the Vendor Delivery Date. Enhancements: A new PUR820 system parameter enables automatic recalculation of the Vendor Delivery Date. Instead of a manual reminder, PUR500 now issues a message: “Vendor Delivery Date recalculated,” showing the updated date. Benefits: Eliminates the need to manually review and update the Vendor Delivery Date. Removes the need to delete and recreate PO lines to trigger automatic date calculation. Read more
10Jun2025 Infor LX/BPCS Tips & Tricks for TECHNOLOGY: User Provisioning Tuesday, June 10, 2025 Read more Enables integration between LX and Infor OS Federation Services (IFS) to automate user provisioning. Bi-directional user synchronization between Infor OS and LX: Infor OS user creation or changes automatically create or update users in LX. IBM i user profiles can be created if needed. Updates to SYS600 user data are reflected in Infor OS. Security Role Integration: LX Security Roles and Units are published as IFS Security Roles via SyncSecurityRoleMaster BODs. LX receives inbound SyncSecurityUserMaster BODs from IFS to create or update user records in SYS600. SYS600 Exit Points trigger ProcessSecurityUserMaster BODs to request user creation or updates in IFS on behalf of LX. Available Versions: 8.3.5, 8.4.1, 8.4.2 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