By clicking on the icon to watch this Wiki page, you will be notified when updates are made - SAP Support. You will need to login to view the icon.
|June 19, 2020||There is a false alert in section 3 after updating to the latest ST-A/PI: |
"Data regarding the performance or configuration of SAP Gateway could not be found in the SDCC download. ST-A/PI function: DCA_NW_GATEWAY in project DCA"
|Development is working on a fix to be released via SCU.||KI202006242|
|June 18, 2020|
This is related to the SAP Support Backbone Update. RFC connections to SAP was no longer supported as of Jan 8, 2020.
Since Jan 8, 2020, a grace period was provided using the temporary workaround (RFC to SAP + Technical Communication user) to send EWAs to SAP. The grace period has ended for non-HANA systems.
Refer to SAP KBA 2923799 - Final Shutdown of RFC Connections From Customer Systems to SAP
For SAP EARLYWATCH ALERT
To resolve this, you must switch to HTTPS based communication.
|June 10, 2020||SM:EXEC SERVICES aborts with dump: |
Category ABAP Programming Error
"46C" cannot be interpreted as a number
|Reset SCU to 11.05.2020. Refer to KBA 1814723 for more instructions.||Development is investigating this issue.||KI202005660|
|May 19, 2020||Java EWA is showing a grey rating with Service Data Quality alert:|
"Installed SAP product version could not be determined for the managed system. Check the SAP product version in the landscape management database (LMDB) of your SAP Solution Manager, or use SAP Note 2376972 for further analysis."
|Reset SCU to an older SCU, like 16.04.2020, to process the EWA sessions.|
Refer to KBA 1814723.
|Development is investigating this issue.||KI202005066|
|March, 2020||The collection of parameter data (ST-A/PI) is unavailable for your session. Run the relevant script attached to SAP Note 1171650 for the DB recommendations.||N/A||Development is working on a fix||KI202003672|
|March 27, 2020|
SM:EXEC SERVICES aborts with dump:
Runtime Errors CALL_FUNCTION_PARM_UNKNOWN
Function module "/BDL/RFC_HTTP_TEST" was called with parameter "NO_MESSAGE".
This parameter is not defined there however.
|Correction was released via SCU on April 21, 2020. |
Refer also to SAP Note 2909623.
|March 16, 2020||Message "Monitoring data from your SAP HANA database could not be read because the related download function module of your ST-PI software component is not up to date. ST-PI Function HDB_COLL_MULTI_DOWN" in section "Quality of Data in Service Data Control Center". The issue occurs for SystemDB and only if using HANA 2.0 >=SPS04||If you want to get rid of these alerts you can switch the processing of the SystemDB off by putting in the description field in DBACockpit of a HANA Database -> NON_EWA_. |
(HANA Checks in EWA Wiki: https://wiki.scn.sap.com/wiki/x/ABdiGg)
|Resolved via Service Content Update (SCU) process.||KI202003306|
|March 12, 2020||Red rating for sub-chapter Critical Number Ranges in EWA report.||N/A||Development is currently working on a fix.|
Refer to KBA 2902989 - EWA - Red rating for sub-chapter Critical Number Ranges.
|Mar 11, 2020||A new section "SAP HANA: SQLDBC Version" is appearing in the "Software Configuration chapter" of the EWA, even though there is no HANA DB system associated to the managed system.||N/A||Resolved via Service Content Update (SCU) process.||KI202003538|
Feb 5, 2020
|EarlyWatch Alert (EWA) has the message 'You are using an Oracle release that is not supported by the used ST-SER release' for Oracle 19.||N/A||Resolved via Service Content Update (SCU) process.||KI202002872|
|Jan 31, 2020||EWA processing of data sent through SAPOSS / SDCC_OSS with technical communication user is not working.||N/A||Issue is fixed on SAP side. Reactivate failed "sent to SAP" in SDCCN.|
|Jan 23, 2020||EWA show recommendations regarding Online Collectors - SAP Note 2827332 "Content is only available if you allow online collectors". You already activated the Online Collectors like described in the EWA but the warning remains. This behavior is affecting systems below SAP_BASIS 740||N/A||Correction was released via SCU on February 17, 2020.||KI202001611|
|Jan 13, 2020||EWA has the message: As immediate work around enter a Technical Communication User in the RFC destination to SAP Support Backbone.||N/A||Under investigation by development.||KI202001984|
|December 02, 2019|
SM:EXEC SERVICES aborts with dump:
Category ABAP Programming Error
Access using a ''NULL' object reference is not possible.
|N/A||Resolved via Service Content Update (SCU) process.||KI201912018|
|November 15, 2019||Solution Manager EarlyWatch Alert (EWA) shows the system is not ready for 2020.|
"System SID is not prepared for SAP Support Backbone update. Enable Solution Manager 7.2 SID to connect with HTTPS to SAP."
In the corresponding table, column 'Destination' contains 'HTTPS→SAP' and column 'User' contains 'S-user' or 'Certificate'.
The Ready for 2020 column is rated Yellow instead of Green.
Correction was released via SCU on December 9, 2019.
|Oct 31, 2019||EarlyWatch Alert report file has increased in size and therefore is not possible to send via email. The root cause is due to an increase in the chapter 'Origin of SQL Statement (ABAP)'||N/A||Resolved via Service Content Update (SCU) process.||KI201910718|
|September 25, 2019||EarlyWatch Alert section Database - Maintenance Phases is blank. The relevant Oracle database version is 12g Release 2 (126.96.36.199).||N/A||Resolved via Service Content Update (SCU) process.||KI201925609|
|September 4, 2019||In EWA chapter Database Perormance, the EWA reports "Oracle Release not Supported by ST-SER Release" for Oracle Database 18.||N/A|
Fix available in ST-SER 720 SP17.
|Feb 5, 2019||SDCCN job /BDL/TASK_PROCESSOR shows the message: Error: RFC SDCC_OSS can no longer be used, You must use new RFCs for connecting SAP backend'. 'Error: Please Run transaction SDCCN to migrate RFC SDCC_OSS to new RFCs.|
Transaction SDCCN shows the error message: 'The infrastructure of the SAP Support Backbone is updated and moved. Therefore, you need to use a new destination to connect to SAP. To migrate the SDCC_OSS RFC to the new destination, choose Yes....'. If you choose 'No' or as long as the new destination is not functional, you cannot use transaction SDCCN
|As a workaround, use 2739614 - Transaction SDCCN is blocked due to HTTP destination for the new communication channel not created|
To solve the issue, use the recommend option by applying the latest SP of component ST-PI.
Refer to SAP Note 2748869 - ST-PI 2008_1_7xx SP20, ST-PI 740 SP10: Corrections for SDCCN regarding SAP Backbone connectivity