Error while creating a support message in satellite system

Hi,
I am facing an error while sending a support message to solman form the satellite system
(( Error Description : Error in Local Message System: Error when opening
an RFC connection Message was Not Created ))
1) I gone through various threads and set the required authorizations like
SAP_SUPPDESK_CREATE and
SAP_SV_FDB_NOTIF_BC_ADMIN ,
SAP_SUPPDESK_ADMIN
for the user in the solman .
2) I checked the RFC connection and it is working fine.
Anyone pls help me to resolve this issue

hi rohit,
thanks for u r immmediate response
do i have to assign the roles to the user in the satellite system or the solman.
some roles in those 4 roles are not in the satellite system.
thanks
Rahul

Similar Messages

Error while creating the support message through "Help" in sol Man system

Hi All,
I am creating the support ticket in solution manager system through "Help". After entering priority, short & long description, i am getting following error:
Error in Local Message System: Access via 'NULL' object reference not possible. Message was Not Created
Message no. BCOS088
Note: Component is getting defaulted.
Please guide me on this
Regards
Senthil

check this IMG activity
SPRO --> SAP Solution Manager Implementation Guide --> SAP Solution Manager -> Configuration -> Basic Settings -> Standard Configuration of Basic Settings -> Specify Satellite Systems Connection -> Define Service Desk Destination in the Satellite Systems
Define Service Desk Destination in the Satellite Systems
Use
In this IMG activity, you make the necessary settings in the satellite systems to enable users working in those systems to send problem messages to the central SAP Solution Manager system.
Requirements
Basis/ABA Support Packages have to be installed on the satellite systems. For further information, see the SAP Solution Manager Configuration Guide.
Activities
In the satellite systems :
In view 'Create Messages: Customizing' (Transaction SM30, view BCOS_CUST), make the following settings for the application OSS_MSG:
Column 1: Application: OSS_MSG
Column 2: + : W
Column 3: RFC Destination:
Column 4: + : CUST620
Column 5: + : 1.0
Note:
We recommend to use the back destination you have already created.
If you want to use a back destination you have created before SAP Solution Manager Release 3.20 SP05, proceed as follows in the SAP Solution Manager System:
Generate the following roles in transaction PFCG.
Assign the following roles additionally to the user for the back destination:
SAP_SUPPDESK_CREATE
SAP_SV_FDB_NOTIF_BC_ADMIN

SOLMAN EHP1 - anyone can create support message in Satellite System's Help?

Hi,
I just curios that why everyone can create support message in satellite system-> help -> create support message?
I tested with restricted profile user and without role SAP_SUPPDESK_CREATE, NO BP created but he still manage to create support message???? Any idea??
Also, same goes to any user can process ticket in SOLMAN with no BP-Employee role and SAP_SUPPDESK_* roles assigned.
Your kind input is very much appreciated.
Thanks,
Nicholas Chang

Hi Nicholas
If you are using a "Named" user instead of the Trusted Relationship in the RFC maintained in BCOS_CUST for entry OSS_MSG then this is quite possible. In this case the "Named" user will be used to call the interface to create message and the calling user ie the end user creating the ticket will only be used as "Reporter" of the message.
The user entered in the RFC details probably has the authorization to create Support desk messages.
Regards
Amit

Create support message in satellite system

Hi,
What are the pre-requisites to configure creating support message in satellite system.
Thanks
Rajesh

Hi,
Follow this blog u can set up ur service desk
mainly it comprises of roles table entry and rfc destination in satellite systems
/people/bruyneel.guillaume/blog/2008/05/02/service-desk-implementation-guide-part-i
/people/bruyneel.guillaume/blog/2008/06/13/service-desk-implementation-guide-part-ii
hope it solves ur problem
Regards
Prakhar

Roles required to create support message from satellite system

Hi Team,
I am trying to create support message from satellite system. i have assigned S_RFC and S_RFCACL to the Zrole. Apart from that, is there any other roles to be assined in satelite system to create support message?
Regards
Kumar

I think that's it.
Of course they roles in the central system too: SAP_SV_FDB_NOTIF_BC_ADMIN and SAP_SUPPDESK_CREATE (or copies thereof).
Regards,
Sean

Error 513 while creating a support message (related to roles/profiles)

Hello everyone,
my user is getting the generous error 513 while sending a support message either on the SAP GUI or Workcenter. I am trying to implement a profile for a key user, who can display, reply and create simple messages without putting in technical data.
I gave him the following roles:
SAP_SMWORK_INCIDENT_MAN
SAP_SUPPCF_CREATE
SAP_SUPPCF_ADMIN
SAP_SUPPDESK_DISPLAY
SAP_SUPPDESK_CREATE
SAP_SV_FDB_NOTIF_BC_CREATE
and a generous role with the missing parts:
ZSAP_SMWC
When I tried sending a message with the GUI I used SU53 to find out which rights are missing and added them to ZSAP_SMWC. Now I got all of them and the SU53 replies that there are no more missing rights.
Thing is: When I add the profile SAPALL to my user, it works just fine. This is leading me to a problem i can't solve._
I also have to say that I accidently deleted some flags inside of sap_suppcf_create without copying it. Is there a way to restore SAP standard settings?
Thanks in advance,
Hendrik

I just seen the following SAP Knowledge Base Article related to ST 400 SP24:
[1522809 - Solution Manager: Because of error 513, no message was created in Support Desk System|www.service.sap.com/sap/support/notes/1522809 ]
Regards, Ruediger

Error creating Service Desk Message in Satellite System

Hi all
We have two satellite system from which I want to create a Support Message. With my current profile/role and can do it from one system and not from the other system. I get "Error in local message system, message xxx not complete". I dont think it is an Authotization fault, but not sure.
How should the Number ranges be setup for more than one satellite system?
Thanx
Jaco Snyman

Hi Tina
This was my answer in a previuos thread:
Hi all
I also struggled with this for 2 weeks. But the problem is fixed.
Do your "normal: config from the IMG and then:
1) Make sure that you have selected for the system NOT to check for the User in SolMan
tr: DNO_CUST04, Go to Detail, Select the field NO_USER_CHECK, "X", this is very important, otherwise you will have to create a username for everyone on the satellite system... far too timeconsuming.
2) In your satellite system under OSS_MSG: Col1:Application: OSS_MSG, Col2: + : W. Col3: RFC Destination: SM_"SOLMANRFC"_BACK. Col4: + : CUST620. COl5: + : 1.0
In the Solman side you maintain Col3 as "NONE".
3) Make sure that ALL users in the satellite system has the following roles: SAP_SUPPDESK_CREATE and SAP_SV_FDB_NOTIF_BC_ADMIN.
4) Make sure that you have TRUSTED RFC to and from your Satellite system and Solution Manager.
The main one to be sure of is: SAP_ALL for all SOLMANxxx user in the Solution Manager system for every satelite system, because the standard roles from SAP does not work.
This should have your Service Desk Messaging working.
Jaco Snyman

With SP16-17 we can't create support message from satellite system anymore

hello,
We have implemented the support package 16 and 17 SAPKITL427 in solution manager last week-end and since then all satellite systems can not create support message anymore.
The process is perfectly working in solman itself and we don't think we have thus a process customizing issue here but who knows...
The key user creates the message with the help -> create support message
and when he saves it (clicking the mailbox button) he gets the following error
Error in Local Message System: Function not available Message was Not
Created
In fact the error Message is BCOS088
We debugged the function BCOS_CREATE_MSG and we found out that the function
DNO_OW_CREATE_NOTIFICATION is returning error code 1.
We checked out RFC connection and it looks ok
There is no dumps in ST22, no error in SLG1 in both system...a nightmare
The notification SLF1 is created in solman but the status field of the notification is empty and it looks that the record is somehow corrupted because you can't modify it with dnotifwl.
Due to the fact that the notification is not correctly created the support message is also not created.
SAP and our solman consultant are working on it since 2 days but don't have a clue. Maybe some program where no regenerated correctly ?
If you would have any idea in which direction to look, i would greatly appreciate
thanks a lot
best regards Xavier

hi Rohit,
on the satellit I have the following versions
SAP_BASIS     700     0012     SAPKB70012     SAP Basis Component
SAP_ABA     700     0012     SAPKA70012     Cross-Application Component
PI_BASIS     2005_1_700     0012     SAPKIPYJ7C     PI_BASIS 2005_1_700
ST-PI     2005_1_700     0006     SAPKITLQI6     SAP Solution Tools Plug-In
SAP_BW     700     0013     SAPKW70013     SAP NetWeaver BI 7.0
SAP_AP     700     0009     SAPKNA7009     SAP Application Platform
SAP_HR     600     0018     SAPKE60018     Human Resources
SAP_APPL     600     0010     SAPKH60010     Logistics and Accounting
EA-IPPE     400     0010     SAPKGPID10     SAP iPPE
EA-APPL     600     0010     SAPKGPAD10     SAP Enterprise Extension PLM, SCM, Financials
EA-DFPS     600     0010     SAPKGPDD10     SAP Enterprise Extension Defense Forces & Public Security
EA-HR     600     0018     SAPKGPHD18     SAP Enterprise Extension HR
EA-FINSERV     600     0010     SAPKGPFD10     SAP Enterprise Extension Financial Services
FINBASIS     600     0010     SAPK-60010INFINBASIS     Fin. Basis
EA-PS     600     0010     SAPKGPPD10     SAP Enterprise Extension Public Services
EA-RETAIL     600     0010     SAPKGPRD10     SAP Enterprise Extension Retail
EA-GLTRADE     600     0010     SAPKGPGD10     SAP Enterprise Extension Global Trade
IS-PS-CA     600     0010     SAPK-60010INISPSCA     IS-PUBLIC SECTOR CONTRACT ACCOUNTING
IS-OIL     600     0010     SAPK-60010INISOIL     IS-OIL
IS-M     600     0010     SAPK-60010INISM     SAP MEDIA
IS-H     600     0010     SAPK-60010INISH     SAP Healthcare
IS-CWM     600     0010     SAPK-60010INISCWM     Industry Solution Catch Weight Management
INSURANCE     600     0010     SAPK-60010ININSURANC     SAP Insurance
FI-CAX     600     0010     SAPK-60010INFICAX     FI-CA Extended
FI-CA     600     0010     SAPK-60010INFICA     FI-CA
ERECRUIT     600     0010     SAPK-60010INERECRUIT     E-Recruiting
ECC-DIMP     600     0010     SAPK-60010INECCDIMP     DIMP
IS-UT     600     0010     SAPK-60010INISUT     SAP Utilities/Telecommunication
SEM-BW     600     0010     SAPKGS6010     SEM-BW: Strategic Enterprise Management
LSOFE     600     0010     SAPK-60010INLSOFE     SAP Learning Solution Front-End
ST-A/PI     01K_ECC600     0000          -     Application Servicetools for ECC 600
APICON     1470000000     0000          -     APICON GmbH, Interface Add ON
thank you Xavier

Creating Support Messages from Satellite System without SolMan user account

Hi
We are having some problems with users "creating support message" from our ECC system to SolMan, if the user does not have a user account in Solution Manager.
It is not correct, that users from Satellite systems can create support messages from these systems, without the user having an account in Solution Manager? And that the user is identified by the business partner for the user, that must exist in the Solution Manager system ?
We have set up the RFC for the supportmessages between SolMan and the ECC system as trusted RFC, with the "Current user" as the user, but how should this be set up, if the user does not have an account in the Solution Manager system. If we enter a user with the right authorizations in the RFC, will the messages that come through not just appear as created by that user, instead of the ECC user and corresponding business partner ?
Regards
Lars

Hi,
you can use the use the user for the RFC-Connection in that case. I have customizied a similar scenario. In my scenario the System from which the message was created, is the business partner (SOLD-TO-PARTY). For that you have to create a communication user (i.e SOLMAN<SYSID>). In TA SM59 in the satellite-system you assign this user for the connection. (Don't forget to assign the user to the role "SAP_SV_FDB_NOTIF_BC_ADMIN"). Now, it schould be possible to create messages from the satellite system to the solution manager. Additionally you should create business-partner for each user of the satellite system, by using TA DSWP>EDIT>CREATE BUSINESS PARTNER.
With this TA, it is easy to create BP for each satellite system.
Best regards
Marc

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

ERROR when Trying to create support message in satellite system

Hi
I have a wired problem.
My user's are opening support message in the solman through the ECC system.
But when a user is open a support message with the component FI he get the following message:
"Error in Local Message System: Component FI does not exist: Check your entry Message was Not Created"
I'm working with ECC6 and SOLAMN 4.
Why I can't generate support message with the component "FI" ?
Please advice
Best regards
Lior Grinberg

Hi
SAP Component is FIN Financials not FI that is why I thnk u r getting an error.
Normal process is
Whenever your user will post any message from any Transactions of FI module in ECC they goto help->create support message
This will automatically fill the SAP Component
Secondly if they are posting from initial logon screen they can choose the value by pressing F4 in SAP component field
Hope it solves ur problem
Regards
Prakhar

Create Support Message from satellite system

Hi, when I create a ticket using "Help - Create support Message" the parameter SY-UNAME is not passed to Service Desk
in other word, the message is created but the field "Reported by" is not filled.
if I want to display the entire message in the form, before saving, I can see that this value is correct...
SY-SYSID             DE1
SY-MANDT             300
SY-UNAME             SOLMAN
SY-DATUM             20080410
etc.
Any suggestion ?
Regards,
Nacho.

Hi,
1) Under identification tab in external BP no. put details as
<Server short name>space<client>space<search term
(which you have maintained in address tab or employee no.
of that user in satellite system)>
2) In ID type put CRM001
3) Under identification put details as <Server short
name>space<installation no.>space<client>space<search
term (which you have maintained in address tab or
employee no. of that user in satellite system)>
4)Go to trns. BP>select BP role as "Employee"> Indentification tab--> Maintain user name same as user id of employee in satellite system or serch term you maintained while creating BP.
Try this. Reward the points for useful answer.
Regards,
Niks

Error while creating Org structure     Message no. BBP_LOCATION009

Hi
Iam trying to build an SRM6.0 with backend as R/3 4.7
I have replicated the plats from back end with report BBP_LOCATIONS_GET_FROM_SYSTEM
On errors rectified the same and finally, SLG1 report shows no errors.
But still noticed that T77S0 table entry with GPID=EBP, SEMID= LMIGR is not set to X (Refer note 563180)
Due to the above problem while creating org structure when I click on Att inheritence or Extended attributes Locations tab,
I get the message:
Start program BBP_LOCATIONS_GET_ALL first (see Note 563180 and long text)
         Message no. BBP_LOCATION009
Diagnosis
    You tried to call a program that uses a location. The locations have not
    yet been replicated.
System Response
    The current program has been terminated.
Procedure
    Start the program to replicate the locations. You can find more
    information in SAPNet in Note .
Procedure for System Administration
You can disable this message by starting table maintenance (SM30) for
table T77S0. Change the entry EBP/LMIGR to "X". Note that the system
cannot supply certain information if the locations are not replicated.
Locations that do not exist can be deleted during attribute maintenance.

are you working with multiple backend systems?
can you retry downloading the plants with the report
BBP_LOCATIONS_GET_ALL
and then give the logical sys name as yr present backend?
BR
Dinesh

An error while creating the originals, Message No:26296

Dear Experts
I have searched the forum but i didn't find the desired solution. Can any one please provide me the solution for this problem. I am getting this error "An error occured while creating the original in the Knowledge Provider with Message No: 26296" while checking an original file to KPRO. I have searched in the table "SDOKPROP" the all DMS entries are proper as per below thread
Re: Error while checking Document in DMS_C1_ST
in the forum, but no luck. Can any body please through some light on this?
Thanks
Prasad

Hi Prasad,
Are you getting only the error, or are you getting any ABAP Short Dump while saving the DIR?
The table setting SDOKPROP as emtnioned in the thread/wiki is required if you get ABAP Dump.
Otherwise there could be problems with your Content Server. Check in CSADMIN whether all content repositories are running fine..
Also check with the BASIS perosn whether Adminstration rights are given for the content server service
Regards,
Aby

How to change number for support message in satellite system

Hi,
When i'm creating the messages in the satellite sytem the messages are generating with internal number range(0000002345) of solman.I would like to change to external number as (9999000000).
Please help me to resolve the issue.
Regards,
Eswar.

Hello,
SPRO > Solution Manager > Basic Settings > Scenario Specific Settings > Service Desk > Check Number Range for Service Desk Message
Check Number Range for Service Desk Message
Use
In this Customizing activity, you check the new internal and external number ranges for the Service Desk.
Activities
1. Select the transaction type SLFN.
2. Choose Goto -> Details.
3. Check the internal number range 01 and the external number range 02 under Transaction / Numbering.
4. Save your entries.
I hope this helps.
Regards,
Paul

Error while creating a support message in satellite system

Similar Messages

Maybe you are looking for