Solution Manager 4.0/When accessing services as ex. showing graphic in Proj

Hi,
We have just upgraded from Solution Manager 3.1 to 4.0. When accessing services as ex. showing graphic in Projects, tab graphics shows: " Service cannot be reached.
What has happened?
URL http://dnismpa.danisco.com:1080/sap/bc/solman/defaultUser/graphic/solmangraphic.htm call was terminated because the corresponding service is not available.".
Services activated as told in IMG/Activate Solution Manager Services. Service user created as in IMG/Create Service User for HTTP access. Alias created as in IMG/Create Alias for Business Server Pages and Create Alias for Document Manager Service.
Please, can anybody advise on this issue. Thanks in advance.
Med venlig hilsen / Best regards
Hanne Münther
Danisco IT/SAP-Basis
Danisco A/S

Hello,
Same problem here. Did you find a solution to your problem ?
Regards.

Similar Messages

Solution Manager prepared for the Remote Service Delivery?

In preparation of GoingLive Session, we received a mail with some questions. Among them the following:
Is your Solution Manager prepared for the Remote Service Delivery? Yes/No
Is the solution transferred to SAP?: Yes/No
What does the first question mean? what should be done to prepare the Solman for session delivery?
How do I check if the solution is transferred to SAP?
Thanks a lot,
    Dino

Hello Dino,
The SAP Solution Manager is a platform for the delivery of services for the following areas:
●     Risk minimization
●     Optimization of SAP solutions
●     Knowledge transfer
Services in the SAP Solution Manager are services which help you to monitor and optimize the performance and availibility of your system landscapes and minimize your system operation risks.
You can have the support services performed by SAP or perform them yourself:
●     Remote Services
SAP experts deliver this service type via a remote connection (SAP Safeguarding Services, e.g. SAP GoingLive Check).
For checking whether solution manager is prepared for remote service delivery u need to check the following.
Prerequisites
You have:
●     created a solution.
●     set-up a connection to the SAP Service Marketplace (Explorer).
Procedure
       1.      Choose the transaction SOLUTION_MANAGER.
       2.      Choose Delivery of SAP Services ® Service Plan, in Operations.
       3.      Choose Order Service from SAP.
You go to the Service Catalog.
       4.      Choose the link to the service.
The system goes to the catalog entry of the service, in the SAP Service Marketplace.
       5.      Follow the procedure described in the SAP Service Marketplace.
=============================================
Solution transfered to SAP means that the u have done the configuration, testing and validation of the SAP system components and then transfered this to the satellite systems connected to Solman. Please note that solman is the central point of access for supporting implementation activities and the satellite systems are SAP systems comnected to solman in the landscape.
Hope this helps. Please assign points and let me know if u need anything specific.
Rgds
Manish

Solution Manager key error when installing ECC6

hi
Iam installing ECC6 abap+java and facing a problem with the solution manager generated key.Each time iam putting in the key its says its the wrong one.
i dont know where iam making a mistake.i managed to generate one before when upgarding to ECC6 and it work withou any problems.
am i making a mistake somewhere?
help appreciated

Hi,
Let me know your SID, Instance No, and Host name. Also write what SOLMAN Key you have entered. I can cross-check that is correct or not.
Rgds,
Mahesh Bansal

Solution Manager ChaRM Issues when Upgrading Satellite System

When upgrading a satellite system that is connected to Solution Manager's Change Request Management, is there anything that we need to be aware of?
Will Change Documents still be able to go to completion (Production status) if we modify the landscape from the time the Change Document is In Development to the time it is moved to Production?
1. Normal Correction (In Development) Development (ECC 5.0) -> Quality (ECC 5.0) -> Production (ECC 5.0)
2. Landscape is changed to Development (ECC 6.0) -> Quality (ECC 6.0) -> Production (ECC 5.0)
3. Normal Correction moved to To Be Tested -> Consolidated -> Production
Will the Normal Correction be in error because the landscape changed for the iBASE?
Are there any other lessons learned that anyone has experienced with Change Request Management or Implementation during and after an upgrade?
Thank You,
Carlen
Edited by: Carlen Yuen on Jan 13, 2009 1:50 AM
Edited by: Carlen Yuen on Jan 13, 2009 1:51 AM

Thanks Subhashini!
We had issues updating the Task List in the past. After we update the landscape and refresh the project and update the Task List, do you foresee any other problems?
Are there any additional items we should look out for? For example, we understand it is a requirement to release all transports prior to beginning the upgrade. However, since the release of the transport locks the change into the cycle for the next production move, this will present a problem if the change is not yet ready to be moved into Production. Do you have any further insight to any additional issues such as this?
Thanks again!
Carlen

Error when accessing service fcom_ip_proj_overall01

Hi all,
When executing a search in Overall Planning using NWBC a 500 SAP Internal Server Error is returned "termination: RABAX_STATE".
The error from the dev_icf log file is below and a screen shot of the dump in ST22 is attached.
I have attempted to implement note 1922770 and 1922817 but neither fixed the problem. I believe the issue has something to do with method _INCL_READ_VIRT in program CL_RSR_HIERARCHY_BUFFER. The notes both talk about a problem in regards to hierarchy. Any help would be greatly appreciated. Thanks!!!
<ErrorInfo URL="https://xxxxxxxxxxxxxxxxx/sap/bc/webdynpro/sap/fcom_ip_proj_overall01">
<ErrorMessage>An exception occurred </ErrorMessage>
<Date>20140527</Date>
<Time>093018</Time>
<Client>800</Client>
<User>JPARKER</User>
<TerminationType>RABAX_STATE</TerminationType>
<ABAP-CallStack>
<Method>
<Name>_INCL_READ_VIRT</Name>
<Program>CL_RSR_HIERARCHY_BUFFER=======CP</Program>
</Method>
<Method>
<Name>CONSTRUCTOR</Name>
<Program>CL_RSR_HIERARCHY_BUFFER=======CP</Program>
</Method>
<Method>
<Name>HIERARCHY_GET</Name>
<Program>CL_RSR_HIERARCHY_BUFFER=======CP</Program>
</Method>
<Form>
<Name>COMPLETE_HIEDIR</Name>
<Program>SAPLRRHI</Program>
</Form>
<Form>
<Name>TRANSIENT_HIEDIR_GET</Name>
<Program>SAPLRRHI</Program>
</Form>
<Function>
<Name>RRHI_HIEDIROLAP_READ</Name>
<Program>SAPLRRHI</Program>
</Function>
<Function>
<Name>RRS_SH_FROM_VREP_FILL</Name>
<Program>SAPLRRS2</Program>
</Function>
<Function>
<Name>RRS_VREP_SH_FILL</Name>
<Program>SAPLRRS2</Program>
</Function>
<Method>
<Name>BLOCK_CHECK</Name>
<Program>CL_RSR_VAR====================CP</Program>
</Method>
<Method>
<Name>IF_RSR_VAR_RUNTIME~CHECK</Name>
<Program>CL_RSR_VAR====================CP</Program>
</Method>
</ABAP-CallStack>
</ErrorInfo>
</ErrorLog>

Issue resolved by changing
LdapResyncOnRestart=No
to
LdapResyncOnRestart=Yes
Regards,
Muhammad Sharfuddin
Originally Posted by sharfuddin
OS: SLES 10 SP4 i586 + online updates
OES2 SP3 + online updates.
Today, I was configuring a POC demo of iFolder to a customer, and faced the following:
iFolder configured with MS AD 2003, and initial configuration(simias-server-setup, ifolder-admin, ifolder-web) went smooth, without errors. But I can't login via ifolder admin(ifadmin) user when accessing Admin Page(http://ip/admin) I got incorrect username password error.
As already informed, that iFolder configuration went smooth(error free) and iFolder Administrator account, plus iFolder Proxy accounts are all available in MS AD 2003, also I have provided the
appropriate DN during configuration(but still I am getting 'username password' error when accessing admin page).
logs says following:
please help asap.

Serialization error when accessing services from AXIS

Have anyone had success in accessing an AXIS service from a JAX-RPC client?
When I called getServiceInfo() method (no parameter), I got the following SOAP message but the JAXRPC client could serialize it and gave me a deserialization error (see bottom).
Thanks for any hint/advice/help
Frank
========= AXIS SOAP MESSAGE =======
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:getServiceInfoResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://www.esri.com/wsdl">
<getServiceInfoReturn xsi:type="xsd:string">-180.0,-90.0,180.0,83.596039,3,CNTRY92|true,LAKES|true,cities|true,0</getServiceInfoReturn>
</ns1:getServiceInfoResponse>
</soapenv:Body>
</soapenv:Envelope>
========= ERROR MESSAGE ==========
java.rmi.RemoteException: Runtime exception; nested exception is:
     deserialization error: XML reader error: unexpected character content: "-180.0,-90.0,180.0,83.596039,3,CNTRY92|true,LAKES|true,cities|true,0"
deserialization error: XML reader error: unexpected character content: "-180.0,-90.0,180.0,83.596039,3,CNTRY92|true,LAKES|true,cities|true,0"
     at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:200)
     at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerImpl.java:115)
     at com.sun.xml.rpc.client.dii.CallInvokerImpl._readFirstBodyElement(CallInvokerImpl.java:147)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:164)
     at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:54)
     at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
     at com.esri.test.SunJAXRPCMapService.getServiceInfo(SunJAXRPCMapService.java:401)
     at com.esri.test.SunJAXRPCMapService.main(SunJAXRPCMapService.java:755)
CAUSE:
XML reader error: unexpected character content: "-180.0,-90.0,180.0,83.596039,3,CNTRY92|true,LAKES|true,cities|true,0"
     at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderBase.java:43)
     at com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.doDeserialize(SOAPResponseSerializer.java:143)
     at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:163)
     at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerImpl.java:115)
     at com.sun.xml.rpc.client.dii.CallInvokerImpl._readFirstBodyElement(CallInvokerImpl.java:147)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:164)
     at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:54)
     at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
     at com.esri.test.SunJAXRPCMapService.getServiceInfo(SunJAXRPCMapService.java:401)
     at com.esri.test.SunJAXRPCMapService.main(SunJAXRPCMapService.java:755)

Hi Frank
I know this topic is fairly old now but I took the chance you might still be watching it. I'm getting deserialization errors on the server side when trying to connect with an Axis client. Did you ever have any joy sorting out the problem?
Cheers,
Jason

SOLUTION MANAGER UPGRADE - Error when shadow system Starting

Hi All, We are upgrading our Solman system from 7.0 EHP 1 to SOLMAN 7.1. But the system is uable to start the Shadow
system. *** ERROR => DpHdlDeadWp: W0 (pid 12046) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12046) exited with exit code 255 *** ERROR => DpHdlDeadWp: W4 (pid 12050) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12050) exited with exit code 255 DpMBufHwIdSet: set Hardware-ID ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296] MBUF state ACTIVE DpWpBlksLow: max wp blocks in queue is 800 (80 %) MBUF component UP DpMsgProcess: 1 server in MBUF DpAppcBlksLow: max appc blocks in queue is 500 (50 %) *** ERROR => DpHdlDeadWp: W3 (pid 12049) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12049) exited with exit code 255 Sun Jan 8 21:50:33 2012 *** ERROR => DpHdlDeadWp: W2 (pid 12048) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12048) exited with exit code 255 *** ERROR => DpHdlDeadWp: W5 (pid 12051) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12051) exited with exit code 255 *** ERROR => DpHdlDeadWp: W6 (pid 12052) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12052) exited with exit code 255 *** ERROR => DpHdlDeadWp: W7 (pid 12053) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12053) exited with exit code 255 *** ERROR => DpHdlDeadWp: W8 (pid 12054) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12054) exited with exit code 255 *** ERROR => DpHdlDeadWp: W9 (pid 12055) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12055) exited with exit code 255 *** ERROR => DpHdlDeadWp: W10 (pid 12056) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12056) exited with exit code 255 *** ERROR => DpHdlDeadWp: W11 (pid 12057) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12057) exited with exit code 255 kill(12045,0) -> ESRCH: process died DpStartStopMsg: send stop message (myname is >solmanqazone_KSQ_04 <) DpStartStopMsg: Write AD_STARTSTOP message with type= 0, name=solmanqazone_KSQ_04 , sapsysnr= 4, hostname=solmanqazone AdGetSelfIdentRecord: > < AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0 AdCallRegisteredCvtToExt: opcode 60 AdCallRegisteredCvtToExt: opcode 60 call 102164870 AdCallRegisteredCvtToExt: opcode 60 exit rc=SAP_O_K AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0 AdCallRegisteredCvtToExt: opcode 4 AdCallRegisteredCvtToExt: opcode 4 call 102160ff8 AdCallRegisteredCvtToExt: opcode 4 exit rc=SAP_O_K DpConvertRequest: net size = 189 bytes NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufSend starting NiIWrite: hdl 17 sent data (wrt=562,pac=1,MESG_IO) MsINiWrite: sent 562 bytes MsISnd2: send msg (ms hdr/msg 110/452 bytes) to name -, type 4, key - DpStartStopMsg: stop msg sent NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufIAlloc: malloc NIBUF-IN, to 32110 bytes NiIRead: hdl 17 received data (rcd=274,pac=1,MESG_IO) NiBufIIn: NIBUF len=274 NiBufIIn: packet complete for hdl 17 NiBufSend starting NiIWrite: hdl 17 sent data (wrt=114,pac=1,MESG_IO) MsINiWrite: sent 114 bytes MsISnd2: send msg (ms hdr/msg 110/4 bytes) to name MSG_SERVER, type 0, key - MsSndName: MS_NOOP ok Send 4 bytes to MSG_SERVER NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufIAlloc: malloc NIBUF-IN, to 32110 bytes NiIRead: hdl 17 received data (rcd=114,pac=1,MESG_IO) NiBufIIn: NIBUF len=114 NiBufIIn: packet complete for hdl 17 NiBufReceive starting MsINiRead: received 114 bytes MsIReceive: received msg (ms hdr/msg 110/4 bytes), flag 3, from MSG_SERVER , typ 0, key - Received 4 bytes from MSG_SERVER Received opcode MS_NOOP from msg_server, reply MSOP_OK MsOpReceive: ok MsISendKeepalive : keepalive sent to message server NiIRead: hdl 17 recv would block (errno=EAGAIN) Sun Jan 8 21:52:21 2012 NiIPeek: peek for hdl 17 timed out (r; 1000ms) NiIRead: read for hdl 17 timed out (1000ms) DpHalt: no more messages from the message server DpHalt: sync with message server o.k. DpHalt: detach from message server ***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 12730] *** ERROR => e=28 semget(20465,1,2016) (28: No space left on device) [semux.c 498] *** ERROR => SemRq: Implicit SemInit failed. Key=65 [semux.c 1129] *** ERROR => Es2Cleanup: SemRq SEM_ES2_ADM (rc=1) [es2xx.c 1082] SemRq( 38, 1, -1) enter SemRq( 38, 1, -1) exit rtc=0, 0us SemRel( 38, 1 ) enter SemRel( 38, 1 ) exit rtc=0, 0us ShmDelete2( 73 ) DpHalt: cleanup event management DpHalt: cleanup shared memory/semaphores SemKeyPermission( 1 ) = 0740 (octal) SemKeyPermission( 1 ) = 0740 (octal) SemKeyPermission( 6 ) = 0740 (octal) SemKeyPermission( 6 ) = 0740 (octal) SemKeyPermission( 7 ) = 0740 (octal) SemKeyPermission( 8 ) = 0740 (octal) SemKeyPermission( 10 ) = 0740 (octal) SemKeyPermission( 11 ) = 0740 (octal) SemKeyPermission( 12 ) = 0740 (octal) SemKeyPermission( 13 ) = 0740 (octal) SemKeyPermission( 14 ) = 0740 (octal) SemKeyPermission( 15 ) = 0740 (octal) SemKeyPermission( 16 ) = 0740 (octal) SemKeyPermission( 17 ) = 0740 (octal) SemKeyPermission( 18 ) = 0740 (octal) SemKeyPermission( 19 ) = 0740 (octal) SemKeyPermission( 20 ) = 0740 (octal) SemKeyPermission( 21 ) = 0740 (octal) SemKeyPermission( 22 ) = 0740 (octal) *** ERROR => e=28 semget(20422,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 24 ) = 0740 (octal) *** ERROR => e=28 semget(20424,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 25 ) = 0740 (octal) *** ERROR => e=28 semget(20425,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 26 ) = 0740 (octal) *** ERROR => e=28 semget(20426,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 27 ) = 0740 (octal) *** ERROR => e=28 semget(20427,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 28 ) = 0740 (octal) *** ERROR => e=28 semget(20428,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 29 ) = 0740 (octal) *** ERROR => e=28 semget(20429,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 30 ) = 0740 (octal) *** ERROR => e=28 semget(20430,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 31 ) = 0740 (octal) *** ERROR => e=28 semget(20431,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 35 ) = 0740 (octal) *** ERROR => e=28 semget(20435,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 42 ) = 0740 (octal) *** ERROR => e=28 semget(20442,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 43 ) = 0740 (octal) *** ERROR => e=28 semget(20443,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 44 ) = 0740 (octal) *** ERROR => e=28 semget(20444,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 45 ) = 0740 (octal) *** ERROR => e=28 semget(20445,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 47 ) = 0740 (octal) *** ERROR => e=28 semget(20447,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 48 ) = 0740 (octal) *** ERROR => e=28 semget(20448,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 49 ) = 0740 (octal) *** ERROR => e=28 semget(20449,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 50 ) = 0740 (octal) *** ERROR => e=28 semget(20450,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 51 ) = 0740 (octal) *** ERROR => e=28 semget(20451,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 53 ) = 0740 (octal) *** ERROR => e=28 semget(20453,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 54 ) = 0740 (octal) *** ERROR => e=28 semget(20454,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 55 ) = 0740 (octal) *** ERROR => e=28 semget(20455,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 56 ) = 0740 (octal) *** ERROR => e=28 semget(20456,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 57 ) = 0740 (octal) *** ERROR => e=28 semget(20457,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 58 ) = 0740 (octal) DpCleanupSharedResources: MpiCleanup ShmCleanup( 62 ) ShmCreate( 62, 0, 2, 0xffffffff7fffea78 ) ShmProtect( 62, 3 ) ShmKeySharedMMU( 62 ) = 0 (octal) ShmProtect: shmat key 62 prot 3/0 done ShmCreate( 62, 0, 2, -> 0xfffffffe1d400000 ) MpiCleanup() -> MPI_OK DpCleanupSharedResources: removing Semaphore-Management DpCleanupSharedResources: removing request queue ShmCleanup( 31 ) ShmCreate( 31, 0, 2, 0xffffffff7fffea78 ) ShmProtect( 31, 3 ) ShmKeySharedMMU( 31 ) = 0 (octal) ShmProtect: shmat key 31 prot 3/0 done ShmCreate( 31, 0, 2, -> 0xffffffff24000000 ) DpCleanupSharedResources: ShmCleanup SHM_SYS_ADM_KEY ShmCleanup( 1 ) ShmCreate( 1, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 1, 3 ) ShmKeySharedMMU( 1 ) = 0 (octal) ShmProtect: shmat key 1 prot 3/0 done ShmCreate( 1, 0, 2, -> 0xffffffff78100000 ) DpCleanupSharedResources: ShmCleanup SHM_DP_ADM_KEY ShmCleanup( 2 ) ShmCreate( 2, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 2, 3 ) ShmKeySharedMMU( 2 ) = 0 (octal) ShmProtect: shmat key 2 prot 3/0 done ShmCreate( 2, 0, 2, -> 0xffffffff28800000 ) DpCleanupSharedResources: ShmCleanup SHM_DP_CA_KEY ShmCleanup( 3 ) ShmCreate( 3, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 3, 3 ) ShmKeySharedMMU( 3 ) = 0 (octal) ShmProtect: shmat key 3 prot 3/0 done ShmCreate( 3, 0, 2, -> 0xffffffff24800000 ) DpCleanupSharedResources: ShmCleanup SHM_PF_KEY ShmCleanup( 4 ) ShmCreate( 4, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 4 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_SAPSCSA_AREA_KEY ShmCleanup( 5 ) ShmCreate( 5, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 5 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PXA_KEY ShmCleanup( 6 ) ShmCreate( 6, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 6 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_VB_ADM_KEY ShmCleanup( 7 ) ShmCreate( 7, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 7 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PAGING_AREA_KEY ShmCleanup( 8 ) ShmCreate( 8, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 8 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_ROLL_AREA_KEY ShmCleanup( 9 ) ShmCreate( 9, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 9 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_CALI_BUFFER ShmCleanup( 11 ) ShmCreate( 11, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 11, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_CCC_KEY ShmCleanup( 12 ) ShmCreate( 12, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 12, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_ALERT_AREA_KEY ShmCleanup( 13 ) ShmCreate( 13, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 13, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_PRES_BUF ShmCleanup( 14 ) ShmCreate( 14, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 14, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup DVS_SHM_KEY ShmCleanup( 15 ) ShmCreate( 15, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 15, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_SEM_MONI_BUFFER ShmCleanup( 16 ) ShmCreate( 16, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 16, 3 ) ShmCreate( 16, 0, 2, -> 0xffffffff29004000 ) ShmDelete2( 10 ) Sun Jan 8 21:52:22 2012 DpCleanupSharedResources: ShmCleanup SHM_ROLL_ADM_KEY ShmCleanup( 17 ) ShmCreate( 17, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 17, 0, 2, 0xffffffff7fffe9e0 ) ShmCreate( 10, 0, 2, 0xffffffff7fffe828 ) ShmKeyPermission( 10 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PAGING_ADM_KEY ShmCleanup( 18 ) ShmCreate( 18, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 18 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_DB_TBUFF ShmCleanup( 19 ) ShmProtect( 52, 3 ) ShmKeySharedMMU( 52 ) = 0 (octal) ShmProtect: shmat key 52 prot 3/0 done ShmCreate( 52, 0, 2, -> 0xffffffff77600000 ) DpCleanupSharedResources: ShmCleanup SHM_ES_ADM_T ShmCleanup( 53 ) ShmCreate( 53, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 53 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_DB_OBJ_BUFFER ShmCleanup( 54 ) ShmCreate( 54, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 54 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_RSPO_LOCAL_KEY ShmCleanup( 55 ) ShmCreate( 55, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 55 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PF_AS_KEY ShmCleanup( 56 ) ShmCreate( 56, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 56 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PROFILE ShmCleanup( 57 ) ShmCreate( 57, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 57, 3 ) ShmKeySharedMMU( 57 ) = 0 (octal) ShmProtect: shmat key 57 prot 3/0 done ShmCreate( 57, 0, 2, -> 0xffffffff75700000 ) DpCleanupSharedResources: ShmCleanup SHM_ENQID_KEY ShmCleanup( 58 )
Regards, VIjay K.G

Hi,
From logs:
28: No space left on device
Check the disk space. If linux, use df -h command. Windows its easier
Check if any drive / file system is 100% used up.
Regards,
Srikishan

Solution Manager: Creating test plan - no test cases uploaded show up

Hi,
I am attempting to create test plans that include all the test case documents that I uploaded to the system. Unfortunately, when I upload the documents, check them out and then in again, and then go to stwb_2 to create a test plan, the documents do not show up in the test plan structure.
Why is this and is there someway to make the documents show up?
Thank you!
Edited by: acraver on Mar 13, 2009 6:37 PM

Have u tried regenerating the Test plan by going to change mode and pressing the generate button after selecting the documents
Secondly what is the status of the doc is it change
Note whn u generate the test plan you have to chooose the Status of the Test Documents.
Hope it solve ur problem
Regards
Prakhar

Service Desk Customizing in Solution Manager 4.0 SPS12

Hello,
I try to customize the service desk in solution manager SPS 12.
I follow the IMG :
1. General Settings of solution Manager (Profiles...) => OK
2. Connection to SAP => OK
3. System Landscape and Solution
    Only One system my solution Manager. => OK
4. Service Desk BC Sets => OK
5. Business Partner :
    I have created two key users (KEY_USER1 & KEY_USER2) as BPs (101 & 106)
    I have created One System Admin (ADMIN) as BPs (105)
    I have created two Message Processors (PROC1 & PROC2) as BPs (102 & 103)
    I have created one Org. as BPs 104.
=> OK
6. iBase
   I have initially created the iBase from my solution => OK
   I try to assign the partner to the iBase component => First Problem : the system do not propose the System Admin & key user function when I go to Goto->Partner. Do I miss something ?
7. Org Model
I try to create my Org. model as follow :
Service Desk (O)
         Team 1 (O)
             Processor1 (S)
                 SDUser1 (BP)
                     PROC1 (U)
         Team 2 (O)
             Processor2 (S)
                SDUser2 (BP)
                     PROC2(U)
=> Second problem : it is said in the documentation and in some blogs on the sdn, that when we create the root org, and the subsequent org, the system will create and assign automatically the BPs. That doesn't work in my system. I do not understand why. So I have assigned directly the position conatining the Users Proc1 & Proc2 as BPs.
8. Partner Determination
    Then I would like to assign automatically messages created by KEY_USER1 to PROC1 and messages created by KEY_USER2 to PROC2 depending on the user group they belong (or depending on the relationship they have with the messages processors).
    => Third Problem : I don't how to do it ! and i don't know what to do with the partner function Support Team.
Could someone help me.
Thanks in advance.
Guillaume Bruyneel.

hello,
I found some interesting information concerning the automatic creation of BP from the Org. Model :
I have activated the HR integration through :
IMG->CRM->Master Data->Business Partner->Integration Business Partner-Organisation Management.
And NOW the automatic creation of the BP is working !
I'm still trying to solve the two other problems.
Guillaume.

Regarding Monitoring Service for Solution manager

We need to configure "Monitoring" services in SAP solution manager 7.0.
Could somebody suggest us what are the main tasks we need to consider for doing Monitoring settings.
How many Minimum servers required to configure Monitoring services in solution manager system.
Also if any good document reference for this?
Thanks

Hi Jai,
welcome to sdn.
COMPONENTS & TOOLS OF SAP NETWEAVER
SAP Solution Manager
The SAP Solution Manager application management solution facilitates technical support for distributed systems u2013 with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. A centralized, robust application management and administration solution, SAP Solution Manager combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. And, as a customer of SAP, you have full access to the core SAP Solution Manager for no extra charge.
SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
SAP Solution Manager features and functions include:
SAP Business Suite implementation and upgrades u2013 SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
Change control management u2013 SAP Solution Manager controls all software and configuration changes of the IT solution. This includes the approval process for change requests, the deployment of changes, and later analysis of changes. This ensures quality of the solution and enables traceability of all changes.
Testing u2013 SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
IT and application support u2013 The service desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
Root cause analysis u2013 The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems, even in heterogeneous environments. This helps to isolate general performance bottlenecks, to isolate exceptional situations, to record the activity of single users or processes, and to identify changes to the productive landscape. As a result, problem resolution is accelerated and business availability increased.
Solution monitoring u2013 SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
Service-level management and reporting u2013 SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
Service processing u2013 SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
Administration u2013 Administration tasks are mainly executed locally on the involved systems, but can be accessed and triggered from a central administration console. The administration work center in SAP Solution Manager offers a central entry point and unified access to all SAP technology.
SAP Solution Manager as the name suggests is for managing the whole gamut of SAP and Non-SAP solutions in the IT Landscape of an organisation. It provides you the tool, content and gateway to create, operate, manage and monitor your solutions over time.
It provides a range of scenarios to support this. Extending from project management to Solution Monitoring to Service Desk to E-learning Management, it provides an efficient way to carry out a plethora of business tasks.
SAP Solution Manager is the successor to ASAP ValueSAP. SAP Solution Manager helps in implementing and managing complex system landscapes. Globally systems are getting distributed across geographies and business processes cover more than one system. In such complex scenarios, integrating technical and business requirements is important for the success of IT. SAP Solution Manager provides SAP customers with an efficient means of handling both the technical and business process side of solution implementation .
As part of SAP Solution Management Solutions, the customers receive best practices relating to:
- Global Strategy and Service Level Management
- Business Process Management
- Management of MySAP Technology
- Software Change Management
- Support Desk Management
SAP delivers this using support programs during implementation of the system solution. Some of the benefits of using SAP's Solution Manager are that it helps:
- Manages the technical risk associated with the implementation of the solution ensuring technical robustness
- Helps leverage users core competencies in implementing solutions
- Ensures solution works as intended with best practices built in.
see these links...
http://www.ne-sap-solution-manager.com/
http://www.saptechies.com/category/sap-solution-manager/
thanks
karthik
reward me if usefull

Solution Manager does not get service definitions from SAP in self diagnosi

Hi,
In our production solution manager transaction solution_manager, self diagnosis we are getting a warning message on our development solution manager.
Solution Manager XXX does not get service definitions from SAP.
The production Solution Manager is the master in SDCCN for the test Solution Manager. In the test Solution Manager, the scheduled task REFRESH SERVICE DEFINITIONS has task System ID of O01. It is pointed to RFC destination SDCC_OSS, not the production Solution Manager system.
It gives the same warning if I point the task to the production Solution Manager system.
Has anyone seen this before? Any ideas?
Best regards,
Russ

Hi,
i guess have you activated SDCCN from your solution manager system too?
if not please activate. since that setup helps solman retrive the service definitions used in SDCCN from SAP (SAPOSS).so this ultimately allows you to set solution manager system as Master, so all the satellite system get the service definition from solman and do not need a direct SAPOSS connection.
and Please check this Note 1143775 - SAP service content update
the wiki for trouble shoot ["EarlyWatch Alert is Red Flagged - how to resolve" |http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=228262728]
please check.
Thanks,
Jansi

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.

Solution Manager Learning Map http error 403

Hi,
I created a new learning map in solution manager using solar_learning_map, when I attempted to display the learning map in the web browser i received the following error.
<i><URL> call was terminated because the corresponding service is not available.
The termination occurred in system ISD with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .</i>
If anyone else has experienced this error before can you please give me some guidance on resolving this issue.

The Note exists in service marketplace. (Topic is Inactive services in the Internet Comm Framework).Here is the solution as per the Note.
Solution
Listed below are some services that must be activated in the system
depending on the operational scenario:
Support for the Internet protocol (HTTP, HTTPS and SMTP) in the SAP Web Application Server
/default_host/sap/public/icman
Note: After you have installed SAP Web Application Server, you must ensure that this service is activated in transaction SICF. Through this the ICMan process can (for example) make decisions concerning the distribution of HTTP requests to the corresponding server.
Using load distribution
with the message server
/default_host/sap/public/icf_info
/default_host/sap/public/icf_info/logon_groups
/default_host/sap/public/icf_info/urlprefix
with the Web Dispatcher
/default_host/sap/public/icf_info
/default_host/sap/public/icf_info/icr_groups
/default_host/sap/public/icf_info/icr_urlprefix
Using Business Server Pages (BSP)
/default_host/sap/bc/bsp/sap
/default_host/sap/bc/bsp/sap/system
/default_host/sap/bc/bsp/sap/public/bc
/default_host/sap/public/bc (available for 620 with Support Package 34)
/default_host/sap/public/bc/ur (available for 620 with Support Package34)
/default_host/sap/public/bsp/sap/public
/default_host/sap/public/bsp/sap/public/bc
/default_host/sap/public/bsp/sap/system
/default_host/sap/public/bsp/sap/htmlb (as of Release 620 Support Package SAPKB62026)
Note: In addition to these general BSP services, you still have to activate the corresponding application services in the ICF tree. The service for the application is generally found under the ICF node /default_host/sap/bc/bsp/sap/<application>.
Using the BSP logon procedure
/default_host/sap/public/bsp/sap
/default_host/sap/bc/bsp/sap/system
/default_host/sap/public/bsp/sap/public
/default_host/sap/public/bsp/sap/system
BSP test applications for troubleshooting
/default_host/sap/bc/bsp/sap/it00
/default_host/sap/bc/bsp/sap/sbspext_htmlb
/default_host/sap/bc/bsp/sap/sbspext_xhtmlb
/default_host/sap/bc/bsp/sap/htmlb_samples
As of Release 6.30:
/default_host/sap/bc/bsp/sap/bsp_verificatio
Using Business Information Warehouse (BW)
/default_host/sap/bw
Web Applications
/default_host/sap/bw/BEx
/default_host/sap/bw/Mime
Reporting agent preliminary calculation
/default_host/sap/bw/ps
Drag and Relate in the portal
/default_host/sap/bw/dr
Data access using XMLA
/default_host/sap/bw/xml and all subordinate subservices
Document integration in the BEx Analyzer and Web Applications.
/default_host/sap/bw/doc and all subordinate subservices
Formatted reporting
/default_host/sap/bw/ce_url
Assignment of SAP icons
/default_host/sap/public/bc
/default_host/sap/public/bc/icons
/default_host/sap/public/bc/icons_rtl
/default_host/sap/public/bc/webicons
/default_host/sap/public/bc/pictograms
Assignment of Web Dynpro ABAP (WDA) applications
/default_host/sap/bc/webdynpro
/default_host/sap/public/bc
/default_host/sap/public/bc/ur
/default_host/sap/public/bc/icons
/default_host/sap/public/bc/icons_rtl
/default_host/sap/public/bc/webicons
/default_host/sap/public/bc/pictograms
/default_host/sap/public/bc/webdynpro/* (ssr, mimes, and so on)
/default_host/sap/public/myssocntl
Note: In addition to these general WDA services, the corresponding application services in the ICF tree also need to be activated. The service for the application is generally found under the ICF node /default_host/sap/bc/webdynpro/sap/<application>.
Assignment of Web Dynpro ABAP (WDA) development environment
/default_host/sap/bc/webdynpro/sap/public/bc/viewdesigner/
/default_host/sap/bc/wdvd/
/default_host/sap/bc/webdynpro/sap/configure_application
/default_host/sap/bc/webdynpro/sap/configure_component
/default_host/sap/bc/webdynpro/sap/wd_analyze_config_appl
/default_host/sap/bc/webdynpro/sap/wd_analyze_config_comp
/default_host/sap/bc/webdynpro/sap/wd_analyze_config_user
Note: These ICF nodes are used for the WDA configuration editor ONLY. The nodes are only allowed to be active in a development system, and under no circumstances in a production system (due to a security risk).
WDA test applications for troubleshooting
/default_host/sap/bc/webdynpro/sap/wdr_test_events
/default_host/sap/bc/webdynpro/sap/wdr_test_ui_elements
/default_host/sap/bc/webdynpro/sap/wdr_test_table
/default_host/sap/bc/webdynpro/sap/wdr_test_popups_rt
ICF test applications:
/default_host/sap/bc/echo
Among other things, this service returns information about the registration procedure being used, the header and form fields, and the generated SSO cookie for the executed request. Therefore, this service should only be activated for troubleshooting purposes.
/default_host/sap/bc/error
This service generates some error situations in the system and should only be activated for troubleshooting purposes.
/default_host/sap/bc/srt/xip/sap
You want to fix the Web service error message "Could not determine WSDL address (ICF_ERROR), SRT_REG038" in connection with XI services.
Using Support Package SAPKB62006, the following problems were solved in connection with inactive services:
The "RAISE_EXCEPTION" ABAP runtime error no longer occurs for an inactive host.
The error text "Forbidden" was replaced with "Service is not active" for an inactive service.
Thanks
Sudhan Shan

Working on Solution Manager

Hi Gurus,
in our project we are having to work through solution Manager. I am new to the solution Manager environment.
a) Is there any link that helps us understand the basics of working on solution manager.
b) Also, i understand we need to give the transaction codes that we work on in solution manager. (But in HCM as we work in the IMG the transaction code is always seen as SPRO for most of the configuration)
c) How do we set the T Codes for entire configuration?
We have the sub modules
a) Personnel Administration (Recruitment Included)
b) Organisation Management
c) Time Management
d) Payroll
e) Personnel Development (PMS- OSA)
f) Training and event Management
g) ESS and MSS
Awaiting your reply and Thanks in advance
Regards
RR

The SAP Solution Manager application management solution facilitates technical support for distributed systems u2013 with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. A centralized, robust application management and administration solution, SAP Solution Manager combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. And, as a customer of SAP, you have full access to the core SAP Solution Manager for no extra charge.
SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
SAP Solution Manager features and functions include:
SAP Business Suite implementation and upgrades u2013 SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
Change control management u2013 SAP Solution Manager controls all software and configuration changes of the IT solution. This includes the approval process for change requests, the deployment of changes, and later analysis of changes. This ensures quality of the solution and enables traceability of all changes.
Testing u2013 SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
IT and application support u2013 The service desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
Root cause analysis u2013 The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems, even in heterogeneous environments. This helps to isolate general performance bottlenecks, to isolate exceptional situations, to record the activity of single users or processes, and to identify changes to the productive landscape. As a result, problem resolution is accelerated and business availability increased.
Solution monitoring u2013 SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
Service-level management and reporting u2013 SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
Service processing u2013 SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
Administration u2013 Administration tasks are mainly executed locally on the involved systems, but can be accessed and triggered from a central administration console. The administration work center in SAP Solution Manager offers a central entry point and unified access to all SAP technology.
The concept is very user friendly and can be easily worked on. Thank you friend for your response.
i used solar 2 and was able to work further.
Regards
RR

View the document in Solution Manager

I am told that there is an option in Solution Manager to have the document generate a link that can be emailed to the approver. This allows the approver to view the document in SM without actually having access to SM. The approver can then reply back to the e-mail with his/her approval after viewing document.
I am new the SM any detailed input with how to steps would really help..
thanks in advance.

Hi B_J,
it is correct, each document has attributes, on the attribute tab in the button bar, there is an icon to generate an url for the selected document. This link is stored in your windows clipboard, so you can past this link in an e-mail or wordfile. The person who gets the e-mail must have access to the Solution Manager via network, he needs no personal user in the system. The link used a service of Solution Manager(check in the Solution Manager IMG at the HTTP services). This service requires a user to read the document. If you have no user, then it is necessary that in the system a default user is assigned to the service or to its alias. Now to your second use case, the approval, you can not bring any information INTO Solution Manager, you can only answer the e-mail, with the info, yes the document is OK, but you can not set a status or an other attribute at the document, that the document is approved.
Regards,
uDo

Solution Manager 4.0/When accessing services as ex. showing graphic in Proj

Similar Messages

Maybe you are looking for