ABAP Classes

This document gives a detailed information about the classes that are generated for a project that comply with OData V4.

Introduction

The Service Builder uses patterns for separation between the generated logic and your own code. It generates two types of classes:

Base Class: The base classes contain the Service Builder generated logic. The logic in the base class is not overwritten on project regeneration. During regeneration if any error is present in the project, a warning message is displayed. Do not modify the code in this class
Extension Class: The extension class names have the suffix, EXT. An extension class is a subclass of the base class that is created once, only when the project is generated for the first time. An extension class contains no logic. Service Builder provides the extension class for you to write own code. Regenerating the project does not overwrite your code in the extension class.

When the classes are created, they are listed in the Runtime Artifacts folder of the project, as follows:

Model Provider Class (MPC): Two classes are generated for the MPC:
- MPC Implementation Class : An automatically generated class for an inherited MPC class of the specific model. You can modify the code to suit your needs
- MPC Base Class : An automatically generated class for the MPC superclass of the specific model. You cannot modify the code. The inherited MPC class is derived from this superclass.

Data Provider Class (DPC): Two classes are generated for the DPC:

DPC extension class: An automatically generated class for an inherited DPC class of the specific model. You can modify the code to suit your needs.
DPC base class: An automatically generated class for the DPC superclass of the specific model. The inherited DPC extension class is derived from this superclass.

You can edit and modify the names of the classes before they are generated.

Note After the classes have been generated, their names cannot be modified.