Transport of Authorizations to Mobile Clients 

Purpose

This process describes the phases involved in transporting authorizations defined on the Mobile Development Workstation (using the Authorization Management Tool) to mobile clients. This process includes:

·        Transporting authorizations from the CRM Server (in the development environment) to the CRM Server (in the production environment) using the SAP Transport Management System

·        Receiving authorizations from the production CRM Server on the mobile clients

This process enables mobile client users to work with a mobile client application according to the authorizations defined through roles.

We recommend that you to locate and view this topic in the SAP Help Portal. If you are viewing this topic on the Mobile Development Workstation, then the hyperlinks in this topic will not work. This is because the topic contains hyperlinks to other topics, which are not part of the AMT documentation. However, all these hyperlinks work properly in the SAP Help Portal.

 

Prerequisites

As a system administrator, you must have:

·        Set up a system landscape that has more than one environment. For this process, we have assumed that a system landscape with development and production environments in set up. For more information about system landscapes, refer to SAP_CRM_4.0_SystemLandscapeGuide available in mySAP Marketplace.

·        Configured the system landscape to enable transports using the SAP Transport Management System. For more information, see Transport Management System – Concept.

·        Authorization to access the development CRM Server and production CRM Server

  

Process Flow

Environment: Development

Phase 1: The system administrator performs the following activities on the CRM Server:

       1.      Executes the report SMO_AUTH_TRANSPORT_40 using the ABAP Editor. This report creates a transport request that includes the authorizations to be transported.

For more information, see ABAP Editor.

       2.      Releases the transport request using the Transport Organizer. This activity transports the authorizations via the transport request to the production CRM Server.

 

Environment: Production

Phase 2: The system administrator performs the following activities on the CRM Server:

...

       1.      Ensures that the sites created for mobile clients do not have subscriptions to the publications Authorization, Authorization1, Authorization2. If the subscriptions exist, then they must be unassigned for the respective sites using the Administration Console.

For more information, see Displaying/Changing or Deleting Subscriptions.

       2.      Executes the report SMO_AUTH_TRANSPORT_40_CLEAN using the ABAP Editor. This report deletes the authorizations, if they were transported earlier to the consolidated database.

For more information, see ABAP Editor.

       3.      Imports the transport request that has been released in the development CRM Sever using the Transport Organizer.

For more information, see Importing Requests.

       4.      Creates subscriptions to the publications Authorization, Authorization1, Authorization2 for all sites assigned to mobile clients.

For more information, see Creating Subscriptions.

 

Phase 3: Each mobile client user performs the following activity on their mobile client

Triggers ConnTrans to connect to the CRM Server in the production environment. This activity transfers the authorizations defined for the specific user, from the production CRM Server onto the mobile client.

 

See also:

Implementation of Authorizations