0
October 2010<br />Four VC Modeling Challenges<br />Lawrence Matusek<br />Managing Partner<br />eLogic Group LLC<br />lmatu...
2<br />Who We Are<br /><ul><li>eLogic provides full-service business solutions that allow companies to simplify and automa...
Our organization, methodologies and tools are tailored to enable a rapid and efficient adoption of proven breakthrough pra...
eLogic brings specialized expertise in sales channel, product, information technology and change management needed to tack...
By leveraging industry best practices, eLogic can guarantee dramatic improvements in productivity, cycle-time and quality ...
For more information, please visit our website at www.elogicgroup.com</li></li></ul><li>3<br />The Four Challenges are…<br...
4<br />A Simple Example – Piping Network<br />Up to 9 instances comprised of the following piping components<br />Straight...
5<br />Sample Configuration 1<br />6 Components:<br />#1: Straight Pipe<br />#2: Elbow<br />#3: Elbow<br />#4: Straight Pi...
6<br />Sample Configuration 2<br />5 Components:<br />#1: Straight Pipe<br />#2: Reducer<br />#3: Elbow<br />#4: Straight ...
7<br />Let’s Start with the Type 300 Classes<br />The Piping Network Material will use a class (PIPE_NETWRK) with these ch...
8<br />Here is our Class Hierarchy for Components<br />This design is flexible and makes our constraints easy to write.<br />
9<br />Let’s Impose Some Simple Constraints<br />Straight Pipes and Elbows are Constant Diameter– DIA_1 must equal DIA_2 f...
10<br />Let’s Impose Some Simple Requirements<br />KISS Design – Each piping component has the same characteristics and bi...
11<br />Let’s Create the BOM Structure<br />Option 1:  BOM contains every possible component for each instance<br />PIPE_N...
Not very elegant but easy enough to understand
Maintenance looks painful especially if component types or positions are added</li></li></ul><li>12<br />Let’s Try a More ...
BOM explosion will fail if overwritten component MATNR is invalid in plant
Each component material that can be used must generally appear as a BOM component at least once to avoid low level code is...
Component type mapped from root to BOM item by a procedure or constraint
Maintenance is modular and straightforward
Class node user exits add very powerful capabilities
This option does not appear to work for this example for technical reasons</li></li></ul><li>14<br />Let’s Constrain the S...
Upcoming SlideShare
Loading in...5
×

Four SAP VC modelling Challenges

2,147

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,147
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
104
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Four SAP VC modelling Challenges"

  1. 1. October 2010<br />Four VC Modeling Challenges<br />Lawrence Matusek<br />Managing Partner<br />eLogic Group LLC<br />lmatusek@elogicgroup.com<br />1<br />
  2. 2. 2<br />Who We Are<br /><ul><li>eLogic provides full-service business solutions that allow companies to simplify and automate core business processes.
  3. 3. Our organization, methodologies and tools are tailored to enable a rapid and efficient adoption of proven breakthrough practices in quote and order simplification / automation.
  4. 4. eLogic brings specialized expertise in sales channel, product, information technology and change management needed to tackle the most complex configurable and engineered product environments.
  5. 5. By leveraging industry best practices, eLogic can guarantee dramatic improvements in productivity, cycle-time and quality with improved customer satisfaction.
  6. 6. For more information, please visit our website at www.elogicgroup.com</li></li></ul><li>3<br />The Four Challenges are…<br />Dynamic BOM Structure – The super BOM may not directly contain all configurable components at design time<br />Adjacency Restrictions – Relationships among configurable materials are based on the manner in which they are connected<br />Summation – Sum the value of numeric characteristics within a multi-level configuration<br />Multiple Instances of the Same KMAT – The multi-level configuration will contain the same configurable material configured in different ways under the same sales document item<br />…using Compatible Mode Configuration<br />
  7. 7. 4<br />A Simple Example – Piping Network<br />Up to 9 instances comprised of the following piping components<br />Straight Pipe (STRT_PIPE)<br />Elbow (ELBOW)<br />Reducer (REDUCER)<br />
  8. 8. 5<br />Sample Configuration 1<br />6 Components:<br />#1: Straight Pipe<br />#2: Elbow<br />#3: Elbow<br />#4: Straight Pipe<br />#5: Reducer<br />#6: Straight Pipe<br />
  9. 9. 6<br />Sample Configuration 2<br />5 Components:<br />#1: Straight Pipe<br />#2: Reducer<br />#3: Elbow<br />#4: Straight Pipe<br />#5: Reducer<br />
  10. 10. 7<br />Let’s Start with the Type 300 Classes<br />The Piping Network Material will use a class (PIPE_NETWRK) with these characteristics.<br />COMPONENT_QTY Number of components in network<br />COMPONENT_1 Type of component 1 (e.g. elbow, reducer, etc.)<br />COMPONENT_2 Type of component 2<br />And so on…<br />Each Piping Component Material will have its own class that is subordinate to a superior class P_COMPONENT shown below. <br />DIA_1 Diameter of the first end (in millimeters)<br />DIA_2 Diameter of the second end (in millimeters)<br />LENGTH Length of the component (in meters)<br />INSTANCE Instance number assigned to a component<br />
  11. 11. 8<br />Here is our Class Hierarchy for Components<br />This design is flexible and makes our constraints easy to write.<br />
  12. 12. 9<br />Let’s Impose Some Simple Constraints<br />Straight Pipes and Elbows are Constant Diameter– DIA_1 must equal DIA_2 for each instance of a straight pipe or elbow<br />Reducers are Variable Diameter– DIA_1 must not equal DIA_2 for any instance of a reducer<br />Components have the Same Diameter at their Connections –DIA_2 of the preceding component must equal DIA_1 of the succeeding component<br />
  13. 13. 10<br />Let’s Impose Some Simple Requirements<br />KISS Design – Each piping component has the same characteristics and bill of materials (i.e. make the design as modular as possible)<br />Fabricate and Assemble the Components – Each piping component must be fabricated from blanks (raw materials) and then welded together to form the finished piping network<br />Total Length of Piping Network– Must calculate the total length of the piping network<br />
  14. 14. 11<br />Let’s Create the BOM Structure<br />Option 1: BOM contains every possible component for each instance<br />PIPE_NETWORK<br /> 0010 N STRAIGHT_PIPE<br /> 0010 N ELBOW<br /> 0010 N REDUCER<br /> 0020 N STRAIGHT_PIPE<br /> 0020 N ELBOW<br /> 0020 N REDUCER<br /> And so on… (7 more groups)<br /> 0100 N DUMMY<br />Commentary<br /><ul><li>All components for a given instance must have the same BOM item number (and are mutually exclusive)
  15. 15. Not very elegant but easy enough to understand
  16. 16. Maintenance looks painful especially if component types or positions are added</li></li></ul><li>12<br />Let’s Try a More Concise BOM Structure<br />Option 2: BOM contains one item for each possible instance<br />PIPE_NETWORK<br /> 0010 N STRT_PIPE<br /> 0020 N ELBOW<br /> 0030 N REDUCER<br /> 0040 N REDUCER<br /> 0050 N REDUCER<br /> 0060 N REDUCER<br /> 0070 N REDUCER<br /> 0080 N REDUCER<br /> 0090 N REDUCER<br /> 0100 N DUMMY<br />Commentary<br /><ul><li>BOM item component (IDNRK) is overwritten by dependency
  17. 17. BOM explosion will fail if overwritten component MATNR is invalid in plant
  18. 18. Each component material that can be used must generally appear as a BOM component at least once to avoid low level code issues</li></li></ul><li>13<br />Let’s Try an Advanced BOM Structure<br />Option 3: Use Type 300 Class Node for each Piping Component<br />PIPE_NETWORK<br /> 0010 K COMPONENT_TYPE<br /> 0020 K COMPONENT_TYPE<br /> 0030 K COMPONENT_TYPE<br /> 0040 K COMPONENT_TYPE<br /> 0050 K COMPONENT_TYPE<br /> 0060 K COMPONENT_TYPE<br /> 0070 K COMPONENT_TYPE<br /> 0080 K COMPONENT_TYPE<br /> 0090 K COMPONENT_TYPE<br /> 0100 N DUMMY<br />Commentary<br /><ul><li>Multiple classification of KMATs is needed
  19. 19. Component type mapped from root to BOM item by a procedure or constraint
  20. 20. Maintenance is modular and straightforward
  21. 21. Class node user exits add very powerful capabilities
  22. 22. This option does not appear to work for this example for technical reasons</li></li></ul><li>14<br />Let’s Constrain the Straight Pipe and Elbow <br />For each instance, starting and ending diameter must be equal<br />OBJECTS: <br />C IS_A (300) ELBOW.<br />RESTRICTION: <br />C.DIA_1 = C.DIA_2.<br />INFERENCES: <br />C.DIA_1, C.DIA_2.<br />
  23. 23. 15<br />Let’s Constrain the Reducer<br />For each instance, starting and ending diameter must not be equal<br />OBJECTS: <br />C IS_A (300) REDUCER. <br />RESTRICTION: <br />C.DIA_1 <> C.DIA_2.<br />
  24. 24. 16<br />Let’s Constrain the Connections<br />Option 1: Use PART_OF statement<br />Commentary<br /><ul><li>Syntax is easy but each connection requires a separate restriction
  25. 25. Maintenance needed for additional connections</li></ul>OBJECTS: <br />PN IS_A(300) PIPE_NETWRK,<br />C1 IS_A(300) P_COMPONENT,<br />C2 IS_A(300) P_COMPONENT.<br />RESTRICTION: <br />C1.DIA_2 = C2.DIA_1<br /> IF PART_OF( C1, PN, ‘0010’) AND PART_OF( C2, PN, ‘0020’),<br />C1.DIA_2 = C2.DIA_1 <br /> IF PART_OF( C1, PN, ‘0020’) AND PART_OF( C2, PN, ‘0030’),<br />And so on… (6 more restrictions)<br />INFERENCES:<br />C1.DIA_2, C2.DIA_1.<br />
  26. 26. 17<br />Let’s Constrain Connections Another Way<br />Option 2: Use an instance characteristic in constraint condition<br />OBJECTS: <br />C1 IS_A(300) P_COMPONENT,<br />C2 IS_A(300) P_COMPONENT.<br />CONDITION: <br />C1.INSTANCE = C2.INSTANCE + 1.<br />RESTRICTION: <br />C1.DIA_2 = C2.DIA_1.<br />INFERENCES:<br />C1.DIA_2, C2.DIA_1.<br />Commentary<br /><ul><li>Each instance characteristic is set by procedure or constraint (there are easy ways to do this)
  27. 27. This option scales well but watch performance in very large models</li></li></ul><li>18<br />Let’s Add Up the Lengths<br />Use native SUM_PARTS statement<br />Commentary<br /><ul><li>Native approach is not very elegant
  28. 28. Sums all components (no conditions)</li></ul>SUM_PARTS( $PARENT, LENGTH)<br />From the SAP help:<br /><ul><li>The procedure can only be processed properly if all the relevant BOM components are known in the configuration. For this reason, only process the procedure at the end of the BOM explosion.
  29. 29. You can create a configurable dummy material to use as the last item in a BOM.
  30. 30. You use a constraint to transfer this value to the superior characteristic</li></li></ul><li>19<br />Let’s Build It<br />If each component in the pipe network is built to order, then how are different instances of same piping component managed?<br />Look at transaction MD04<br />Commentary<br /><ul><li>Multiple requirements for same component configured differently in the same sales item may present an IM issue (i.e. GR/GI)
  31. 31. Reservations are managed properly with individual configurations</li></li></ul><li>20<br />What do we do now?<br />Summary of Workarounds:<br />The requirement is not sent on the upper level (but at lower levels)<br />A separate material is created for each lower-level configurable material<br />Lower-level configurable materials are defined as phantom assemblies<br />Lower-level configurable materials are switched to direct production<br />
  32. 32. 21<br />What does all that mean for our example?<br />The requirement is not sent on the upper level<br />Each pipe component must have its own sales order item and the pipe network must be field assembled (i.e. not in the factory)<br />A separate material is created for each lower-level material<br />Example: REDUCER_INST1, REDUCER_INST2, and so on<br />Lower-level materials are defined as phantom assemblies<br />The pipe network and its components are all built under a single production order (orders for individual components are not possible)<br />Lower-level materials are switched to direct production<br />The pipe network and its components all have separate production orders, but component inventory is not managed in sales stock<br />And what if you don’t like these options?<br />
  33. 33. 22<br />Talk with eLogic @ (585) 506-4600 <br />This presentation only scratches the surface of how these problems can be solved. A few solutions that eLogic has implemented:<br />Order BOMs with Instantiation – Allows ad hoc addition / deletion of configurable assemblies in a configuration and supports matching and automatic creation of assembly material variants<br />Manual Sales Sets – Like order BOMs, allows ad hoc addition and deletion of configurable assemblies as sales items in a configuration <br />Custom Summing Functions – Sum values conditionally (i.e. not all materials in BOM) and without a dummy material in the BOM<br />Configuration Browser Modifications – Show material descriptions by default and change descriptions by dependency<br />http://elogicgroup.com/<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×