Service Desk Determination. In the support message Sold to party &

[Former Member]

Dear Friends,

Sold to Party , IBASE & Component are not fetching the support message created from Satellite system BI.

I have configured the Service Desk for satellite system ECC 6.0. Now I have configured it to BI, but Sold to party & IBASE & Component are not fetching in the support desk message.

Following things done for adding satellite system BI to Solman.

1) IBase creation for BI is done.

2) SMSY configiration also done for BI

3) BP no created in Solman, mapped identification also.

What else i need to check.

Can anybody tell me which roles I need to assign the BI end users for raising the message. Is this issue related to roles

Regards

PK

[Former Member]

Hi,

There are several predefined roles for Support Desk, containing specific authorizations.

Rolle

SAP_SUPPDESK_ADMIN Administrator role for Support Desk. Comprises

authorizations to configure Support Desk

SAP_SUPPDESK_PROCESS Role for processing Support notifications. Comprises all the

authorizations for notification processing and using the Solution Database

SAP_SUPPDESK_DISPLAY General display role, no authorization to create or change

notifications

SAP_SUPPDESK_CREATE Role to create Support notifications. This role must be

assigned to both users who will create notifications in the

SAP Solution Manager and to users who will create

notifications from the satellite systems in the SAP Solution

Manager.

Regards,

Deepanshu

[Former Member]

Hi,

I deleted the entry TST_CUS under Appl column in BCOS_CUST table.

Same As said Sergey Rybakov.

Regards

PK

[Former Member]

Hi

For Ibase go to dswp - edit - click Initial Data Transfer for ibase

For sold to party go to IB52 choose Installed base 1 locate system Choose system with correct client then click GOTO and choose partner specify Sold To Party bp and save

For Bp go to trans BP find bp go to Identification tab make sure the bp has system details of the bi system

Santosh

[Former Member]

2PK

how you solved this problem?

[Former Member]

Solution is found in snote 449330

Solution

Maintain the contents of table BCOS_CUST via Transaction SM30 
and delete the record with the key TST_CUS (in field APPLI).
After this record has been deleted, the correct installation number 
will be then located in the corresponding field for the messages generated i
n this system and thus there should not be any problems when sending to SAP with the correct S-User.