Configuration Guide SAP: Transaction Types

SAP CRM 7.0 EHP1

December 2011

English

CRM Transaction Types – Basic Settings (C20)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices CRM Transaction Types – Basic Settings (C20): Configuration Guide

Copyright

© 2012 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 22


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

1 Purpose.......................................................................................................................... 5

2 Preparation.....................................................................................................................5

2.1 Prerequisites............................................................................................................5

3 Business Process Configuration.....................................................................................5

3.1 Settings for Basic Functions....................................................................................5

3.1.1 Defining Partner Determination..........................................................................5

3.1.1.1 Defining Partner Functions.......................................................................5

3.1.1.2 Defining Access Sequence......................................................................6

3.1.1.3 Defining Partner Determination Procedure..............................................7

3.1.1.3.1 Defining Partner Determination Procedure for Activities....................7

3.1.1.3.2 Defining Partner Determination Procedure for Tasks........................8

3.2 Settings for Transactions.........................................................................................9

3.2.1 Defining BP Transaction Types..........................................................................9

3.2.2 Adjusting UI Settings for Transaction Type BP Task........................................10

3.2.3 Deactivating Standard Transaction Types........................................................11

3.2.4 Defining Item Category Determination.............................................................12

3.2.5 Defining Categories for Activities.....................................................................13

3.3 Actions...................................................................................................................13

3.3.1 Defining Action Profiles and Actions.................................................................13

3.3.2 Defining Conditions..........................................................................................14

3.4 Maintaining Organizational Data Profile.................................................................15

3.5 Assigning Profiles and Procedures to Transaction Types......................................16

3.5.1 Assigning Organizational Data Profile to Transaction Types............................16

3.5.2 Assigning Partner Determination Procedure to Transaction Types..................17

3.5.3 Assigning Action Profile to Transaction Types.................................................17

3.5.4 Assigning Category to Transaction Types........................................................18

3.5.5 Assigning Transaction Types to Categories for Activities.................................18

3.5.6 Assigning Text Determination Procedure to Transaction Types.......................19

3.6 One to One E-Mail Integration...............................................................................19

3.6.1 Defining Multipart E-Mail Option.......................................................................19

3.6.2 Assigning Transaction Types...........................................................................20

3.6.3 Activating HTTP Services.................................................................................21

3.6.4 Setting Up E-Mail Transfers from Microsoft Outlook........................................21



CRM Transaction Types – Basic Settings: Configuration Guide

1 PurposeThis Configuration Guide provides the information you need to set up the configuration of this building block manually.

2 Preparation

2.1 PrerequisitesBefore starting with the installation of this building block, please have a look at the document Quick Guide to Installing SAP Best Practices for CRM.

3 Business Process Configuration

3.1 Settings for Basic Functions

3.1.1 Defining Partner DeterminationIn this section you do the settings for partner processing. You should carry out the following:

1. Define partner functions

2. Define access sequences

3. Define partner determination procedures in which you specify an access sequence

4. Assign the partner determination procedures to the required business transaction types and item categories.

3.1.1.1 Defining Partner Functions

UseIn this activity, you define partner functions by entering short descriptions (such as pharmacist or stock options analyst), assigning them to partner function categories and entering usages, such as Customer Relationship Management or Enterprise Buyer. In some cases, you also specify a corresponding business partner relationship category.

The descriptions you enter here are displayed in the transactions that include these partner functions.

Procedure1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu Customer Relationship Management Basic Functions Partner Processing Define Partner Functions

2. Select partner function 00000015 Contact Person and set the Block indicator.



This indicator defines whether the source partner is added during partner determination for the resulting quantity. If the source does not provide a standard partner, the source partner himself becomes the standard partner. If you mark this field, the source partner is not copied with the resulting quantity.

3. Choose Save.

ResultA block indicator for the partner function contact person has been set.

3.1.1.2 Defining Access Sequence

UseThe purpose of this activity is to define a new access sequence for the determination of the partner function Sales Representative from the entered Activity Partner.



SAP CRM IMG menu Customer Relationship Management Basic Functions Partner Processing Define Access Sequences

2. Select sequence 0002, Preceding Document Business Partner Relationships: Activity Partner and copy as Y002, BP Preceding Document Business Partner Relationships: Activity Partner User with all entries.

3. Choose Copy all.

4. Go to Individual Accesses and choose New Entries:

5. Make the following entries:

Attribute Value

Batch Seq: 0040

Dialog Seq: 0040

Source Business Partner Assigned to the User

As a prerequisite for the automatic determination of the partner function Sales Representative from the Activity Partner it is necessary to maintain a relationship in the master data. Otherwise this function would be filled with the current User.

6. Choose Save.

Result

A new access sequence for partner determination has been created.



3.1.1.3 Defining Partner Determination Procedure

3.1.1.3.1 Defining Partner Determination Procedure for Activities

UseThe purpose of this activity is to define new partner determination procedures for activities both with and without triggering calendar entries.



SAP CRM IMG menu Customer Relationship Management Basic Functions Partner Processing Define Partner Determination Procedure

2. Select Procedure 00000002 Business Activities and copy as Y0000002 BP Business Activities (with all entries).

3. Select Procedure Y0000002 Activities and go to folder Partner Functions in Procedure.

4. Make a new entry for partner function 00000014 Employee Responsible (CRM) with the following data:

Attribute Value

Changeable (if Correct After Entry or Determination)

No. of Occurrences (Lowest) 1

No. of Occurrences (Highest) 1

Calendar maintenance

Changeable address

Access Sequence 0008 (Preceding Document User)

5. Create a new entry for partner function 00000012 Sales Representative (CRM) with the following data:

Attribute Value

Changeable (if Correct After Entry or Determination)




Changeable address

Access Sequence Y002 (Preceding Document User)

6. Delete the following Functions: 00000022 Person Responsible (CRM), 00000032 Attendee (CRM) and 00001000.



7. Select Partner Function Sales Representative (CRM), go to Details and change Access sequence to Y002 (BP Preceding Document Business Partner Relationships: Activity Partner User)

8. Select Partner Function Contact Person (CRM) and change the following attributes:

Attribute Value


Selection Limit (Select.Screen) 2

9. Double-click on folder User Interface Settings and make the following entries for Procedure Y0000002 Activities at Header Screen:

Partner Function1: 00000009 Activity Partner (CRM)

Partner Function2: 00000015 Contact Person (CRM)

Partner Function3: 00000012 Sales Representative (CRM)

Partner Function4: 00000014 Employee Responsible (CRM)

10. Choose Save.

11. Create a new partner determination procedure by copying the before created procedure Y0000002 to the new Y0000004 with description BP Business Activities 2.

Do not set the Calendar Maintenance indicator in step 4.

12. Save your entries.

In section Assigning Profiles and Procedures to Transaction Types the Partner Determination Procedure is assigned to the relevant transaction types.

ResultNew partner determination procedures have been created.

3.1.1.3.2 Defining Partner Determination Procedure for Tasks

UseThe purpose of this activity is to define a partner determination procedure for tasks.



SAP CRM IMG menu Customer Relationship Management Basic Functions Partner Processing Define Partner Determination Procedure

2. Select Procedure 00000003 Tasks and copy as Y0000003 BP Task (with all entries).



3. Select Procedure Y0000003 Task and go to folder ‘Partner Functions in Procedure’.

4. Make the following entries for partner function 00000014 Employee (CRM):

Attribute Value




Access Sequence 0008 (Preceding Document User)

5. Go to folder ‘User Interface Settings’ and make the following entries:

Attribute Value

Partner Function 1 00000014 Employee (CRM)

Partner Function 2 00000009 Activity Partner (CRM)

Partner Function 3 00000015 Contact Person (CRM)

6. Choose Save.

In section Assigning Profiles and Procedures to Transaction Types the Partner Determination Procedure is assigned to the relevant transaction type.

3.2 Settings for Transactions

3.2.1 Defining BP Transaction Types

UseA transaction type controls the processing of a specific business transaction. It defines the properties and characteristics (for example, sales order, service request, sales call) and defines further on the control attributes (for example, text determination procedure, partner determination procedure, status profile, organizational data profile).

A transaction type is assigned to one or several business transaction categories. This category determines the business context in which the transaction type can be used (for example, service, sales, activity). One business transaction category must be defined as the leading category. This one is not related hierarchically to other transaction categories, but represents a preference. A sales transaction with business activity data would, for example, be more likely to have sales as leading business transaction category than business activity. Depending on the leading business transaction category, only specific combinations are possible with further business transaction categories.

The purpose of this activity is to reduce and adapt the required transaction types.



SAP CRM IMG menu Customer Relationship Management Transactions Basic Settings Define Transaction Types

2. Copy the following transaction types to the new transaction types with the following description. The advantage is that the related activities will be sorted.



Trans. Type

Description New Trans. Type

English Description

German Description (optional)

0002 Incoming Phone Call Y007 BP Interaction Log BP Kontaktbericht

0005 Outgoing E-Mail Y010 BP E-Mail BP E-Mail

0020 Bus.Act.:With Prods Y020 BP Visit with Prod. BP Besuch mit Prod.

1003 Task Y030 BP Task BP Aufgabe

3. Assign new Categories and Directions to the following Transaction Types at the Customizing header level for business transaction category Business Activity.

Trans. Type Description Category Direction

Y007 BP Interaction Log 203

Y010 BP E-Mail 401

Y020 BP Visit with Prod. 201 Outbound

Y030 BP Task 101

Please check the relevant settings. For transaction types Y007 to Y010 they should already be correct (copy from standard).

4. Choose Save.

Result

Several new transaction types for activities and tasks have been created.

3.2.2 Adjusting UI Settings for Transaction Type BP Task

UseAs tasks are not only be used for interaction with customers, but also internally, it is necessary to make sure, that the entry of the account within this transaction is not mandatory for entering on the WebUI.


Transaction code BSP_WD_CMPWB

SAP CRM IMG menu Customer Relationship Management UI Framework UI Framework Definition Access UI Component Workbench

2. In field Component enter value BT125H_TASK and choose Display.

3. In the Component Structure Browser of component BT125H_TASK select the view Component Views BT125H_TASK/TaskDetails. Open this view with double-click.

4. Select tab Configuration.

5. Connect to the host server with your CRM system user and password.



6. Choose button Edit to switch from Display to Change mode and select a customizing request if necessary.

7. Choose Choose Configuration and select the existing SAP standard configuration having Config Key <DEFAULT>, Component Usage <DEFAULT>, Object Type <DEFAULT>, and Object Subtype <DEFAULT> with double-click.

8. Choose Copy Configuration and choose YES on the confirmation screen.

9. Now you can decide on which level the adapted view will be visible. Typically the view changes have to be visible on the level of a Business Role. In this case you have to select an existing Role Config. Key, i.e. YBP and choose Continue.

10. Set the cursor in the field Account.

11. Choose button Show Field Properties.

12. Deselect the radio button Mandatory.

13. Choose Apply.

14. Set the cursor in the field Contact.

15. Choose button Show Field Properties.

16. Deselect the radio button Mandatory.

17. Choose Apply.

18. Save your entries.

Result

The fields for Account and Contacts have been marked as optional for entry on the WebUI.

3.2.3 Deactivating Standard Transaction Types

UseIf you only want to use the Best Practices transaction types for Activity Management, you can deactivate the standard transaction types. Otherwise you can skip this section.




2. Deactivate the following transaction types:

Trans. Type Description Inactive

0002 Incoming Phone Call X Inactive

0003 Outgoing Phone Call X Inactive

0004 Incoming E-Mail X Inactive

0005 Outgoing E-Mail X Inactive

0010 Business Activity X Inactive



Trans. Type Description Inactive

0020 Bus.Act.:With Prods X Inactive

0100 Lean Int. Record X Inactive

1001 Meeting X Inactive

ACCP Act. Channel Partner X Inactive

ACTI Business Activity X Inactive

ACPO Channel Activity X Inactive

CHM1 Ch. Partner Registr. X Inactive

CX01 Date X Inactive

RECU Repetitive Task X Inactive

SCCP Partner Report X Inactive

SCPO Channel Report X Inactive

ATCP Task Channel Partner X Inactive

ATPO Task Channel Manager X Inactive

HTSP Request for Sample X Inactive

HTAP Approve X Inactive

CHM4 Req. Brand Owner X Inactive

CHM2 Request for Partner Qualification X Inactive

CHM3 Request for Partner Qualification X Inactive

FCC0 FCC Interact. Record X Inactive

3. Choose Save.

Result

A number of selected transaction types have been deactivated.

3.2.4 Defining Item Category Determination

UseIn this process, you can define, per business transaction category and item category group, which item categories the system defaults for processing business transactions. At the same time, you can define which item categories can alternatively be entered manually for system default. A maximum of three alternative item categories are possible.



SAP CRM IMG menu Customer Relationship Management Transactions Basic Settings Define Item Category Determination

2. Create new entries with the following data:



Trans. Type

Description Trans.

Item cat. usage

Item Category

Alt. itm cat. 1

Alt. itm cat. 2

Y020 Visit with Prod. --- ACT ACT0 ACT1

Y020 Visit with Prod. ACT0 ACT0 ACT ACT1

Y020 Visit with Prod. ACT1 ACT1 ACT ACT0

3. Choose Save.

ResultNew item categories for activities have been created.

3.2.5 Defining Categories for Activities

UseYou can create categories to further define your activity types, for example:

Customer Visit

Telephone Call

E-Mail

Tasks



SAP CRM IMG menu Customer Relationship Management Transactions Settings for Activities Maintain Categories, Goals, and Priorities Maintain Categories

2. Select Category 301 and copy as YVT, BP Visit.

3. Choose Save.

In a customer system, you can delete all other categories that are not used.

ResultA new category for activities has been created.

3.3 Actions

UseActions in CRM use the Post Processing Framework (PPF). The Post Processing Framework is a Basis component which generates actions (for example, sales call or workflow) from the data for an application according to an action definition (for example, a follow-up sales activity). The actions are processed at a specific time. The PPF provides the tools for planning, starting and monitoring the actions.

3.3.1 Defining Action Profiles and Actions

Use



The purpose of this activity is to create an action profile and templates for actions. When creating an action profile, note for which business transaction type you can use this action profile. You must assign the relevant business object type to the action profile. The assignment of the business object type makes sure that the attributes for the relevant business transaction type (for example, business activity) can be used for defining and processing the conditions. Only one business object can be assigned for each action profile. You can find out the business object type for the transaction type or the item category in Customizing for transactions under Define transaction types or Define item categories.

All maximum allowed actions are defined for a transaction type. You also specify general conditions in the action profile for the actions contained in the profile.

In this activity, you create an action profile and templates for actions. You can define the action templates more closely in the following step Defining Conditions.

Procedure1. Access the activity using one of the following navigation options:

Transaction code CRMC_ACTION_DEF

SAP CRM IMG menu Customer Relationship Management Basic Functions Actions Actions in Transaction Change Actions and Conditions Define Action Profiles and Actions

2. Copy the action profile ACTIVITY with the description Activities to create a new action profile entitled Y_ACTIVITY with the description BP Activity for Visit and Meeting.

3. Choose Enter and then rename the following action definitions to:

- Y_ACTIVITY_FOLLOWUP

- Y_ACTIVITY_PRINT

- Y_ACTIVITY_REMINDER_MAIL

4. Choose Save.

Result

New Action Profiles and Actions for Activities have been created.

3.3.2 Defining Conditions

UseIn this step, you process the action templates you have created in the activity Defining Action Profiles and Actions. Define the following characteristics in the newly created action profile BP Activity for Visit and Meeting.


Transaction code CRMC_ACTION_CONF

SAP CRM IMG menu Customer Relationship Management Basic Functions Actions Actions in Transaction Change Actions and Conditions Define Conditions

2. Double-click BP Activity for Visit and Meeting under Scheduling of Actions.

3. Choose Create from the toolbar on the right-hand side and then choose Create follow-Up Task from the drop-down list.



4. Select the action definition Create Follow-Up Task and then go to the Processing Details tab.

5. Deselect Default Settings from Action Definition.

6. On the Settings Method Call tab, choose Change Parameters.

7. Double-click on Expression PROCESS TYPE: 1003.

8. Click on the value in the PROCESS_TYPE Area and overwrite it with Y030 (BP Task).

9. Choose Apply Values.

10. Choose Save.

Check which other actions are also relevant for your scenario and add them.

ResultA new condition for action processing in the activities has been created.

3.4 Maintaining Organizational Data Profile

UseThe purpose of this activity is to create a new organization determination profile that allows you to determine the responsible organizational unit by means of the assignment of the respective system user, which creates a business transaction, in the organizational model.

PrerequisitesThe organizational model has been created and all persons creating business transactions in the CRM system are assigned to an organizational unit - either as user or as business partners with an assigned user.


Transaction code CRMC_ORGPROF

SAP CRM IMG menu Customer Relationship Management Master Data Organizational Management Organizational Data Determination Change Rules and Profiles Maintain Organizational Data Profile

2. To create the new organizational data determination profile Y00000000001 perform the following steps:

3. Choose New Entries and enter the following values:

When creating new data manually (not using the BC Set) for both languages (EN and DE), you need to maintain translation-sensitive data (descriptions, titles, texts etc.) twice, after having logged on the system with the appropriate language (EN and/or DE).

Field Entry

Profile (first field) Y00000000001



Field Entry

Profile (second field) BP Sales Org. Data Profile – Country/Reg (EN)

Scenario SALE Sales

Determination Rules

Organizational Model Determin. Rule 10000166 Det. acc. to partner attr. (Reg, country)

Responsibilities rule

Mandatory

Sales Organization

Distribution Channel

Sales Office

4. Choose Save and select a customizing request if required.

ResultA new organizational data determination profile has been created and is ready to be assigned to one or more CRM business transactions.

3.5 Assigning Profiles and Procedures to Transaction Types

3.5.1 Assigning Organizational Data Profile to Transaction Types




2. Assign the Org. Data Profile to the following transaction types:

Trans. Type Description Org Data Profile

Y007 BP Interaction Log Y00000000001

Y010 BP E-Mail Y00000000001

Y020 BP Visit with Prod. Y00000000001

Y030 BP Task delete

3. Delete the Organizational Data Profile 000000000001/ Standard Org. Data Profile (Header) from Transaction Type Y030/ BP Task. The purpose of this activity is to bypass the Organizational Data search at transaction Tasks.

4. Choose Save.

ResultThe newly created transaction types have been assigned to organizational profiles.



3.5.2 Assigning Partner Determination Procedure to Transaction Types

UseThe Partner Determination Procedure Y0000002 is assigned to the following transaction types.




2. Assign the Partner Determination Procedure Y0000002 to the following transaction types:

Trans. Type Description

Y020 BP Visit with Prod.

3. Assign the Partner Determination Procedure Y0000004 to the following transaction types:


Y007 BP Interaction Log

Y010 BP E-Mail

4. Assign the Partner Determination Procedure Y0000003 Task to the following transaction type:


Y030 BP Task

5. Choose Save.

Result

The newly created partner determination procedures have been assigned to the new transaction types.

3.5.3 Assigning Action Profile to Transaction Types

UseThe Action Profile Y_ACTIVITY is assigned to transaction type Y020.

The Action Profile BP_TASK is assigned to transaction type Y030 according to the note 900293 to allow the functionality of merging accounts.




2. Assign the Action Profile Y_ACTIVITY to the following transaction types:




Y020 BP Visit with Prod.

3. Assign the Action Profile BP_TASK to the following transaction type:


Y030 BP Task

4. Choose Save.

Result

The newly created action profile has been assigned to the new transaction types.

3.5.4 Assigning Category to Transaction Types




2. Assign the new Category to the following Transaction Type at the Customizing header level:

Trans. Type Description Category Direction

Y020 BP Visit with Prod. BP Visit Outbound

3. Choose Save.

Result

The new category has been assigned to the transaction type.

3.5.5 Assigning Transaction Types to Categories for Activities



SAP CRM IMG menu Customer Relationship Management Transactions Settings for Activities Maintain Categories, Goals, and Priorities Assign Categories to Transaction Types

2. Make the following entries:

Trans. Type Category

Y007 BP Interaction Log 202 Telephone call

Y007 BP Interaction Log 203 Various

Y007 BP Interaction Log CX5 Customer Visit

Y010 BP E-Mail 401 e-mail



Trans. Type Category

Y020 BP Visit with Prod. YVT BP Visit

Y030 BP Task 101 Task

3. Choose Save.

In a customer system, you can delete all other assignments that are not used.

ResultCategories for activities have been assigned to transaction types.

3.5.6 Assigning Text Determination Procedure to Transaction Types

UseYou can assign Text Determination Procedures to Transaction Types.




2. Select Transaction Type Y020 BP Visit with Prod.

3. Choose Details.

4. In the Profiles area, change the Text Det. Procedure to ACT00004 Meeting.

5. Choose Save.

ResultText Determination procedure has been assigned to the new Transaction Type.

3.6 One to One E-Mail Integration

If you do not want to use this functionality, you can skip this step.

3.6.1 Defining Multipart E-Mail Option

UseIn this step you make the different basic settings for the one-to-one e-mail function. You identify whether Emails created in HTML format are to be automatically duplicated in plain text format both for MS Outlook and Lotus Notes.



To send and receive Emails a connection to an Email Server is required. The mail server needs to be connected to SAP CRM system.

To enable Email Exchange, Collaboration Data Objects need to be installed as well. These data need to be installed separately starting with Exchange 2007 and Outlook 2007. The CDO’s can be downloaded from the Microsoft Website e.g. from here:

http://www.microsoft.com/downloads/en/details.aspx?familyid=2714320d-c997-4de1-986f-24f081725d36&displaylang=en



SAP CRM IMG menu Customer Relationship Management → Basic Functions → One-to-One E-Mail → Define Multipart E-Mail Option and Groupware Integration

2. Enter the following entries depending on your Groupware Solution:

Setting MS Outlook Lotus Notes

HTML with Text-Only X X

Address Search in Groupware 1 MS Outlook 2 Lotus Notes

Groupware for E-Mail Integration

1 MS Outlook 2 Lotus Notes

Groupware/E-Mail Copies 1 MS Outlook 2 Lotus Notes

Groupware/E-Mail Formats1 HTML and Plain Text

1 HTML and Plain Text.

3. Choose Save.

3.6.2 Assigning Transaction Types

UseIn this step, you assign transaction types for incoming and outgoing e-mail.



SAP CRM IMG menu Customer Relationship Management → Basic Functions → One-to-One E-Mail → Assign Transaction Types

2. Choose the following entries:

Customizing Setting Value

Transaction Type for Activities from Incoming E-Mails Y010

Transaction Type for Activities from Outgoing E-Mails Y010





3. Choose Save.

3.6.3 Activating HTTP Services

UseIn this step, you check the activation status of several services that are used by the One-to-One E-Mail Integration. If a service is not yet activated, you can activate it here.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SICF

SAP CRM IMG menu SAP NetWeaver → Application Server → Internet Communication Framework → Configure and Activate HTTP Services Individually

2. Choose Execute (F8).

3. Navigate to default_host → sap → bc → bsp → sap → crm_gw_integ

4. Check if the service is active. If yes, the service is black, if not it is gray.

5. If the service is not activated, do a right mouse-click and choose Activate Service.

6. Repeat step 3-5 for the following services:

/sap/bc/bsp/sap/crm_gw_integ

/sap/bc/bsp/sap/BT126H_MAIL

/sap/bc/bsp/sap/CRMCMP_GW_INBOX

/sap/bc/bsp/sap/crm_send_screen

/sap/bc/bsp/sap/crm_email_bo

/sap/crm/crm_addr_inp

/sap/crm/crm_src_provide

/sap/crm/crm_att_provide

7. You can also check the activation state with a program. To do so, run the following report in transaction SE38: CRM_EMAIL_HTTP_SERVICE_CHECKER

3.6.4 Setting Up E-Mail Transfers from Microsoft Outlook

UseIn e-mail integration with Microsoft Outlook, there are two variants available for transferring e-mails:

1. Alternative 1: From the inbox in this SAP software, you can transfer e-mails from Microsoft Outlook into this SAP software.

2. Alternative 2: You can transfer e-mail messages to SAP software right from Microsoft Outlook. To set up this option for transferring e-mail messages, carry out the settings described in the Procedure section.

For e-mail integration with IBM Lotus Notes, e-mails are only transferred from the inbox of the SAP software. In this case, the following procedure is not relevant.



Procedure1. To carry out the activity, log on to the SAP CRM WebClient.

2. Click on Personalize.

3. Click the hyperlink Set Up E-Mail Transfer in the area Groupware Integration.

4. A dialog box appears. Choose OK so that the folder that is necessary for transferring e-mail is created automatically in Microsoft Outlook.

5. A second dialog box appears that confirms that the folder SAP CRM E-Mail Transfer was successfully created in Microsoft Outlook.

6. The dialog box also contains your user name for this SAP software, which you will need when you log on during e-mail transfer in Microsoft Outlook.

7. Choose OK.

ResultE-mail transfer has been set up in Microsoft Outlook.


Configuration Guide SAP: Transaction Types

Documents