SAP Solution Manager
SMD Agent Offline at Agent Administration
Symptom Your SMD Agent started correctly in the OS and You can see the process through tme command ps -ef | grep daaadm But when You go to the transaction SOLMAN_WORKCENTER in the option Agent Administration SMD Agent is offline Another way to Agent Administration by link http://server:port/webdynpro/dispatcher/sap.com/tc~smd~navigation/StandaloneApp?APP_ID=ADMIN_AGENT Solution All action will be performed in managed system. Log on OS level user daaadm su – daaadm Stop SMD Agent stopsap SMDA97 Perform configuration for direct connect to solution manager /usr/sap/DAA/SMDA97/script/smdsetup.sh managingconf hostname:”sapms://<hostname>” port:”<message server port>” user:”SMD_ADMIN” pwd:”<password>” servername=”<hostname>” Start SMD Agent startsap SMDA97 Now SMD Agent in Agent Administration … Continue Reading
Registering JAVA system in CEN rz21 error
Symptom When We register java system to monitoring from RZ21 Choose Technical Infrastructure → Configure Central System → Create Remote Monitoring Entry we must define HTTP Port of the Message Server. When We try set HTTP Port of the Message Server 50000, or 3901, We have error No valid XML document received. ( http://hostname:50000/msgserver/xml/logon ) Solution Set HTTP Port of the Message Server to 81XX
Note 176492 – Automatic email when an alert occurs (RZ20)
Note 176492 – Automatic email when an alert occurs (RZ20) Reason and Prerequisites The CCMS monitor architecture (transaction RZ20) allows you to define auto-reaction methods (reports, function modules) that are executed automatically when alerts occur. As of R/3 Release 4.6A, technical basic requirements have been provided for sending SAPOffice documents from CCMS monitor architecture. As of this release, a predefined CCMS_OnAlert_Email auto-reaction method has also been delivered. Consequently, when an alert occurs, emails with alert information are automatically sent from a SAP system (called C11 below) to 1. a SAPoffice user in client 000 in the same system. 2. a … Continue Reading
CHARM Configuration
CHARM Configuration SAP Note 1520678 – Change Request Management Configuration & Operation Guide
Изменение программы, выполняемой для задачи Task List для срочных корректур
Задача: Изменение программы, выполняемой для задачи Task List для срочных корректур. Настройка производится с помощью транзакции SOLAR_PROJECT_ADMIN для определенного проекта. Путь по закладкам: Системный ландшафт – Запросы на изменения Нажимаем на четвертую в первом ряду кнопок ПлЗадач (Управление списками задач). Этой кнопке соответствует транзакция /TMWFLOW/MAINTINST. В появившемся окне транзакции /TMWFLOW/MAINTINST выбираем закладку Параметры На данной закладке вызываются программы настройки конфигурации Планов задач. Используем следующие настройки: Пункт 1 Варианты для списка задач в плане задач По умолчанию мы видим два варианта SAP0 и SAP1 Пункт 2 Вариант списков задач по умолчанию в типов задач для типов проекта SMI Видим что для срочных … Continue Reading
SAP Solution Manager Managed System Check Error
SAP Solution manager 7.1 You configure Managed system. On step Check Configuration You have an error: The user SM_SM1 cannot be checked on satellite system: No RFC authorization for function module BAPI_USER_EXISTENCE_CHECK. Solution In managed system go to transaction PFCG modify role Z_SOLMAN_READ, in authorization objects S_RFC set value for parameter RFC_NAME to *
Quick Approve Download Basket
For quick approve download basket SAP Download Area You can use function module /TMWFLOW/MO_UI_BASKET_AUTHORIZ Launch transaction se37, set Function Module name /TMWFLOW/MO_UI_BASKET_AUTHORIZ and press button Test/Execute (F8) On next Screen press Execute (F8)
Upgrade Solman – import error repaired object
We experienced the same thing on our sandbox. However, in our case we had an earlier error during DDIC Activation. We upgraded from Solution Manager 7.0 SPS 17 to EhP 1 SPS 20. The DDIC Activation got resolved by implementing Note 1256384 manually. However the request was not released when we resumed the SAINT. This caused the IMPORT_PROPER to stop at SAPK-701DOINSAPBASIS. At this point the system was basically paralized. No Easy Access menu, no SAINT, only dumps. SE10 could not be used to release the repair request and resulted in dump. Since we know that the only request still … Continue Reading
An error occured while processing the UME command READ_USER
Managed System Configuration In phase Create Users you have error: An error occured while processing the UME command READ_USER Solution: Create role Z_SPML_ADMIN Add follow actions to Z_SPML_ADMIN Spml_Write_Action Spml_Read_Action Assign the role Z_SPML_ADMIN to user
SAP Solution Manager не работает отправка сообщения в SAP
После начальной настройки SAP Solution Manager не работает отправка сообщения в SAP. Наши действия: 1. Определить ответственную группу обработчиков, отредактировать правило присвоения отвественной группы. 2. Выставить пользовательский статус сначала “в обработке”, сохранили, потом “Отправлено в SAP “, сохранить. 3. После этого выбрать действие “Отправить в SAP”. В случае ошибки “нет с юзера для отправки” нужно добавить в пераметры пользователя строчку SIDXXXXXXXXXX100USER, где SID – SID системы, XXXXXXXXXX – номер системы, 100 – клиент, USER – пользователь