Fast Entry in Solution Manager 4.0
Dear all,
I am gettign this wierd error in solman 4.0. When i am in Service message monitor, and click on a message.
I only get two Status : New and In Process. and nothing else.
I went into spro and tried finding where it has to be activated but i could not find it out.
I am guessing there are a couple of places we have to change to get this status.
Kindly Help
Nirmit Gang
Hi Nirmit
Goto spro --> sap solution manager -> configuration ->scenario specific settings ->
service desk -> status profile-> change status profile for user status -> look for service desk status header.
There u will find the status available....
Reward points if usefull..
Similar Messages
-
Solution manager system log - strange entries
Hi Everyone,
the problem we are facing in Solution Manager system log every five minutes appears a new error message:
2 Database error -30082 at CON
0 > SQL30082N Security processing failed with reason "24"
0 > ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
First of all the landscape: ECC, BI, CRM, PI and Solman. Each system is DEV, QUA, PRD - except Solution Manager.
Result of going to see the logs within work directory:
Connect to %_DCR_XXXXX as db2dcr with DB6_DB_NAME=DCR;DB6_DB_HOST=xxxxxx;DB6_DB_SCHEMA=SAPSR3;DB6_DB_SVCENAME=5912
C *** ERROR in DB6Connect[dbdb6.c, 1727] CON = 1 (BEGIN)
C &+*** DbSlConnectDB6( SQLDriverConnect ): [IBM][CLI Driver] SQL30082N Security processing failed with reason "24" ("USE
C &+*** RNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
C &+***
C &+***
C &+*** ABAP location info 'CL_SQL_CONNECTION=============CP', 337
C &+***
C *** ERROR in DB6Connect[dbdb6.c, 1727] (END)
C *** ERROR => DbSlConnect to 'DCR' as 'db2dcr' failed
[dbdb6.c 1732]
Some of the systems are being connected successfully and the error messages in SM21 are not related to those systems. But some of the systems like DCR cannot be reached. And this fact causing the error messages.
I haven't configured Solution Manager because I have joined the project later. I would like to know what job is trying to access the satellite system and for what purpose.
On solution manager side I have checked all the scheduled background jobs - all of them have been executed successfully.
There some of them are scheduled but it is hard understand what is purpose of the job.
I have checked and corrected system landscape through SMSY and have maintained all the RFCs. They all OK now.
What else could force to make a connection to satellite system? And where is the place where it is hardcoded local(satellite) db2 connection entry?
Like I said before, some of the systems are being connected but some not. The one which has not been connected - there was recently changed SAP master password. I believe this is the key to resolve the problem. But the system itself operating 100% correctly.
Perhaps it could be CCMS that makes some extra connections to collect the data from the monitored systems. But I have checked all the RFC's in SM59 and they were OK.
Any ideas or suggestions would be appreciated.
Thanks in advance,
Kind regards,
Artjom.Kaustubh Krishna,
thank you for respond.
It was dbacockpit. The connection was maintained with old db2sid password. And it was causing problematic log entries.
Problem was solved.
Points awarded.
Thanks,
kind regards,
Artyom -
Solution Manager Create remote monitoring entry
Hello,
I need some help or clarification please. We just upgraded our Solution Manager to EHP1 spk25 and I'm trying to setup Solman to support central system monitoring. I'm on the last step to enter the moitored ABAP system in CEN through RZ21 Techincal >Configure Central System>Create remote monitoring entry.
I can enter my own System ID but can't enter the RFC destination ? These default to *_RZ20_Collect and *_RZ20_Analyze. I want to use the RFC's already in place through Charm since these are already setup and working correctly. Can someone tell me how to change this or why we have to use the defaults.
Thanks in advance
StephaniePlease disregard.
Thanks -
XRPM Resource management fast entry screen
When I user the staffing in resource management, I can see the project for which I have been assigned as resource manager and also resources in my pool. But the entry screens are non editable. Is there any setting to make this fast entry screen editable
ThanksHi,
Please check whether you have the resources in the Staffing filed or not.
I would suggest if you can have it after the Cache clearance once, if you are checking the above functionality immediately after creating the resources.
As you said you have the Project manager and other resources as viewable, please also check their availability maintained during the period.
Hope it will solve your query.
Regards,
Nishit -
Follow Up Transaction Default screen in Solution Manager
SAp has provided Screen profile and Function code for creation of incident.Chnage request in Solution Manager.But when i try to create a new incident/CR from existing Incident as follow up transaction, the same screen doenot get defaulted.Item details is the first screen which come in front when we create a follow up transaction from existing SLFN incident.
Please suggest how should i get the Fast entry screen when i am creating follow up transaction from SLFN.hi
pls check the sap note
[1362264- Work Centers: Incident Create default Priority & Category|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1362264]
jansi -
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
RRThe 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 -
Solution Manager 4.0 install Error
I am trying to install Solution Manager 4.0 on a IA64 server running Windows 2003(64 bit edition). I have SQL Server 2005. I have JDK versionj2sdk1.4.2_12-x64.
The sapinst.exe error log is as follows:
+++++++++++++++++++++++++++++++++++++++++++++++++++++
SAPINST.EXE error
ERROR 2006-08-09 11:00:23
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2006-08-09 11:00:23
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|
ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|
NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import
|ind|ind|ind|ind|0|0|runMigrationMonitor was executed
with status ERROR .
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
The Error entries in the Import_monitor log is as follows:
+++++++++++++++++++++++++++++++++++++++++++++++++
ERROR: 2006-08-09 10:39:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2006-08-09 10:39:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL0.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
++++++++++++++++++++++++++++++++++++++++++++++++++++
The error entry in the SAPSSEXC.log mention in the Import_monitor log is as follows:
++++++++++++++++++++++++++++++++++++++++++++++++++
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPSSEXC.TSK.bck already seems to exist
a previous run may not have been finished cleanly
file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPSSEXC.TSK possibly corrupted
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809103927
++++++++++++++++++++++++++++++++++++++++++++++++++++
The error entry in the SAPAPPL0.log mention in the Import_monitor log is as follows:
+++++++++++++++++++++++++++++++++++++++++++++++++
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPAPPL0.TSK.bck already seems to exist
a previous run may not have been finished cleanly
file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPAPPL0.TSK possibly corrupted
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809103927
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: START OF LOG: 20060809111000
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Apr 3 2006 02:55:14
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPAPPL0.TSK.bck already seems to exist
a previous run may not have been finished cleanly
file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
\AS\SAPAPPL0.TSK possibly corrupted
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809111001
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please let me know.
Thanks
MikirHello.
I'm currently installing SAP BW 3.50 on Oracle 10.2, Windows 2003, J2SDK 1.4.2_11. As of now, i've got an error when i put these reference:
SAP:BW-MMR:630_SP3_REL:::*
SAP:BW-SDK:630_SP3_REL:::*
Kindly help on how to resolve this.
Thanks. -
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?
ThanksHi 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 -
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
PaulHi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role. -
Error while installing solution manager 7.1
Hi All,
I am installing SAP Solution Manager 7.1 SR1 i am facing below issue ,any one please suggest me how to proceed further.I am new to sybase .
An error occurred while processing option SAP Solution Manager 7.1 Support Release 1 > SAP Systems > SAP ASE > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS.
import_monitor.java log:
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.016)
SAP Java Server VM (build 4.1.016 1.6-b03, Dec 31 2011 00:41:53 - 41_REL - optU - windows amd64 - 6 - bas2:164914 (mixed mode))
Import Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29.
import_monitor Log:
INFO: 2014-07-01 10:49:48
Import Monitor is started.
CONFIG: 2014-07-01 10:49:48
Application options:
dbCodepage=4103
dbType=SYB
extFiles=no
importDirs=D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP2;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP3;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS
jobNum=8
loadArgs=-c 99000000 -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2014-07-01 10:49:48
List of packages with table structure: 'SAP0000'.
CONFIG: 2014-07-01 10:49:48
List of packages with views: 'SAPVIEW'.
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is started.
INFO: 2014-07-01 10:49:48 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2014-07-01 10:49:48
Data codepage 1100 is determined using TOC file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2014-07-01 10:49:48
Version table 'SVERS' is found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 10:49:48
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29 Package Group max threads: 1 current running threads : 0 processing package: SAPNTAB
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
INFO: 2014-07-01 10:49:59 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29 error processing of package SAPNTAB
ERROR: 2014-07-01 10:49:59 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is interrupted with R3load error.
Process 'D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast' exited with return code 2.
For mode details see 'SAPNTAB.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-01 10:50:18
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2014-07-01 10:50:18
1 error(s) during processing of packages.
INFO: 2014-07-01 10:50:18
Import Monitor is stopped.
INFO: 2014-07-01 11:09:16
Import Monitor is started.
CONFIG: 2014-07-01 11:09:16
Application options:
dbCodepage=4103
dbType=SYB
extFiles=no
importDirs=D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP2;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP3;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS
jobNum=8
loadArgs=-c 99000000 -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2014-07-01 11:09:16
List of packages with table structure: 'SAP0000'.
CONFIG: 2014-07-01 11:09:16
List of packages with views: 'SAPVIEW'.
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is started.
INFO: 2014-07-01 11:09:16 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2014-07-01 11:09:16
Data codepage 1100 is determined using TOC file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2014-07-01 11:09:16
Version table 'SVERS' is found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 11:09:16
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29 Package Group max threads: 1 current running threads : 0 processing package: SAPNTAB
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
INFO: 2014-07-01 11:09:27 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29 error processing of package SAPNTAB
ERROR: 2014-07-01 11:09:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is interrupted with R3load error.
Process 'D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast' exited with return code 2.
For mode details see 'SAPNTAB.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-01 11:09:46
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2014-07-01 11:09:46
1 error(s) during processing of packages.
INFO: 2014-07-01 11:09:46
Import Monitor is stopped.
NOTE:
The same issue has been solved in SCN Thread http://scn.sap.com/thread/3360385. As suggested in that note i am trying to look into the sap note
Note 1716201 - SYB:Update control.xml files for installation: Sybase ASE
in service market place but it is displaying as Document not released.
Kindly can any one help me in provind the above mentioned note or help me how to resolve this issue.
Regards,
SURYA.HI Divyanshu,
Below is the SAPNTAB.log:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 1680
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -ctf I D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL SAPNTAB.TSK SYB -l SAPNTAB.log
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job completed
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 1904
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) INFO: SVERS created
(IMP) INFO: import of SVERS completed (1 rows) #20140630211544
(DB) INFO: SVERS~0 created
(DB) INFO: DDNTF created
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF~0 created
(DB) INFO: DDNTF_CONV_UC created
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC~0 created
(DB) INFO: DDNTT created
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC created
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140630211555
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701104948
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2304
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701104959
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701110916
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2056
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701110927
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701120231
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2288
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701120242 -
Job Scheduling in Solution Manager - Error creating Periodic Job
Hi all,
I am in the process of testing the Job Scheduling functionality using the Solution Manager. I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well.
I am able to successfully setup up a 'on-time' job.
it's only when I try to setup a periodic job, I end up getting following error
Any thoughts? Is there any piece of config that's missing? All the SICF services needed for this functionality are running fine.
Thanks for the help.
500 Internal Server Error
Error when processing your request
What has happened?
The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
Note
The following error text was processed in the system PSM : Message was not created
The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CPHello,
This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
Have you performed the IMG Activiteis in SPRO?
See the following Help link:
http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
Change a job
You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
Make changes.
Note
When you change a periodic job, the system searches for the changeable successor and only changes this successor.
If there is more than one changeable job with the same name, the system does not change any of these jobs.
End of the note.
Save your entries.
To release the job in the target system, select Release.
You go to the transaction SM37 in the target system.
You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
Regards,
Paul -
SM:SELFDIAGNOSIS background job getting failed in Solution manager
Hi All,
SM:SELFDIAGNOSIS background job getting failed in Solution manger server :
Job Log:
2-22-2012 16:44:02 Job started 00 516 S
2-22-2012 16:44:02 Step 001 started (program RDSWP_SELF_DIAGNOSIS, variant &0000000000324, user ID BASISUSER) 00 550 S
2-22-2012 16:45:07 Internal session terminated with a runtime error (see ST22) 00 671 A
2-22-2012 16:45:07 Job cancelled 00 518 A
ST22: Dump:
Runtime Errors ITAB_DUPLICATE_KEY
Date and Time 02-22-2012 16:45:07
Short text
A row with the same key already exists.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An entry was to be entered into the table
"\CLASS=CL_DSWP_SD_DIAGNOSE_CONSISTENT\METHOD=CHECK_USERS_BP\DATA=LT_USCP"
(which should have
had a unique table key (UNIQUE KEY)).
However, there already existed a line with an identical key.
The insert-operation could have ocurred as a result of an INSERT- or
MOVE command, or in conjunction with a SELECT ... INTO.
The statement "INSERT INITIAL LINE ..." cannot be used to insert several
initial lines into a table with a unique key.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"ITAB_DUPLICATE_KEY" " "
"CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" or "CL_DSWP_SD_DIAGNOSE_CONSISTENTCM00M"
"CHECK_USERS_BP"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
KIndly Suggest to resolve the above issue
Thanks
NekkalapuHI,
Deatils:
SAP EHP 1 for SAP Solution Manager 7.0
SAP_ABA 701 0006 SAPKA70106
SAP_BASIS 701 0006 SAPKB70106
PI_BASIS 701 0006 SAPK-70106INPIBASI
ST-PI 2008_1_700 0002 SAPKITLRD2
CRMUIF 500 0004 SAPK-50004INCRMUIF
SAP_BW 701 0006 SAPKW70106
SAP_AP 700 0019 SAPKNA7019
BBPCRM 500 0016 SAPKU50016
BI_CONT 704 0007 SAPK-70407INBICONT
CPRXRPM 400 0016 SAPK-40016INCPRXRP
ST 400 0024 SAPKITL434
ST-A/PI 01M_CRM570 0000 -
ST-ICO 150_700 0009 SAPK-15079INSTPL
ST-SER 701_2010_1 0002 SAPKITLOS2
Thanks
Nekkalapu -
What are installations material for Solution Manager 7.0 EHP 1
hi friends,
we plan to do installing Solution Manager 7.0 ehp1,
can any help me to get the path for installation media for Solution Manager 7.0 EHP 1 in service market place.
thanks..https://service.sap.com/swdc
-> SAP Installations and Upgrades
-> Installations and Upgrades - Entry by Application Group
-> SAP Technology Components
-> SAP SOLUTION MANAGER
-> SAP SOLUTION MANAGER 7.0 EHP 1
-> Installation and Upgrade
Also check https://service.sap.com/instguides for the install guide and SAP Note 1276022 - SAP Solution Manager 7.0 EHP1
Installation.
Nelis -
Error While Applying patch ST-PI 2008_1_700 to solution Manager
Dear Techies,
Thanks alot for your fast response.
We are trying to upgrade Solution Manager Stack from
ST-PI 2005_1_700 to ST-PI 2008_1_700 ,
While applying patch it was suddenly stopped with an error
"Manual modification adjustment is neccessary"
While I tried to adjust it.
In Note correction tree. This the message with " green tick"
"0001293326 EWA: Newest ST-PI Is Rated 'Outdated'; Wrong RTCCTOOL Date"
and is not allowing me to proceed further.
How to go about.
Thanks in advance.
regards,
KiranHi Varun,
Thanks for your reply.
As suggested by you, I executed "RTCCTOOL" programme.
It Has given that 4 notes were in red status.
They are.
1. [Note 69455 ] Addon upgrade ST-A/PI 01N_700SOL
Description "Servicetools for Applications Plug-In" for Solution Manager 4.0-7.10 (Addon delta upgrade package)
Implementation From http://service.sap.com/supporttools->ST-A/PI download the addon upgrade package ST-A/PI
01N_700SOL. Upload to tx SAINT (just as you would do for an installation) and install as per note 69455
Then restart report RTCCTOOL and choose 'List->Refresh from SAPNet'.
4. [Note 539977 ] ST-PI Support Packages
Description Addon supportpackage level 4 for ST-PI 2008_1_700 for 7.00 [patches up to level 4 for Basis tools for services]
Implementation Open http://service.sap.com/supporttools-> ST-PI 2008_1_700 ->Supportpk. Add patch SAPKITLRD4 (and predecessors if not yet implemented) to download basket. Release basket via Maintenance optimizer. Upload from frontend int transaction SPAM, define a queue and import the queue.
6. [Note 539977 ] Note 1312413 for ST-PI
Description Maintenance Certificates for SPAM/SAINT may get periodically overwritten by invalid ones on ST-PI
2008_1_7* SP 00. Prevent this proactively,even if you do not yet use the automatic maint. certificate
distribution.
Implementation We recommend that you implement the Supportpackage SP1 for ST-PI 2008_1* to solve the error. Only if
not possible implement note 1312413 with not version >=12 using SNOTE. Regarding automatic maint.
certificate distribution see http://service.sap.com/maintenancecertificate.
9. [Note 1293326 ] EWA serviceprep correct. in sequence.
Description Wrong alerts appear in EWAlert Service preparation section (Newest ST-PI Rated Outdated / Wrong
RTCCTOOL Date) if Solution Manager ST-SER < 701_2008_2 SP1 and satellites on ST-PI 2008_1* / ST-A/PI 01L*.
Implementation Implement the coding correction of this note 1293326 with SNOTE to solve the wrong service preparation alerts. Else if you do not mind the wrong alerts simply set this recommendation manually to green after reading.
These are in green status
Successfully implemented addons/ transports/ notes
2. [Note 69455 ] Proc. after addon impl.
3. [Note 539977 ] Addon ST-PI 2008_1_700
5. [Note 539977 ] Note 1300023 for ST-PI
7. [Note 539977 ] Note 1293657 for ST-PI
8. [Note 12103 ] Collectors and TCOLL.
While I tried to implement the note "69455" system is giving the message that there are no valid corrections and is coming out of the process
"Note 0000069455 cannot be implemented since no valid correction is available."
And is same for other notes also.
How to go ahead.
Thanks in advance.
Regards,
Kiran -
Background job failing - ECC 6.0, Solution Manager 7.0
Dear All,
Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
In both server, latest kernel patch has been applied.
The Support package versions are (both server):
KERNEL (Release 700) 146
SAP_BASIS 0014
SAP_ABA 0014
PI_BASIS(2005_1_700) 0014
ST-PI 0005
SAP_BW 0016
While checking the the jobs from SM37, in both the server,
I am observing that following jobs are always failing with
same reason:
SAP_COLLECTOR_FOR_PERFMONITOR
=============================
Date Time Message text Message class Message no. Message type
========== ======== ====================================================================== ============= =========== ============
15.05.2008 06:25:12 Job started 00 516 S
15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER) 00 550 S
15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV on server gcbeccd DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3 DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:finished DB6PM 000 S
15.05.2008 06:25:18 Database system not supported S1 101 S
15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR 00 671 A
15.05.2008 06:25:36 Job cancelled 00 518 A
SAP_REORG_UPDATERECORDS
=======================
Date Time Message text Message class Message no. Message type
========== ======== ===================================================================== ============= =========== ============
14.05.2008 00:31:01 Job started 00 516 S
14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER) 00 550 S
14.05.2008 00:31:01 Reorganization of update date not allowed in batch 15 100 A
14.05.2008 00:31:02 Job cancelled 00 518 A
SAP_WP_CACHE_RELOAD_FULL
========================
Date Time Message text Message class Message no. Message type
========== ======== ============================================================================================ ============= =========== ============
15.05.2008 00:30:11 Job started 00 516 S
15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER) 00 550 S
15.05.2008 00:30:11 No component system chosen URL_GEN_MSGS 031 E
15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE 00 564 A
Please help to resolve this issue.
Thanks in advance.
Regards
Sudip GhoshHi Markus,
Thanks for the reply.
Below is the dump:
======
======
Runtime Errors DBIF_DSQL2_SQL_ERROR
Date and Time 15.05.2008 06:25:36
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 3113 occurred in the current database connection "DEFAULT".
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel"
Database error code........: 3113
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
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:
"DBIF_DSQL2_SQL_ERROR" " "
"RSORAVSH" or "RSORAVSH"
"FILL_DBVSE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 15
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1117216
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 695792
MM Free. 400816
User and Transaction
Client.............. 000
User................ "BGDUSER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
Program............. "RSORAVSH"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
The main program was "RSORAVSH ".
In the source code you have the termination point in line 48
of the (Include) program "RSORAVSH".
The program "RSORAVSH" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BGDUSER"
Job Number..... 05251100
Source Code Extract
Line
SourceCde
18
INCLUDE STRUCTURE v_system_event_struc.
19
DATA: END OF v_system_event_tab .
20
21
check sy-dbsys(3) = 'ORA' .
22
23
Get the new snapshots
24
25
PERFORM fill_dbvse TABLES v_system_event_tab.
26
27
28
Get the old snapshots from database table MONI
29
30
startday = sy-datum - days_to_keep .
31
32
33
Save new data now (otherwise these data will be selected twice)
34
35
CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO monikey .
36
37
EXPORT sy-datum
38
sy-uzeit
39
v_system_event_tab
40
TO DATABASE moni(db) ID monikey .
41
42
*& Form FILL_DBVSE
43
44
FORM fill_dbvse TABLES v_system_event_tab.
45
date = sy-datum .
46
time = sy-uzeit .
47
EXEC sql performing append_v_system_event .
>>>>>
select event,
49
total_waits,
50
total_timeouts,
51
time_waited * 10,
52
average_wait * 10
53
into :v_system_event_struc
54
from v$system_event
55
ENDEXEC .
56
ENDFORM. " FILL_DBVSE
57
58
59
*& Form APPEND_V_SYSTEM_EVENT
60
61
FORM append_v_system_event.
62
v_system_event_tab-date = date .
63
v_system_event_tab-time = time .
64
65
MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
66
APPEND v_system_event_tab .
67
ENDFORM. " APPEND_V_SYSTEM_EVENT
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
16
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report for Collecting Data from V$SYSTEM_EVENT Hourly
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080515
SY-UZEIT
062520
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM RSORAVSH RSORAVSH 48
FILL_DBVSE
1 EVENT RSORAVSH RSORAVSH 25
START-OF-SELECTION
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name FILL_DBVSE
SY-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
V_SYSTEM_EVENT_STRUC
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222220000000000000000
0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
%_SPACE
0
0
2
0
SY
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
No. 1 Ty. EVENT
Name START-OF-SELECTION
SY-LDBPG
SAPDB__S
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
SY-DBSYS+0(6)
ORA
000
000
454
F21
SYST
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
V_SYSTEM_EVENT_TAB[]
Table[initial]
V_SYSTEM_EVENT_TAB
00000000000000 ################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
SY-DATUM
20080515
00000000
00000000
33333333
20080515
DAYS_TO_KEEP
30
0001
000E
STARTDAY
00000000
00000000
00000000
33333333
00000000
MONIKEY
0000000000000000000000
0000000000000000000000
2222222222222222222222
0000000000000000000000
SY-UZEIT
062520
000000
000000
333333
062520
SYST-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
MONI-CLUSTR
0
00
00
MONI
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ExecuteCall"
of the SAP kernel, in line 1190 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080515062520.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x40000000047b51e0 Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000003d777f0 Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
(5) 0x4000000003d7e7b0 Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
(6) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(7) 0x4000000003f53bc0 Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003d9f210 Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003d9ebe0 ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001caa820 N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cb40f0 dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001caf260 dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001fb54e0 TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(20) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(21) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAVSH
0
30.03.2005
10:21:59
19456
E
1
Prg
SAPMSSY0
1
17.12.2007
15:41:05
92160
E
2
Prg
SAPMSSYD
1
12.09.2006
11:33:31
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
RSDBRUNT
0
17.12.2007
16:04:40
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
12.09.2006
11:25:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Prg
SAPLSABE
11
09.09.2004
14:18:36
13312
E
12
Prg
SAPLSECU
12
17.12.2007
15:31:45
87040
E
13
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
14
Prg
SAPLSTUP
14
17.12.2007
15:29:58
74752
E
15
Prg
SAPLCNDP
15
11.09.2007
15:24:45
195584
E
16
Prg
SAPLSCNT
16
18.02.2005
14:16:06
30720
E
17
Prg
SAPSHDTV
16
05.01.2005
16:26:16
33792
E
18
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
19
Prg
SAPLOLEA
19
11.09.2007
11:17:30
96256
E
20
Prg
SAPLSGUI
20
17.12.2007
15:41:05
84992
E
21
Prg
SAPLSTTM
21
05.07.2005
13:10:18
69632
E
22
Prg
SAPLSBDC
22
17.12.2007
15:30:54
44032
E
23
Prg
SAPLSFES
23
17.12.2007
16:04:40
260096
E
24
Prg
SAPLTHFB
24
17.12.2007
15:41:05
394240
E
25
Typ
WPINFO
0
26.02.1999
14:49:01
6144
26
Prg
SAPLURFC
26
17.12.2007
15:37:35
22528
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
29
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
30
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
31
Typ
SYST
0
09.09.2004
14:18:12
31744
32
Typ
MONI
0
31.03.2004
16:41:21
5120
Directory of Application Tables
Name Date Time Lngth
Val.
Program RSORAVSH
SYST 09.09.2004 14:18:12 00004612
\0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
MONI . . : : 00002944
\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
71
PAR2
03
0000
0014
002B
RSORAVSH
37
73
PAR2
03
0000
0015
002D
RSORAVSH
37
75
PAR2
03
0000
0016
0026
RSORAVSH
37
77
00
0000
RSORAVSH
37
78
PERP
00
0002
RSORAVSH
44
79
PERP
1C
0000
RSORAVSH
44
80
PERP
04
0000
RSORAVSH
44
81
mvqk
10
0005
0044
04EC
RSORAVSH
45
83
mvqk
0C
0005
0054
052E
RSORAVSH
46
85
DSQL
00
0017
RSORAVSH
48
86
DSQL
01
0018
RSORAVSH
48
87
DSQL
04
0025
RSORAVSH
48
>>>>>
DSQL
16
0025
RSORAVSH
48
89
BRAN
05
0004
RSORAVSH
48
90
perf
00
000A
RSORAVSH
48
91
PERP
80
0000
RSORAVSH
48
92
BRAX
00
FFFC
RSORAVSH
48
93
DSQL
23
0000
RSORAVSH
48
94
ENDF
00
0000
RSORAVSH
56
95
00
0000
RSORAVSH
56
===========
===========
Please check and advise.
Also, I am trying to search for the note 6083 in market place, but not getting the same.
Please advise.
Thanks & Regards
Sudip
Maybe you are looking for
-
Not able to capture HD content from Sony HDR-HC3
I recently purchased Final Cut Express 4, after successfully using iMovie HD for the past year. I successfully captured some DV content (non-HD) from my Sony HDR-HC3 for a project. However, when trying to capture HD footage for a 2nd project, I'm not
-
Total order value (net) per PO with ME2N (Purchase order List display)
Hello, with ME2N I can see the order value (net) of a PO per item line. Is it also possible to see the the total order value for all item lines in a PO? Thanks for coming back to me! Sofia
-
Software Update can't connect to server -- error
I have Tiger 10.4.7 on a 600mH white G3 dual USB iBook. When I try to use the SoftwareUpdate function off the Apple Menu to check for any updates to Tiger, the "checking for new software" window starts up all right but immediately the error message w
-
Connection Error between ITS and SAP: R/3 system
Dear All, Recently we have migrated our Backend SAP: R/3 Servers to AIX/Oracle platform. The server landscape is running on two application servers and one central instance with load balancing. We have changed all RFC destinations from the SAP:R/3 an
-
How do you adjust the size of icons in folders?
I downloaded an application and inside it's folder in applications, the icons are gigantic. Larger than all my other icons. Is there like a size adjustment somewhere? They also move around weird when I try to drag them which I think had something to