12 a Product configurator Example and data flow

12 a Product configurator Example and data flow

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 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. © beas 2009/Page 2

Requirements for this Tutorial What you need to know n The basics of SAP n The basics be. as n Bais commercial understanding © beas 2009/Page 3

Learning Targets After working through the lesson, you will be able to: n understand the possible levels of complexity n understand the process logic n know the data flow regarding the product configuration n you got an overview on coding © beas 2009/Page 4

Agenda Explanation of product configurator 1: Possible levels of complexity 2: Decision tree (bicycle example) 3: Realization 4: Data flow 5: Coding © beas 2009/Page 5

Possible levels of complexity - Very simple - 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 © beas 2009/Page 6 - Normal - Complex - graphical surface, built up dynamically - in the item the creation of the surface is coded - based on maximum BOMs and routings - BOMs and routings are extendable dynamically - assignment of values ( via decisions YES/NO or exchange) stored in BOM and item master in appropriate fields (eg. via formulas) - assignment of values stored in BOM and item master and can be extended by be. as-scriptprogramming - Very complex - 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-scriptprogramming

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

Decision tree (Bicycle example, normal complexity) Ausführung 1. Frame 17 inches 19 inches Resulting BOM 21 inches Frame „ 19 inches“ 23 inches Wheel „ 26 inches“ 2. Wheel 26 inches Tires „Michelin“ Handlebar „M 1 (sportive“ 28 inches Light „standard“ 2. 1. Tires f. 26“ Dunlop 2. 2. Tires f. 28“ Michelin 3. Handlebar M 1 sportive Zubehör © beas 2009/Page 8 M 2 classic Dunlop Goodyear 4. Light Standard Bell „red“ 5. Bell LED 5. 1 yes red 5. 2 no blue

Agenda Explanation of product configurator 1: Possible levels of complexity 2: Decision tree (bicycle example) 3: Realization 4: Data flow 5: Coding © beas 2009/Page 9

Realization (Bicycle example, Configuration block „execution“) Configuration block: execution - Frame „ 19 inches“ - Wheel „ 26 inches“ - Tires „Dunlop“ © beas 2009/Page 10

Realization (Bicycle example, Configuration block „accessories“) Configuration block: accessories - Handlebar „Model 1“ - Light „standard“ - Bell „red“ © beas 2009/Page 11

Agenda Explanation of product configurator 1: Possible levels of complexity 2: Decision tree (bicycle example) 3: Realization 4: Data flow 5: Coding © beas 2009/Page 12

Data flow (from / to product configurator) SAP-Form Data base Call from offer or customer order Item master data STL: BOM APL: Operation PK: Definition of Product configurator-GUI STL APL PK Data for configurator Variant data Header level Row level Save configuration (as variant) © beas 2009/Page 13 Product configurator

Data flow (Creation of pre-calculation / work order Pre-calculation (be. as) Data base Item master data STL APL Variant Data Header level © beas 2009/Page 14 Row level Porcessing data (at new creation) Work order (be. as)

Agenda Explanation of product configurator 1: Possible levels of complexity 2: Decision tree (bicycle example) 3: Realization 4: Data flow 5: Coding © beas 2009/Page 15

Coding (Product configurator surface) © beas 2009/Page 16

Coding (Assignment of parameters/Variables to single fields in BOM /routing) © beas 2009/Page 17

Summary You can now: n understand the possible levels of complexity n understand the process logic n know the data flow regarding the product configuration n you got an overview on coding © beas 2009/Page 18

Thank you for your cooperation!