CHECK_GROUPS parameter in SOLMAN_SETUP with SolMan EHP1 SPS19

Hello to everybody!
I'm trying to add a new Java System to the SolMan. Everything in SMSY seems to be ok.
This is my way:
- TA SOLMAN_SETUP -> Configure Managed Systems -> switch to Java Systems -> select new Java system and start the wizard
- After executing the first step (checking prerequisites of Diagnostics) a error message is displayed with a red indicator:
"The result of prerequisite check cannot be analysed". The detailed message says "The checkgroup Managed systems setup prerequisite is unknown. Please check the CHECK_GROUPS parameter."
The last massage causes a lot of question marks. Does anybody know anything about this parameter? Where can I find and how do I configure this parameter?
Looking forward to the light of knowlege!
Sascha

Hello Andreas,
I got the solution of this problem from SAP Support:
Please have a look at the following note #1309758. With the installation via SNOTE the bug was killed and I'm now able to go ahead with the configuration wizard.
Have a nice day!
Sascha

Similar Messages

How to install diagnostic agent for nw 7.0sp17, with solman ehp1- sp25

Hi Gurus,
we are using NW 7.0 Enterprise portal at SP17, want to configure E2E. So installed solution manager 7.0 EHP1 SPS 25.
Ran the Guided procedure solman_setup successfully. with intitial config, basic config and pending at managed system config.
Here my question is:
do i need to install smd agent on solman? or solman itself comes with agent. i cannot see any agent in mmc on solution manager.
What is SOLMANDIAG and SOLMAN AGENT, SMD Agent and Host agent.
The guide (https://websmp207.sap-ag.de/~sapidb/011000358700000952852009E) says before install SMD agent, install host agent, diagnostics agents are available 7.11 on wards, while installing smd agent sapinst asking SAP Unicode Kernel 711 , but currently my NW Portal system is using kernel 7.0..
Any guide, how to proceed for E2E on nw7.0 SP17 with solman ehp1 sp25( highest availale spack)
Thanks in advance.
Regards
Balaji

Hi Balaji,
As per the SMD agent 7.11 installation guide (https://service.sap.com/~sapidb/011000358700000952852009E) , Page 6 and 8, you would need to download the standard NW 7.11 DVDSs( usually kernel and Installation master) and SMD agent installation packages from the SMP. Location is mentioned in the guide as well.
For your query that Portal is based in i386, these are two different things. The SMD Agent will be installed with its own kernel and also 7.11 kernel is not support edon 32bit. However the SMD agent will use its own 7.11 64bit kernel and Portal will use its i386 kernel. Hopefully your hardware is able to support both. I recommend to proceed with x86_64 7.11 kernel for your SMD installation. Incase the hardwar does not support this, go for alower release of SMD Agent wherein the kernel supports 32 bit hardware.
Best Regards,
Srikishan

E2E_EXTRACTOR_CONTROLLER jobs don't run with SOLMAN EhP1

Hi!
I am using SAP Solution Manager 7.0 EhP1 and would like to use Solutio Manager Diagnostics functions there.
I already installed Wily Introscope 8.0, the SMD agent. I configured all the satellite system and can already see some graphics and BI data within Workload Analysis, Change Analysis.
My problem is that since almost one month no E2E_EXTRACTOR_CONTROLLER jobs
are scheduled in SOLMAN.
Question:
Can some one explain how to schedule these jobs in order to see actual data for WA, CA, etc.?
What I already done:
I run several times again the SMD Setup for Managing and Managed system without any errors
I traced the entries in table E2E_ACTIVEEXTR (set for all the entries the "x" flag in field "Active")
I have a look int the table E2E_ACTIVE_WLI. This table is not empty and contains a lot of entries.
I have a look int the table E2E_ECSTATUS . This table is not empty and contains a lot of entries.
It will be great to get some helpful information
Thank you very much

Hi!
Many thanks for your response.
Unfortunately when I access to
http://<host>:<port>/smd I can see only Diagnostic Setup tab.
Question:
Do you know whether with EhP1 the Extractor jobs are also calling "E2E_EXTRACTOR_CONTROLLER"?
How can I manually schedule these jobs?
Thank you very much!
regards
Holger

Solman EHP1 upgrade Stack 20 - cannot log in to system

Hi all,
I am currently doing a patch of Stack 20 for solman EHP1. I was able to create the queue, was able to continue until import proper phase 2. After a while, i cannot log on the system.
CX_WB_ED_SYNTAX_ERROR is unknown. abap program SAPMSYST had to be terminated. status LIVE of the user interface SAPLSRABAX_EXC missing.
also we found a deadlock in the ora alert trace file.
here are the logs:
SLOG0944.log
ERROR SAPK-701DRINSAPBASIS SOL I 0012 20091027160822 SAPBASISUSER SAPBASIS     cbcsapsolm 20091027142413047
STOP MAIN IMPORT          SOL I      20091027160831              SAPBASIS     cbcsapsolm 20091027142413047
ERROR: stopping on error 12 during MAIN IMPORT
START INFORM SAP-SYSTEM OF SOL Q      20091027160831              SAPBASIS     cbcsapsolm 20091027142413047
START tp_getprots          SOL Q      20091027160831              SAPBASIS     cbcsapsolm 20091027142413047
WARNING: System SOL. Warning.        20091027161236 :
WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.
      Please check that the R/3 system is running.
      Please check the system. Use transactions SM21, SM37, SM50.
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System SOL. Warning.        20091027170810 :
ERROR:       The following call returned with exit code -100:
ERROR:         sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=SOL
ERROR:       Background jobs cannot be started.
ERROR:       Please check trace file dev_evt.
WARNING:       (This warning is harmless if no further warnings follow.)
STOP imp all              SOL   7006 20091027170857              SAPBASIS     cbcsapsolm 20091027142413047
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
dev_evt
Tue Oct 27 17:08:08 2009
Trace File of External Event Raiser (Level=2, Append=0)
EventID: SAP_TRIGGER_RDDIMPDP
SAP message server host: cbcsapsolm
SAP message server service (new): 3900
SAP message server service (old): sapmsSOL
MsIAttachEx: connect to cbcsapsolm / 3900
NiIInit: allocated nitab (2048 at 0000000002980080)
NiHsLInit: alloc host/serv bufs (100/100 entries)
NiPGetNodeAddrList: got 1 interface(s) from operating system
          [0] IP-Address: 172.20.20.128
NiHsLGetNodeAddr: got hostname 'cbcsapsolm' from operating system
HN='cbcsapsolm.cbcmain.cbc.chinabank.ph'; Add[0]=172.20.20.128
NiIGetNodeAddr: hostname 'cbcsapsolm' = addr 172.20.20.128
NiIGetServNo: servicename '3900' = port 0F.3C/3900
NiICreateHandle: hdl 0 state NI_INITIAL
NiIInitSocket: set default settings for new hdl 0 / sock 1812 (I4; ST)
NiIBlockMode: set blockmode for hdl 0 FALSE
NiITraceByteOrder: CPU byte order: little endian, reverse network, low val .. high val
NiIConnectSocket: hdl 0 is connecting to 172.20.20.128:3900 (timeout=5000)
Tue Oct 27 17:08:09 2009
SiPeekPendConn: connection of sock 1812 broke (10061-WSAECONNREFUSED: Connection refused)
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2835]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 1812
    (SI_ECONN_REFUSE/10061; I4; ST; 172.20.20.128:3900) [nixxi.cpp    2835]
NiICloseHandle: closing initial hdl 0
ERROR => MsIAttachEx: NiBufConnect to cbcsapsolm/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
ERROR ***: MsAttach (host=cbcsapsolm, serv=3900), rc = -100
MsIAttachEx: connect to cbcsapsolm / sapmsSOL
NiHsLGetNodeAddr: found hostname 'cbcsapsolm' in cache
NiIGetNodeAddr: hostname 'cbcsapsolm' = addr 172.20.20.128
NiHsLGetServNo: got service name 'sapmsSOL' from operating system
SN='sapmsSOL'; Port=0E.10/3600; PC=tcp
NiIGetServNo: servicename 'sapmsSOL' = port 0E.10/3600
NiICreateHandle: hdl 0 state NI_INITIAL
NiIInitSocket: set default settings for new hdl 0 / sock 1800 (I4; ST)
NiIBlockMode: set blockmode for hdl 0 FALSE
NiIConnectSocket: hdl 0 is connecting to 172.20.20.128:3600 (timeout=5000)
Tue Oct 27 17:08:10 2009
SiPeekPendConn: connection of sock 1800 broke (10061-WSAECONNREFUSED: Connection refused)
NiHsLGetServName: found port number 0E.10/3600 in cache
NiIGetServName: port 0E.10/3600 = servicename 'sapmsSOL'
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2835]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 1800
    (SI_ECONN_REFUSE/10061; I4; ST; 172.20.20.128:3600) [nixxi.cpp    2835]
NiICloseHandle: closing initial hdl 0
ERROR => MsIAttachEx: NiBufConnect to cbcsapsolm/sapmsSOL failed (rc=NIECONN_REFUSED) [msxxi.c      652]
ERROR ***: MsAttach (host=cbcsapsolm, serv=sapmsSOL), rc = -100
alert_sol
Tue Oct 27 16:08:17 2009
ORA-00060: Deadlock detected. More info in file f:\oracle\sol\saptrace\usertrace\sol_ora_5280.trc.
Tue Oct 27 16:08:20 2009
Completed checkpoint up to RBA [0x5e7.2.10], SCN: 17756362
Tue Oct 27 16:08:22 2009
ORA-00060: Deadlock detected. More info in file f:\oracle\sol\saptrace\usertrace\sol_ora_188.trc.
hope you can help!
Many thanks!
Edited by: Jeb Barrios on Oct 28, 2009 3:11 AM
Edited by: Jeb Barrios on Oct 28, 2009 3:13 AM
Edited by: Jeb Barrios on Oct 28, 2009 3:15 AM

Hi,
Based on my checks, in my opinion its best to open an OSS msg, as most of the time it will require the message processor on SAP side to apply some internal tool to resolve this. Since it is a matter with package stuck scenario.
You may want to open under BC-UPG-OCS
Hope this helps.
Cheers
SH

SOLMAN EhP1 xml file problem

I am upgrading my Solution Manager 7.0 from stack 17 to stack 18(EHP1) but whenever I try to generate the xml file on the service marketplace, all I get is "The table does not contain any entries"
To recreate...
go to service.sap.com/swdc --> SAP Support Packages --> Support Package Stacks --> SAP Solution Manager 7.0
Then...
Target Stack = SAP SOLUTION MANAGER 7.0 EHP 1-Initial Delivery
Source Stack = 17 (8/2008)
when I click NEXT, it goes straight to page 3 of 3, and I get buttons for Previous Step, Print List, Save as file, Add to download basket, Side Effects report, etc...
Then the table where all the packages should be is empty, except for the message "the table does not contain any entries"
We have tried this with multiple people on multiple machines, all the same result. By the way I just upgraded from abap & java stack 15 to 17.. and I had no issues getting the xml file there. (I downloaded the DVDs of the actual patches so I just need the xml)
Thanks!
Edited by: Bill McCrea on Jan 15, 2009 2:42 PM

After reading your question, I went to the SPstack webpage, and selected a SOLMAN EHp1 stack 16-17, DB2 UDB. when I was on the "Step 3 of 3 Downloadable support packages" I was able to select the Save as File button and I was able to generate the XML. It may have been a temporary problem. Make sure that you don't have a pop-up blocker that would prevent the window from appearing.
Regards
---Bill

Solman ehp1 installation error

Hi all,
we are facing some problem while installing Solman EHP1 on solaris_X64. with SID = SOL
we are getting the following error while giving the binaries for the installation export
An error occurred while processing option SAP Solution Manager 7.0 EhP1 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :Assertion failed: in function (sid, fileName) { if (!sid) { installer.writeError("ind-rel.ind-os.ind-db.j2ee-eng.noSID"); } var result = false; var unicode; var nw = NW.getSystem(sid); var unicode = nw.isUnicode(); var product = installer.getInstallationParameter("INSTPARA_PRODUCT"); var prodrel = installer.getInstallationParameter("INSTPARA_PRODUCT_VERSION"); var dbHost = nw.getDB().getDBHost(); var localhost = installer.getHostName(); var osFAName = (new SystemMgt()).getSystemInfo().getOSFAName(); var dbOsFAName = "ALL"; OraCom.trace("OraCom localhost: ", localhost, " dbHost: ", dbHost); OraCom.trace("OraCom nw.getDB()getDBHost(): ", nw.getDB().getDBHost()); OraCom.trace("OraCom dbOsFAName: ", dbOsFAName, " osFAName: ", osFAName); dbOsFAName = (dbHost.equals(localhost)) ? osFAName : "ALL"; OraCom.trace("OraCom dbOsFAName: ", dbOsFAName); templateFilePathOra = "/COMMON/INSTALL/ORA/"; var unicode = (parseBool(unicode)) ? "YES" : "NO"; OraCom.trace("OraCom importOradbpar unicode: " + unicode); if (!fileName) { fileName = "ORADBPAR.XML"; } var fileMgt = new FileMgt(); if (!fileMgt.isExisting(fileName, "FILE")) { var fileSrc = installer.getCD("SAPINST") + templateFilePathOra + "ORADBPAR.XML"; if (!fileMgt.isExisting(fileSrc, "FILE")) { installer.abortInstallation("dbmodora.fileNotFound", fileSrc); } var file1 = fileMgt.getNode(fileSrc); file1.copy(fileName); } installer.writeTrace("Reading volatile database parameters from '" + fileName + "'."); var client = ; client.files.push(fileName); installer.setKdbClient(client); var where = " WHERE PRODUCT = '" + product + "' AND PRODREL = '" + prodrel + "' AND OsFAName = '" + dbOsFAName + "'"; installer.writeTrace("where: " + where); var se = OraCom._getTableSVE(); var s = OraCom._getTableSV(); s.remove(); var fields = new Array("OsFAName", "serverVersion", "UNICODE"); var rows_s = se.arraySelect(fields, where); ASSERT(arguments.callee, rows_s.length > 0, "found no server version for this where clause: " + where); for (var i = 0; i rows_s.length; ++i) { var temp = rows_s; OraCom.trace("OraCom(row: ", dump_properties(temp)); var v_row = new Array(); if (temp.UNICODE == "" || temp.UNICODE == unicode) { v_row.OsFAName = temp.OsFAName; v_row.serverVersion = temp.serverVersion; s.insertRow(v_row); } } var where = " WHERE PRODUCT = '" + product + "' AND PROD_REL = '" + prodrel + "' AND OsFAName = '" + osFAName + "'"; installer.writeTrace("where: " + where); var ce = OraCom._getTableCVE(); var c = OraCom._getTableCV(); c.remove(); var fields = new Array("OsFAName", "clientVersion", "UNICODE"); var rows_c = ce.arraySelect(fields, where); ASSERT(arguments.callee, rows_c.length > 0, "found no client version for this where clause: " + where); for (var i = 0; i rows_c.length; ++i) { var temp = rows_c; OraCom.trace("OraCom(row: ", dump_properties(temp)); var v_row = new Array(); if (temp.UNICODE == "" || temp.UNICODE == unicode) { v_row.OsFAName = temp.OsFAName; v_row.clientVersion = temp.clientVersion; c.insertRow(v_row); } } var se = OraCom._getTableSBE(); var s = OraCom._getTableSB(); s.remove(); var where = " WHERE OsFAName = '" + dbOsFAName + "'"; OraCom.trace("where: ", where); var rows_s = se.arraySelect(undefined, where); ASSERT(arguments.callee, rows_s.length > 0, "found no server Bit for this where clause: " + where); for (var i = 0; i rows_s.length; ++i) { OraCom.trace("OraCom(row: ", dump_properties(rows_s)); s.insertRow(rows_s); } var se = OraCom._getTableCBE(); var s = OraCom._getTableCB(); s.remove(); var where = " WHERE OsFAName = '" + dbOsFAName + "'"; OraCom.trace("where: ", where); var rows_s = se.arraySelect(undefined, where); ASSERT(arguments.callee, rows_s.length > 0, "found no client Bit for this where clause: " + where); for (var i = 0; i rows_s.length; ++i) { OraCom.trace("OraCom(row: ", dump_properties(rows_s)); s.insertRow(rows_s); } tORA_TablespaceNameMapping_External = new Table("tORA_TablespaceNameMapping_External"); tORA_TablespaceNameMapping = new Table("tORA_TablespaceNameMapping"); tORA_TablespaceNameMapping.remove(); var v_fields = new Array("oldName", "newName"); var v_where = " WHERE PRODUCT IN ('','" + product + "')"; var rows_t = tORA_TablespaceNameMapping_External.arraySelect(v_fields, v_where); for (var i = 0; i rows_t.length; ++i) { tORA_TablespaceNameMapping.insertRow(rows_t); } result = true; } found no server version for this where clause: WHERE PRODUCT = 'SOLMAN' AND PROD_REL = '40' AND OsFAName = 'SOLARIS_X86_64').
Any suggestion on this is welcome
regards,
sen

Hi
solution for this error is as below
Oracle, SOLARIS_X86_64: Error message: found no server version
Symptom:
You get an error message like the following:
found no server version for this where clause: WHERE PRODUCT = 'SOLMAN' AND PROD_REL = '40' AND OsFAName = 'SOLARIS_X86_64'
Solution:
Proceed ad follows:
 1. Stop SAPinst.
 2. Go to the installation directory sapinst_instdir.
 3. Edit the ORADBPAR.XML file.
 4. In the ORADBPAR.XML file, search for the following:
 <row>
 <fld name="PRODUCT">
 <strval><![CDATA[SOLMAN]]>
 </strval>
 </fld>
 <fld name="PROD_REL">
 <strval><![CDATA[70]]>
 </strval>
 </fld>
 <fld name="UNICODE">
 <strval><![CDATA[]]>
 </strval>
 </fld>
 <fld name="OsFAName">
 <strval><![CDATA[SOLARIS_X86_64]]>
 </strval>
 </fld>
 <fld name="serverVersion">
 <strval><![CDATA[102]]>
 </strval>
 </fld>
 5. Replace '70' with '40':
 <row>
 <fld name="PRODUCT">
 <strval><![CDATA[SOLMAN]]>
 </strval>
 </fld>
 <fld name="PROD_REL">
 <strval><![CDATA[40]]> <<<<<<<<<<<<<< change 70 to 40
 </strval>
 </fld>
 <fld name="UNICODE">
 <strval><![CDATA[]]>
 </strval>
 </fld>
 <fld name="OsFAName">
 <strval><![CDATA[SOLARIS_X86_64]]>
 </strval>
 </fld>
 <fld name="serverVersion">
 <strval><![CDATA[102]]>
 </strval>
 </fld>
 6. Save the ORADBPAR.XML file.
 7. Restart SAPinst and choose "Continue with the old option" on the "What do you want to do" screen.
Regards,
Bharathy

Error in Integration of Defect Module of HP QC with SolMan Ehp 1

Hi,
We are using QC version 10 patch 12 and connected with SolMan Ehp 1 for testing.
We are facing a problem in integrating the defect module of QC with Service desk of SolMan.
The required settings are done in SPRO -> SAP Solution Manager -> Scenario-Specific Settings -> Third Party Integration -> SAP Quality Center by HP -> Integration Defect Management.
SPRO -> SAP Solution Manager -> Scenario-Specific Settings -> Third Party Integration -> External Service Desk
We have also implemented the SAP note 1289155.
We are not using the Standard message type SLFN instead we have ZLFN.
See the bellow error message in QC during field maping.
The number of required defect fields in Quality center is different from the number of required support message fields in Application: u201Ceclsh112; WAS; 100u201D. Make sure the number of required fields is equal in both systems before you continue.
Can any one suggest on this.
Thanks in advance.
Praveen

Hi Praveen,
Try this it should solve the issue.
It seems that there is something wrong with your configuartion for the external service desk.
If possible could you remove the external service desk from in
Transaction ICTCONF and redefine it again?
Once you have done that please do the following steps:
- Go to the Solution Manager project
- Open the dialog to connect to a QC project
- Confirm the dialog.
This will update the assignment with all technical details.
You can check the results in the Site Admin. There navigate to the corresponding QC project and check the content of table BLUEPRINTS. There should be exactly 1 entry with the relevant information for the service desk integration (see attached "BLUEPRINTS(QC).doc").
Hope this helps.
Thanks,
Raghavendra.

Multiple Backend Scenario with SolMan

Hi Gurus,
i need the information about the multiple backend scenarios implementation with SolMan. In the Note 1084315 - Consulting: Information about the multiple backend scenario, there is the Way decribed:
You can find documentation about this in Solution Manager under 'Basic Settings for SAP CRM' -> 'Multiple Systems Exchange Projects: Multiple Backends'.
But i can not find it in Solution Manager, where can it be?
Thanks and Regards,
Stefan

Hi Alagammai,
    We are also implementing CRM Middleware - Multiple Backend Scenario (MEP / MBE Concept) in our client landscape for SAP CRM on HANA (Ehp3) set-up.
Required some Information on the below Query.
For Customizing Adapter Object:
1) Does MEP Concept support the Customizing Adapter object to download from more than one ECC System to single CRM System.
    If Yes, Could you please provide the Configuration steps or Procedure to download the customizing data.
For Master Adapter Object:
2) The Adapter objects for Master Data like Customer and Materials are technically supported under MEP for the data exchange.
     However, is it possible to download the Equipments Master Data from more than one ECC System to single CRM System?
     If Yes, Could you please provide the steps or Procedure to download the Equipments Master Data.
And please provide if you have done the Solution Manager Configuration mapping for MEP Scenario, which is required for the maintenance and transfer of customizing mappings to CRM and Mapbox.
Thanks,
Mohanram.
7829055537

Incomplete control parameter for commmunication with the BW system

Hi expert's,
when i am loading my infopackage it's giving the error as follows
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
System response
There are IDocs with incorrect status.
Procedure
Check the IDocs in Source System . You can get here using the BW Monitor.
Removing errors:
How you remove the errors depends on the error message you receive.
for that i checked in idoc maintenance in OLTP
it's showing the following error
"Incomplete control parameter for commmunication with the BW system"
how to resolve this issue
Regards
Harikrishna N

Hi Imtiaz Karedia ,
thank you for your quick reply.
i checked with source system in RSA1. it's saying that source system connection is ok.
Regards
Harikrishna N

QC Adapter with SolMan - step by step guidance, if possible please

Hi experts,
I am embarking on linking QC tool with SolMan and request any help you can provide, including the following aspects -
(1) Sequence of steps from downloading the license from SAP - in brief
(2) Authorisation aspects
(3) Any SAP Notes that are must read before proceeding
(4) Any 'traps' to avoid or error messages to look out for
I have files from service.sap.com/solutionmanager and also from service.sap.com/rkt-solman
Your tips/inputs beyond these files will be valuable. If you would like to relate to those files, a clear guidance on sequence of reading/ executing them would be helpful too.
Thanks and regards,
Srini

Hello there!
The list of interfaces for archiving are located in transaction
SXMB_ADMIN -> Integration Engine -> Configuration -> "Define
Interfaces for Archivng and Retention Periods").
All interfaces which are not found in that list are flagged for
deletion by default.
Mor information in note: #872388 - Troubleshooting Archiving and Deletion in PI
Now, I'd like to give you a little explanation regarding the Archiving/Deleting procedures:
Checking out the report RXMB_SHOW_STATUS,
you can see the status of some messages, for example, if they're not in
status 000, 003 and 006, which means they're in final state, then it may
means that some messages were not ready to be processed by the default
job you configure.
There're three pre-requisites for deleting/archiving messages:
1- Age of message (older than the retention period)
2- Message status is final
3- Adapter status is final
Also, we have to consider the messages in report
RSXMB_SHOW_REORG_STATUS, that shows us the messages that are being
'considered' and those are being 'ignored'.
The first one takes all the three pre-requisites in account; the second
one takes only the first pre-requisite in account.
The status of the messages are take in account when the default job
you set up runs.
Hope it is complete to you
Best regards,
Caio Cagnani

CProjects with SolMan

Hello,
I am new to SolMan und would like to use cProjects with SolMan. There the questions are starting
I have seen the documents of the ramp up but I have no clue if I have to set up the project first or not. I think yes.
When I want to connect an existing project (with the correct project type) to the project (in the solar_project_admin -> system landscape -> change request | activate change request management checked) the "assign cProjects Project" buttons is disabled?
What is neccessary to get it enabled?
How are you using cProjects in SolMan. I cannot get any good documentation and best practices about this (maybe I am searching wrong). Could someone please give some keywords which functionalities it has?
Is it only used with change requests?
I have the project types, phase types and already some projects in cProject that are waiting to be assigned.
Is there anything to configure (and a guide on what to configure)?
It would be really nice if someone could help me.
Thank you,
Vanessa

Hi
Another way could be create an implementation project in Solman and use BPR for PLM. I found the next link in another forum, hope it can help you: https://websmp207.sap-ag.de/~sapidb/011000358700006935382005E.sim
Regards
Ivá

Incomplete control parameter for communication with the BW system

Hello SAP Experts!
We have R/3, which is ECC 6.0 and BI 7. While loading data to target, we are facing errors BD87.
Application Document not posted.
R3/030:Incomplete control parameter for communication with the BW sys.
Please, I invite your valuable inputs
Thanks & Regards
Vanitha

Seems like your source system is not active...
Try transaction RSA1 -> Source Systems -> select system and
click 'activate'.
Also read,
Note 398335 - Error message R3 030
Note 359412 - Error message R3030, control parameter incomplete
Regards
Juan

SMD not communicating with SOLMAN

Hi,
The SMD instance on our portal servers is supposed to talk to SOLMAN. This was working fine until I had to change the J2ee_admin password on SOLMAN. After that, the SMD instances will not start because they can not communicate due to the password being changed. I have no way of knowing the old password. How can I update the password for these SMD instances? I found note 903080 which mentions a URL (.../smd/admin URL) but I can not access this URL. I've tried http://servername:50000/smd/admin but the page is not found.
Any ideas?
Thank you very much.
Shelby

Hi,
Basically, the SMD agent registers itself with solman using the SMD_ADMIN user. I think that you may have given J2EE_ADMIN user earlier and thats why when the password for J2EE_ADMIN was changed, the issue happened.
You can try and register the agent again using one of the following ways:
1. On solman host, go to Solman Diagnostics workcenter and under Agent Administration, in the Agent Credentials panel, fill the previous login of the Diagnostics Agents and enter the new one (or enter the same login with a new password). Click on the Update all agents button.
2. If the previous step is not possible, reregister the SMD agent on the portal server using the following command:
smdsetup managingconf hostname:"sapms://<J2ee_Message_server_hostname>" port:"<http_port_message_server>" user:"<SMD_ADMIN or J2EE_ADMIN>" pwd:"xxxxxx"
This will reregister the SMD agent with the new user credentials.
Please try and let me know if this works.
Regards,
Shitij

Connecting 2 different with Solman

Dear All,
Is it possible to connect 2 systems in different server with solman for service desk functionality.
Eg :- Ecc 6.0 server is india and another server of ECC 6.0 is in Sri Lanka. Solman server is in India.
We have already configured ECC 6.o server of India with Solman and it is working fine. Now we need to connect Ecc 6.0 server of Sri Lanka.
If this is possible then please tell me what are the steps to do and what are all the pre-requisites required like RFC connections, SAP router etc.
Raj

Dear Raj,
I believe you are trying to add another system to your solution manager system for your service desk functionality. This is possible if there is any type of network connection exists between the systems. If your systems are there in the same transport domain, the task is very simple.
You just need to add the system at Srilanka to your solman in SMSY and proceed as you did for the ECC one in India lke creating RFC etc. You can go ahead with as many as you need provided there is a network connection between the systems.
I hope it clears your doubt.
Rajeev.

ARIS with SolMan - installation/configuration guides pls...

Hello All,
Can anybody of you please share any installation/configuration guides you used/prepared when you installed/configured the interaction between ARIS & Solution Manager?
Your help will be greatly appreciated pls.
Thanks & Best regds,
Alagammai.

Hi ,
Could you please send me the Configuration Document/.sim files on ARIS with Solman,..to my email id : [email protected] as well..
Thanks
Vinni..
Edited by: Vinni8797 on Jan 29, 2008 6:33 PM

CHECK_GROUPS parameter in SOLMAN_SETUP with SolMan EHP1 SPS19

Similar Messages

Maybe you are looking for