Managing and Monitoring BW Requests for Mobile Clients 

Use

BW requests allow you to load data from SAP BW systems to the SAP CRM server.

Prerequisites

The BW system from which the data is to be transferred was defined on the CRM server and can be accessed from the Administration Console (see the section Settings To Be Made Once in Making Settings on the SAP CRM Server).

Features

To access the Manage and Monitor BW Requests for Mobile Clients screen, choose Environment ® Display BW Systems in the Administration Console menu. Here you can use BW requests to control, firstly, which data is called up from the selected BW systems and sent to employees working locally, and secondly, how regularly this data is to be called up.

The following functions are offered:

·         Refresh

Choose this function to update the displayed tree structure.

You can use the middleware parameter TREEEXPAND in parameter table SMOFPARSFA to specify the level to which this tree structure is expanded when it is called up or refreshed (standard setting is 2).

·         New Requests

Choose this function to expand the new requests added to the tree structure. These are all requests that are still inactive and not older than the number of days specified in the middleware parameter NEW_REQUESTS_AGE in parameter table SMOFPARSFA (default value is 1).

The requests are highlighted in different colors for ease of identification:

¡        Activated requests are not considered new and are displayed in black.

¡        Inactive, older requests are highlighted in gray.

¡        New requests are highlighted in red (if the request itself is new).

¡        If new users were found for an old request, the request is highlighted in blue.

·         Display Log

Choose this function to display the whole processing log.

·         BW Metadata

Choose this function to load into CRM existing metadata (that is, the roles including workbooks and queries) found in SAP BW and to display it graphically in a tree structure.

The name and the technical name of each of the following are displayed:

¡        The RFC destination of the BW system

¡        The role

¡        The workbook

¡        The query.

You can also see the date of the next update and how often it is repeated.

·         Request

Choose this function to send scheduled requests to the respective BW systems. The data that is sent back (workbooks and queries) is written into the tables SMOREPMA and SMOREPMAL.

·         User Links

Choose this function to make an assignment between a BW user ID and a mobile employee. This assignment is only necessary if the user ID in SAP BW differs from that on the mobile client. The mobile user MILLER should therefore also have MILLER as his/her user ID in SAP BW. Note that these user IDs are case-sensitive.

If naming conflicts occur when you are using generic variant definitions, you can enter in the BW Variant field a name that differs from the standard names for a generated variant.

You can use the Inactive column to globally deactivate the user-specific queries for individual users or individual BW systems. They can be deactivated for a given period or indefinitely (such as if a particular user is off sick or on vacation). In such cases, a note appears in the log of the request run. This deactivation does not apply to queries valid for all users or to workbooks because they are constantly available for all users.

By double-clicking a user, you call up a dialog box that allows you to load a log file from the mobile client to the CRM server. For more information, see Solving Problems on Mobile Clients).

·         Delete All Unnecessary BW Variants

You execute this function in the menu by choosing Request. This function allows you to tidy up generic variant definitions, user links, and variant assignments.

¡        Variant definitions are then deleted if no more requests exist for them.

¡        User links are deleted if the corresponding user has been removed.

¡        If generic variant definitions exist, entries under Variant in the details screens are deleted.

Deletion is not performed automatically, thereby preventing variant definitions that are no longer used from being deleted prematurely.

·         Sort

You can sort all the lists by any column. You just need to select the column and choose .

·         Setting Middleware Parameters

To set the middleware parameters for BW requests, choose Goto ® Parameter Maintenance.

·         Add BW or Remove BW

In the Requests menu, choose one of these two functions either to make available existing BW systems that are not connected or to remove a connected BW system from the display.

When you double-click a request in the tree structure, a dialog box appears in which you can make more detailed settings (see Detail Settings for BW Requests).

Activities

To edit and execute BW requests, proceed as follows in the same order:

1.       Use BW Metadata to read the information on roles, workbooks, and queries from SAP BW.

2.       Double-click a workbook request or a query request and enter the detail settings (see Detail Settings for BW Requests).

3.       Create any necessary generic variant definitions.

4.       Check whether you have entered the variant names in the right place for reading the data from SAP BW according to your needs (see Lookup for BW Variant Names).

5.       Make any necessary settings under User Links.

6.       Schedule the BW requests regularly under Request. All the data is then read from SAP BW according to the settings you made.

7.       Choose Display Log to check the processing log.