title: What are the pros and cons of typing interface method parameters generic to make the interface more accessible?
body: <p>I have an application that creates xml strings from abap structures using many different simple transformations and consequently many different abap structures.</p>
  <p>I want to use a more flexible OO approach with an Interface to do this but due to the different structures the method signatures importing parameter is always different.</p>
  <p>What are the pros and cons of typing the importing parameter generic instead so I can implement one method from one interface in each class handling the different transformations?</p>
  <pre><code>INTERFACE if_transformer.
    METHODS transform_xml
      IMPORTING isource_structure TYPE REF TO data
      RETURNING VALUE(rxml_string) TYPE string.
  ENDINTERFACE. 
  
  ...
  
  CLASS material_transformer definition.
    PUBLIC SECTION.
      INTERFACES if_transformer.
  ENDCLASS.
  
  CLASS material_transformer IMPLEMENTATION.
  METHOD if_transformer~transform_xml.
    FIELD-SYMBOLS &lt;structure&gt; TYPE concrete_structure.
    ASSIGN isource_structure-&gt;* TO &lt;structure&gt;.
    ...
  ENDMETHOD.
  ENDCLASS.
  
    
  </code></pre>