Estimated end of support message mandatory

Hi,
I am having a requirement like, when i change the catgory from 1 category to other, Estimated end of support message should become mandatory, How to do this?
Raj

Hi
Either you can implement SLA which changes the date range on changing input parameters
or
Without it you can implement BADI for Crmd_order dno_event_save to achieve this.
Hope it helps
Since both topics are already discussed in detail in several thread earlier...you can search sdn for more info
Regards
Prakhar

Similar Messages

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.

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

Service desk error creating support message "help- create support message"

Hi
I'm customizing SM 7.0 SP Stack 15 service desk scenario. I'm in a VAR SAP, so It's a mandatory scenario.
I've done all basic settings from General Settings, Connection to SAP, Online Documentation, ...,
Business Partners, iBase, Basic BC-Sets for Configuration, Number Ranges. After them , for Scenario-Specific Settings-> Service Desk->Service Provider I've done all these steps. At SAP System Solution Manager, I've created solutions at dswp transaction and EW Alert are centralized these steps works. Transaction notif_create works and iBase are well mantained.
The problem is when I try create a support message from satellite SAP system. I logged With a SAP user which is BP, key user and has authorizations in a satellite system and I choose help->create support message, so a pop-up appears and I fill the fields, and I press button (Save/Send). An error appears:
Error in Local Message System: Access via 'NULL' object reference not possible. Message was Not Created
In order solve the error I review:
- The satellite SAP system is at the iBase installed components.
- I've Assign Number Range for ABA notifications at SLF1 transaction.
- I've Checked number range for Service Desk Message at SLFN transaction.
- I've configured ABA Message transaction DNO_CUST01, transaction DNO_CUST04
- (satellite system) Transaction sm30, table BCOS_CUST:
   Appl.            +       Dest.                                  +                     +
   OSS_MSG   W     SM_SMGCLNT010_BACK    CUST620          1.0
   TST_CUS                                                        0120009939
   RFC SM_SMGCLNT010_BACK works, SM recollects EW Alert from this satellite system
- (satellite system) I logged with a SAP user with these roles:
SAP_SUPPDESK_CREATE
SAP_BC_CUS_CUSTOMIZER according SAP NOTE 834534
SAP_BC_CUS_ADMIN       according SAP NOTE 834534
SAP_SV_FDB_NOTIF_BC_CREATE
SAP_SV_FDB_NOTIF_BC_ADMIN
All these roles are mantained.
- I've review SAP Notes 834534, 864195, 621927(I haven't applied this SAP Note because it's older)
Please could you help me?
Thanks and Regards
Raul

Hi,
When I try create a SAP message via help->create suuport message, I get the same error so I run help->create support message in a satellite system so I run help->create support message in Solution Manager
system. Also, a dump is generated in Solution Manager when I try create support message or from satellite or from solution manager.
========================================================================
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
Date and Time          10.07.2008 10:17:26
Short text
    Access via 'NULL' object reference not possible.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_BOR_SERVICE_PPF============CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: " ").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "OBJECTS_OBJREF_NOT_ASSIGNED" " "
    "CL_BOR_SERVICE_PPF============CP" or "CL_BOR_SERVICE_PPF============CM004"
    "PROFILE_CONTAINS_PARTNERDEP"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
Information on where terminated
    Termination occurred in the ABAP program "CL_BOR_SERVICE_PPF============CP" -
     in "PROFILE_CONTAINS_PARTNERDEP".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 41
    of the (Include) program "CL_BOR_SERVICE_PPF============CM004".
=========================================================================
Thanks and Regards
Raul

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

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

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

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

Howto Close support message in Solution Manager

Hello,
Iu2019m installing and setting up the Service Desk on my Solution Monitoring system.
Iu2019m able now to create a support message in my satellite system with menu action u201CHelp  Create Support Messageu201D. The message is put in the queue and could be edited in the tr-Solution_Manager under the Item u201CService Desk  Messagesu201D. When I open a message Iu2019m able to change the status of the message form u201CNewu201D to u201C in progressu201D etc. but the item u201CConfirmedu201D is always gray!
Could anyone explain to me how I or the end user could confirm thesupport message?
I couldnu2019t find a detailed description about the process flow only a global one.
Thanks for the information.
Kind regards,
Richard Meijn

Hi Meijn,
Already solved? If no, check the following customizing.
In SPRO, SAP Solution Manager -> Scenario-Specific Settings -> Service Desk -> Service Desk -> Status Profile -> Change Status Profile for User Status, then choose status profile "SLFN0001" or your customized profile.
"Lowest status no." and "Highest status no." shows which status it can be changed to.
For example, in the following case, you can not change the status from NEW to Confirmed. Also, you can not change it from WIP to NEW. In such cases, target status which you can not change to will be shown as gray in status list.
Status Text low high
10   NEW 10 20
20...WIP    20 40
30...
40   Confirmed 40 40
I hope this could help...
Kobayashi

Support Message and cProject

Hi experts,
I'm working with Solman Service desk and I would like to know
how can I do to create support message in cProject?
Somebody help me.
Thanks
Daniely

Hi Ragu,
I'm implementing the SolMan - Service Desk.
So the end-user can create support message in many system like CRM, R/3, and BW. The end-user working in c-Project too but, in this system there isn't the same option (through help- create support message).
I wouldnu2019t like available a link to SolMan - Service desk because, in this way the system not fill the component system automatically for example.
Is it possible to available u2018help-create support messageu2019 like the other system?
Do you know how can I do this?
Thanks
Daniely

How to Create Support Message with no SolMan User

Hi all,
I would like to test if it is possible to create a support message from ECC system, if the same user do not have a SolMan user.
Now, in few other threads, like
Creation of support message in SolMan without having user id in SolMan
Re: Do End User Require Login in Solman to raise Support Messages !!
show to the user there support message list
e.t.c.
it is clearly stated: it is possible.
I have done the next steps:
In ECC:
- created a test user
- assighned him a "sap_all" profile (and "Z_SAP_SV_FDB_NOTIF_BC_CREATE" role) + user comparasion
- assighned him a "Z_SAP_S_RFCACL" role + user comparasion
In Solman:
- No user created
- In TX DNO_CUST04 the Field Name "NO_USER_CHECK" is maintained with the value "X".
- In tx BP business partner is created as a general BP, with valid external SYS ID no (other users with both ECC and SM user are OK), and changed to "employee" with ECC username defined.
Now, the problem is when I try to create a support message as a test user in ECC, I get an error:
"Error in Local Message System: No authorization to logon as trusted system (Trust Message was Not Created"
All I could find is the tread:
solution maanger issue
and this one is basicly different:
the mentioned user has both ECC and SM user.
And one of the answers was the user must have S_RFCACL roles in BOTH ECC ans SM systems...
In ST22 (in solman) I get error description:
" An RFC call (Remote Function Call) was sent with the invalid user ID
"TEST_T01230 "
. Or the calling system is not registered as trusted system in the
target system."
Now, the calling system IS regged as a trusted sys (as I mantioned - other users with both ECC and SM users can send supp. msgs)
So - the only answer is "invalid user ID".
The short message is
" No authorization to logon as trusted system (Trusted RC=0)"
and the trusted return codes ( 0 ) have the following meaning: Invalid logon data (user ID and client) for the trusting system.
So. how can I perform trusted Logon with no user in SM?
Thank you in advance,
cheers
Nenad

Hi again,
thank you for your help.
At first I thought you meant *_back dest. directly in SM, and now I see you ment to use SMSY to go to ECC sys, and maintain the RFC conns on ECC diredtly from SMSY, "clean-up RFC Destinations". Yes, can do
So:
The problem is solved.
I deleted the *_back user from ECC to SM, and re-generated the connection with default system pre-defined user SMB_T01. (it is interesting that SU01 reports - user SMB_T01 does not exist)
I even deleted a SRFCACL role from the test user in ECC, and the user was still able to create the support message (certanly he was, as he uses a *:back rfc with SMB_T01to log on to SM)
So, resume:
To be able to create / send a support message from another system, with no user in SolMan, it is needed:
- a user in other system with roles needed for everyday work, + "Z_SAP_SV_FDB_NOTIF_BC_CREATE" role;
- a not trusted SM_<SID>CLNT<CLNT_NB>_BACK rfc connection from satelite system to SolMan, with defined logon user (with apropriate authorisations) - generated by the system.
- the BCOS_CUST table in ECC system should be onfigured like: OSS_MSG W SM_<SID>CLNT<CLNT_NB>_BACK CUST 620 1.0
- a Business Partner for user in SM with identification number for system from where the massege will be sent from. (the user can send the note with out this condition, but the "created by" field in message will be empty in that case)
Once again thank you,
cheers,
Nenad
Case closed.
Edited by: Nenad nikolic on Mar 23, 2010 10:54 AM
Edited by: Nenad nikolic on Mar 23, 2010 10:57 AM

How to Activate component is Support Message

Dear Friends,
Path: Support Message -> Transaction Data -> SAP Attributes-> Component Field, press F4
in the F4 I will get list of components. But for ' MM Material Management' its Grey. If I select MM, system gives error"Software component PP not available , check your entry"
So if I activate this componet MM, then I think it will allow to choose MM & will not give error.
Regards
Praveen K

Dear Rajeev,
The path which I have mentioned. Path: Support Message -> Transaction Data -> SAP Attributes-> Component Field
In this filed MM comes automatically, since end user has raised the support desk message with MM component.so that it will determine MM support team.
Once the support desk message is in process & if I want to change the component (which is already having MM) in the path :Support Message -> Transaction Data -> SAP Attributes-> Component Field
If I edit this MM coponent & try to enter PP it will give error, but even if I want save it with same MM component it give error. ANy way if I want to select MM from F4 , it will not select, Becoze MM Grey color(Not active)
Regards
Praveen K
Edited by: PK on Mar 19, 2010 10:26 AM

End of support for BO XI R3 SP5

Hi, Please anyone can tell me when is end of support for BO XI R3 SP5 as per SAP officials. I read existing threads, few tell March'2013 and few tell March'2015. I will appreciate the correct and exact reply. Thanks Akash

Better to raise a message to SAP support in SMP.

End of Support for Netscape web browsers

Sorry if this has been here before and I missed it....
"We'll continue to release security patches for the current
version of
the browser, Netscape Navigator until February 1, 2008. After
February
1, there will be no more active product support for Navigator
9, or
any previous Netscape Navigator browser. This includes
Netscape
v1-v4.x, Netscape v6, Netscape v7 Suite, Netscape Browser v8,
and
Netscape Navigator/Messenger 9."
http://blog.netscape.com/2007/12/28/end-of-support-for-netscape-web-browsers/
~Malcolm N....
~

What's Netscape? :)
Kind Regards
Paul Dell
An Eye of Menorca
www.dellimages.com
Blog
www.paul-dell.com
"Malcolm N_" <[email protected]> wrote in message
news:[email protected]..
>
> Sorry if this has been here before and I missed it....
>
> "We'll continue to release security patches for the
current version of
> the browser, Netscape Navigator until February 1, 2008.
After February
> 1, there will be no more active product support for
Navigator 9, or
> any previous Netscape Navigator browser. This includes
Netscape
> v1-v4.x, Netscape v6, Netscape v7 Suite, Netscape
Browser v8, and
> Netscape Navigator/Messenger 9."
>
>
>
http://blog.netscape.com/2007/12/28/end-of-support-for-netscape-web-browsers/
> --
>
> ~Malcolm N....
> ~

Java MQ 3.6 End of Support date?

Is there an announced date for the End of Support of Java System Message Queue 3.6?
TIA!

The following are the end of support dates for MQ 3.6
Product Name Prod Status EOL Date Full Support End Date Limited Support End Date (EOSL)
Sun Java System
Message Queue 3.6 SPx EOL 08/2008 08/2009 08/2013
There won't be any bug fixes after Full Support End Date.

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

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

Estimated end of support message mandatory

Similar Messages

Maybe you are looking for