Set sap Component mandatory while creating the support desk message

Hi,
When create the support desk message from any application sysytem, the sap component get selected automatically but when we create the suppport desk message from the Easy Access the component wiil be blank, so some user create the support message without giving the component. So we want to make the component as mandatory while createing the support desk message from application system and also set mandatory when we create support message in solman.can anybody help me in setting component mandatory.
Regards
charan

Dear Charan,
The logic of setting the SAP Component mandatory is explained in the note 640532.
Kindly use the note to resolve the purpose.
Hope this solution helps.
Regards
Amit

Similar Messages

Create a Support Desk Message from WEB

Hi All,
I am trying to create a web message from the web.
I am trying the following link:
http://dodsm.domain.com:8081/sap/bc/bsp/sap/dswp_create_msg?sap-client=<001>
I get a login screen into the web application server(webas). when i enter a valid user of the webas, it fails with the folowing message.
Logon failed
What has happened?
Call of URL http://dodsm.domain.com:8081/sap/bc/bsp/sap/dswp_create_msg terminated due to error in logon data.
Note
Logon performed in system SOL.
Logon performed for client <00, user j2ee_admin, and language EN.
Error Code: ICF-LE-http-c:<00-l:E-T:231-C:3-U:5-P:5-L:7
HTTP 401 - Unauthorized
Your SAP Internet Communication Framework Team
Please help. in the above i could see that i have entered the client as <001> where as the error says it is seeing only <00
any authorisation i am missing?

hi,
I want to place a button in the web template of bi 7, so that when the user clicks on the button i want to call bsp appliaction which creates the support desk ticket. so that the user can fill/edit and submit his support request.
Regards,
Shamila

From which table is the support desk message picked?

Hi Experts,
In CRM_DNO_MONITOR tcode, i want to know from where support desk message number picking from(from which table).i want where this support desk message number(number range) is maintained in SPRO.
steps i'm working out:
I'm executing CRN_DNO_MONITOR tcode with transaction number, after executing i double click on the details where it will display the details. Going to <b>business transaction</b> and click on create where it will display create business transaction options. Select <b>Support Desk Message</b> and click on create.
In the very next screen, it will display the support desk message number. I want to know from where this support desk message number is picking(table name or settings in spro).
Thanks,
Pawan

Hey pavan,
The tcode for number range maintancance is crmc_nr_ra_service.
Every number range has some number like 01, 02 03 assigned to it..
TO find out which number range your transaction type is using go to : Spro->Customer relationship managemnt->transaction type-> Selct the desired transac tion type and click on details:::
There you can find the number range assignment in field internal number range...
Revert for ny clarifications and plz do forget to reward if this post was usefull..

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

Create support desk message through "Help"

Dear friends,
I am creating support desk message in my Sol Man system through "Help" menu. At that time, system automatically calling transaction type "SLF1".
Now i have created the new transaction type "ZZSL" by copying from SLF1.
Now i want the system to call the new transaction type "ZZSL", when i create a support ticket through "Help".
How to enable this?
Please guide me on this.
Regadrs
Senthil

Dear Anand,
Thank you for the reply. But this one will work, if i create a support desk message through t.code NOTIF_CREATE.
But i am NOT creating the support desk message through the transaction NOTIF_CREATE.
I think you are of aware of creating the support desk message through "Help" menu.
At that time i want to link transaction type "ZZSL".
or..can u give u mail ID ..i will send the screen shots
Senthil

How to make the fields of the table mandatory while creating new entries..?

Hi,
I have created a new Z table which has 6 fields. All the 6 fields are KEY fields and all are of CHAR type. I have generated the table maintenance generator for the same. My requirement is all the fields should be MANDATORY while creating the entries. No field should be BLANK.
When creating the new entries in the table, even if I don't give any values to some of the fields, it is saving the entry. But, it shouldn't happen like that. If any of the field is kept blank, it should not allow the user to save the entry. Can someone tell me how to approach this. Will there be any settings while creating the table which takes care of this.
I read somewhere that this can be done using the Table EVENTS. Can someone tell me what is the code that we should write there in the Events which prevents the user from saving the blank fields. While writing the logic in the events, how to check whether the particular field is BLANK or not. Will the values be stored in any internal table kind of thing..?
My table name is ZCRF_TAB and the fields are FLD!, FLD2, FLD3, FLD4, FLD5 & FLD6. Can someone provide me sample code for my requirement. Thanks in advance.
Best regards,
Paddu.

Hi,I think u have generated Table Maintainance Generator, goto Environment->Modifications->Events
Select appropriate option by using F4,I think value 05 is appropriate for u r requirement.Enter From routine name.Dbl click on the routine.
Write the appropriate code like:
If ZTABLE-FIELD1 is initial.
Message (E000) with "Fill all the manadatory fields".
Thats it.Just look at the following docu with screenshots,by this understand how u can use Table Events:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/how%20to%20implement%20events%20in%20table%20maintenance.doc
Regards,
Rock.

Error while creating the HTTP client with destination GB_DPSRetrieve

Hi All,
It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
Please find the error log below and throw some light why the HTTP adapter is getting error -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
<SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
<SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
<SAP:Service>GGMailbox</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SAP_DEV_ERP2005</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
<SAP:P1>GB_DPSRetrieve</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20071121</SAP:Date>
<SAP:Time>155130</SAP:Time>
<SAP:Host>lbsth-tb1ci</SAP:Host>
<SAP:SystemId>XIS</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PISUPER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>0</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>15</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
<Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
</SOAP:Body>
</SOAP:Envelope>
Regards,
Kishore

Hi,
In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
Also check if the Target system can be reached from the XI server to validate the configuration parameters.
Regards,
S.Santhosh Kumar

To Add additinal feilds in the Standard Support Desk message screen

Hello Experts,
                    The requirement is to add the attachment feild in the support desk message screen in the Fast track tab , although in the transaction tab already the document option is available for attachments the end user's want it in intial screen
    I think this can be done EASY ENHANCEMENT WORKBENCH - EEWB but i have not worked with it,can anyone tell me about its working?....IS there any screen Exits or USer Exits available for the same?
IS it possible to do this?
if anyone has woked with this please give me your valuable suggestions.This is a urgent requirement give me a solution ASAP.
Thanks & Regards,
Mohana Priya

Hi Suzzane,
                 Thank you for sending me the useful link that gave me the steps to go ahead in EEWB.
Now i have created a object and extention in EEWB ,the it took me to the wizard automatically ,i followed up the notes in wizard and after it is completed, it shows a ERROR message as "Definition CRM_BTX_ADD_NEW_FIELDS is of the type 'TSK' and should run on an external system. This is not permissible. Only definitions of type 'SEQ' may be created for external systems."
The inputs that i gave in while creating Extention are :
1)EEW Businness object : BUSINESS_TRANSACTION ( i.e) CRM BUSINESS
TRANSACTION)
2)Extention type : ADD_NEW_FIELDS
The inputs that i gave in wizard inorder to add attachment as a new feild in CRMD_ORDER transaction are:
1) In step 2 of wizard to select thae business transaction type i choose service process and tried even business activity .
2) While defining the feild name, i gave Attachment as the feild name and choos check box.
then follwed with the rest of the steps and completed the wizard.
Now can you tell me,if the steps and the inputs that i gave are right or nt?
and what does the Error Message mean? i think it is some system settings ,how to resolve this ?
Please give me your suggestions ASAP.

Change the status of a Support Desk Message in Sol. Man.

Hello,
On the Solution manager system I have configured the service desk functionality. So end users are able to create support messages from the satellite systems as well on the solution manager system. For the confirmation of a proposed solution I want to use a workflow which asks the creator if the proposed solution is correct yes or no.
Is there a BAPI or function which change the status of the support desk message? If so how does this BAPI or function work. An example would be great.
Kind regards,
Richard Meijn

decveloped the custom rfc

RE: Mail notification on changing the status of the spport desk messages

Hi,
I am facing problem with the automatic mail notification in service desk configuration.
When i create a support desk message in the satellite system, the message appears in crn_dno_monitor in solution manager. When i change the status of the message from new to in process, i get a mail only with the subject line "MESSAGE IN PROCESS STATUS' and the pdf attachement (sapscript) is missing. I have checked all the configurations in SPPFCADM but i am not able to figure out the problem. Please help me out of this problem.
Regards,
Sowmya

Hi,
there is a SAP Note with a tutor for send_mail via action. See Note 691303 and the attached .zip-file.
It shows step by step how to set it up and is a very good tutorial. You'll need additional (free) software to let it run.
Regards,
Dirk
@Sowmya: what content does the mail have? None? There is a possibility in SolMan where you can choose whether you want the content as a .PDF-Attachment (which, in my eyes, isn't that sparkling) or as regular mail text.
It is located in TA SCOT. Double klick on "SMTP", then klick on "Internet" and there choose in the Drop Down Menu of Sapscript. When you have trouble, look at my [screenshot|http://home.arcor.de/dirk.malas/solman/Mail_TXT_PDF.JPG].

Problem in assigning number range to support desk messages

Gurus ,
we are in the process of configuring service desk in solution manager
7.0 .
so far the following steps were done ,
- implemented note 898614
-Activate Solution Manager Services via SICF
-activated BC sets for service desk
-Fetched SAP components vis DSWP
-Assigned number range for ABA notification via DNO_CUST01
but while assigning the support desk for service messages via ,
SPRO--> SAP Solution Manager --> Basic Settings --> SAP Solution
Manager System --> Service Desk --> Number Ranges for Notifications.
Then press the execute icon ( ) next to Assign number range for Service
Desk Messages.,
when assigning internal number as '01' and external number as '02' and clicking on save button we
get the error as "Enter valid number range interval '

Hi Susin,
you may have a look at this to get more information about number ranges
http://help.sap.com/saphelp_nw70/helpdata/EN/2a/fa02fd493111d182b70000e829fbfe/frameset.htm
A number range is a range of numbers which are assigned to objects uniquely.
Such numbers are some kind of identifiers (which may be used to describe obejcts). In your case the ABA / Basis notifications are identified by those unique numbers.
Hope this clarifies things a bit.
/cheers

Automation of support desk message

How to create support desk messages to some concern persons automatically when a new record is created in a table..

Hello Kumar,
This is how you can achieve whatever you want to
Option 1) Try and find a BADI which gets triggered when a new Personnal nos is created....In this BADI you need to Write a code which eventually creates a Service desk message for you ( This might require CRM technical help fo finding out the right function module.....)
Option 2) Run a report in the background daily which keep on figuring out whether a new Personnel is created or not... and accordingly creates a service desk message for you..which again requires CRM technical expertise who would help u creating the service desk message...
These are the only two options you have.... Revert for any clarifications you might need and inspire ppl by rewarding...
Regards,
Anand..

Problem while updating the Support Package 17 on my SAP WAS SP9

Hi,
I'm facing problem while updating the Support Package 17 on my SAP WAS SP9
ERROR 2006-10-13 10:23:22
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).
Please help me in this regard.....
Thanks in advance...
Satya

Hello gentlemen, I am also having problem with the following running on 64 bit Windows and SQL2005/64 bit. I am erroring in Step 8 'Updating JDBC' driver. I am attempting to update from SP9 to SP18. The WEBAS Jave installed went flawless but I seem to be stuck here. Any help is appreciated...
ERROR 2006-11-22 10:13:57
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).

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 while creating the 'LOV' type parameter in Siebel 8.1.1.5

Hi,
One of my Customer is facing the below error while creatting the parameter of type 'LOV' in Parameter applet in Siebel 8.1.1.5
Runtime Error!
Program: C:\Program Files\Internet Explorer\iexplorer.exe
This application has requested the Runtime to terminate it in an usual way. Please contact the application’s support team for more information
Could some please let me know what would be the reason for this issue?
Thanks in advance for your help.
Thanks,
Ravi

Please close this thread...it appears that the error occurs when the report involves a big set of records. I tried trying to filter only one record and was able to produce the pdf

Set sap Component mandatory while creating the support desk message

Similar Messages

Maybe you are looking for