Hello,

Sign up to join our community!

Welcome Back,

Please sign in to your account!

Forgot Password,

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

You must login to ask a question.

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

OO ABAP

Object Oriented Programming

Share
Followers
0 Answers
15 Questions

SAP EWM Help Latest Questions

  • 0
DPM125
Beginner

An interface in ABAP defines a contract that any implementing class must follow. It contains only declarations of: Methods (without implementation) Constants Types Attributes Interfaces do not contain implementation. Any class that implements an interface must provide the logic for all its methods. Feature Description No implementation Only method ...

  • 0
DPM125
Beginner

While ABAP classes can’t inherit from multiple classes, they can implement multiple interfaces, achieving interface-based multiple inheritance. INTERFACE if1.   METHODS: method1. ENDINTERFACE. INTERFACE if2.   METHODS: method2. ENDINTERFACE. CLASS my_class DEFINITION.   PUBLIC SECTION.     INTERFACES: if1, if2. ENDCLASS. CLASS my_class IMPLEMENTATION.   METHOD if1~method1.     WRITE: 'Method1 from IF1'.   ENDMETHOD.   METHOD if2~method2.     WRITE: 'Method2 from IF2'.   ENDMETHOD. ENDCLASS.

  • 0
DPM125
Beginner

1. Single Inheritance (Supported in ABAP) Definition: One subclass inherits from one superclass. Use: Most common form of inheritance. CLASS parent_class DEFINITION.  PUBLIC SECTION.    METHODS: display.ENDCLASS.CLASS parent_class IMPLEMENTATION.  METHOD display.    WRITE: 'Parent class method'.  ENDMETHOD.ENDCLASS.CLASS child_class DEFINITION INHERITING FROM parent_class.ENDCLASS.CLASS child_class IMPLEMENTATION.ENDCLASS.

  • 0
DPM125
Beginner

Instance Members (Methods & Data) Belong to individual objects (instances). Created using DATA and METHODS. Each object has its own copy of the data. Accessed using the object reference: lo_obj->method_name. Useful when each object should maintain its own state. Destroyed when the object goes out of ...