https://community.sap.com/t5/application-development-and-automation-discussions/why-is-quot-to-access-components-using-the-interface-component-selector/m-p/12535404#M2005725 <P>For a pure Object Oriented point of view:</P><P>In the first case the instance of your object are using an interface and stay in the "contract" manage by the interface</P><P>In the second case, your instance doesn't follow any interface, you have create an instance using directly the Class. You could access all the methods proposed by all the related interfaces .... it is the jungle! </P><P>In Oo concept, all class should have one or several interfaces, and instance creation must always use interface. (and you should not have public method / data available directly in the class)</P> Tue, 15 Mar 2022 11:53:31 GMT FredericGirod 2022-03-15T11:53:31Z https://community.sap.com/t5/application-development-and-automation-discussions/why-is-quot-to-access-components-using-the-interface-component-selector/m-p/12535403#M2005724 <P>According to the sap help, it says "It is possible to access components using the interface component selector, but it is not recommended." Can anyone help me understand why is this not recommended. Below is the snippet.</P> <P><IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2031649-image.png" /></P> Tue, 15 Mar 2022 11:24:52 GMT https://community.sap.com/t5/application-development-and-automation-discussions/why-is-quot-to-access-components-using-the-interface-component-selector/m-p/12535403#M2005724 pradeep3811 2022-03-15T11:24:52Z https://community.sap.com/t5/application-development-and-automation-discussions/why-is-quot-to-access-components-using-the-interface-component-selector/m-p/12535404#M2005725 <P>For a pure Object Oriented point of view:</P><P>In the first case the instance of your object are using an interface and stay in the "contract" manage by the interface</P><P>In the second case, your instance doesn't follow any interface, you have create an instance using directly the Class. You could access all the methods proposed by all the related interfaces .... it is the jungle! </P><P>In Oo concept, all class should have one or several interfaces, and instance creation must always use interface. (and you should not have public method / data available directly in the class)</P> Tue, 15 Mar 2022 11:53:31 GMT https://community.sap.com/t5/application-development-and-automation-discussions/why-is-quot-to-access-components-using-the-interface-component-selector/m-p/12535404#M2005725 FredericGirod 2022-03-15T11:53:31Z https://community.sap.com/t5/application-development-and-automation-discussions/why-is-quot-to-access-components-using-the-interface-component-selector/m-p/12535405#M2005726 <P><A href="https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/index.htm?file=abenclass_component_glosry.htm">According to the SAP help</A>... because it's uselessly complex</P> Tue, 15 Mar 2022 17:38:54 GMT https://community.sap.com/t5/application-development-and-automation-discussions/why-is-quot-to-access-components-using-the-interface-component-selector/m-p/12535405#M2005726 Sandra_Rossi 2022-03-15T17:38:54Z