Currently Being Moderated

<body>http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/webcontent/uuid/925b02f9-0b01-0010-bbbf-c68268bb3c41|border=0! http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/webcontent/uuid/7ec202f9-0b01-0010-589e-a51bcd596fed|border=0!

 

First of all, you will need to perform some preparation steps, follow these instructions below:

Check level of Basis and ABAP Support Packs in the Satellite Systems. For example: for release 4.6C, Support Package 51 (or Support Package 50 with Notes 832585 and 838537) is required. For WAS 620 Support Package 54 is then required.

 

Let’s now start with the required configuration steps to setup Service Desk in SAP Solution Manager 3.2.

 

1. Activate Solution Manager Services:

 

 

a.

Go to transaction

SICF

. Navigate the tree below to each of the services listed. If the service is currently grayed out you will need to activate it. For example, navigate to /sap/public/bsp/sap/htmlb

 

image

 

b.

If the service is grayed out, as in the example, you need to activate it, for this, select the service, go to Service/VirtualHost Menu and then select

Activate

. In the following screen, select the

Y

button, to activate the service and all the dependent services.

 

image

 

Now, the BSP service is activated, see below:

 

image

 

c.

The same procedure needs to be performed also for the following services:

 

     /sap/public/bsp/sap/htmlb

     /sap/bc/bsp/sap/ai_proj_setup

     /sap/bc/bsp/sap/dswpnotifcreate

     /sap/bc/bsp/sap/dswp_create_message

     /sap/bc/bsp/sap/dswp_bsp

     /sap/bc/bsp/sap/learning_map

     /sap/bc/bsp/sap/public/bc

     /sap/bc/bsp/sap/solutionmanager

     /sap/bc/bsp/sap/system

     /sap/bc/contentserver

     /sap/bc/solman

 

2. Activating Solution Manager BC-Sets required for Service Desk:

 

 

a.

Go to transaction

SCPR20

. The following screen will be shown:

 

image

 

b.

In the BC set enter the BC set that needs to be activated, for example:

SERVICE_DESK_CHANGE_REQUEST_32A

 

image

 

c.

Press the activate (!https://weblogs.sdn.sap.com/weblogs/images/26943/BCSets_Activate.JPG|height=20|alt=image|width=24|src=https://weblogs.sdn.sap.com/weblogs/images/26943/BCSets_Activate.JPG|border=0!) button. The following screen will be shown:

 

image

 

d.

Make sure to select Expertmode and Overwrite All Dataoptions, and then, click on the continue button (!https://weblogs.sdn.sap.com/weblogs/images/26943/BCSets_OK.JPG|height=22|alt=image|width=23|src=https://weblogs.sdn.sap.com/weblogs/images/26943/BCSets_OK.JPG|border=0!). The BC set will be now activated.

e.

Now repeat steps

a

through

d

to activate also the following BC Sets:

 

     SERVICE_DESK_CHANGE_REQUEST_32A

     SERVICE_DESK_CHANGE_REQUEST_32F2

     SERVICE_DESK_CHANGE_REQUEST_32A7

     SERVICE_DESK_CHANGE_REQUEST_32A8

     SERVICE_DESK_CHANGE_REQUEST_32A9

     SVDSK_CORPFUNC_SECURE_AREA_32_01

 

3. Fetching SAP components:

 

 

This will transfer the standard SAP components from SAPNet R/3 Frontend into the Solution Manager system. Go to transaction

DSWP

then select

Edit/Fetch SAP Components

from the menu.

 

4. Assign the number ranges for ABA notifications:

 

 

a.

Go to transaction

DNO_CUST01

and select notification type

SLF1

, see screen below:

 

image

 

b.

Select in the menu

Goto -> Details

 

image

 

c.

Assign internal number range

01

in the in the Number Range field. Then press the save (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|border=0!) button, see screen below:

 

image

 

5. Assign number range for Service Desk Messages:

 

 

a.

Go to transaction

SPRO

Open the tree and navigate to SAP Solution Manager Implementation Guide --> SAP Solution Manager --> Basic Settings --> SAP Solution Manager System --> Service Desk --> Number Ranges for Notifications. Then press the execute icon (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Execute.JPG|height=25|alt=image|width=26|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Execute.JPG|border=0!) next to

Assign number range for Service Desk Messages

.

 

image

 

b.

Select transaction type

SLFN

from the Definition of Transaction types window, see screen below for details:

 

image

 

image

 

c.

Choose

Goto -> Details

from the menu:

 

image

 

d.

Assign the internal number range

01

and the external number range

02

under Transaction / Activity Numbering:

 

image

 

e.

Now press the (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|border=0!)button.

 

6. Configuring the ABA Messages:

 

 

a.

Go to transaction

DNO_CUST01

then select notification type

SLF1

.

 

image

 

b.

Choose

Goto -> Details

from the menu:

 

image

 

c.

Check whether action profile

SLFN0001_STANDARD_DNO

is assigned, if not assign it, see below:

 

image

 

d.

Now press the (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|border=0!)button.

e.

Go to transaction

DNO_CUST04

. Select the field

NO_USER_CHECK

, see details below:

 

image

 

f.

Choose

Goto -> Details

from the menu:

 

image

 

g.

Enter

X

in Field Value.

 

image

 

h.

Now press the (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|border=0!)button.

 

7. Generate Business Partners:

 

 

 

 

See details in the screen below:

 

image

 

8. Create Message Processors:

 

 

a.

Go to transaction

BP

(Business Partner). From the menu, choose <b>Business Partner -> Create -> Person</b> or edit an existing Business Partner of type person.

 

image

 

b.

Choose the role

Employee

.

 

image

 

c.

Choose the

Address

tab and enter the address data for the message processor, see details below:

 

image

 

d.

Choose the

Identification

tab and go to the

Employee

data section:

 

image

 

e.

Enter the user ID of the message processor in the User field. The message processor has to have a user in the SAP Solution Manager system.

f.

Click the save icon (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|border=0!).If an error message is displayed from the program

CRM_MKTBP_ZCAL_UPDATE_30

, see SAP Note 450640.

g.

To create additional users, repeat the steps from

a

through

f

.

 

9. Create Organization Business Partners:

 

 

a.

In transaction

Maintain Business Partners

(transaction BP), choose Business Partner -> Create -> Organization</b>:

 

image

 

b.

Choose the role

Sold-to Party

.

 

image

 

c.

Choose the

Address

tab and enter the address data for the sold-to party, see below:

 

image

 

d.

Choose the

Sales Area Data

button.

 

image

 

e.

Choose the

Choose Sales Area...

button.

 

image

 

f.

Select

Sales Organization – Sales

 

image

 

g.

In the Sales tab, select

Sol_Customergroup

from the input help in field

Customer Group 1

.

 

image

 

h.

Click the save icon (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|border=0!).

i.

Repeat the steps to create additional sold-to parties.

 

10. Define Service Desk destinations in the Solution Manager System:

 

 

a.

Go to transaction

SPRO

. Open the tree and navigate to <b>SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> SAP Solution Manager System -> Service Desk</b>. Press the execute icon (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Execute.JPG|height=25|alt=image|width=26|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Execute.JPG|border=0!) next to Define Service Desk Destination in the Solution Manager System.

 

image

 

b.

In view

Create Messages: Customizing

, check whether application

OSS_MSG

exists. If it exists, go to the following step, if not, continue to

c.

to create it.

c.

Press the modify button and then the

New Entries

Button next to it.

 

image

 

d.

Make the following settings for the application

OSS_MSG

:

Column 1: Application: OSS_MSG
Column 2: + : W
Column 3: RFC Destination: NONE
Column 4: + : CUST620
Column 5: + : 1.0

e.

Click the save icon (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|border=0!).

 

11. Schedule the background jobs in Solution Manager:

 

 

a.

Go to transaction

SM36

. For Job name enter

SOLMAN_ISSUE_STATUS_REFRESH

, Job class

C

, then press the Step (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Step.JPG|height=23|alt=image|width=65|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Step.JPG|border=0!) button.

 

image

 

b.

  Enter the information as in the screen below, and press the save icon (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|border=0!).

 

image

 

12. Define Service Desk destination in the Satellite systems:

 

 

Note:

for this you need to log in the satellite system.

a.

Go to transaction

SM30

.

b.

In table/view field, enter BCOS_CUST. Then press the

Maintain Button

. See example below:

 

image

 

c.

Press the

Continue

button in the following screen:

 

image

 

d.

You should see the following screen, no entries should be seen in the table. Press the

New Entries

button:

 

image

 

e.

In the next screen, enter the following information:

!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_33.JPG|height=220|alt=image|width=538|src=https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_33.JPG|border=0!

Comments