Show TOC

Function documentationInbox Maintenance

 

This function allows you to maintain values to navigate from a notification or rejection in the Inbox component of a mobile application to another component. These values are the mappings of a BDoc type to the corresponding business query.

For more information about notifications and rejections, see Rejections and Notifications.

Example Example

A rejection is triggered due to an error in data relating to the Business Partners component. When you choose the hyperlink provided in the rejection, the record containing the error appears in the Business Partners/Details tile set. This navigation is made possible by the values that you enter in the Inbox Maintenance component of Mobile System Maintenance (MSY).

End of the example.

Prerequisites

You have subscribed to the Inbox Mapping subscription for the mobile client. Only those mobile clients that have subscribed to the respective publication can receive data.

Note Note

Subscriptions determine the distribution of data to mobile clients based on previously defined publications. The assignment of a subscription to one or more mobile clients triggers the actual replication of data. For more information, see Managing Subscriptions.

Publications are logical data containers.

End of the note.

Features

  • Provides a set of predefined values

    These predefined values are provided in the consolidated database (CDB) and are downloaded to each mobile client during initial download of data.

    The predefined values are available for the following business components:

    • Components of Mobile Sales: Business Partners, Contact Persons, Opportunities, Activities, Marketing, and Sales Transactions.

      A rejection triggered for any of these business components can be resolved in Mobile Sales.

    • Components of Mobile Service: Calendar, Service Orders, Service Confirmation, and Installed Base.

      A rejection triggered for any of these business components can be resolved in Mobile Service.

  • Allows you to view existing values

    Field

    Description

    Example Value

    Transaction Name

    Name of the business document (BDoc type), for which the rejection is to be resolved

    ACTIVITY_OBJECT

    Business Component

    Short name of the business component

    ACT

    View Name

    Name of the tile set to which the user is to be directed

    ACTIVITY OVERVIEW

    Query Object Name

    Name of the business query, which can be mapped to the business document

    BSACTIVITY

    Business Object

    The corresponding business object for the business query

    BOACTIVITY is the business object for the business query BSACTIVITY

    Bus. Entity

    Name of the business component

    Activities

    Field Name

    Stores the root segment field name of the associated BDoc type of a component.

    The BDoc for the Activities component is ACTIVITY_OBJECT and the corresponding root segment field name identified is KTEXT. The value in this field is used to identify the record that was rejected or for which a notification was triggered.

    Activate Notification

    Allows you to indicate whether the values maintained are also valid for notifications

  • Allows you to create customized values

    A set of predefined values is provided for selected business components. If you want to resolve rejections for other business components in any mobile application (example: Business Partners), you can create your own values and ensure that the user is directed to the business component from which the rejection or notification was triggered.

    Note Note

    In addition, you must make changes to the rejection routine in CRM Enterprise and to the application code in Mobile Application Studio.

    End of the note.

More Information

Integrating Inbox with Business Components