Skip to Content

Introduction

With Duet Sales Management, users can replicate accounts, contacts and activities from CRM to their familiar Microsoft Outlook environment. In a recent Duet Sales Management – what’s been replicated to my users ? of mine I talked about how you can check which data has been replicted to your Duet endusers. In contrast to that, this blog talks about how you can analyze the amount of data which will be replicated to your Duet users.

What would be replicated for a single user ?

In order to find out how many business objects would be replicated for a given user, you can use the report CRM_OSP_OUTPUT_15 in Duet 1.5. This report will show you exactly how many accounts, contacts and activities would be replicated for a given user. This report reads the Duet customizing for the respective replication rules and lists the number of business objects. It is important to understand that those figures are not showing you what really has been replicated for this user, it only shows what would be replicated if this user would connect from his Duet client at this moment in time. So you can use the report to test your customizing and system settings upfront; you don’t need to set up a Duet client for this user in order to find out which business objects would make it to his or her client:

image

What would be replicated for a bunch of users ?

The above mentioned report is fine if you want to verify your Duet customizing in CRM or if you want to check a single user’s data replication volume in terms of number of business objects. However, you sometimes need to answer different kind of questions, such as

  • For all of my future (or present) Duet users, how many business objects will be replicated overall?
  • For all of my future (or present) Duet users, how much data in terms of kilobytes/megabytes/gigabytes will actually be sent over the network ?
  • How much impact does Duet have on my endusers mailbox size ?

In order to answer those kinds of questions, the standard report CRM_OSP_OUTPUT_15 doesn’t help you. Therefore, I created a report called Z_DUET_SAMA_REPL_SIZE which tries to answer those questions. The report is based on the source code of CRM_OSP_OUTPUT_15 (which means that parts of the report are a result of copy-and-pasting CRM_OSP_OUTPUT_15 source code). You can find the source code at the Code Gallery Wiki.

The selection screen

image

  • Username: You can specify a single username or a collection of usernames for which the report will do analysis. If you enter a username or usernames, entering an additional role will result in a error message, the report only works if you enter users or roles, not if you enter both.
  • Rolename: You can specify a single username or a collection of usernames for which the report will do analysis. If you enter a rolename or rolenames, entering an additional user will result in a error message, the report only works if you enter roles or users, not if you enter both.
  • Size of Control Message: This value is defaulted to 20 KB and represents an average size of a Duet message.
  • Address of system user: This flag determines if the output table should display the user’s address based on the system user data (transaction su01).
  • Address of Business Partner: This flag determines if the output table should display the user’s address based on the crm business partner data (transaction bp).

The result screen

image

Each line in the ALV output table is dedicated to a single user and consists of the following columns:

  • Username: The system user name.
  • BP: The name of the mapped business partner of the system user.
  • Fullname: The full name of the user. Based on the flag you chose in the selection screen, this is the full name coming from transaction su01 or bp.
  • City: The user’s city from the address data. Based on the flag you chose in the selection screen, this is the city coming from transaction su01 or bp.
  • Accounts: The number of accounts which would be replicated for this user.
  • Contacts: The number of contacts which would be replicated for this user.
  • Activities: The number of activities which would be replicated for this user.
  • Sum: The overall number of accounts, contacts and activities which would be replicated for this user.
  • KB/MB/GB: The overall amount of data which would be replicated for this user in Kilobytes, Megabytes, Gigabytes. This is the size that is occupied in the enduser’s mailbox.

The last line in this ALV output table (the yellow one) sums up the respective columns and gives you data aggregated over all users. So you will find out how many emails will be sent out overall (=column Sum , as the overall number of business objects equals the overall number of emails which are sent by Duet. ). Another thing this line tells you is how much data volume you can expect to flow through your landscape towards the exchange server, and especially through your SAPAgent mailbox (= columns KB, MB, GB).

Since the report produces an ALV output, you can export the table to Excel or other formats and work with the data from there.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply