Update from SAP DITA CMS (squashed):

ditaccms-bot · ditaccms-bot · commit a6237d371433 · 2025-09-18T07:34:09.000Z
commit 3e9432c9ed73a9a9c3833dc7bffd89066ac6a521
Author: REDACTED
Date:   Thu Sep 18 06:17:10 2025 +0000

    Update from SAP DITA CMS 2025-09-18 06:17:10

    Project: dita-all/slu1713332208086
    Project map: 6d6c94be23b547a19d534f13dd6d51a7.ditamap
    Output: loiocc0ab4c7365e43bbbee9eae27deb32da
    Language: en-US
    Builddable map: 446771d4951c4a6988252269c21d94ba.ditamap

commit 6ecf6092edf60880d69c2a0d4b7e4523f0750fe9
Author: REDACTED
Date:   Thu Sep 18 05:59:01 2025 +0000

    Update from SAP DITA CMS 2025-09-18 05:59:01

    Project: dita-all/slu1713332208086
    Project map: 6d6c94be23b547a19d534f13dd6d51a7.ditamap
    Output: loiocc0ab4c7365e43bbbee9eae27deb32da
    Language: en-US
    Builddable map: 446771d4951c4a6988252269c21d94ba.ditamap

commit 99da5b28320970e340f3b21e4d32dad3b4c56f67
Author: REDACTED
Date:   Thu Sep 18 05:44:16 2025 +0000

    Update from SAP DITA CMS 2025-09-18 05:44:16

    Project: dita-all/slu1713332208086
    Project map: 6d6c94be23b547a19d534f13dd6d51a7.ditamap

##################################################
[Remaining squash message was removed before commit...]
diff --git a/docs/ISuite/40-RemoteSystems/images/Inbound_SFTP_26595de.png b/docs/ISuite/40-RemoteSystems/images/Inbound_SFTP_26595de.png
diff --git a/docs/ISuite/40-RemoteSystems/images/Inbound_SFTP_959f228.png b/docs/ISuite/40-RemoteSystems/images/Inbound_SFTP_959f228.png
diff --git a/docs/ISuite/40-RemoteSystems/inbound-sftp-with-public-key-authentication-97e2baa.md b/docs/ISuite/40-RemoteSystems/inbound-sftp-with-public-key-authentication-97e2baa.md
@@ -84,7 +84,7 @@ A tenant can connect as an SFTP client to an SFTP server \(the latter either hos
 
 The following figure shows the basic setup of components used for SFTP for inbound communication \(when the data flow is directed from an SFTP server to the tenant\).
 
-![](images/Inbound_SFTP_26595de.png)
+![](images/Inbound_SFTP_959f228.png)
 
 To specify the technical details of the message flow from the SFTP sender to the tenant \(SFTP client\), a **sender SFTP adapter** has to be configured for the related integration flow.
 
diff --git a/docs/ISuite/50-Development/define-edi-to-xml-converter-6a3d12b.md b/docs/ISuite/50-Development/define-edi-to-xml-converter-6a3d12b.md
@@ -32,7 +32,6 @@ Use this procedure to convert EDIFACT, ODETTE, TRADACOMS, and ASC-X12 format int
 > -   EDI to XML converter version 1.6 and above supports LS/LE segments.
 > -   Cloud Integration does not support repetition characters. Repetition character is a single character which separates the instances of a repeating data element. For example, *^* \(caret sign\) is a repetition character.
 > -   For X12 format, EDI to XML converter v1.8.0 and v2.2.0 onwards support same group name with different definition in XSD.
-> -   For X12 format, the Target Root Element is available for EDI to XML converter version 2.7 and above.
 
 
 
@@ -330,6 +329,8 @@ Use this procedure to convert EDIFACT, ODETTE, TRADACOMS, and ASC-X12 format int
     *Target Root Element*
 
     \(only available if *Exclude Interchange and Group envelopes* is not selected\)
+
+    \(Available from version 2.7 and above\)
     
     </td>
     <td valign="top">
diff --git a/docs/ISuite/50-Development/external-logging-ad719c1.md b/docs/ISuite/50-Development/external-logging-ad719c1.md
@@ -6,6 +6,9 @@ The external logging feature enables customers to send message processing logs t
 
 The major customer use cases for the external logging feature are the integration into existing monitoring solutions in Splunk, or the consolidation of logs of multiple tenants. You can use it for high-throughput scenarios \(currently limited by our systems and databases\) and high volume queries. And it also suitable for advanced analysis, as well as for correlation with business data and long-term archiving.
 
+> ### Recommendation:  
+> Avoid transmitting message payloads or other large data volumes to an external logging system through custom headers. This may affect the performance of the data replication to the external logging system.
+
 If you've already set up Splunk as your external logging destination, you can enable the external logging feature.
 
 To activate external logging in the Cloud Foundry Environment on your tenant, you have to fulfill the following prerequisites:
diff --git a/docs/ISuite/50-Development/handling-prepackaged-sap-to-sap-integration-content-2dc4d87.md b/docs/ISuite/50-Development/handling-prepackaged-sap-to-sap-integration-content-2dc4d87.md
@@ -4,7 +4,7 @@
 
 Learn the SAP recommendations for reusing SAP-to-SAP prepackaged content within and across tenants.
 
-If you deploy and process an integration flow from a predefined content package, it's metered. You can edit such prepackaged content or use them as is. For more information on the metering metrics, see SAP Note [2942344](https://launchpad.support.sap.com/#/notes/2942344).
+If you deploy and process an integration flow from a predefined content package, it's metered. You can edit such prepackaged content or use them as is. For more information on how tenant is defined and metered, see SAP Note [3654389](https://launchpad.support.sap.com/#/notes/3654389).
 
 
 
diff --git a/docs/ISuite/50-Development/message-mapping-459ccdf.md b/docs/ISuite/50-Development/message-mapping-459ccdf.md
@@ -19,6 +19,8 @@ Let us consider the example of replicating employee details from system A to sys
 
 In the same scenario, let us assume that the date of birth in system A is in YYYY-MM-DD format. You want to change the format to DD-MM-YYYY, the format in system B. In this case, you can use a mapping function that transforms the data into the format that you want, which in this case is DD-MM-YYYY.
 
+For more details on using 'AND' standard fucntion see, [0003653876](https://me.sap.com/notes/0003653876)
+
 ![](images/mapping_function_8ea50e9.png)
 
 The mapping editor provides some standard functions like *Arithmetic*, *Boolean*, *Constants*, *Conversions*, and *Date*.
diff --git a/docs/ISuite/50-Development/message-mapping-ec59f97.md b/docs/ISuite/50-Development/message-mapping-ec59f97.md
@@ -12,3 +12,8 @@ To apply this design guideline, consider the following rules:
 
 [Use a Message Mapping to Map XML to JSON](use-a-message-mapping-to-map-xml-to-json-fb7c1df.md)
 
+**Related Information**  
+
+
+[SAP Note 0003653876](https://me.sap.com/notes/0003653876)
+
diff --git a/docs/ISuite/50-Development/monitor-apis-399b6c6.md b/docs/ISuite/50-Development/monitor-apis-399b6c6.md
@@ -123,6 +123,11 @@ The header area also provides certain functions:
 
     Allows you to download the API to your computer.
 
+    > ### Note:  
+    > Importing an API using the ZIP file downloaded from *Monitor* \> *Integrations and APIs* \> *Integration Content Details* is not supported. These ZIP files may contain runtime-specific or system-generated artifacts that are not intended for design-time import.
+    > 
+    > Always export APIs directly from *Design* by opening the content package, selecting the API artifact, and choosing *Export*. Avoid using the *Download* option under *Integration Content Details* for this purpose.
+
 
 Below the header, the following sections contain detailed information about the selected artifact:
 
diff --git a/docs/ISuite/50-Development/monitor-event-mesh-d975934.md b/docs/ISuite/50-Development/monitor-event-mesh-d975934.md
@@ -46,6 +46,9 @@ Choosing a particular queue will enable you to see the following usage informati
 -   Time Sent: Time the message was sent.
 -   Message size: The size of the message content, in bytes.
 -   Redelivered: Indicates if the message was redelivered or not.
+-   Delivery Count: The number of times a message has been delivered. Each time the message remains unacknowledged or unprocessed, the broker retries delivery. This count reflects the number of delivery attempts.
+-   Spool Time: The timestamp marking when the message was first stored in the queue. This indicates when the message began waiting in the spool before being consumed.
+-   Expiration: The timestamp marking when the message will expire in the queue. After this time, the message is no longer eligible for delivery and may be purged or sent to a DMQ.
 -   Destination: Destination of the message
 -   DMQ Eligible: Indicates whether the message is eligible for the Dead Message Queue \(DMQ\).
 
diff --git a/docs/ISuite/edge-integration-cell-runtime-scope-144c64a.md b/docs/ISuite/edge-integration-cell-runtime-scope-144c64a.md
@@ -34,7 +34,103 @@ Integration content
 
 2 GB
 
-Refer to the SAP Community blog: [Content Size Limits](https://blogs.sap.com/2020/08/02/cloud-integration-content-size-limits/)
+For more information, refer to the SAP Community blog: [Content Size Limits](https://blogs.sap.com/2020/08/02/cloud-integration-content-size-limits/)
+
+> ### Note:  
+> When the content size exceeds 250 MB, the metaspace increases accordingly. See the table below for more details:
+> 
+> 
+> <table>
+> <tr>
+> <th valign="top">
+> 
+> Content Size
+> 
+> </th>
+> <th valign="top">
+> 
+> Container Size
+> 
+> </th>
+> <th valign="top">
+> 
+> Metaspace
+> 
+> </th>
+> </tr>
+> <tr>
+> <td valign="top">
+> 
+> Up to 250 MB
+> 
+> </td>
+> <td valign="top">
+> 
+> 8 GB
+> 
+> </td>
+> <td valign="top">
+> 
+> 500 MB \(default\)
+> 
+> </td>
+> </tr>
+> <tr>
+> <td valign="top">
+> 
+> 250-500 MB
+> 
+> </td>
+> <td valign="top">
+> 
+> 12 GB
+> 
+> </td>
+> <td valign="top">
+> 
+> 750 MB
+> 
+> </td>
+> </tr>
+> <tr>
+> <td valign="top">
+> 
+> 500 MB- 1 GB
+> 
+> </td>
+> <td valign="top">
+> 
+> 16 GB
+> 
+> </td>
+> <td valign="top">
+> 
+> 1250 MB
+> 
+> </td>
+> </tr>
+> <tr>
+> <td valign="top">
+> 
+> 1-2 GB
+> 
+> </td>
+> <td valign="top">
+> 
+> 20 GB
+> 
+> </td>
+> <td valign="top">
+> 
+> 1750 MB
+> 
+> </td>
+> </tr>
+> </table>
+> 
+> Use the `JBP_CONFIG_JAVA_OPTS` parameter configuration to update the metaspace size. See: [Runtime Parameters](runtime-parameters-63c5276.md).
+
+
 
 </td>
 </tr>
diff --git a/docs/ISuite/known-limitations-of-migration-tooling-7a552d4.md b/docs/ISuite/known-limitations-of-migration-tooling-7a552d4.md
@@ -30,7 +30,7 @@ XML to CSV Converter
 
 For the patterns that support CSV to XML or XML to CSV converter, the following limitations apply:
 
--   XSD schema files from the source integration object aren't migrated. As an integration developer, you must manually download the schema files from the Enterprise Services Repository of SAP Process Orchestration and upload the same as resources in the integration flow. Then, configure the converter flow step before you deploy the integration flow.
+-   XSD schema files from the source integration object aren't migrated. As an integration developer, you must manually download the schema files from the Enterprise Services Repository of SAP Process Integration/SAP Process Orchestration and upload the same as resources in the integration flow. Then, configure the converter flow step before you deploy the integration flow.
 
 -   Field Fixed-Length separator isn't supported. You can't directly migrate field fixed length file-based integration objects.
 
@@ -47,7 +47,7 @@ File-based adapters with encryption/decryption
 </td>
 <td valign="top">
 
-For File-based adapter scenarios in Process Integration/Process Orchestration that require decryption, the migration tool does not automatically map the adapter module properties to the corresponding encryptor/decryptor step in the integration flow. You must manually add the PGP Encryptor/PGP Decryptor flow step in the migrated integration flow to maintain the same configuration as in the respective adapter's communication channel.
+For File-based adapter scenarios in SAP Process Integration/SAP Process Orchestration that require decryption, the migration tool does not automatically map the adapter module properties to the corresponding encryptor/decryptor step in the integration flow. You must manually add the PGP Encryptor/PGP Decryptor flow step in the migrated integration flow to maintain the same configuration as in the respective adapter's communication channel.
 
 </td>
 </tr>
@@ -59,7 +59,7 @@ SuccessFactors Adapter
 </td>
 <td valign="top">
 
-For integration scenarios in Process Integration/Process Orchestration that use SFSF adapter channels, the migration tool does not automatically map the SuccessFactors adapter in SAP Integration Suite. You must manually add it.
+For integration scenarios in SAP Process Integration/SAP Process Orchestration that use SFSF adapter channels, the migration tool does not automatically map the SuccessFactors adapter in SAP Integration Suite. You must manually add it.
 
 </td>
 </tr>
@@ -97,7 +97,7 @@ JDBC transaction handling
 </td>
 <td valign="top">
 
-The use of JDBC Sender scenarios, where data is selected and later updated within the same transaction, is not supported in SAP Cloud Integration. This behaviour is also not handled by the migration tool when moving from SAP PI.
+The use of JDBC Sender scenarios, where data is selected and later updated within the same transaction, is not supported in SAP Cloud Integration. This behaviour is also not handled by the migration tool when moving from SAP Process Integration/SAP Process Orchestration.
 
 Even if you try to replicate the logic using a Timer and Request-Reply pattern, there is the possibility that the records selected at the beginning may not match those updated at the end, potentially leading to data inconsistencies. To prevent inconsistent data or failed updates, a redesign is needed — typically involving stored procedures and intermediate status flags at the database layer.
 
diff --git a/docs/ISuite/patch-releases-for-cloud-integration-and-related-components-023a472.md b/docs/ISuite/patch-releases-for-cloud-integration-and-related-components-023a472.md
@@ -79,6 +79,159 @@ Patches for different components are associated with different major software ve
 
 
 
+<a name="loio023a4725bb734f86be8a5625abe54110__section_bwm_psr_pgc"/>
+
+## September 2025
+
+Software Increment: 2507
+
+****
+
+
+<table>
+<tr>
+<th valign="top">
+
+Technical Component
+
+</th>
+<th valign="top">
+
+Software Version
+
+</th>
+<th valign="top">
+
+Description
+
+</th>
+</tr>
+<tr>
+<td valign="top">
+
+Cloud Integration
+
+</td>
+<td valign="top">
+
+6.69.45
+
+</td>
+<td valign="top">
+
+This patch fixes the following issues:
+
+-   When the syntax version is null, the UI incorrectly displays "Release undefined." The UI now shows this field as empty.
+-   The patch addresses an internal dependency update to align with Jakarta-compliant libraries identified during DTS consumption. This change is internal and has no customer-facing impact. It doesn't affect performance, database, or memory.
+-   Basic Auth was failing for API Management capability + Integration Cell use cases due to credential store separation for Integration Cell specific scenarios. The patch fixes this by creating the key in the generic secure store.
+-   The patch addresses issues related to the Design Page during API Management capability and Integration Cell reactivation.
+
+
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Cloud Integration
+
+</td>
+<td valign="top">
+
+6.69.49
+
+</td>
+<td valign="top">
+
+This patch icludes the following items:
+
+-   JDBC adapter moved to a stable version.
+
+-   Enhancements related to load distribution.
+
+-   Updates related to Message Processing Log Attachment view on Monitor Message Processing screen.
+
+
+
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Cloud Integration
+
+</td>
+<td valign="top">
+
+8.33.18
+
+</td>
+<td valign="top">
+
+This patch icludes the following items:
+
+-   JDBC adapter moved to a stable version.
+
+-   Enhancements related to load distribution.
+
+
+
+
+</td>
+</tr>
+</table>
+
+
+
+<a name="loio023a4725bb734f86be8a5625abe54110__section_hhl_pqr_pgc"/>
+
+## September 2025
+
+Software Increment: 2506
+
+****
+
+
+<table>
+<tr>
+<th valign="top">
+
+Technical Component
+
+</th>
+<th valign="top">
+
+Software Version
+
+</th>
+<th valign="top">
+
+Description
+
+</th>
+</tr>
+<tr>
+<td valign="top">
+
+Cloud Integration
+
+</td>
+<td valign="top">
+
+6.68.26
+
+</td>
+<td valign="top">
+
+This patch fixes issues with Unicode characters parsing in extracted XML files.
+
+</td>
+</tr>
+</table>
+
+
+
 <a name="loio023a4725bb734f86be8a5625abe54110__section_epj_r1i_3fa"/>
 
 ## August 2025
diff --git a/docs/ISuite/what-is-sap-integration-suite-5cc6987.md b/docs/ISuite/what-is-sap-integration-suite-5cc6987.md
@@ -365,7 +365,7 @@ Check out the following resources:
 
 -   Get access to SAP Integration Suite community, Pricing models and all the technical resources, tutorials, blogs, and support you need: [Integration Platform as a Service](https://www.sap.com/products/integration-suite.html).
 
--   For more information on how usage information is recorded for billing and other cost assessments, see SAP Note [2942344](https://me.sap.com/notes/2942344).
+-   For more information on how a tenant is defined, usage information is recorded for billing and other cost assessments, see SAP Note [3654389](https://me.sap.com/notes/3654389).
 
 
 **Related Information**  

Original file line number	Diff line number	Diff line change
`@@ -4,7 +4,7 @@`
`4`	`4`
`5`	`5`	`Learn the SAP recommendations for reusing SAP-to-SAP prepackaged content within and across tenants.`
`6`	`6`
`7`		`-If you deploy and process an integration flow from a predefined content package, it's metered. You can edit such prepackaged content or use them as is. For more information on the metering metrics, see SAP Note [2942344](https://launchpad.support.sap.com/#/notes/2942344).`
	`7`	`+If you deploy and process an integration flow from a predefined content package, it's metered. You can edit such prepackaged content or use them as is. For more information on how tenant is defined and metered, see SAP Note [3654389](https://launchpad.support.sap.com/#/notes/3654389).`
`8`	`8`
`9`	`9`
`10`	`10`