<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SAP Basis World</title>
	<atom:link href="https://sapbasisworld.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://sapbasisworld.com/</link>
	<description>Pomagam Lepiej Zrozumieć Świat SAP Basis</description>
	<lastBuildDate>Wed, 03 Dec 2025 22:07:40 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.1</generator>

<image>
	<url>https://sapbasisworld.com/wp-content/uploads/2021/11/cropped-SAP-Basis-World-favicon-32x32.png</url>
	<title>SAP Basis World</title>
	<link>https://sapbasisworld.com/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Fixing “Timeout is over” When InboundRA Fails to Start in SAP PI/PO</title>
		<link>https://sapbasisworld.com/fixing-timeout-is-over-when-inboundra-fails-to-start-in-sap-pi-po/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 03 Dec 2025 22:07:38 +0000</pubDate>
				<category><![CDATA[PO]]></category>
		<category><![CDATA[#Basis]]></category>
		<category><![CDATA[#PO]]></category>
		<guid isPermaLink="false">https://sapbasisworld.com/?p=3299</guid>

					<description><![CDATA[<p>When you restart your SAP Process Integration / Process Orchestration system, you may notice that the InboundRA resource adapter does not come up. In the default trace you’ll typically see a deployment error for inboundRA and a runtime exception indicating that the timeout is over and the RA is blocking during startup. This behavior is [&#8230;]</p>
<p>The post <a href="https://sapbasisworld.com/fixing-timeout-is-over-when-inboundra-fails-to-start-in-sap-pi-po/">Fixing “Timeout is over” When InboundRA Fails to Start in SAP PI/PO</a> appeared first on <a href="https://sapbasisworld.com">SAP Basis World</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Upcoming expiration of certificates tc_trust_class_2_ii and tc_trust_class_2_L1_CA_XI</title>
		<link>https://sapbasisworld.com/upcoming-expiration-of-certificates-tc_trust_class_2_ii-and-tc_trust_class_2_l1_ca_xi/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 03 Dec 2025 07:13:12 +0000</pubDate>
				<category><![CDATA[Admin]]></category>
		<category><![CDATA[#Basis]]></category>
		<category><![CDATA[#Java]]></category>
		<category><![CDATA[#security]]></category>
		<guid isPermaLink="false">https://sapbasisworld.com/?p=3297</guid>

					<description><![CDATA[<p>In SAP NetWeaver AS Java environments, two trust center certificates — tc_trust_class_2_ii and tc_trust_class_2_L1_CA_XI — are approaching their expiration date. These certificates are part of the platform’s built-in trust store and are used for validating secure communication scenarios, including SSL/TLS handshakes and signature verification between SAP components or external services. When these certificates expire, systems [&#8230;]</p>
<p>The post <a href="https://sapbasisworld.com/upcoming-expiration-of-certificates-tc_trust_class_2_ii-and-tc_trust_class_2_l1_ca_xi/">Upcoming expiration of certificates tc_trust_class_2_ii and tc_trust_class_2_L1_CA_XI</a> appeared first on <a href="https://sapbasisworld.com">SAP Basis World</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>SAP BTP &#8211; Root Certificate Replacement</title>
		<link>https://sapbasisworld.com/sap-btp-root-certificate-replacement/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 15 Jul 2025 16:26:00 +0000</pubDate>
				<category><![CDATA[SAP BTP]]></category>
		<category><![CDATA[#Basis]]></category>
		<category><![CDATA[#BTP]]></category>
		<guid isPermaLink="false">https://sapbasisworld.com/?p=3292</guid>

					<description><![CDATA[<p>SAP is switching to the &#8220;DigiCert TLS RSA4096 Root G5&#8221; and “DigiCert Global Root G3” Public Key Infrastructures (PKI). Unfortunately, these root certificates are only available in the JDK trust store of relatively new JDK versions so that the version, which is used for running Cloud Connector, is very likely lacking trust to the G5 [&#8230;]</p>
<p>The post <a href="https://sapbasisworld.com/sap-btp-root-certificate-replacement/">SAP BTP &#8211; Root Certificate Replacement</a> appeared first on <a href="https://sapbasisworld.com">SAP Basis World</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>How to check whether XSA get installed on HANA system</title>
		<link>https://sapbasisworld.com/how-to-check-whether-xsa-get-installed-on-hana-system/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 08 Jun 2025 17:40:13 +0000</pubDate>
				<category><![CDATA[HANA]]></category>
		<category><![CDATA[#Basis]]></category>
		<category><![CDATA[#Hana]]></category>
		<category><![CDATA[#XSA]]></category>
		<guid isPermaLink="false">https://sapbasisworld.com/?p=3276</guid>

					<description><![CDATA[<p>Solution If XSA is started, use below steps to check whether XSA is installed: If hdbxscontroller, hdbxsexecagent and hdbxsuaaserver&#160;are listed then XSA is installed.By default XS Classic (XSC) is installed in HANA system. In some system&#160;hdbxsengine is listed for XSC, in some system the XSC is embedded thus no hdbxsengine can be seen at OS [&#8230;]</p>
<p>The post <a href="https://sapbasisworld.com/how-to-check-whether-xsa-get-installed-on-hana-system/">How to check whether XSA get installed on HANA system</a> appeared first on <a href="https://sapbasisworld.com">SAP Basis World</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Hana Cockpit &#8211; how to check installed coponent version</title>
		<link>https://sapbasisworld.com/hana-cockpit-how-to-check-installed-coponent-version/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 08 Jun 2025 17:35:03 +0000</pubDate>
				<category><![CDATA[HANA]]></category>
		<category><![CDATA[#Basis]]></category>
		<category><![CDATA[#Cockpit]]></category>
		<category><![CDATA[#Hana]]></category>
		<guid isPermaLink="false">https://sapbasisworld.com/?p=3271</guid>

					<description><![CDATA[<p>Below, You&#8217;ll find short instructions on how to check the version of the installed component in Hana Cockpit from the console. sidadm@hostname:/usr/sap/SID/HDB96&#62; xs loginAPI_URL: https://hostname:39630USERNAME&#62; cockpit_adminPASSWORD&#62;Authenticating...ORG: HANACockpitSPACE: SAPAPI endpoint: https://hostname:39630 (API version: 1)User: cockpit_adminOrg: HANACockpitSpace: SAPsidadm@hostname:/usr/sap/SID/HDB96&#62; xs versionClient version: xs v1.2.3.240612140739Server version information: name = XS Controller support = http://service.sap.com/message build = v1.2.3.240612140739 version = [&#8230;]</p>
<p>The post <a href="https://sapbasisworld.com/hana-cockpit-how-to-check-installed-coponent-version/">Hana Cockpit &#8211; how to check installed coponent version</a> appeared first on <a href="https://sapbasisworld.com">SAP Basis World</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>HANA Studio/Eclipse error: Server not compatible</title>
		<link>https://sapbasisworld.com/hana-studio-eclipse-error-server-not-compatible/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 27 May 2025 15:38:00 +0000</pubDate>
				<category><![CDATA[HANA]]></category>
		<category><![CDATA[#Basis]]></category>
		<category><![CDATA[#Eclipse]]></category>
		<category><![CDATA[#Hana]]></category>
		<category><![CDATA[#Studio]]></category>
		<guid isPermaLink="false">https://sapbasisworld.com/?p=3267</guid>

					<description><![CDATA[<p>While trying to access content in HANA Studio or Eclipse development perspective, the error &#8216;Server not compatible&#8217; is being displayed. Solution</p>
<p>The post <a href="https://sapbasisworld.com/hana-studio-eclipse-error-server-not-compatible/">HANA Studio/Eclipse error: Server not compatible</a> appeared first on <a href="https://sapbasisworld.com">SAP Basis World</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>SAP Security Notes Summary – May 2025</title>
		<link>https://sapbasisworld.com/sap-security-notes-summary-may-2025/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 18 May 2025 19:14:10 +0000</pubDate>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[#Basis]]></category>
		<category><![CDATA[#security]]></category>
		<guid isPermaLink="false">https://sapbasisworld.com/?p=3262</guid>

					<description><![CDATA[<p>Traditionally, once a month I’ll publish a review of all SAP security notes and news that were released in a given month. SAP Security Notes contain SAP’s expert advice regarding important action items and patches to ensure the security of your systems. SAP Component Number Title CVSS Score  Released On EP-VC-INF 3604119 [CVE-2025-42999] Insecure Deserialization [&#8230;]</p>
<p>The post <a href="https://sapbasisworld.com/sap-security-notes-summary-may-2025/">SAP Security Notes Summary – May 2025</a> appeared first on <a href="https://sapbasisworld.com">SAP Basis World</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>System setting does not allow changes to be made to object NOTE &#8220;Note Number&#8221;</title>
		<link>https://sapbasisworld.com/system-setting-does-not-allow-changes-to-be-made-to-object-note-note-number/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 18 May 2025 18:59:39 +0000</pubDate>
				<category><![CDATA[Admin]]></category>
		<category><![CDATA[#Basis]]></category>
		<category><![CDATA[#notes]]></category>
		<guid isPermaLink="false">https://sapbasisworld.com/?p=3253</guid>

					<description><![CDATA[<p>In transaction SNOTE I was unable to Download SAP Note. I received below error: Solution How to find a namespace: and here Code Changes. The namespace is /SLOAP</p>
<p>The post <a href="https://sapbasisworld.com/system-setting-does-not-allow-changes-to-be-made-to-object-note-note-number/">System setting does not allow changes to be made to object NOTE &#8220;Note Number&#8221;</a> appeared first on <a href="https://sapbasisworld.com">SAP Basis World</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>SAP PO &#8211; ID21108: Invalid PBE algorithm parameters</title>
		<link>https://sapbasisworld.com/sap-po-id21108-invalid-pbe-algorithm-parameters/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Sun, 18 May 2025 18:37:57 +0000</pubDate>
				<category><![CDATA[PO]]></category>
		<category><![CDATA[#Basis]]></category>
		<category><![CDATA[#Certificate]]></category>
		<category><![CDATA[#PO]]></category>
		<guid isPermaLink="false">https://sapbasisworld.com/?p=3231</guid>

					<description><![CDATA[<p>Last time I generated p12 certificate, and next I tried to import it using Key Storage. I received an error like on the below screen&#8230; The problem is because cert is generated with algorithms that are not supported by SAP JVM 8 and my IAIK library version built-in the AS Java is too low. The fix [&#8230;]</p>
<p>The post <a href="https://sapbasisworld.com/sap-po-id21108-invalid-pbe-algorithm-parameters/">SAP PO &#8211; ID21108: Invalid PBE algorithm parameters</a> appeared first on <a href="https://sapbasisworld.com">SAP Basis World</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>SAP Security Notes Summary – April 2025</title>
		<link>https://sapbasisworld.com/sap-security-notes-summary-april-2025/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Mon, 28 Apr 2025 16:04:00 +0000</pubDate>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[#Basis]]></category>
		<category><![CDATA[#security]]></category>
		<guid isPermaLink="false">https://sapbasisworld.com/?p=3248</guid>

					<description><![CDATA[<p>Traditionally once a month I’ll publish a review of all SAP security notes and news that were released in a given month. SAP Security Notes contain SAP’s expert advice regarding important action items and patches to ensure the security of your systems. SAP Component Number Title CVSS Score  Released On EP-VC-INF 3594142 [CVE-2025-31324] Missing Authorization [&#8230;]</p>
<p>The post <a href="https://sapbasisworld.com/sap-security-notes-summary-april-2025/">SAP Security Notes Summary – April 2025</a> appeared first on <a href="https://sapbasisworld.com">SAP Basis World</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
