Skip to end of metadata
Go to start of metadata

Model View Controller design pattern is used to make our Business logic separate from the output of the information generated from Business Logic. Usually, we call this design patterns as the MVC. Here Business logic is the Model; Output of the data is the View and the link which connects the Business logic to output is the Controller.

MVC is useful when user have to select the output type or data representation type e.g. Report, Grid or List, Charts - barchart, pie chart, and so on. In this type of application, we can create a MODEL class and put our business logic into it which will be isolated from the way output is being generated. Controller class will control the information flow between the Model and Views. All the types of data representation can be created in different View classes. In turn, this view will access the Controller and than Controller will provide the data to View.

You can follow this link for more information on MVC:

  1. ABAP Objects Design Patterns - Model View Controller (MVC) Part 1 - In this part you can find the introduction on the MVC
  2. ABAP Objects Design Patterns - Model View Controller (MVC) Part 2 - In this part you will find how we can implement the MVC in ABAP using the ABAP objects (Model and Controller)
  3. ABAP Objects Design Patterns - Model View Controller (MVC) Part 3 - In the continuation with the example on implementing the MVC (Views)

Please note that all the links are out of SDN links.

All Design Patterns

Check out all design patterns