BAPI Wrapper Configuration

A BAPI wrapper is created by the application developer to expose SAP data and business logic to the mobile application. By design, the BAPI wrapper does not contain any business logic. Each BAPI wrapper is assigned to a specific method type (GET, CREATE, UPDATE, or DELETE) of an MDO to perform the required business logic. By decoupling the business logic from the BAPI wrapper, it is possible to switch MDOs without affecting the underlying mobile application definition.

The BAPI wrapper Configuration screen contains the following tabs:

  • General

  • Assignment

General Tab

Use the General tab to modify general settings for a selected BAPI wrapper.

  • BAPI Wrapper Info fields:

    • BAPI Wrapper Name: Technical name of the Remote Function Call (RFC) function module defined in the system

    • Description: Description of the BAPI wrapper, limited to 60 characters (required)

    • Function Group: Function group to which the BAPI belongs

    • Function Group Description: Description of the function group, limited to 60 characters

    • Package: SAP group to which the function group and the BAPI wrapper both belong

  • Technical Info: The Technical Info, or BAPI wrapper list, provides an expandable tree of the available BAPI wrapper function groups and the BAPI wrapper names associated with each function group. Use the arrows to the left of the function name to display all BAPI wrapper names under the function group.

Assignment Tab

Use the Assignment tab to hook up BAPI wrapper assignments to mobile data objects. In this tab, you can change the assignment of a BAPI wrapper to specific mobile data objects, assign a new mobile data object to the BAPI wrapper, or delete a mobile data object assignment from the BAPI wrapper.

  • BAPI Wrapper Info fields:

    • BAPI Wrapper Name: Technical name of the Remote Function Call (RFC) function module defined in the system

    • Description: Description of the BAPI wrapper, limited to 60 characters (required)

  • Mobile Data Object Assignment List:

    • Mobile Data Object Assignment table: Table that displays which mobile data objects are assigned to each BAPI wrapper. All column information is replicated in the Assignment Detail section below the table.

      To highlight an individual row, click the gray square to the left of the Mobile Application column in that row.

  • Assignment Detail fields: Information in these fields changes depending on which row you highlight in the Mobile Data Object Assignment List table

    • Mobile Application: The specific mobile application and its release number. This field is noneditable

    • Mobile Data Object ID: The name of the mobile data object in a dropdown field

    • Description: A brief, easy to understand description of the mobile data object, limited to 60 characters. This field is noneditable

    • Method Type: Mobile data object method (GET, CREATE, UPDATE, or DELETE) that is assigned to the BAPI wrapper

    • Active Flag: When checked, the mobile data object is in an active state. If unchecked, the mobile data object performs no actions

    • Default Assignment: When checked, the specific mobile data object assigned to that BAPI wrapper is primary. If no mobile data object ID is specified in the standard BAPI wrapper input parameter <IS_BAPI_INPUT-DO_ID>, then the primary mobile data object is used during runtime.

      It is possible to assign multiple MDOs to the same BAPI in a single mobile application.

      To override the default MDO assignment at runtime and to specify the desired MDO, define the <DO_ID> field in <IS_BAPI_INPUT>.