Show TOC

Overview of Data SourcesLocate this document in the navigation structure


When you have selected the data source and created an empty Data Model, the Data Model Generator screen displays so that you can create the mapping and generate the Data Model.

At the top of the Data Model Generator screen is the name you specified for the Data Model, the menus for generating the models and switching between the Data Model Generator tool, and the Object Navigator in the ABAP Workbench.

The main screen is split into two parts; Data Source and Data Model Details.

Data Source

The left of the main screen presents the specified data source and the system alias. Find the data items such as, objects, properties, and operations you want to use from the specified data source.

Business Objects Repository (BOR) Data Source

BOR data source objects come from the SAP backend system, defined in the system alias. You can view the function modules and the BAPIs available in the system, in the data source screen.

You can display the BAPIs in alphabetical order (the default) or in a hierarchical order using the Alphabetical or Hierarchical tabs at the top.

The Alphabetical tab lists business objects (BOs) in alphabetical order. Selecting the icon in front of each business object expands it.

  • Key parameters

  • Operations (or BAPIs)

  • Parameters

Each item in the list has a different icon in front of it, similar to those in transaction BAPI.

The Hierarchical tab shows a hierarchical view of the business objects.

For more information, see Business Object Repository.

Screen Scraping Data Source

Screen Scraping data sources come from your SAP backend system. The data source screen is initially empty.

You must create recording groups in the data source screen to hold your recordings. Later, you record the transactions you want to use in your Data Model.

There are two types of objects that you can create for use in your model. These are:

  • Recordings

  • Search Help

For more information, see Screen Scraping.

Remote Function Call (RFC) Data Source

Remote Function Calls (RFC) is the standard SAP interface for communication between two SAP systems, or between an SAP system and an external system, and calls a function to be executed in a remote system.

The RFC data source screen is initially empty because there are too many function modules to display.

Select the binoculars icon to restrict the RFC display to function modules you want to use in your Data Model. You can also search for a particular function module by name.

You can display the RFC function modules in alphabetical order (the default) using the Alphabetical tab at the top.

The Alphabetical tab lists the function modules in alphabetical order. Selecting the icon in front of each function module expands it to show the following:

  • Parameters

  • Operations (or BAPIs)

To create a Data Model using RFC as your data source, you must make sure that the function modules you choose as your data source items are supported by the Data Model Generator tool.

For more information, see Remote Function Calls.

Data Model Details

The Data Model Details screen is on the right side of the data source view. It has two tabs: Structure and General Data.

General Data

The General Data tab displays read-only information about the Data Model in two sections, Identification and Technical Details.

In the Identification section, the name of the Data Model and the specified description is displayed. You can edit the description you provided.

Under Technical Details, the following displays:

  • Package:

    Specifies the objects in the ABAP Workbench that belong together. The assignment of an object to the package is recorded in the object directory (TADIR).

  • Transport Request:

    Specifies the request with which the transport will take place.

  • Transport Task:

    Specifies the number of the request or task.

  • Customizing Request:

    Specifies the changes recorded for Customizing settings and transporting them

  • RFC Destination:

    Specifies the RFC destination that points to an SAP business system. When they are assigned to SAP system aliases, that system alias points correspondingly to that business system.

  • Original language:

    Specifies the language in which the Data Model is created.

  • Created by:

    Specifies the name of the person who created the Data Model, and the date on which it was created.

  • Last Change:

    Specifies the date on which current changes were applied to the Data Model, and the name of the person who made the changes.

  • Channel Type:

    Specifies the channel type of the Data Model, either OData Channel or Generic Channel.


The Structure tab displays the following:

  • Create Mapping:

    Choose this button when you want to map an operation from the data source to the Data Model.

  • Change Mapping:

    Choose this button when you want to edit the mapped operations in the Data Model.

  • Remove Mapping:

    Choose when you want to remove mapped operations in the Data Model.

In addition, it shows the following: <Data_model – Operations> and Data Model.

The <Data_model – Operations> area displays information about the operations that are mapped to the methods from the data source. By default, it is empty.

The Data Model section of the screen displays a toolbar and the name of the Data Model as the root Data Object. By default, the root Data Object is empty.

Use the toolbar above the Data Objects section to do the following:

  • View, expand, and collapse the Data Objects and their properties within the Data Model. When expanded, it shows the keys defined for the operations and the properties, indicated by the Key icon next to it.

  • Add and remove Data Objects and Properties.

  • Select and remove selection for the operations and Properties in a Data Object.

  • Rename a Data Object or Property.

  • Display the legend for the different icons used for the content of the Data Model.

  • Set and reset the keys for an operation.

You can edit and modify the Data Model until you have the structure you require, and the appropriate fields and operations are mapped.

More Information