12a Product configurator Example and data flow 29.07.2018

This documentation and training is provided to you by beas gmbh This documentation and training is provided to you by beas gmbh. The documents are neither approved nor in any way acknowledged or endorsed by SAP. For SAP Business One, only the documentation and training officially released by SAP shall be binding upon SAP. SAP shall not be responsible for any content of this documentation and training and this documentation and training shall not be binding upon SAP in any way. The official current SAP Business One documentation and training for SAP Business One is available at http://service.sap.com/sbocustomer/documentation and http://service.sap.com/sbocustomer/training. 29.07.2018

Requirements for this Tutorial What you need to know The basics of SAP The basics be.as Bais commercial understanding 29.07.2018

Learning Targets After working through the lesson, you will be able to: understand the possible levels of complexity understand the process logic know the data flow regarding the product configuration you got an overview on coding 7/29/2018

Agenda Explanation of product configurator 1: Possible levels of complexity 2: Decision tree (bicycle example) 3: Realization 4: Data flow 5: Coding 7/29/2018

Possible levels of complexity - - - - Very simple Normal Complex Very complex No graphical surface enter data in UDF into SBO form (measures, weight etc.) assignemt of values stored in fields in BOM and item master (formulas may be used) based on maximum BOMs and routings graphical surface, built up dynamically in the item the creation of the surface is coded based on maximum BOMs and routings assignment of values ( via decisions YES/NO or exchange) stored in BOM and item master in appropriate fields (eg. via formulas) graphical surface, built up dynamically in the item the creation of the surface is coded BOMs and routings are extendable dynamically assignment of values stored in BOM and item master and can be extended by be.as-script-programming static programmed surface (incl. functional logic), depending on the item BOMs and routings are extendable dynamically assignment of values stored in BOM and item master and can be extended by be.as-script-programming Very simple: The product configuration is realized without the grapfical surface. This is useful if the configuration is limited to a few characteristics. Parameters can be entered via UDF fields at the row level. Functional logic is stored in the BOM items and operations in the item master. Usually, this consists of formulas, variables and tables. Normal: A dynamic surface is created for the respective item via code. Based on the maximum bill of materials and operations. Functional logic is stored in BOM items and operations in the item master. This consists of formulas, variables and tables, as well as decisions yes / no or active / inactive. Complex: A dynamic surface is created and saved for the respective item. Based on the maximum bill of materials and operations, positions can be added. Functional logic is stored in BOM items and operations in the item master. This consists of formulas, variables and tables, as well as decisions yes / no or active / inactive. Very complex: A customized surface based on be.as windows is created (in PowerBuilder). Thus, almost any design can be constructed, eg. drop-down lists. In addition to maximum BOMs and operations positions can also be added. Functional logic is stored in BOM items and operations in the item master. This consists of formulas, variables and tables, as well as decisions yes / no or active / inactive. 29.07.2018

Agenda Explanation of product configurator 1: Possible levels of complexity 2: Decision tree (bicycle example) 3: Realization 4: Data flow 5: Coding 7/29/2018

Decision tree (Bicycle example, normal complexity) Ausführung 1. Frame Resulting BOM Frame „19 inches“ Wheel „26 inches“ Tires „Michelin“ Handlebar „M1 (sportive“ Light „standard“ Bell „red“ 17 inches 19 inches 21 inches 23 inches 2. Wheel 26 inches 28 inches 2.1. Tires f. 26“ 2.2. Tires f. 28“ The resulting BOM (on the right margin) represents the selection (in red) from the decision tree. The structure is divided into two independent blocks. Dunlop Michelin Dunlop Goodyear Zubehör 3. Handlebar 4. Light 5. Bell M1 sportive M2 classic Standard LED 5.1 yes 5.2 no red blue 29.07.2018

Agenda Explanation of product configurator 1: Possible levels of complexity 2: Decision tree (bicycle example) 3: Realization 4: Data flow 5: Coding 7/29/2018

Realization (Bicycle example, Configuration block „execution“) Frame „19 inches“ Wheel „26 inches“ Tires „Dunlop“ The upper block "execution" of the decision tree has been realized with the be.as Product Configurator. Operation runs from top –> down as in the decision tree. The configuration is created by selection of elements. 29.07.2018

Realization (Bicycle example, Configuration block „accessories“) Handlebar „Model 1“ Light „standard“ Bell „red“ Lower block: „accessories“, the decision tree is created by the product configurator 29.07.2018

Agenda Explanation of product configurator 1: Possible levels of complexity 2: Decision tree (bicycle example) 3: Realization 4: Data flow 5: Coding 7/29/2018

Data flow (from / to product configurator) SAP-Form Data Data base Call from offer or customer order Item master data SBO-Form: For an offer or a customer order data is called from item master . If an SBO form contains an item, for which a configuraiton was stored, the configurator can be called directly. Product configurator: For starting the configurator definitions are read out from the data base. Saving a configuration creates a new variant for a selected item. Parameters from the configurations screen are transferred to the data base. Please note, that no new BOM or routing is created for the variant. STL: BOM APL: Operation PK: Definition of Product configurator-GUI STL APL PK Data for configurator Variant data Header level Row level Product configurator Save configuration (as variant) 29.07.2018

Data flow (Creation of pre-calculation / work order Pre-calculation (be.as) Data base Item master data STL APL Porcessing data (at new creation) Variant Data Data processing: If calling the pre-calculation or creating the work order, for the variant saved in item master data, a BOM and a routing are created under consideration of the stored configuration parameters. Formulas, tables, variables, and scripts, stored in item master are used. Work order (be.as) Header level Row level 29.07.2018

Agenda Explanation of product configurator 1: Possible levels of complexity 2: Decision tree (bicycle example) 3: Realization 4: Data flow 5: Coding 7/29/2018

Coding (Product configurator surface) With simple mapping the surface of the product configuration is created. At any time during the process the results can be displayed by presing the “test” button. 29.07.2018

Coding (Assignment of parameters/Variables to single fields in BOM /routing) Parameters from the surface of the product configurator, formulas, tables, variables and scripts can be deposited in individual fields of BOM and rounting. Creating a pre-calculation or a work order, this will affect the BOM or the routing of an item. 29.07.2018

Summary You can now: understand the possible levels of complexity understand the process logic know the data flow regarding the product configuration you got an overview on coding 7/29/2018

Thank you for your cooperation! 7/29/2018