ConfigPanel - Mobile Application Configuration Settings

General Tab

Use the General tab to create or change basic information about a mobile application.

• Basic Data fields:

  • Mobile Application: For this required field, enter the name of the mobile application, limited to 40 characters.

  • Description: For this required field, enter a brief, easy to understand description of the mobile application, limited to 60 characters.

  • Release: Release number of the mobile application

  • Type: Type of application

• User Management Setting:

  Disable Automatic User Creation: When checked, a new user GUID is not automatically created when a new mobile client is detected in the system. The system administrator must manually create and maintain mobile users through the Administration portal.

• Server Management Setting:

  Disable Automatic Server Registration: When checked, a new server GUID is not automatically created when a new server is detected in the system. The system administrator must manually create and maintain servers through the Administration Portal.

• Life-cycle management fields:

  • Application Blocked: If set (checked), this mobile application is disabled. The mobile user can no longer connect to the back-end system for this mobile application. The xchange process is also disabled for this mobile application.

  • Effective Date and Time: The date and time this block flag takes effect.

• Inbound Transaction Management fields:

  • Inbound Transaction Active: If set (checked), you enable inbound transaction management on the back end.

  • Standard Inbound Queue ID: If you are using asynchronous inbound transaction, you can select one queue as the primary queue from the <Standard Inbound Queue ID> dropdown. Selecting a primary queue means that all transactions have the same properties and are used for simple mappings. However, out of the box, the selection dropdown is blank. Further customization is needed in the object type assignment of the primary type queue for BAPI wrapper settings, cross references, key mappings, and other settings not detailed in this guide.

• Multi Back End Setting fields:

  • Multi Back End Enabled: When checked, enables a specific mobile application to connect to multiple SAP systems, consisting of one host server and one or more satellite servers.

  • System Role: Dropdown menu listing Host or Satellite.

    A host system is the connection between SAP and the Agentry application in the SAP Mobile Platform server. The host server provides the logic to the Agentry application and functions as a bridge to the satellite servers. There can only be one host server per system.

    Satellite servers communicate with SAP through the host server.

    To complete multi back end enabled configuration, configure the host and satellite servers on the System Components tab.

Mobile Status Setting Tab

Use the Mobile Status Setting tab to map the available mobile statuses that a mobile data object (MDO) supports on the client side. If a user status also exists for the same object type, you can link it to the mobile status and the system status through this tab.

• Mobile Application Info fields:

  • Mobile Application: (Read Only) The name of the mobile application

  • Mobile Application Description: (Read Only) A brief, easy to understand description of the mobile application

  • Release: (Read Only) The release number of the mobile application

• Mobile Status Mapping fields:

  • Add Status button: Click Add Status to create a new mobile status mapping.

  • Delete Status button: Click Delete Status to delete an existing mobile status mapping. To delete a mobile mapping status, click the rectangle to the left of the Object Type column in the row you want to delete and click Delete.

  • Object Type: Object type from the Mobile Status Detail section

  • Mobile Status: Mobile status from the Mobile Status Detail section

  • System Status: System status from the Mobile Status Detail section

  • User Status: User status from the Mobile Status Detail section

• Mobile Status Details fields:

  • Object Type: The specific object in a mobile application, ex., NOTIFICATION

  • Mobile Status: Status defined by the mobile application

  • Label on Mobile: Not used

  • System Status: Standard SAP status code

  • User Status: SAP user status code as defined in SAP (note that the status code should be language-independent codes)

  • Mobile Status Alias List: Language-specific mobile status aliases can be defined

In the following example screen, the highlighted row in the mapping table indicates that if a user sets a work order to completed, the application sets the work order system status to 10072 in SAP.

If there is no system status or user status, the mobile status only affects the mobile device and does not affect the backend SAP system.

If there is a user status specified but no status profile when the mobile user sets the mobile status, the app sets that user status for the object, disregarding the status profile of that object.

If there is a user status and status profile specified when the mobile user sets the mobile status, the app sets that user status if the object uses that status profile.

Conversion Exit Setting Tab

A conversion exit is a function module that converts a value from an external format to an internal, SAP format. A conversion exit can also convert an internal SAP value to a readable, external, value, that is then displayed on a mobile device. However, you may want to completely exclude some conversion routines from your mobile application altogether. Configure those specific conversion exit settings using the Conversion Exit Setting tab.

• Mobile Application Info fields:

  • Mobile Application: (Read Only) The name of the mobile application

  • Mobile Application Description: (Read Only) A brief, easy to understand description of the mobile application

  • Release: (Read Only) The release number of the mobile application

• Conversion Exit List fields:

  • Add button: Click Add to create a new conversion exit detail. Fill in the fields in the Conversion Exit Detail section to automatically fill in the fields in this table.

  • Delete button: Click Delete to delete an existing conversion exit detail. To delete a conversion exit detail, click the rectangle to the left of the Conversion Exit column in the row you want to delete and click Delete.

  • Conversion Exit: (Read Only) Conversion exit from the Conversion Exit Detail section.

  • Active Flag (column 1): (Read Only) When checked, the Skip Conversion box is checked in the Conversion Exit Detail section

  • Skip Conversion (column 2): (Read Only) When checked, the Skip on Initial box is checked in the Conversion Exit Detail section

  • Skip On Initial (column 3): (Read Only) When checked, the Setting Scope box is checked in the Conversion Exit Detail section

  • Setting Scope: (Read Only) Conversion exit scope from the Conversion Exit Detail section

• Conversion Exit Detail fields:

  • Conversion Exit: Name of the conversion exit as found in SAP

  • Setting Scope: Choose from the dropdown menu choices:

    • All Conversion Exit: Both input and output conversion exit routines are excluded

    • Input Conversion Exit: Conversion routines are exited when data is sent to SAP

    • Output Conversion Exit: Conversion routines are exited when data is pulled out of SAP

  • Skip Conversion: When checked, the conversion routine is always exited. When you check this box, it automatically checks the box in the first Active flag column in the table above.

  • Skip on Initial: When checked, the conversion routine is only excluded when the initial field does not contain a value. If the initial field contains any value, the conversion routine runs. When you check this box, it automatically checks the box in the second Active flag column in the table.

  • Setting Enabled: When checked, the settings configured for the conversion exit are enabled and the exit is active. When you check this box, it automatically checks the box in the third Active flag column in the table.

System Components Tab

Use this tab to define system components in a multi back-end system. Configuration in this tab is not necessary if the application does not require a multi back-end system.

Parameters Tab

Use this tab to define system parameters.

• Mobile Application Info fields:

  • Mobile Application: (Read Only) The name of the mobile application

  • Mobile Application Description: (Read Only) A brief, easy to understand description of the mobile application

  • Release: (Read Only) The release number of the mobile application

• Parameter List fields:

  • Add button: Click Add to create a new parameter detail. Fill in the fields in the Parameter Detail section to automatically fill in the fields in this table.

  • Delete button: Click Delete to delete an existing parameter detail. To delete a parameter detail, click the rectangle to the left of the Parameter Group column in the row you want to delete and click Delete.

  • Parameter Group: Parameter group from the Parameter Detail section

  • Param. Name: Parameter name from the Parameter Detail section

  • Param. Value: Parameter value from the Parameter Detail section

  • Param. Scope: Parameter scope from the Parameter Detail section

  • Active Flag: When checked, the Active Flag box is checked in the Parameter Detail section

  • No Runtime Change: When checked, the No Runtime Change box is checked in the Parameter Detail section

  • Comment: Comments from the Parameter Detail section

• Parameter Detail fields:

  • Parameter Group: The group to which the parameter belongs. Groups are a means of organizing parameters. References to a parameter include both the group name and the parameter name.

  • Param. Name: The unique name of the parameter

  • Param. Scope: The scope of the parameter value. There are two options:

    • Mobile Application: Value for all users of the application

    • Mobile User: Value that can be overridden for individual users. To override a parameter value of a user, see the Administration & Monitoring portal information on parameters.

  • Param. Value: The currently configured value of the parameter. References to this parameter return the parameter value

  • Rule ID: If enabled, the ID is the rule used at runtime

  • Use Rule: When checked, you can define a rule to be used at run time

  • Rule Input Param: If the specified rule has optional parameters, define them here

  • Active Flag: When checked, the parameter is used by the mobile application. Inactive parameters are not available to the mobile application.

  • No Runtime Change: When checked, the value of the parameter cannot be overridden. The configured value is always the value. If not checked, parameter values can be overridden at runtime through synchronization processing.

  • Comment: Any comments applicable to the parameter that describe its purpose or value. Comments have no effect on the behavior of the parameter and are provided for reference purposes only.

Client Globals Tab

Use this tab to define client globals.

• Mobile Application Info fields:

  • Mobile Application: (Read Only) The name of the mobile application

  • Mobile Application Description: (Read Only) A brief, easy to understand description of the mobile application

  • Release: (Read Only) The release number of the mobile application

• Client Global List fields:

  • Add button: Click Add to create a new global. Fill in the fields in the Client Global Detail section to automatically fill in the fields in this table.

  • Delete button: Click Delete to delete an existing global. To delete a global, press the rectangle to the left of the Global Group column in the row you wish to delete and click Delete.

  • Global Group: Global group from the Client Global Detail section

  • Global Name: Client global group name from the Client Global Detail section

  • Global Value: Client global value from the Client Global Detail section

  • Global Scope: Global scope from the Client Global Detail section

  • Active Flag: When checked, the Active Flag box is checked in the Client Global Detail section

  • No Runtime Change: When checked, the No Runtime Change box is checked in the Client Global Detail section

  • Comment: Comments from the Client Global Detail section

• Client Global Details fields:

  • Client Global Group: The group to which the global belongs. Groups are a means of organizing globals. References to a global include both the group name and the global name.

  • Client Global Name: The unique name for the global

  • Global Scope: The scope of the global value. There are two options:

    • Mobile Application: Value for all users of the application

    • Mobile User: Value that can be overridden for individual users

  • Client Global Value: The currently configured value of the global. References to the global return this value.

  • Rule ID: Name of the ABAP class

  • Use Rule: When checked, the rule listed in the Rule ID field is active. If this value is active, then the Client Global Value field is not used.

  • Rule Input Param: Parameters to use with the rule. Examples include a key value pair, a user parameter, or a table.

  • Comment: Displays any comments added to the global to describe its purpose or current value. Comments have no effect on the behavior of the global and are provided for reference purposes only.

  • Active Flag: When checked, the client global is activated in the system. Inactive globals are not available to the mobile application.

  • No Runtime Change: When checked, the value of the global cannot be overridden. The configured value in the ConfigPanel is always the value. Globals without this setting can be overridden at runtime through synchronization processing.

User Attributes Tab

Use this tab to create new user attributes.