Skip to content

Commit f833ac7

Browse files
committed
Update from SAP DITA CMS (squashed):
commit 8933eb21e0922a3a183eb565f2ba49a0a1f404ae Author: REDACTED Date: Tue Nov 26 16:34:56 2024 +0000 Update from SAP DITA CMS 2024-11-26 16:34:56 Project: dita-all/nih1586262997200 Project map: baa817af5a7c4aa798ad5d2792ae0111.ditamap Output: loio0f341afe0f5e4107ad982c53bfc412dc Language: en-US Builddable map: 6dd68ae2cfea4cdf8ba6b96497472829.ditamap commit c7163e67927afb7dd834c40eb5ae107866eb00a6 Author: REDACTED Date: Tue Nov 26 13:51:55 2024 +0000 Update from SAP DITA CMS 2024-11-26 13:51:55 Project: dita-all/nih1586262997200 Project map: baa817af5a7c4aa798ad5d2792ae0111.ditamap Output: loio0f341afe0f5e4107ad982c53bfc412dc Language: en-US Builddable map: 6dd68ae2cfea4cdf8ba6b96497472829.ditamap commit 61389e3fcbee1900e89829d11941f350582f13cd Author: REDACTED Date: Tue Nov 26 09:21:12 2024 +0000 Update from SAP DITA CMS 2024-11-26 09:21:12 Project: dita-all/nih1586262997200 Project map: baa817af5a7c4aa798ad5d2792ae0111.ditamap ################################################## [Remaining squash message was removed before commit...]
1 parent 65d566c commit f833ac7

12 files changed

+62
-34
lines changed

docs/01_required_setup/role-collections-e1915af.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
Role collections in SAP Cloud ALM are delivered predefined and ready to use.
66

7-
Each application role in SAP Cloud ALM represents a role collection in your SAP BTP subaccount, which in turn corresponds 1:1 to the respective role template \(with the exception of the *Cross Global Administrator* and the *User & Access Management Administrator*\). This means that you don't have to configure any role collections yourself. Instead, you can simply assign the relevant role collections to the users based on their tasks and requirements.
7+
Each application role in SAP Cloud ALM represents a role collection in your SAP BTP subaccount, which in turn corresponds 1:1 to the respective role template \(with the exception of the *Cross Global Administrator*, the *User & Access Management Administrator*, and the *Deployment Manager*\). This means that you don't have to configure any role collections yourself. Instead, you can simply assign the relevant role collections to the users based on their tasks and requirements.
88

99
Each application role contains all the necessary authorizations that are required for all tasks that belong to a certain business role, rather than being confined to a single task. For example, the role *Health Monitoring Administrator* also contains authorizations in apps other than *Health Monitoring* because someone in that role also needs to be able to configure events and set up notifications.
1010

@@ -533,7 +533,9 @@ Deploy transports into test and production systems
533533
</td>
534534
<td valign="top">
535535

536-
`imp_cdm_DeploymentManager`
536+
`imp_cdm_DeploymentManagerTest`
537+
538+
`imp_cdm_DeploymentManagerProd`
537539

538540
</td>
539541
</tr>

docs/02_integration_and_config_options/-b788f20.md

Lines changed: 0 additions & 4 deletions
This file was deleted.

docs/02_integration_and_config_options/integration-and-configuration-options-a4ea6fa.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,4 @@ In addition to manual testing, which is performed directly in SAP Cloud ALM, you
3030
- **[Enabling Service Delivery](enabling-service-delivery-a1b2494.md "An SAP service is usually delivered as part of a service contract like SAP MaxAttention,
3131
SAP ActiveAttention or SAP Enterprise Support.")**
3232
An SAP service is usually delivered as part of a service contract like SAP MaxAttention, SAP ActiveAttention or SAP Enterprise Support.
33-
- **[](-b788f20.md "")**
34-
3533

docs/02_integration_and_config_options/sap-cloud-transport-management-service-and-the-ci-cd-use-case-235276e.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ SAP Cloud Transport Management Service and the CI/CD Use Case
1515
![](images/Diagram_85f60ba.png)
1616

1717

18-
For the initial setup of SAP Continuous Integration and Delivery \(CI/CD\), see [Initial Setup](https://help.sap.com/docs/continuous-integration-and-delivery/sap-continuous-integration-and-delivery/initial-setup?version=Cloud)
18+
For the initial setup of SAP Continuous Integration and Delivery \(CI/CD\), see [Initial Setup](https://help.sap.com/docs/continuous-integration-and-delivery/sap-continuous-integration-and-delivery/initial-setup?version=Cloud).
1919

2020
To integrate CTMS into your CI/CD pipeline, see [Configure a Cloud Foundry Environment Job in Your Repository](https://help.sap.com/docs/continuous-integration-and-delivery/sap-continuous-integration-and-delivery/configure-sap-cloud-application-programming-model-job-in-your-repository?q=configure+sap+fiori+in+cloud+foundry+environment+job+in+your+repository&version=Cloud#release).
2121

docs/02_integration_and_config_options/sap-s-4hana-cloud-private-edition-and-on-premise-systems-5aa24f0.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,8 @@ Currently any kind of consistent Transport Management System \(TMS\) landscape i
4242
>
4343
> - Replacing or deleting the development systems isn't supported. The transports of replaced or deleted development systems are still available in the assign pop-up, feature,*Transport Analysis* app, and *Feature Traceability* app.
4444
>
45+
> - Manually deleted transports in the managed system are still available in the assign pop-up, feature, *Transport Analysis* app, and *Feature Traceability* app.
46+
>
4547
> - Switching on or off client-specific transport routes isn't supported.
4648
>
4749
> - We recommend avoiding manual import activities in CTS with transports managed by SAP Cloud ALM.

docs/02_integration_and_config_options/setting-up-the-managed-systems-21e0843.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Make sure that you fulfill the *Technical Prerequisites*, *Network Prerequisites
4343
>
4444
> - You can request user `CUST_TC` for client 000. This user is authorized to run the setup transaction.
4545
>
46-
> - User `BATCH_USER` can be specified as background user.
46+
> - `BATCH_USER` is always available in the managed system and doesn't expire. You can also specifiy it as background user.
4747
4848

4949

docs/administration-52d7d71.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,15 @@ Most of these tasks can be completed directly in SAP Cloud ALM. Others need to b
88

99
If you originally requested the provisioning of SAP Cloud ALM, you've received all required authorizations to work in these tools. If you didn't request SAP Cloud ALM, make sure that the required roles that are detailed in the **Prerequisites** sections of the following pages are assigned to you.
1010

11-
- **[Finding Your Systems on SAP for Me](finding-your-systems-on-sap-for-me-9d4aa2a.md "The Systems & Provisioning dashboard on SAP for Me is your one-stop
12-
place for all your active public cloud systems on SAP BTP.")**
11+
- **[Finding Your Systems on SAP for Me](finding-your-systems-on-sap-for-me-9d4aa2a.md "The Systems & Provisioning dashboard on SAP for Me is your
12+
one-stop place for all your active public cloud systems on SAP BTP.")**
1313
The *Systems & Provisioning* dashboard on SAP for Me is your one-stop place for all your active public cloud systems on SAP BTP.
1414
- **[Managing Users](managing-users-04a9231.md "After the initial onboarding of users during the required setup, other tasks may
1515
arise for the administration of users in SAP Cloud ALM.")**
1616
After the initial onboarding of users during the [required setup](01_required_setup/step-2-assign-roles-to-users-in-sap-cloud-alm-7304b17.md), other tasks may arise for the administration of users in SAP Cloud ALM.
17-
- **[Configuring Advanced Access](configuring-advanced-access-b7c1490.md "In addition to the role management options in the User Management app, with
18-
which you can give users the authorizations for certain tasks and to certain apps, you can
19-
also restrict access to certain objects.")**
17+
- **[Configuring Advanced Access Authorizations](configuring-advanced-access-authorizations-b7c1490.md "In addition to the role management options in the User Management
18+
app, with which you can give users the authorizations for certain tasks and to certain apps,
19+
you can also restrict access to certain objects.")**
2020
In addition to the role management options in the *User Management* app, with which you can give users the authorizations for certain tasks and to certain apps, you can also restrict access to certain objects.
2121
- **[Setting Up Email Notifications](setting-up-email-notifications-1d1fa37.md "To make sure that users are aware of tasks or monitoring events that require their
2222
attention, you can set up two different kinds of email notifications.")**
@@ -32,9 +32,9 @@ The integration between SAP Cloud ALM and several SAP cloud services is orchestr
3232
- **[Activating the SAP Audit Log Viewer Service](activating-the-sap-audit-log-viewer-service-59fd2a4.md "By using the SAP Audit Log Viewer service for SAP BTP, you can view the
3333
audit logs to track the end user activity in SAP Cloud ALM.")**
3434
By using the SAP Audit Log Viewer service for SAP BTP, you can view the audit logs to track the end user activity in SAP Cloud ALM.
35-
- **[Terminating Your Account](terminating-your-account-219d7d0.md "When your SAP contracts expire, your SAP Cloud ALM tenant and all related data will be
36-
terminated after a grace period has passed.")**
37-
When your SAP contracts expire, your SAP Cloud ALM tenant and all related data will be terminated after a grace period has passed.
35+
- **[Closing Your Account](closing-your-account-219d7d0.md "When your SAP contracts expire, your SAP Cloud ALM tenant and all related data will be
36+
deleted after a grace period has passed.")**
37+
When your SAP contracts expire, your SAP Cloud ALM tenant and all related data will be deleted after a grace period has passed.
3838

3939
**Related Information**
4040

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
<!-- loio219d7d0c369c4c7bb68860e7710f25b3 -->
22

3-
# Terminating Your Account
3+
# Closing Your Account
44

5-
When your SAP contracts expire, your SAP Cloud ALM tenant and all related data will be terminated after a grace period has passed.
5+
When your SAP contracts expire, your SAP Cloud ALM tenant and all related data will be deleted after a grace period has passed.
66

77
> ### Tip:
88
> You can always check the contract end date on the [Provisioning](https://me.sap.com/systemsprovisioning/provisioning) dashboard on SAP for Me, in the column *Contract Start*.
99
10-
The termination process starts with a notice period. The requester of the global account that contains your SAP Cloud ALM entitlement receives an email about the expiring contract, and a warning banner is displayed for the global account in the SAP BTP cockpit. If this happens, you can request an export of your data by opening an incident on component SV-CLM-INF-ONB, if required.
10+
The closing process starts with a notice period. The requester of the global account that contains your SAP Cloud ALM entitlement receives an email about the expiring contract, and a warning banner is displayed for the global account in the SAP BTP cockpit. If this happens, you can request an export of your data by opening an incident on component SV-CLM-INF-ONB, if required.
1111

1212
30 days after your contracts with SAP end, the SAP BTP global account is closed and access to your SAP Cloud ALM tenant is blocked. At this point, if you renew your SAP contracts, your account can still be restored to a fully active state without data loss.
1313

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
<!-- loiob7c1490d97ec465180d7831ef3b225f8 -->
22

3-
# Configuring Advanced Access
3+
# Configuring Advanced Access Authorizations
44

55
In addition to the role management options in the *User Management* app, with which you can give users the authorizations for certain tasks and to certain apps, you can also restrict access to certain objects.
66

77
These access restrictions can apply to single apps or to entire application areas.
88

9-
- **[Activating Access Control](activating-access-control-4d0162b.md "With access control lists in the Landscape Management app, you can give
10-
users authorization for accessing specific landscape objects (services, systems, and
11-
business services).")**
9+
- **[Activating Access Control](activating-access-control-4d0162b.md "With access control lists in the Landscape Management app, you
10+
can give users authorization for accessing specific landscape objects (services, systems,
11+
and business services).")**
1212
With access control lists in the *Landscape Management* app, you can give users authorization for accessing specific landscape objects \(services, systems, and business services\).
13-
- **[Configuring Project User Permissions](configuring-project-user-permissions-a2c0029.md "Assign project access levels and project roles in the Projects and Setup
14-
app to control the access to and ability to display or change application objects in SAP
15-
Cloud ALM for implementation apps.")**
13+
- **[Configuring Project User Permissions](configuring-project-user-permissions-a2c0029.md "Assign project access levels and project roles in the Projects and
14+
Setup app to control the access to and ability to display or change
15+
application objects in SAP Cloud ALM for implementation apps.")**
1616
Assign project access levels and project roles in the *Projects and Setup* app to control the access to and ability to display or change application objects in SAP Cloud ALM for implementation apps.
1717

docs/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@
4545
- [Managing Users](managing-users-04a9231.md)
4646
- [Add, Deactivate, and Delete Users](add-deactivate-and-delete-users-eaa4cab.md)
4747
- [Process Approval Requests](process-approval-requests-3a0cad5.md)
48-
- [Configuring Advanced Access](configuring-advanced-access-b7c1490.md)
48+
- [Configuring Advanced Access Authorizations](configuring-advanced-access-authorizations-b7c1490.md)
4949
- [Activating Access Control](activating-access-control-4d0162b.md)
5050
- [Configuring Project User Permissions](configuring-project-user-permissions-a2c0029.md)
5151
- [Setting Up Email Notifications](setting-up-email-notifications-1d1fa37.md)
@@ -54,6 +54,6 @@
5454
- [Enabling the Creation of Public Views](enabling-the-creation-of-public-views-ec0293f.md)
5555
- [Using SAP-Managed Connectivity](using-sap-managed-connectivity-934c2a1.md)
5656
- [Activating the SAP Audit Log Viewer Service](activating-the-sap-audit-log-viewer-service-59fd2a4.md)
57-
- [Terminating Your Account](terminating-your-account-219d7d0.md)
57+
- [Closing Your Account](closing-your-account-219d7d0.md)
5858
- [Troubleshooting and FAQ](troubleshooting-and-faq-737bcf7.md)
5959

0 commit comments

Comments
 (0)