cancel
Showing results for 
Search instead for 
Did you mean: 

Missing texts in Solution manager when creating message via satelite system

Former Member
0 Kudos

Hello everyone,

We have a problem when we create a message via 'help -> create support message' in a satelite system. The message is created in solution manager, but without the description in the log, in case the user has a business partner assigned.

To test we have two users:

user 1: no business partner assigned: message is created perfectly

user 2: business partner assigned: message is created, but without the short text and long text in the suzz log. The short text is copied to the description though.

User 2 has sap_all, sap_new and some roles I found in other blogs (just to be sure it is not an authorisation error): SAP_S_RFCACL, SAP_SM_ADMIN_COMPONENT_DIS, SAP_SUPPDESK_CREATE, SAP_SV_FDB_NOTIF_BC_ADMIN. The trace in St01 gives no error.

Futhermore I checked the ABA message. The log of the description is also not available in there.

I also checked if the action profile  SLFN0001_STANDARD_DNO is active. This is active (and we use SLFN)

We use different document flows: SLFN -SDCR - SDHF, SLFN - SDAD and ZDCR - SDHF. Can this be the cause of our problem?

We are on SAP_BASIS 701 level 10 and SAP EHP 1 for SAP Solution Manager 7.0.

Does anyone know the solution to this problem?

Thanks, Katrin

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Whe sended the message to SAP, and in the end got the following usefull reaction:

When creating a new "Support Message" with an user with business partner assigned to it, the system add this BP for the Partner Function SLFN0002(Reported By).

Now after you have inputted the texts and press saved, the system will trigger the following Partner Determination Procedure - SLFN0001 which is defined for this Transaction type - SLFN. In this Partner Determination Procedure, the Sold-to Party is defined to be fetched according to the Access Sequence - Z004. Hence the system determines that the BP is suitable to be used as Sold-to Party and it will add it to Partnerset.

Hence, because of this Partner addition which is seen as a Partner Change by the system, it triggers a new Text Determination from scratch, removing any previous text entered. This behaviour of the system is the standard and expected based on the current customizing.

But this not the expected behaviour for your scenario and in order for text to be saved, there are two options which you can try:

1. If it is not necessary to determined the Sold-to Party, then the assigned Access Sequence - Z004 can be removed from the definition of Partner Determination Procedure - SLFN0001.

2. In case the Sold-to Party is necessary, then you can disable the Text Determination to trigger whenever there is Partner Change in a transaction. To disable the Text Determination for Partner change follow these steps:

~> Open the table SMOFPARSFA through transaction SE16

~> Enter COM_TEXT in the PARSFAKEY field and hit execute

~> Go into Edit mode and remove the value in the PARVAL1 field

~> Save the changes.



We choose option 2 and this works for us.


Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Katrin:

Did you check the copy controls when you made copies to ZDCR...

Former Member
0 Kudos

Hi Ajay,

Thanks for your reply.

The copy controls are fine.

katrin