SCN : Unanswered Discussions - SAP Solution Manager

Hello,

we have following System constellation:

Solution Manager 7.1 SP13

SAP_BASIS 702 0016 SAPKB70216 SAP Basiskomponente

SAP_ABA 702 0016 SAPKA70216 Anwendungsübergreifende Komponente

CTS_PLUG 200 0016 SAPK-20016INCTSPLUG SAP CTS Plugin

PI_BASIS 702 0016 SAPK-70216INPIBASIS Basis Plug-In

ST-PI 2008_1_700 0011 SAPKITLRDK SAP Solution Tools Plug-In

BI_CONT 707 0010 SAPK-70710INBICONT Business Intelligence Content

GW_CORE 200 0008 SAPK-20008INGWCORE SAP GW CORE 200

SAP_BS_FND 702 0014 SAPK-70214INSAPBSFND SAP Business Suite Foundation

SAP_BW 702 0016 SAPKW70216 SAP Business Warehouse

UISAPUI5 100 0010 SAPK-10010INUISAPUI5 SAP UI5

UI_INFRA 100 0010 SAPK-10010INUIINFRA SAP UI INTEGRATION INFRASTRUCTURE

IW_GIL 100 0004 SAPK-10004INIWGIL Generic Interaction Layer

SAP_AP 700 0032 SAPKNA7032 SAP Application Platform

WEBCUIF 701 0013 SAPK-70113INWEBCUIF SAP Web UI Framework

BBPCRM 701 0013 SAPKU70113 BBPCRM

CPRXRPM 500_702 0013 SAPK-50013INCPRXRPM SAP Portfolio and Project Management 5.0 (ABAP)

Is it possible to run a managed System with Netweaver 7.40 (SAP_BASIS 740) and working ST-PI 740 Version ?

I can remember that the Solution Manager always must have the same or newer version of the ST-PI component ?

Thanks

Lukas

Hi all,

I have a question related to Solman and HPQC integration. My company is tracking multiple releases in the same project in Solution manager. How should I set up the processes so that only the blueprint attached to the new scope is being added to HPQC?

I read that one method for delta blueprint generation is to create a new project with reference to the existing blueprint. I'm not sure how the new project should be linked to HPQC project. I'd like to keep everything in the same project in HPQC, to re-use the existing scripts.

Thank you!

Hi Experts,

I am working SOLMAN_SETUP process at Step 6.4 Migrate SMSY data into LMDB ( System preparation) and below manual steps have received the attached the error, kindly help me to resolve this issue.

Step 6.4 Migrate SMSY data into LMDB

Manual Activities:

1.Migrate Installed Prod Instances

2.Migrate Diagnostics Relevant Flags

3. Migrate Host Router Data

4.Migrate Custom attributes

Regards

Karthik.M

Hello,

While doing basic configuration on our solution manager, I received this error on Activate Services, automatic activity in Configure Automatically part of configuration. All other services were successfully activated, I also can´t find this service in SICF transaction to activate it manully. I would really appreciate if anyone know how to solve this.

Hi all,

I installed solman 7.2.

solman_setup is working and I managed to configure some of the solman features.

But:

I can't see the documentation of the steps (which gets on my nerves because on some of the steps I really need to guess what needs to be done). Whenever I click on 'display' in the documentation column, I get an empty screen, no documentation is displayed. In developer tools of chrome i always see this (don't know if this causes the error):

http://SERVERNAME:8000/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sap/bsp_sise_doc_ru/src/main/webapp/i18n/i18n_de_DE.properties 404 (Business Server Page (BSP) Error)

The following error text was processed in the system:
BSP exception: Object src/main/webapp/i18n/i18n_de_DE.properties is not valid in URL /sap(bD1lbiZjPTAwMQ==)/bc/bsp/sap/bsp_sise_doc_ru/src/main/webapp/i18n/i18n_de_DE.properties

Any ideas on this?

Regards

Martina

Hi all,

we have updated for CR content for Solman after that LMDB status was error with the below error.

"SM239: An error occurred during content synchronization: "HTTP status: 401 "

Below is the Display all details at once.

Extract of the Most Important Messages; Result Status for Executed Checks: Error

Logged messages start with a message code. Check SAP-Note 1670464 for known issues and solutions; (check runtime 109.6 s)

Performance Measurements for LMDB

[WARNING] RM116: 8293.80 (5764.90) ms runtime to query a SAP_SoftwareComponent instance

Configuration Source http://host:50000/sld/cimom, Object Server server, Namespace sld/active

[ERROR] SM239: An error occured during content synchronization: "HTTP status: 401 Unauthorized - User logon data is invalid or user has no authorization"
[WARNING] SM238: Last polling of data: 25.01.2016 13:04:32 (More than 12 hours ago)
[WARNING] CS205: Get amount of failed pending changes: HTTP status: 401 Unauthorized - User logon data is invalid or user has no authorization

Notification Status Consumer: Landscape API cache (LAPI Cache) synchronization (CL_LAPI_NOTIFICATION_CONSUM)

[WARNING] NT606: Pending changes have not been synchronized for more than 12 hours

Notification Status Consumer: Synchronization from LMDB to SMSY (CL_LMDBS_NOTIFICATION)

[WARNING] NT606: Pending changes have not been synchronized for more than 12 hours

Notification Status Consumer: Host Switch (CL_LMDB_HOST_SWITCH_CONSUME)

[WARNING] NT606: Pending changes have not been synchronized for more than 12 hours

Notification Status Consumer: CL_LMDB_SISE_AUTOMAT_CONSUM

[WARNING] NT606: Pending changes have not been synchronized for more than 12 hours

Authority Check of Batch User to Acess LMDB RFC Destinations, Technical System, and Host

[WARNING] AU708: User SOLMAN_BTC has no backend user authorization

Model Versions for Namespace active

[WARNING] NS307: Version of content repository: 11.2 (export 01.06.2015, imported 11.06.2015) outdated; check SAP Note 669669

Instance Counts for Central CIM Classes of Namespace active (Selection Runtime 3.968 s)

[WARNING] CL408: 1 of 71 installed product instances with missing assignment to CR content...

Technical System - Consistency Checks - CR Content Associations for Installed Product Instances

[WARNING] TS752: 1 installed product instances with missing assignment to CR content...
[WARNING] TS759: 1 installed product instances where corresponding CR content is not available (Check SAP note 669669):

SMSY Synchronization and Migration Status for Product Systems (Calculation Runtime 0.617s)

[WARNING] PS200: 1 systems in SMSY are not in LMDB yet; e.g. migration might be missing or incomplete data from TMS in SMSY

SMSY Migration Status for Logical Components (Calculation Runtime 0.140s)

[WARNING] LC104: Different amount of logical componets in SMSY (0), and in new storage (); possible data inconsistency
--------------------------------------------------------------------

Local Solution Manager Software Stack

Software Components of the Local Solution Manager (From CVERS)

SW851: Software Component BBPCRM (Release 701, Support Package 0012)

SW851: Software Component BI_CONT (Release 707, Support Package 0007)

SW851: Software Component CPRXRPM (Release 500_702, Support Package 0011)

SW851: Software Component CTS_PLUG (Release 200, Support Package 0013)

SW851: Software Component GW_CORE (Release 200, Support Package 0008)

SW851: Software Component IW_BEP (Release 200, Support Package 0008)

SW851: Software Component IW_FND (Release 250, Support Package 0008)

SW851: Software Component IW_GIL (Release 100, Support Package 0004)

SW851: Software Component PI_BASIS (Release 702, Support Package 0015)

SW851: Software Component RTCISM (Release 100, Support Package 0000)

SW851: Software Component SAP_ABA (Release 702, Support Package 0015)

SW851: Software Component SAP_AP (Release 700, Support Package 0031)

SW851: Software Component SAP_BASIS (Release 702, Support Package 0015)

SW851: Software Component SAP_BS_FND (Release 702, Support Package 0013)

SW851: Software Component SAP_BW (Release 702, Support Package 0015)

SW851: Software Component SOCO (Release 101, Support Package 0003)

SW851: Software Component ST (Release 710, Support Package 0012)

SW851: Software Component ST-A/PI (Release 01R_700, Support Package 0002)

SW851: Software Component ST-BCO (Release 710, Support Package 0010)

SW851: Software Component ST-ICC (Release 200, Support Package 0000000000)

SW851: Software Component ST-ICO (Release 150_700, Support Package 0041)

SW851: Software Component ST-PI (Release 2008_1_700, Support Package 0012)

SW851: Software Component ST-SER (Release 701_2010_1, Support Package 0023)

SW851: Software Component UISAPUI5 (Release 100, Support Package 0007)

SW851: Software Component UI_INFRA (Release 100, Support Package 0007)

SW851: Software Component WEBCUIF (Release 701, Support Package 0012)

LMDB Performance Indicators

Profile Parameter of ABAP Shared Memory: 500 MB

LMDB Shared Memory Is Used on Host 'servervr', Namespace 'active'

[ok] SM101: 1 versions active
[ok] SM102: 0 versions obsolete
[ok] SM103: 0 versions under construction
SM107: Technical information for LMDB shared memory (transaction SHMM):

SM108: Shared memory area: CL_LMDB_MODEL_SHM_AREA

SM109: Shared memory instance: LDB:0000000001

SM110: LMDB shared memory built on 29.02.2016 11:14:55

SM111: LMDB shared memory starting from change log ID 1456740886000002000

SM112: LMDB shared memory detach information: DETACH_INFO_HANDLE: Released Using the Handle

Performance Measurements for LMDB

RM125: The value in brackets '( )' represents the runtime for a second call

[ok] RM114: 1.12 (1.06) ms runtime to access a CIM class definition

[ok] RM120: 5.37 ms runtime to select a CIM instance directly from database

[ok] RM124: 2.17 (0.19) ms runtime to access an association with 0 targets

[ok] RM122: 38.55 (0.27) ms runtime to access an association with 1 targets

[ok] RM123: 0.02 ms runtime to access the associated (already buffered) instance

[ok] RM115: 2.57 (0.02) ms runtime to access a CIM instance (class SAP_SoftwareComponent)

[WARNING] RM116: 8293.80 (5764.90) ms runtime to query a SAP_SoftwareComponent instance

Status for SLD -> LMDB Content Synchronization

Configuration Source http://host:50000/sld/cimom, Object Server server, Namespace sld/active

SM233: Configuration description: LMDB_host
[ok] SM235: Connection status: Incremental synchronization is active | Details: SM37 for job SAP_LMDB_LDB_0000000001, user *
SM232: Source for CR content: Yes
[ERROR] SM239: An error occured during content synchronization: "HTTP status: 401 Unauthorized - User logon data is invalid or user has no authorization"
[WARNING] SM238: Last polling of data: 25.01.2016 13:04:32 (More than 12 hours ago)
SM230: Change date of last synchronized change: 25.01.2016 12:17:54
[WARNING] CS205: Get amount of failed pending changes: HTTP status: 401 Unauthorized - User logon data is invalid or user has no authorization

Status for Consumers of LMDB Change Notifications (Namespace active)

Notification Status Consumer: Landscape API notifications (CL_DIAGLS_LMDB_NOTIF_MANAGE)

[ok] NT602: Consumer Landscape API notifications (CL_DIAGLS_LMDB_NOTIF_MANAGE) is enabled | Details: SM37 for job SAP_LMDB_NOTIFY_LDB_0000000001, user *

NT610: Change date of last synchronized change: 25.01.2016 12:24:32

NT605: Amount of pending changes: 0

[ok] NT608: User who processed the last notification: SOLMAN_BTC at 25.01.2016 12:24:33

Notification Status Consumer: Landscape API cache (LAPI Cache) synchronization (CL_LAPI_NOTIFICATION_CONSUM)

[ok] NT602: Consumer Landscape API cache (LAPI Cache) synchronization (CL_LAPI_NOTIFICATION_CONSUM) is enabled | Details: SM37 for job SAP_LMDB_NOTIFY_LDB_0000000001, user *

NT610: Change date of last synchronized change: 25.01.2016 10:34:33

NT605: Amount of pending changes: 1

[WARNING] NT606: Pending changes have not been synchronized for more than 12 hours

[ok] LA551: LAPI cache is up-to-date; target version: R7.1_SP12_00; current version: R7.1_SP12_00 (last change of version: 30.11.2014 05:03:22)

[ok] LA556: Full synchronization of cache finished at *00.00.0000 00:00:0

[ok] NT608: User who processed the last notification: SOLMAN_BTC at 25.01.2016 12:24:33

Notification Status Consumer: Synchronization from LMDB to SMSY (CL_LMDBS_NOTIFICATION)

[ok] NT602: Consumer Synchronization from LMDB to SMSY (CL_LMDBS_NOTIFICATION) is enabled | Details: SM37 for job SAP_LMDB_NOTIFY_LDB_0000000001, user *

NT610: Change date of last synchronized change: 25.01.2016 10:34:33

NT605: Amount of pending changes: 1

[WARNING] NT606: Pending changes have not been synchronized for more than 12 hours

[ok] NT608: User who processed the last notification: SOLMAN_BTC at 25.01.2016 12:24:33

Notification Status Consumer: Customer Products in SMSY (CL_LMDB_CUST_PROD_NTF_CONS)

[ok] NT602: Consumer Customer Products in SMSY (CL_LMDB_CUST_PROD_NTF_CONS) is enabled | Details: SM37 for job SAP_LMDB_NOTIFY_LDB_0000000001, user *

NT610: Change date of last synchronized change: 25.01.2016 12:24:32

NT605: Amount of pending changes: 0

[ok] NT608: User who processed the last notification: SOLMAN_BTC at 25.01.2016 12:24:33

Notification Status Consumer: CL_LMDB_EXTSID_MAP_CONSUMER

[ok] NT602: Consumer CL_LMDB_EXTSID_MAP_CONSUMER is enabled | Details: SM37 for job SAP_LMDB_NOTIFY_LDB_0000000001, user *

NT610: Change date of last synchronized change: 25.01.2016 12:24:32

NT605: Amount of pending changes: 0

[ok] NT608: User who processed the last notification: SOLMAN_BTC at 25.01.2016 12:24:33

Notification Status Consumer: Host Switch (CL_LMDB_HOST_SWITCH_CONSUME)

[ok] NT602: Consumer Host Switch (CL_LMDB_HOST_SWITCH_CONSUME) is enabled | Details: SM37 for job SAP_LMDB_NOTIFY_LDB_0000000001, user *

NT610: Change date of last synchronized change: 25.01.2016 10:34:33

NT605: Amount of pending changes: 1

[WARNING] NT606: Pending changes have not been synchronized for more than 12 hours

[ok] NT608: User who processed the last notification: SOLMAN_BTC at 25.01.2016 12:24:33

Notification Status Consumer: Product System Update (CL_LMDB_IPI_UPDATE_CONSUMER)

[ok] NT602: Consumer Product System Update (CL_LMDB_IPI_UPDATE_CONSUMER) is enabled | Details: SM37 for job SAP_LMDB_NOTIFY_LDB_0000000001, user *

NT610: Change date of last synchronized change: 25.01.2016 12:24:32

NT605: Amount of pending changes: 0

[ok] NT608: User who processed the last notification: SOLMAN_BTC at 25.01.2016 12:24:33

Notification Status Consumer: CL_LMDB_SISE_AUTOMAT_CONSUM

[ok] NT602: Consumer CL_LMDB_SISE_AUTOMAT_CONSUM is enabled | Details: SM37 for job SAP_LMDB_NOTIFY_LDB_0000000001, user *

NT610: Change date of last synchronized change: 25.01.2016 10:34:33

NT605: Amount of pending changes: 1

[WARNING] NT606: Pending changes have not been synchronized for more than 12 hours

[ok] NT608: User who processed the last notification: SOLMAN_BTC at 25.01.2016 12:24:33

Notification Status Consumer: Technical Scenario Dual Stack (CL_LMDB_TSCEN_DUALSTK_CONSU)

[ok] NT602: Consumer Technical Scenario Dual Stack (CL_LMDB_TSCEN_DUALSTK_CONSU) is enabled | Details: SM37 for job SAP_LMDB_NOTIFY_LDB_0000000001, user *

NT610: Change date of last synchronized change: 25.01.2016 12:24:32

NT605: Amount of pending changes: 0

[ok] NT608: User who processed the last notification: SOLMAN_BTC at 25.01.2016 12:24:33

Content Synchronization SLD->LMDB - Authority Checks

Authority Check of Batch User to Acess LMDB RFC Destinations, Technical System, and Host

[WARNING] AU708: User SOLMAN_BTC has no backend user authorization

Change Log Extract

Change Log Extract from 29.02.2016 14:39:32 to 15:39:16, Namespace active

CE455: Overall, 0 changes were made and distributed on 0 instances (runtime 0.12 s)

CE452: No changes found in the change log

Top 10 Changed CIM Instances (from 29.02.2016 14:39:32 to 15:39:16, Excluding SAP_SuppliedElements Instances)

CE456: 0 instances found with 0 changes; 0 different CIM classes are involved (runtime 0.01 s)

Changes for SAP_SuppliedElements Instances from the Last 12 Hours

CE453: From 29.02.2016 14:39:32 to 15:39:32; changes: 0, runtime to calculate this result: 0.90 s

CE453: From 29.02.2016 13:39:32 to 14:39:32; changes: 0, runtime to calculate this result: 0.01 s

CE453: From 29.02.2016 12:39:32 to 13:39:32; changes: 0, runtime to calculate this result: 0.01 s

CE453: From 29.02.2016 11:39:32 to 12:39:32; changes: 0, runtime to calculate this result: 0.01 s

CE453: From 29.02.2016 10:39:32 to 11:39:32; changes: 0, runtime to calculate this result: 0.01 s

CE453: From 29.02.2016 09:39:32 to 10:39:32; changes: 0, runtime to calculate this result: 0.01 s

CE453: From 29.02.2016 08:39:32 to 09:39:32; changes: 0, runtime to calculate this result: 0.01 s

CE453: From 29.02.2016 07:39:32 to 08:39:32; changes: 0, runtime to calculate this result: 0.01 s

CE453: From 29.02.2016 06:39:32 to 07:39:32; changes: 0, runtime to calculate this result: 0.01 s

CE453: From 29.02.2016 05:39:32 to 06:39:32; changes: 0, runtime to calculate this result: 0.01 s

CE453: From 29.02.2016 04:39:32 to 05:39:32; changes: 0, runtime to calculate this result: 0.01 s

CE453: From 29.02.2016 03:39:32 to 04:39:32; changes: 0, runtime to calculate this result: 0.01 s

Settings for Current LMDB Namespace

Model Versions for Namespace active

NS305: Model version: 1.6.44
[WARNING] NS307: Version of content repository: 11.2 (export 01.06.2015, imported 11.06.2015) outdated; check SAP Note 669669

Generic Attributes of Table LMDB_NSP_CONFIG for Namespace active

NS304: Entry LAPI_CACHE_DISABLED - value <;empty>; - last changed by user SOLMAN_BTC at 30.11.2014 05:03:22
NS304: Entry LMDB_ADM_STATUS - value ESM239: An error occured during content synchronization: "HTTP status: 401 ... - last changed by user INFOBASIS2 at 29.02.2016 15:38:43
NS304: Entry LMDB_EXEC_VERIFICAT - value 1 Product Systems (batch mode) - last changed by user INFOBASIS at 17.12.2014 14:08:14
NS304: Entry LMDB_LAPI_STATUS - value R7.1_SP12_00 - last changed by user SOLMAN_BTC at 30.11.2014 05:03:22
NS304: Entry MIG_OSS_SYNC_FLAG - value auto_solman_setup - last changed by user SOLMAN_BTC at 28.09.2015 12:42:32
NS304: Entry MIG_PROD_SYSTS_ALL - value 1 - last changed by user SOLMAN_ADMIN at 02.12.2014 03:21:04
NS304: Entry MIG_PROD_SYSTS_LAST - value 1 - last changed by user SOLMAN_ADMIN at 02.12.2014 03:21:04
NS304: Entry N_CONSUMER_CLEANUP - value 160205 - last changed by user SOLMAN_BTC at 15.01.2016 19:44:56

CIM Class Statistics

Instance Counts for Central CIM Classes of Namespace active (Selection Runtime 3.968 s)

CL405: 0 technical systems of type .NET System found within LMDB (CIM class sap_standalonedotnetsystem)

CL405: 0 technical systems of type Apache Tomcat Server found within LMDB (CIM class sap_atcserver)

CL405: 5 technical systems of type Application Server ABAP found within LMDB (CIM class sap_bcsystem)

CL405: 3 technical systems of type Application Server Java found within LMDB (CIM class sap_j2eeenginecluster)

CL405: 0 technical systems of type CA Introscope Enterprise Manager (Cluster) found within LMDB (CIM class sap_ismomserver)

CL405: 0 technical systems of type CA Introscope Enterprise Manager (Standalone) found within LMDB (CIM class sap_isemserver)

CL405: 7 technical systems of type Database System found within LMDB (CIM class sap_databasesystem)

CL405: 0 technical systems of type Diagnostics Agent found within LMDB (CIM class sap_diagnosticsagentinstance)

CL405: 0 technical systems of type External Service found within LMDB (CIM class sap_externalapplicationserver)

CL405: 0 technical systems of type IBM WebSphere Application Server found within LMDB (CIM class sap_ibmwscell)

CL405: 0 technical systems of type Microsoft Internet Information Services found within LMDB (CIM class sap_msiisinstance)

CL405: 0 technical systems of type SAP BusinessObjects Cluster found within LMDB (CIM class sap_bocluster)

CL405: 0 technical systems of type SAP HANA Database found within LMDB (CIM class sap_hdbsystem)

CL405: 0 technical systems of type SAP NetWeaver Master Data Management Server found within LMDB (CIM class sap_mdmdataserver)

CL405: 0 technical systems of type SAP Web Dispatcher found within LMDB (CIM class sap_bcwebdispatcher)

CL405: 0 technical systems of type SAP liveCache found within LMDB (CIM class sap_livecache)

CL405: 0 technical systems of type Sybase Unwired Platform found within LMDB (CIM class sap_supcluster)

CL405: 0 technical systems of type TREX System found within LMDB (CIM class sap_trexsystem)

CL405: 0 technical systems of type Unspecific 3-Tier System found within LMDB (CIM class sap_unspecificthreetiersystem)

CL405: 0 technical systems of type Unspecific Cluster System found within LMDB (CIM class sap_unspecificclustersystem)

CL405: 0 technical systems of type Unspecific Standalone Application System found within LMDB (CIM class sap_unspecificstandaloneapplicationsystem)

CL401: 7 instances of SAP_ComputerSystem within LMDB; database count: 100

CL401: 26 instances of SAP_InstalledProduct within LMDB; database count: 386

CL401: 71 instances of SAP_InstalledSoftwareFeature within LMDB; database count: 1036

[WARNING] CL408: 1 of 71 installed product instances with missing assignment to CR content...

CL410: ... Detailed Analysis: Go to LMDB_ADM -> Overview -> LMDB Content Analysis -> Technical System

CL401: 5058 instances of SAP_MemberOfProductLine within LMDB; database count: 28844

CL401: 5058 instances of SAP_Product within LMDB; database count: 100753

[ok] CL403: Each SAP_Product instance has an association to one SAP_ProductLine (5058 instances found) --> Indicates that CR content is okay

CL401: 2986 instances of SAP_ProductLine within LMDB; database count: 38308

CL401: 8 instances of SAP_ProductSystemLandscape within LMDB; database count: 65

CL401: 70 instances of SAP_SoftwareFeatureType within LMDB; database count: 413

CL401: 3 instances of SAP_TechnicalScenario within LMDB; database count: 27

LMDB Technical System - Consistency Checks

Technical System - Consistency Checks - CR Content Associations for Installed Product Instances

TS750: 71 installed product instances (SAP_InstalledSoftwareFeature) in LMDB (query runtime 0.108 s)
TS751: 70 associations from installed product instances to CR content (SAP_SoftwareFeatureType) (query runtime 0.743 s)
[WARNING] TS752: 1 installed product instances with missing assignment to CR content...
TS756: Detailed Analysis for CR Associations: Check if CR content is correct (runtime 86.715 s)
[ok] TS757: 0 installed product instances with missing CR content association, but CR data is available (refer to SAP Note 1881516):

[WARNING] TS759: 1 installed product instances where corresponding CR content is not available (Check SAP note 669669):

LBD (Application Server ABAP), Product Instance: SAP NETWEAVER: 1, 7.5 on LBD.SystemNumber.0020809376.SystemHome.

LMDB Product System - Consistency Checks

SMSY Synchronization and Migration Status for Product Systems (Calculation Runtime 0.617s)

All names of product systems (LMDB-PS), technical systems of type AS ABAP (LMDB-ABAP) and SMSY systems (SMSY) are collected
For each name it is checked if the corresponding entity exists in LMDB-PS, LMDB-ABAP and SMSY
For example LMDB-PS[X] means that a product system with the name exists in LMDB; LMDB-PS[_] means that it does not exist
All combinations of LMDB-PS[?], LMDB-ABAP[?] and SMSY[?] are checked for their count of occurences
The first names (max. 15) are listed; the names represent a LMDB product system, LMDB technical system ABAP or SMSY system

LMDB-PS[X]__LMDB-ABAP[X]__SMSY[X] - Count 5

Example System Names: DEV, QUA, PRD, SOL
PS182: Okay: 5 product systems and AS ABAP from LMDB are synchronized to SMSY

LMDB_PS[X]__LMDB_ABAP[_]__SMSY[X] - Count 2

Example System Names: EED, EEP
PS188: Okay: 2 product systems in LMDB synchronized to SMSY

LMDB-PS[X]__LMDB-ABAP[_]__SMSY[_]__LMDB-PIs[_] - Count 1

Example System Names: ID9

PS192: Partly Okay: 1 product systems in LMDB not synchronized to SMSY because of missing product instance assignment

LMDB-PS[_]__LMDB-ABAP[_]__SMSY[X] - Count 1

Example System Names: LVV

[WARNING] PS200: 1 systems in SMSY are not in LMDB yet; e.g. migration might be missing or incomplete data from TMS in SMSY

Logical Components - Consistency Checks

SMSY Migration Status for Logical Components (Calculation Runtime 0.140s)

LC105: 468 logical componets found in the new repository (4 created by customer, 464 delivered by SAP)
[ok] LC100: All logical componets from SMSY were migrated to the new store
[WARNING] LC104: Different amount of logical componets in SMSY (0), and in new storage (); possible data inconsistency
LC103: 467 logical component found in SMSY (for downward compatibility data is synchronized to SMSY).

Namespaces and Technical Parameters of CIM Domain

LMDB Configurations with Effect Across LMDB Namespaces

NS303: Version of CIM server: 1.0
NS304: Entry NUC_CONVERSION_DONE - value X - last changed by user SOLMAN_BTC at 29.11.2014 07:01:47

All Active Namespaces Within LMDB

[ok] NS361: One default namespace found with name active | namespace ID 0000000001, rank 200

NS362: Domain LDB; namespace ID 0000000001; display name active; rank 200

Domain Settings of WBEM Client

DO502: ApplicationLog.ExpirationDays = 30
DO502: AutomaticActions.HostSwitchTTLSecs = 8640
DO502: AutomaticActions.UpdateDiagnosticsRelFlag = true
DO502: AutomaticActions.UpdateProductSystemInstances = true
DO502: CachingClient.InstanceBufferSize = 5000
DO502: ContentSync.AllowFastFullSync = true
DO502: ContentSync.BatchSize = 100
DO502: ContentSync.ConflictResolutionOnPropertyLevel = true
DO502: ContentSync.ConsistentReadTimeout = 10000
DO502: ContentSync.DelayForJobDebugging = false
DO502: ContentSync.FullSyncContinueAfterAbort = true
DO502: ContentSync.FullSyncMaxLoops = 20
DO502: ContentSync.FullSyncModelOneTransaction = true
DO502: ContentSync.FullSyncRelaxedModelCheck = true
DO502: ContentSync.GenerateEsid = true
DO502: ContentSync.IgnoreErrors =
DO502: ContentSync.JobExecutionWithSyUname = false
DO502: ContentSync.MaxErrorsUntilAbort =
DO502: ContentSync.PingReadTimeoutSec = 60
DO502: ContentSync.PollingIntervalMinutes = 10
DO502: ContentSync.ReadTimeoutSec =
DO502: ContentSync.ReadTimeoutSecUI = 120
DO502: ContentSync.SelectIntervalSec =
DO502: CustomAttributes.DisplayFullList = false
DO502: DefaultNamespace = active
DO502: LAPI.DisableFQDNCheck = false
DO502: LAPI.FullSyncViaCachedClient = true
DO502: LAPI.GracePeriodSystemUpdate = 120
DO502: LAPI.LockTimeoutForHostInSec = 10
DO502: LAPI.LockTimeoutForTechnicalSystemInSec = 120
DO502: LAPI.NotificationErrorCountLimit = 1
DO502: NeverHideLMDBMigration = false
DO502: Notification.AverageProcessingTimePerConsumerMinutes = 30
DO502: Notification.IntervalMinutes = 5
DO502: Notification.PageSize = 256
DO502: Notification.VerboseJobLog = false
DO502: ObjectManager.CheckValuemapIntegerRangesForOverlaps = false
DO502: ObjectManager.CreateDefaultNamespaceOnRead = false
DO502: ObjectManager.LockChangeLogOnWrite = true
DO502: ObjectManager.LockingTimeoutSecLong = 60
DO502: ObjectManager.LockingTimeoutSecShort =
DO502: ObjectManager.StrictModifyClassChecks = true
DO502: ObjectManager.StrictModifyQualifierChecks = true
DO502: ObjectManager.SupportNamespaceChangeWithinTransaction = true
DO502: ObjectManager.SynchronousDequeue = true
DO502: ObjectManager.TXLockMode = 3
DO502: ObjectManager.UseEnqueueService = true
DO502: ObjectManager.UseSharedMemory = true
DO502: ObjectManager.WriteChangeLog = true
DO502: ObjectServerExternal = <;empty>;
DO502: ObjectServerInternal = LMDB_host
DO502: Persistence.ChangeLogLookAheadCutOffLimit = 50000
DO502: Persistence.ChangeLogLookAheadStartLimit = 1000
DO502: Persistence.ChangeLogReadCommitted = true
DO502: Persistence.CleanupIntervalSize = 500
DO502: Persistence.CleanupMaxIntervalCount = 10000
DO502: Persistence.NamespaceDeletionDays = 30
DO502: Persistence.StorageFormat = CXML
DO502: ReadTimeoutSecShort = 2
DO502: Reporting.ShowProductSystemLandscapeVeriReport = false
DO502: Reporting.ShowTechnicalSystemLandscapeCheckStatusReport = false
DO502: RequiredCRVersion = 9.10
DO502: RequiredCRVersionExpirationWeeks = 26
DO502: RequiredModelVersion = 1.6.36
DO502: SMSY_Synchronization.DisableLandscapeFetch = true
DO502: SMSY_Synchronization.FetchSize = 256
DO502: SMSY_Synchronization.Notify.DSWP = false
DO502: SMSY_Synchronization.Notify.IBase = false
DO502: SMSY_Synchronization.SyncForDeveloperTestingActive = false
DO502: Transactions.CommitAfter = 256
DO502: UI.SelfMonitoringStatusExpirationHours = 48

Could you please help on the above error.

I have given full authirization to solman_btc user id.

Regards

Suresh

Dear Experts,

I am upgrading SAP Solman 7.1 SPS 5 to SPS 14 with SUM SPS10SPS14

On ABAP Extraction Phase PRE_INPUT_CHK/READCVERS_DUMP i m getting error (Screenshots and Logs attached)

Kernel 7.21 EXT with Oracle 11.2 on Windows 64.

I have completed all stuff for SSFS..

Plz suggest the solution.

Regards,

Qazi

hi,

I am trying to download SPS14 for Netweaver7.4 via Solution Manager 7.1 (SPS13) MOPZ transcation. SPS14 was released on 02/26/2016. Somehow when it come to target stack selection i can get only till SPS13.

Are there any wait period before i can download this SPS ? Any thoughts ? or Am i missing anything here ?

Thanks Sheril

Hi SOLMAN Experts,

we want to configure our machines to create OSS messages via SAP GUI's Help Button "Create Support Message" tab,

we have solution manager but we are not using ITSM also not configured.

can we do that without ITSM configuration ? if yes then can you please help me to do that ?

Regards,

Mohinder

Dear Moderators,(Barbara Buchholz , Dolores Correa ,Tobias Hauk , Paul Babier )

I recently saw the categorization of posts in SAP Fiori (SAP Fiori) homepage in SCN. This looks neat & well organized.

I do see the Categories while posting my questions here, but they do not appear in the homepage as we see in Fiori space. So according to me, that beats whole purpose of this exercise. Also, going forward I propose to make the categorization selection mandatory for anyone posting a discussion or or blogs in SAP Solution Manager SCN space.

Please provide your feedbacks.

Thanks,

Vivek

Hi,

I have an issue with SODOCA in solman manager 7.1 , in HR since we use the same transaction PA40 in different process like recruitment ,leaves ...

we can't have the real situation of the frequency of using special HR process, have someone fit the same problem and have we the possibility to add type of actions in business blue print configuration for example "RC: recruitment"

thank you for considering my question.

Hi All,

When i try to produce the stack xml file for my solution manager patch update process getting error. When i try to synchronize the technical system to lmdb does not exist. RLMDB_SYNC_TECHNICAL_SYSTEM tell does not contain smr(our system id).

Thanks in advance

Hello Experts!

I have a question that I'm stuck on. In summary, I added a custom assignment block (a "form" table) in the AET in tcode SM_CRM in ChaRM transaction type ZMCR. The new custom fields are editable and saveable using the standard AET generated logic.

Following the same steps, I created another custom assignment block (also a form table) for ChaRM transaction type ZMAD - a Change Document.

The standard AET generated logic does not allow edit or save. This link has my related post that has the screen shots for my issue.

http://scn.sap.com/thread/3863581

To allow the new fields to be editable, I generated the setter and getter methods and changed method GET_I_field. That works fine now.

I still can't get values entered on new field to be saved. Collection_wrapper->get_current is Initial. How do I bind the context node to the entity? I have tried a custom controller to try to bind it to BTAdminH, but that didn't work. Am I missing something?

Researching on here, I'm finding several posts on the topic, but nothing that clearly details what is needed. Is a custom controller needed? Where is additional code needed? Can anyone explain in detail what is needed to allow the new field to be saved?

Thanks in advance for your help! I'm looking forward to rewarding points!!!

Robyn

Hi experts,

I want to attach html form instead of smartforms in Incident Management in sap solman, can u suggest me.please

Dear All,

I am getting below error in Manged System Configuration final step - Configuration Check

The Definition of Technical System 'SID-ABAP' is not correct :

'SID-ABAP' : Operating System 'Linux-defa' of host 'hostname' must have atleast one Software Component Version.

Diagnostic Agent is recently installed on all managed systems and also the host agents are upgraded on all hosts.

SLD has the information about installed products and software component versions under Technical Systems.

When i check in LMDB, details of Software Component Versions is present under Software but there is no data about Installed Software Component versions under hosts and Technical Instances.

The error which i see in LMDB --> Data Supplier Status is as below

Can someone please guide how to proceed.

Thanks

Aadil