12a Product configuratorExample and data flow
© beas2009/Page 2
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.
© beas2009/Page 3
Requirements for this Tutorial
What you need to know The basics of SAP The basics be.as Bais commercial understanding
© beas2009/Page 4
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
© beas2009/Page 5
Agenda
Explanation of product configurator
1: Possible levels of complexity
2: Decision tree (bicycle example)
3: Realization
4: Data flow
5: Coding
© beas2009/Page 6
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
- -Normal Complex
-
- 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 orexchange) 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
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-script-programming
© beas2009/Page 7
Agenda
Explanation of product configurator
1: Possible levels of complexity
2: Decision tree (bicycle example)
3: Realization
4: Data flow
5: Coding
© beas2009/Page 8
Zubehör
Ausführung
Decision tree(Bicycle example, normal complexity)
1. Frame
17 inches 19 inches
2. Wheel
2.2. Tires f. 28“
GoodyearDunlop
26 inches 28 inches
2.1. Tires f. 26“
Dunlop Michelin
3. Handlebar
M1 sportive Standard
red
Resulting BOM
Frame „19 inches“
Wheel „26 inches“
Tires „Michelin“
Handlebar „M1 (sportive“
Light „standard“
Bell „red“
21 inches 23 inches
4. Light 5. Bell
M2 classic LED
blue
5.1 yes 5.2 no
© beas2009/Page 9
Agenda
Explanation of product configurator
1: Possible levels of complexity
2: Decision tree (bicycle example)
3: Realization
4: Data flow
5: Coding
© beas2009/Page 10
Realization(Bicycle example, Configuration block „execution“)
Configuration block: execution
- Frame „19 inches“
- Wheel „26 inches“
- Tires „Dunlop“
© beas2009/Page 11
Realization (Bicycle example, Configuration block „accessories“)
Configuration block: accessories
- Handlebar „Model 1“
- Light „standard“
- Bell „red“
© beas2009/Page 12
Agenda
Explanation of product configurator
1: Possible levels of complexity
2: Decision tree (bicycle example)
3: Realization
4: Data flow
5: Coding
© beas2009/Page 13
Data base
Item master data
STL APL PK
Product configurator
STL: BOMAPL: OperationPK: Definition of Product configurator-GUI
Header level
Row level
Variant data
Data for configurator
Save configuration (as variant)
Call from offer or customer order
Data
SAP-Form
Data flow (from / to product configurator)
© beas2009/Page 14
Data base
Item master data
STL APL
Work order (be.as)Header
levelRow level
Variant Data
Porcessing data
(at new creation)
Pre-calculation (be.as)
Data flow (Creation of pre-calculation / work order
© beas2009/Page 15
Agenda
Explanation of product configurator
1: Possible levels of complexity
2: Decision tree (bicycle example)
3: Realization
4: Data flow
5: Coding
© beas2009/Page 16
Coding (Product configurator surface)
© beas2009/Page 17
Coding (Assignment of parameters/Variables to single fields in BOM /routing)
© beas2009/Page 18
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
Thank you for your cooperation!