The log for the SDCCN "Maintenance Package" task for logging the retrieval process of the maintenance certificate is not activated.
ST-PI
2005_1_46C Support Package 8
2005_1_620 Support Package 8
2005_1_640 Support Package 8
2005_1_700 Support Package 6
2005_1_710 Support Package 4 Other terms Maintenance certificate, key, licence, SolMan, Solution Manager Reason and Prerequisites An inactive delivery was made. Solution This note activates the log in the "Maintenance Package" task.
With SAP Solution Manager 7.0 Support Package 16, the job REFRESH_ADMIN_DATA_FROM_SUPPORT returns any errors in the job log when calling maintenance certificates for customers if the service provider function is active. The system-specific maintenance certificates are called partly using incorrect RFC destinations of the SAP backbone.
Other terms Service provider, VAR, ISV, Solution Manager, SolMan, SP16, maintenance certificate, licenses
Reason and Prerequisites This is caused by a program error and a missing BAdI filter entry.
Solution The error is solved when you implement this note, and the call of the maintenance certificate for the service provider is corrected.
Sometimes systems are excluded from the requirement process of the maintenance certificate. As a result, no maintenance certificates are required and collected by SAP (by SAP Solution Manager) for these systems.
Other terms Maintenance certificate, maintenance, licenses, automatic distribution
Reason and Prerequisites The error occurs because of an incorrect database selection.
Solution The error is corrected when you implement this note.
Transactions SPAM and SAINT issue the warning "No valid maintenance certificate found for system XXX."
Transactions SPAM and SAINT issue the error message "No valid maintenance certificate found for system XXX."
Other terms SPAM, SAINT, maintenance certificate
DB2/400, DB4, AS400, AS/400, DB400
TN 805, TN 806, TN 808, TN 809
TN 805 No valid maintenance certificate found (see long text)
TN 806 A valid maintenance certificate was found for system &1
TN 808 No queue calculation because of a missing maintenance certificate
TN 809 The maintenance certificate check requires a kernel patch level >= 145 Reason and Prerequisites Maintenance certificates are provided for all systems with NetWeaver 7.0 and higher.
The software lifecycle management tools SPAM and SAINT check whether there is a valid maintenance certificate as of SPAM/SAINT 700/0031.
The check can be executed only as of SAP_BASIS 700 Support Package 16 or SAP_BASIS 701 Support Package 00 and subsequent versions. For lower Support Package levels, the maintenance certificate is always regarded as valid.
SPAM/SAINT 700/0031, 700/0032, 700/0033, and 710/0034 issue a warning if no valid maintenance certificate was found.
SPAM/SAINT 700/0034 issues an error message if no valid maintenance certificate was found.
In this case, the queue can no longer be calculated.
A) You have not installed a valid maintenance certificate in the system. B) You use SAP kernel patch level 144 or lower in your system.
SPAM/SAINT 700/0031 does not recognize an installed maintenance certificate and issues the warning. C) You use the database system AS/400.
SPAM/SAINT 700/0031 does not recognize an installed maintenance certificate and issues the warning.
Solution
A) Install a maintenance certificate in the system.
This can be installed automatically using the SAP Solution Manager.
Proceed according to the application help:
DE: 7.0 SP16 Automatic Distribution of Maintenance Certificates
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000646691& _SCENARIO=01100035870000000112&_OBJECT=011000358700000574762008D
EN: 7.0 SP16 Automatic Distribution of Maintenance Certificates
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000646691& _SCENARIO=01100035870000000112&_OBJECT=011000358700000574752008E
as of Support Package 18: http://help.sap.com/saphelp_smehp1/helpdata/en/89/a7c08d740c4cffb491f98801f17d30/frameset.htm
Alternatively, you can request a maintenance certificate via the SAP Support Portal (http://www.service.sap.com/licensekey) and install it like a license key using transaction SLICENSE.
Information about how to proceed is available under http://www.service.sap.com/~sapidb/011000358700001504082008E
For general information about requesting and downloading license keys, see Note 94998.
B) You must use SAP kernel patch Level 145 or higher in your system to ensure that the installed maintenance certificate can be recognized by SPAM or SAINT.
As of SPAM/SAINT 700/0032 the system issues a relevant information message in systems with SAP kernel patch level 144 or lower.
C) Use at least SPAM/SAINT 700/0032 with the database system AS/400.
Symptom Systems are excluded from the requirement process for maintenance certificates.
Other terms Maintenance certificate, SolMan, SAP Solution Manager, license data
Reason and Prerequisites The affected systems are not maintained completely in the Solution Manager system landscape. In other words, the software components are missing and the relevance check fails. As a result, the system is not included in the requirement process for maintenance certificates. The purpose of this check is to keep the load on the SAP backbone as low as possible.
Solution After you implement this note, the relevance check is less strict. As a result, maintenance certificates are also required for systems that are not maintained completely.
This note addresses problems in the automatic distribution of Maintenance Certificates from a Solution Manager system to a managed system by the "Maintenance Package" task of SDCCN:
1) The activity "Get License Data" within the "Maintenance Package" task is never executed. In the log of the task you find "Not due, due every 0 , ...", although in the settings you provided an appropriate, non-zero period for "License Data".
2) You are not able to switch off the transfer of Maintenance Certificates inside the "Maintenance Package" task by setting the periodicity of the "License Data" section to zero.
Other terms SDCCN, Solution Manager, Maintenance certificate, Maintenance key Reason and Prerequisites
1) Due to a program error the periodicity specified in the settings for the "Licence Data" section is used only when a new "Maintenance Package" task is created. If a periodic "Maintenance Package" task was already existing when ST-PI 2008_1 was installed, it will always have period 0 for the "License Data" section.
2) Periodicity zero for the License Data section of the "Maintenance Package" task is rejected by the screen.
Solution Please implement the correction instructions attached to this note.
1) The next run of the "Maintenance Package" task will use the correct periodicity for the "License Data" section specified in the settings.
Alternatively, you can delete the "Maintenance Package" task and create a new one.The new task will have the correct periodicity.
2) In order to switch of the transfer of Maintenance Certificates by the "Maintenance Package" task of SDCCN, go to the settings for this task (menu Goto -> Settings -> Task-specific; Task-specific settings -> Session Data Collection -> Maintenance -> Settings), select the tab "License Data" and set the "Repeat every ..." value to zero.
Please note that this change is effective only for new tasks, so you have to delete an already existing "Maintenance Package" task and create a new one.
Be aware that this note is only valid for ST-PI 2008_1_* support package 0. If you import a transport request containing this note into a system with ST-PI 2008_1_* + Support package 1 this will cause syntax errors in function group /BDL/BDL11. See note 1403021 how to resolve these errors.
