Update from SAP DITA CMS (squashed):

commit 2c8af51bca6e36c4568aa25ec2c2e5f794009152 Author: REDACTED Date: Wed Mar 20 13:37:05 2024 +0000 Update from SAP DITA CMS 2024-03-20 13:37:04 Project: dita-all/yyw1670851768207 Project map: 7c4b3cee0296494b992ad6e7db79b26a.ditamap Language: en-US commit 2e73e6166e45072a2e975bb458952922074da5bc Author: REDACTED Date: Wed Mar 20 10:58:48 2024 +0000 Update from SAP DITA CMS 2024-03-20 10:58:48 Project: dita-all/yyw1670851768207 Project map: 7c4b3cee0296494b992ad6e7db79b26a.ditamap Language: en-US commit 8229d0b2f75565faecda59208f52b93a8d960780 Author: REDACTED Date: Tue Mar 19 15:39:35 2024 +0000 Update from SAP DITA CMS 2024-03-19 15:39:35 Project: dita-all/yyw1670851768207 Project map: 7c4b3cee0296494b992ad6e7db79b26a.ditamap Language: en-US commit 09836d289ab1815dec3bb22c8734d796ca94d6fe Author: REDACTED Date: Tue Mar 19 13:30:43 2024 +0000 Update from SAP DITA CMS 2024-03-19 13:30:43 ################################################## [Remaining squash message was removed before commit...]
SAP-docs · Mar 20, 2024 · 2d47617 · 2d47617
1 parent 248805c
commit 2d47617
Show file tree

Hide file tree

Showing 9 changed files with 152 additions and 32 deletions.
diff --git a/docs/20-whats-new/what-s-new-for-sap-task-center-1bcdd45.md b/docs/20-whats-new/what-s-new-for-sap-task-center-1bcdd45.md
@@ -84,6 +84,70 @@ SAP Task Center
 
 
 
+</td>
+<td valign="top">
+
+Pushing SAP S/4HANA and SAP S/4HANA Cloud, private edition Tasks Enabled
+
+</td>
+<td valign="top">
+
+You can now enable task updates to be pushed from SAP S/4HANA or SAP S/4HANA Cloud, private edition. For more information, see the *Prerequisites* section and *tc.clientId* in [Connect SAP S/4HANA and SAP Task Center](../40-administration/connect-sap-s-4hana-and-sap-task-center-143af9b.md) and [Connect SAP S/4HANA Cloud, private edition and SAP Task Center](../40-administration/connect-sap-s-4hana-cloud-private-edition-and-sap-task-center-50ce133.md).
+
+</td>
+<td valign="top">
+
+Info only
+
+</td>
+<td valign="top">
+
+
+
+</td>
+<td valign="top">
+
+New
+
+</td>
+<td valign="top">
+
+Technology
+
+</td>
+<td valign="top">
+
+Not applicable
+
+</td>
+<td valign="top">
+
+
+
+</td>
+<td valign="top">
+
+2024-03-20
+
+</td>
+<td valign="top">
+
+2024-03-20
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+SAP Task Center 
+
+</td>
+<td valign="top">
+
+-   Cloud Foundry
+
+
+
 </td>
 <td valign="top">
 

diff --git a/docs/40-administration/connect-sap-s-4hana-and-sap-task-center-143af9b.md b/docs/40-administration/connect-sap-s-4hana-and-sap-task-center-143af9b.md
@@ -27,7 +27,14 @@ Find information about the destination configuration that needs to be done for S
     -   *Virtual Host* and *Virtual Port* from step *Configure access control in the Cloud Connector for your SAP S/4HANA back-end system*
 
 
--   You have performed the steps in [SAP Task Center Integration](https://help.sap.com/viewer/0f18dddf28764f5b807ecd80549044cc/latest/en-US/1da230b82a984cda85d0041e13060a87.html) and have a user name and password for granting access to the task pull service, as described in *Create Service User for Task Pull Service*.
+-   Create a dedicated service instance for SAP Task Center in the Cloud Foundry subaccount, where your initial SAP Task Center instance was created. This enables task updates to be pushed from your ABAP system. Follow the steps in [Create a Service Instance Using the SAP BTP Cockpit](https://help.sap.com/docs/TASK_CENTER/08cbda59b4954e93abb2ec85f1db399d/dc9af9fd363b4e989af6ff2f19548d32.html?version=Cloud) and create a service key for the service instance. Open the JSON file of the service key and get the following values:
+
+    -   *endpoints* \> *inbox\_rest\_url*
+    -   *uaa* \> *url*
+    -   *uaa* \> *clientid*
+    -   *uaa* \> *clientsecret*
+
+-   You have performed the steps in [Integrating SAP Task Center](https://help.sap.com/viewer/0f18dddf28764f5b807ecd80549044cc/latest/en-US/1da230b82a984cda85d0041e13060a87.html) and have a user name and password for granting access to the task pull service, as described in *Create Service User for Task Pull Service*.
 
     Use the prepared SAP Cloud Connector for the step *Tunnel the request using, for example, the Cloud Connector* in [Configuring SAP Task Center Integration](https://help.sap.com/viewer/0f18dddf28764f5b807ecd80549044cc/latest/en-US/5117f21ef28f4e698d99fe3fdbc1be2a.html).
 
@@ -294,6 +301,30 @@ Find information about the destination configuration that needs to be done for S
     <tr>
     <td valign="top">
 
+    *tc.clientId*
+
+    </td>
+    <td valign="top">
+
+    This property is used to enable task updates to be pushed from SAP S/4HANA.
+
+    The value of this property is the value of the *uaa* \> *clientid* from the service key of the new service instance \(see *Prerequisites*\).
+
+    > ### Note:  
+    > Set this property only when you have completed *Integrating SAP Task Center* from the *Prerequisites* section. If you haven't completed this step, you might not be able to receive tasks from SAP S/4HANA.
+
+
+
+    </td>
+    <td valign="top">
+
+    **Value** of *clientid*
+
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
     *tc.notifications.enabled*
 
     </td>

diff --git a/...ration/connect-sap-s-4hana-cloud-private-edition-and-sap-task-center-50ce133.md b/...ration/connect-sap-s-4hana-cloud-private-edition-and-sap-task-center-50ce133.md
@@ -24,7 +24,14 @@ Find information about the destination configuration that needs to be done for S
     -   *Virtual Host* and *Virtual Port* from step *Configure access control in the Cloud Connector for your SAP S/4HANA back-end system*
 
 
--   You have performed the steps in [SAP Task Center Integration](https://help.sap.com/viewer/0f18dddf28764f5b807ecd80549044cc/latest/en-US/1da230b82a984cda85d0041e13060a87.html) and have a user name and password for granting access to the task pull service, as described in [Create Service User for Task Pull Service](https://help.sap.com/viewer/0f18dddf28764f5b807ecd80549044cc/latest/en-US/229c5a1f659341efa2bb6205159d6209.html).
+-   Create a dedicated service instance for SAP Task Center in the Cloud Foundry subaccount, where your initial SAP Task Center instance was created. This enables task updates to be pushed from your ABAP system. Follow the steps in [Create a Service Instance Using the SAP BTP Cockpit](https://help.sap.com/docs/TASK_CENTER/08cbda59b4954e93abb2ec85f1db399d/dc9af9fd363b4e989af6ff2f19548d32.html?version=Cloud) and create a service key for the service instance. Open the JSON file of the service key and get the following values:
+
+    -   *endpoints* \> *inbox\_rest\_url*
+    -   *uaa* \> *url*
+    -   *uaa* \> *clientid*
+    -   *uaa* \> *clientsecret*
+
+-   You have performed the steps in [Integrating SAP Task Center](https://help.sap.com/viewer/0f18dddf28764f5b807ecd80549044cc/latest/en-US/1da230b82a984cda85d0041e13060a87.html) and have a user name and password for granting access to the task pull service, as described in *Configuring SAP Task Center Integration*.
 
     Use the SAP Cloud Connector from the previous prerequisite for the step *Tunnel the request using, for example, the Cloud Connector* in [Configuring SAP Task Center Integration](https://help.sap.com/viewer/0f18dddf28764f5b807ecd80549044cc/latest/en-US/5117f21ef28f4e698d99fe3fdbc1be2a.html).
 
@@ -291,6 +298,30 @@ Find information about the destination configuration that needs to be done for S
     <tr>
     <td valign="top">
 
+    *tc.clientId*
+
+    </td>
+    <td valign="top">
+
+    This property is used to enable task updates to be pushed from SAP S/4HANA Cloud, private edition.
+
+    The value of this property is the value of the *uaa* \> *clientid* from the service key of the new service instance \(see *Prerequisites*\).
+
+    > ### Note:  
+    > Set this property only when you have completed *Integrating SAP Task Center* from the *Prerequisites* section. If you haven't completed this step, you might not be able to receive tasks from SAP S/4HANA Cloud, private edition.
+
+
+
+    </td>
+    <td valign="top">
+
+    **Value** of *clientid*
+
+    </td>
+    </tr>
+    <tr>
+    <td valign="top">
+
     *tc.notifications.enabled*
 
     </td>

diff --git a/docs/40-administration/monitoring-9b30be7.md b/docs/40-administration/monitoring-9b30be7.md
@@ -5,30 +5,6 @@
 Once you create a destination configuration to connect SAP Task Center to a task provider application, SAP Task Center creates a connector internally for this configuration.
 
 
-<table>
-<tr>
-<th valign="top">
-
-Content
-
-</th>
-</tr>
-<tr>
-<td valign="top">
-
-[Task Center Administration App](monitoring-9b30be7.md#loio9b30be76f14f48c5a72dd7ed7e9babe0__section_AdminApp)
-
-[Connector Status API](monitoring-9b30be7.md#loio9b30be76f14f48c5a72dd7ed7e9babe0__section_ConnectorStatusAPI)
-
-[Service Status API](monitoring-9b30be7.md#loio9b30be76f14f48c5a72dd7ed7e9babe0__section_ServiceStatusAPI)
-
-[Integration with SAP Alert Notification Service for SAP BTP](monitoring-9b30be7.md#loio9b30be76f14f48c5a72dd7ed7e9babe0__section_IntegrationWithAlert)
-
-</td>
-</tr>
-</table>
-
-
 
 For this new configuration, SAP Task Center creates the following background connector job types:
 

diff --git a/...rk-with-sap-advanced-financial-closing-tasks-from-a-local-subaccount-e28e2af.md b/...rk-with-sap-advanced-financial-closing-tasks-from-a-local-subaccount-e28e2af.md
@@ -122,7 +122,7 @@ Follow the procedure below to complete the setup and receive tasks from an SAP A
     </td>
     <td valign="top">
 
-    Add the *endpoints \> task-center* value from the *Prerequisites* in [Connect SAP Advanced Financial Closing and SAP Task Center](connect-sap-advanced-financial-closing-and-sap-task-center-2873c51.md) and append `/api` to the URL.
+    Add the *endpoints \> task-center* value from the *Prerequisites* in [Connect SAP Advanced Financial Closing and SAP Task Center](connect-sap-advanced-financial-closing-and-sap-task-center-2873c51.md) and remove `/task-provider/v2` from the URL.
 
     > ### Note:  
     > If you change the *URL* of an already configured destination, for which there are stored tasks in the task cache, the tasks in it will be repopulated.

diff --git a/...k-with-sap-advanced-financial-closing-tasks-from-a-remote-subaccount-09cee80.md b/...k-with-sap-advanced-financial-closing-tasks-from-a-remote-subaccount-09cee80.md
@@ -137,7 +137,7 @@ To work with tasks coming from an SAP Advanced Financial Closing subaccount, you
     </td>
     <td valign="top">
 
-    Add the *endpoints \> task-center* value from the *Prerequisites* in [Connect SAP Advanced Financial Closing and SAP Task Center](connect-sap-advanced-financial-closing-and-sap-task-center-2873c51.md) and append `/api` to the URL.
+    Add the *endpoints \> task-center* value from the *Prerequisites* in [Connect SAP Advanced Financial Closing and SAP Task Center](connect-sap-advanced-financial-closing-and-sap-task-center-2873c51.md) and remove `/task-provider/v2` from the URL.
 
     > ### Note:  
     > If you change the *URL* of an already configured destination, for which there are stored tasks in the task cache, the tasks in it will be repopulated.

diff --git a/...ork-with-sap-build-process-automation-tasks-from-a-remote-subaccount-1d3e69d.md b/...ork-with-sap-build-process-automation-tasks-from-a-remote-subaccount-1d3e69d.md
@@ -2,19 +2,19 @@
 
 # Work with SAP Build Process Automation Tasks from a Remote Subaccount
 
-Follow the procedure below to complete the setup and receive tasks from SAP Build Process Automation instance, which is in a different \(remote\) subaccount than the SAP Task Center subaccount.
+Follow the described procedure to complete the setup and receive tasks from SAP Build Process Automation instance, which is in a different \(remote\) subaccount than the SAP Task Center subaccount.
 
 
 
 <a name="loio1d3e69d3bcd044b892e7c6e145de19e5__prereq_mrn_nvp_qjb"/>
 
 ## Prerequisites
 
--   You have a subaccount with an SAP Task Center service instance in the Cloud Foundry environment. In the procedure below we refer to this account as the 'SAP Task Center subaccount'.
+-   You have a subaccount with an SAP Task Center service instance in the Cloud Foundry environment. In the following procedure we refer to this account as the 'SAP Task Center subaccount'.
 
--   You have created a second subaccount with an SAP Build Process Automation instance. In the procedure below we refer to this account as the 'SAP Build Process Automation subaccount'. This subaccount is configured to authenticate users via the same Identity Authentication server as the SAP Task Center subaccount.
+-   You have created a second subaccount with an SAP Build Process Automation instance. In the following procedure we refer to this account as the 'SAP Build Process Automation subaccount'. This subaccount is configured to authenticate users via the same Identity Authentication server as the SAP Task Center subaccount.
 
--   You have performed the steps in [Set Up Principal Propagation Between Subaccounts](https://help.sap.com/docs/PROCESS_AUTOMATION/a331c4ef0a9d48a89c779fd449c022e7/644357977e414211a730dab2e3094585.html).
+-   You have performed the steps in [Set Up Principal Propagation Between Subaccounts](https://help.sap.com/docs/build-process-automation/sap-build-process-automation/set-up-principal-propagation-between-subaccounts-87df988656ad4190900c209b1d1780b0).
 
 
 > ### Note:  

diff --git a/docs/60-security/credentials-rotation-8080abf.md b/docs/60-security/credentials-rotation-8080abf.md
@@ -24,6 +24,14 @@ By creating a new service key, only the `clientsecret` changes and the other par
 
 
 
+### Rotate Credentials for SAP S/4HANA
+
+1.  Create a new service key for the existing service instance, which you created in step *Create a dedicated service instance for SAP Task Center in the Cloud Foundry subaccount, where your initial SAP Task Center instance was created* in [Connect SAP S/4HANA and SAP Task Center](../40-administration/connect-sap-s-4hana-and-sap-task-center-143af9b.md).
+
+2.  Copy the new `clientsecret` and update it in the *Maintain OAuth 2.0 Client for Task Push Service* step in your SAP S/4HANA system. For more information, see *Execute the activities under SAP Task Center Integration* in [Configuring SAP Task Center Integration](https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/0f18dddf28764f5b807ecd80549044cc/5117f21ef28f4e698d99fe3fdbc1be2a.html?version=latest).
+
+
+
 ### Rotate Credentials for SAP S/4HANA Cloud, public edition
 
 1.  Create a new service key for the existing service instance, which you created in step *Create a dedicated service instance for SAP Task Center in the Cloud Foundry subaccount, where your initial SAP Task Center instance was created* in [Connect SAP S/4HANA Cloud, public edition and SAP Task Center](../40-administration/connect-sap-s-4hana-cloud-public-edition-and-sap-task-center-0aff1b4.md).
@@ -32,6 +40,14 @@ By creating a new service key, only the `clientsecret` changes and the other par
 
 
 
+### Rotate Credentials for SAP S/4HANA Cloud, private edition
+
+1.  Create a new service key for the existing service instance, which you created in step *Create a dedicated service instance for SAP Task Center in the Cloud Foundry subaccount, where your initial SAP Task Center instance was created* in [Connect SAP S/4HANA Cloud, private edition and SAP Task Center](../40-administration/connect-sap-s-4hana-cloud-private-edition-and-sap-task-center-50ce133.md).
+
+2.  Copy the new `clientsecret` and update it in the *Maintain OAuth 2.0 Client for Task Push Service* step in your SAP S/4HANA system. For more information, see *Execute the activities under SAP Task Center Integration* in [Configuring SAP Task Center Integration](https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/0f18dddf28764f5b807ecd80549044cc/5117f21ef28f4e698d99fe3fdbc1be2a.html?version=latest).
+
+
+
 ### Rotate Credentials for SAP SuccessFactors
 
 1.  Create a new service key for the existing service instance, which you created in step *Create a new service instance to enable task updates to be pushed from SAP SuccessFactors* in [Creating the Primary Destination with the Technical User](../40-administration/creating-the-primary-destination-with-the-technical-user-dc5407b.md).

diff --git a/docs/60-security/security-2ab2142.md b/docs/60-security/security-2ab2142.md
@@ -17,5 +17,7 @@ This guide provides an overview of the security-relevant information that applie
 
 [Auditing and Logging Information](auditing-and-logging-information-09dcab2.md "Here you can find a list of the security events that are logged by the SAP Task Center service.")
 
+[Credentials Rotation](credentials-rotation-8080abf.md "Change your credentials at regular intervals to ensure a higher level of security.")
+
 [Security Guide for SAP Business Technology Platform \(SAP BTP\)](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/e129aa20c78c4a9fb379b9803b02e5f6.html)