Show TOC

Function documentationRapid Applications Based on Database Tables

 

To create, edit, or delete a rapid application, you have the following options:

  • In the work center Administration, you choose Start of the navigation path Manage Rapid Applications Next navigation step Rapid Application Next navigation step Create from DB Table End of the navigation path.

  • In the page configuration, choose Start of the navigation path Embedded Views Next navigation step Display All Next navigation step Rapid Applications Next navigation step Create from DB Table End of the navigation path.

Features

The function is provided in the form of a guided activity that guides you through the process of creating or changing a rapid application. Within the process, you can navigate backwards and forwards as required.

Creating a Rapid Application Based on Database Tables

Screen 1: Application Details

Enter the name and description of the rapid application. The rapid application name is used for the UI object type.

Show Technical Details: The fields Search Page Target ID and Target ID (for creation pages) are filled automatically. You can enter a name of up to 10 characters.

Authorization Group: If you enter an authorization group, the system performs an authorization check. For more information, see Creating and Editing User Master Records.

You can choose from the following options:

  • You can leave the field empty. If you do so, the system does not perform an authorization check.

  • You can choose an authorization group. The system checks this in the standard implementation with authorization object S_TABU_DIS.

  • You can modify the authorization check with Business Add-In (BAdI) BAdI: Authorization Check (AXT_RT_TABLES_AUTHORITY_CHECK). The authorization check is performed for the following activities, with the following constants:

    • Change: GC_ACTIVITY_CHANGE

    • Display: GC_ACTIVITY_DISPLAY

    • Lock: GC_ACTIVITY_LOCK

    • Save: GC_ACTIVITY_SAVE

    • Delete: GC_ACTIVITY_DELETE

    • Create: GC_ACTIVITY_CREATE

    The constants are in class CL_AXT_TABLES_BUSINESS_API.

Screen 2: DB Model

You can choose from the following options:

  • You can choose Add to select existing database tables or database views. If you want to use several database tables as a basis, enter the relationship hierarchy of the tables.

    When you select an existing table, you can overwrite the description. By default, the system uses the table description as the title of the assignment block. Select a table to display the corresponding table fields in the Field List block.

  • You can choose New to create a new database table.

    Select the table to create the table fields in the block Field List.

Note Note

You cannot add an ABAP Dictionary table as a subordinate table of a new table.

End of the note.

Under Cardinality, you specify how many relationships an object can have:

  • 1: N Table View

    This relationship specifies that the table contains an unlimited number of entries.

  • 1: 1 Form View

    This relationship specifies that the table contains one entry for every parent object.

    The cardinality determines whether you create a view as a form view or table view during UI modeling.

If you create a new database table or select an existing database table, the following applies:

  • New database tables

    Logical Key: When you create a new database table, you define the logical key. Superordinate tables need a logical key; you can optionally define a logical key for subordinate tables.

    All fields that are available as keys in the database table are activated as search criteria by default.

    If you have created a new database table, you define the field details. For more information, see Adding Fields. In addition to the field types described there, you can use field type Long Text. For more information on this field type, see Adding Tables.

  • Existing database tables

    Note Note

    Existing database tables can only be part of one rapid application.

    End of the note.

    Enable: If you activate fields here, these fields will subsequently be available in the UI configuration. You cannot deactivate key fields.

    Logical Key: You cannot change database keys. You cannot change these fields, with the exception of the option Render/Validate As. For fields that are not key fields you can also change the Search Criteria checkbox.

    Note Note

    The following restrictions apply to existing database tables (ABAP Dictionary tables):

    • The table must have the same namespace as the rapid application. To ensure data integrity, you cannot access existing SAP tables via rapid applications.

    • Only transparent tables and database views are supported. If a database view contains several tables, only read access is possible.

    • Each database field must use a data element.

    • If one key field of a table is not supported, the entire table is not supported.

    • The reference fields for currency and quantity must be in the same table.

    • The following field names must not be contained in the table:

      • RECORD_ID

      • PARENT_ID

      • DATE_FROM

      • DATE_TO

      • RECORDMODE

      • TIMESTAMP

      • KEY

      • OBJECT_ID

      • KZ

      • TR_USER

      • TR_ID

      • TR_STATUS

      • TIMESTAMP

      • DELETED

      • TR_ROOTID

      • SFACUS

      • SFAPARENT

      • SOURCE

      • OLD_KEY

      • The reserved field names in the table TRESE

    • The following data types are not supported:

      • VARC: Character string of variable length

      • PREC: Accuracy of field QUAN

      • LCHR: Long character string, requires preceding field INT2

      • LRAW: Long byte string, requires preceding field INT2

      • ACCP: Posting period (YYYYMM)

      • CLNT: Client

      • RSTR: Byte string of variable length

      • SSTR: Short character string of variable length

      • RAW: Byte string, cannot be displayed in WebClient UI

      If a table contains these data types in a field that is not a key field and the table semantics allow it, you can ignore this field and use the other fields.

    End of the note.

Screen 3: UI Model

Here you define the UI model of the rapid application.

You can choose from the following options:

  • If you choose Auto Create, the system derives the UI model from the database model.

  • You can add UI elements manually.

    If you have not selected a UI element, you can only add a search page, overview page, and an embeddable search. To add the other UI elements, you must have already selected a UI element as a parent element.

If you choose Start of the navigation path More Next navigation step Details End of the navigation path, you can define the following for each UI element:

  • Field that acts as the navigation link from the search results page to the overview page

    Here you determine in which column of the results table of the rapid application the entries act as links. You use the links to access the overview page of the corresponding data record.

  • Whether the UI element data is editable

  • Whether the UI element data can be deleted

Alias: The alias is assigned automatically, based on the name you defined in the previous step. It is used as the basis for names of the generated UI elements.

Select a UI element to display the related fields. Here you can specify the field details that affect the UI.

Render/Validate As: Here you can determine the display, for example, as selection list, e-mail address, hyperlink. For more information, see Adding Fields.

Search Criteria: Here you select whether you can assign the database table fields to fields in the application when embedding the rapid application. These fields are also available as search criteria in the advanced search of the standalone variant. The database key is automatically inserted as a search criterion.

To display or edit additional field details, select a field and choose Details.

Screen 4: Profile Customizing

In this step you define the access type used for the rapid application. You can assign the rapid application to a navigation bar profile. To do so, you add the business role for which you want the rapid application to be available. In the Create Logical Link column, you define the logical link to the create page. In the Search Logical Link column, you define the logical link to the search page. You choose the level on which you want to include the rapid application in the navigation bar: work center, work center link group, direct link group. For each of these levels, the following methods of inserting a rapid application are available:

  • Navigation Bar Profile

    The rapid application is hidden by default but can be displayed via the Customizing of the business role. For more information, see the Customizing documentation for UI Framework under Start of the navigation path Business Roles Next navigation step Define Business Role End of the navigation path.

  • Navigation Bar Profile and Business Role

    The rapid application is displayed for the business role.

Here you define the Customizing settings for the business role and the navigation bar profile. If you want to make additional settings for the navigation bar profile, you make these in Customizing for UI Framework under Start of the navigation path Technical Role Definition Next navigation step Define Navigation Bar Profile End of the navigation path. For more information, see the Customizing documentation.

To transport the Customizing settings, proceed as follows, depending on the client settings:

  • If the client settings do not allow you to create and transport Customizing settings, you create only the required metadata with the tool. To generate and transport the Customizing settings, use report AXT_EXT_GENERATE_CUST in the Customizing client or choose the Regenerate button on the WebClient UI.

  • If the client settings allow you to create but not transport Customizing settings, you create the Customizing settings with the tool. To transport the Customizing settings, use report AXT_EXT_GENERATE_CUST in the Customizing client or choose the Regenerate button on the WebClient UI.

  • If the client settings allow you to create and transport Customizing settings, you can transport the Customizing settings with a workbench request.

Note Note

You have to restart the session to make your settings visible.

End of the note.

Screen 5: Overview

Here you check your entries and choose Save and Generate. For more information about the generation, see Adding Fields.

Note Note

Generating a rapid application can take some time. An HTTP timeout may occur; however, the generation continues. For more information about error handling during generation, see Error Handling.

End of the note.

After the rapid application has been generated, the business user can use it to display, create, edit, or delete data in the underlying database.

Recommendation Recommendation

We recommend that you adapt the UI configuration of the generated UI elements.

End of the recommendation.

Note Note

The database table can contain multiple fields that use the same data element. After the generation, these fields have the same field label. The medium length variant of the data element short text is used as the field label for multiple fields. To distinguish the fields, you must define new field labels for each field in the UI configuration tool.

End of the note.
Changing a Rapid Application Based on Database Tables

You can change some properties of existing rapid applications in the guided activity.

Note Note

You cannot deactivate fields that are activated as search criteria. You can only define additional fields as search criteria.

End of the note.