Skip to content

Commit 2eebcc7

Browse files
authored
Update cloud.md
1 parent 9333255 commit 2eebcc7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/advanced/technical/cloud.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,18 +10,18 @@ Cloud Readiness means that an ABAP project:
1010
- Complies with the restricted **ABAP for Cloud Development** language scope
1111
- Avoids any modifications or direct access to SAP tables
1212

13-
Such developments can run on the standalone BTP ABAP Environment (Steampunk) or the Embedded ABAP Environment (e.g., S/4HANA Cloud Public Edition), making them future-proof and compatible with upcoming SAP upgrades.
13+
Such developments can run on the standalone BTP ABAP Environment (Steampunk) or the Embedded ABAP Environment (e.g., S/4HANA Cloud Public Edition). Even if still operating on ECC, projects built this way are future-proof and ensure safe, low-effort migration to cloud environments without rework or additional costs.
1414

1515
#### Why is abap2UI5 Cloud Ready?
1616

17-
abap2UI5 fully meets the requirements of a cloud-compliant ABAP project:
17+
abap2UI5 fully meets the criteria of a cloud-compliant ABAP project:
1818

1919
- It is written entirely using **ABAP for Cloud Development**, with no use of restricted language features or unreleased objects
2020
- It only relies on internally defined classes or released APIs
2121
- It requires no core modifications, making it fully **Clean Core compliant**.
2222
- The UI5 frontend is a static UI5 freestyle app
2323

24-
abap2UI5 is cloud-ready, clean-core compliant, and supports modern, upgrade-safe development practices.
24+
abap2UI5 is cloud-ready by design, Clean Core compliant, and supports modern, upgrade-safe development practices.
2525

2626
#### Do I Have to Use RAP to Be Cloud Ready?
2727

@@ -32,7 +32,7 @@ The RESTful Application Programming Model (RAP) is SAP's official model for buil
3232
- OData Services for standardized CRUD operations
3333
- Fiori Elements for automatic UI generation
3434

35-
While tightly integrated with ABAP Cloud, RAP is not **mandatory**. Cloud readiness depends on technical compliance, not on using RAP specifically. Any solution that respects SAP’s released APIs and language scope can be considered cloud-readyeven without RAP.
35+
While RAP is tightly integrated with ABAP Cloud, it is not mandatory. Cloud readiness depends on technical compliancenot on the use of RAP. Any solution that adheres to SAP’s released APIs and language scope is considered cloud-ready, even without RAP.
3636

3737
#### Conclusion
3838

0 commit comments

Comments
 (0)