
<body>http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/webcontent/uuid/925b02f9-0b01-0010-bbbf-c... http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/webcontent/uuid/7ec202f9-0b01-0010-589e-a...
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.
a.
Go to transactionSICF
. 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/htmlbb.
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 selectActivate
. In the following screen, select theY
button, to activate the service and all the dependent services.Now, the BSP service is activated, see below:
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
a.
Go to transactionSCPR20
. The following screen will be shown:b.
In the BC set enter the BC set that needs to be activated, for example:SERVICE_DESK_CHANGE_REQUEST_32A
c.
Press the activate (!https://weblogs.sdn.sap.com/weblogs/images/26943/BCSets_Activate.JPG|height=20|alt=image|width=24|sr...!) button. The following screen will be shown: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=http...!). The BC set will be now activated.e.
Now repeat stepsa
throughd
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
This will transfer the standard SAP components from SAPNet R/3 Frontend into the Solution Manager system. Go to transaction
DSWP
then selectEdit/Fetch SAP Components
from the menu.a.
Go to transactionDNO_CUST01
and select notification typeSLF1
, see screen below:b.
Select in the menuGoto -> Details
c.
Assign internal number range01
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...!) button, see screen below:a.
Go to transactionSPRO
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=ht...!) next toAssign number range for Service Desk Messages
.b.
Select transaction typeSLFN
from the Definition of Transaction types window, see screen below for details:c.
ChooseGoto -> Details
from the menu:d.
Assign the internal number range01
and the external number range02
under Transaction / Activity Numbering:e.
Now press the (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https....a.
Go to transactionDNO_CUST01
then select notification typeSLF1
.b.
ChooseGoto -> Details
from the menu:c.
Check whether action profileSLFN0001_STANDARD_DNO
is assigned, if not assign it, see below:d.
Now press the (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https....e.
Go to transactionDNO_CUST04
. Select the fieldNO_USER_CHECK
, see details below:f.
ChooseGoto -> Details
from the menu:g.
EnterX
in Field Value.h.
Now press the (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https....See details in the screen below:
a.
Go to transactionBP
(Business Partner). From the menu, choose <b>Business Partner -> Create -> Person</b> or edit an existing Business Partner of type person.b.
Choose the roleEmployee
.c.
Choose theAddress
tab and enter the address data for the message processor, see details below:d.
Choose theIdentification
tab and go to theEmployee
data section: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... an error message is displayed from the programCRM_MKTBP_ZCAL_UPDATE_30
, see SAP Note 450640.g.
To create additional users, repeat the steps froma
throughf
.
a.
In transactionMaintain Business Partners
(transaction BP), choose Business Partner -> Create -> Organization</b>:b.
Choose the roleSold-to Party
.c.
Choose theAddress
tab and enter the address data for the sold-to party, see below:d.
Choose theSales Area Data
button.e.
Choose theChoose Sales Area...
button.f.
SelectSales Organization – Sales
g.
In the Sales tab, selectSol_Customergroup
from the input help in fieldCustomer Group 1
.h.
Click the save icon (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https...!).i.
Repeat the steps to create additional sold-to parties.a.
Go to transactionSPRO
. 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=ht...!) next to Define Service Desk Destination in the Solution Manager System.b.
In viewCreate Messages: Customizing
, check whether applicationOSS_MSG
exists. If it exists, go to the following step, if not, continue toc.
to create it.c.
Press the modify button and then theNew Entries
Button next to it.d.
Make the following settings for the applicationOSS_MSG
:e.
Click the save icon (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Save.JPG|height=18|alt=image|width=22|src=https...!).a.
Go to transactionSM36
. For Job name enterSOLMAN_ISSUE_STATUS_REFRESH
, Job classC
, then press the Step (!https://weblogs.sdn.sap.com/weblogs/images/26943/ABA_Step.JPG|height=23|alt=image|width=65|src=https...!) button.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...!).
Note:
for this you need to log in the satellite system.a.
Go to transactionSM30
.b.
In table/view field, enter BCOS_CUST. Then press theMaintain Button
. See example below:c.
Press theContinue
button in the following screen:d.
You should see the following screen, no entries should be seen in the table. Press theNew Entries
button:e.
In the next screen, enter the following information: