From c43afe13556768f4cc5d2e22df21cdd2709c697a Mon Sep 17 00:00:00 2001
From: Peter Persiel <6087940+peterpersiel@users.noreply.github.com>
Date: Fri, 7 May 2021 13:46:21 +0200
Subject: [PATCH] Update limitations in abapEnvironmentAddons (#2821)

* Update limitations in abapEnvironmentAddons

* Update abapEnvironmentAddons.md
---
 documentation/docs/scenarios/abapEnvironmentAddons.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/documentation/docs/scenarios/abapEnvironmentAddons.md b/documentation/docs/scenarios/abapEnvironmentAddons.md
index cdddf350e..9d29261b1 100644
--- a/documentation/docs/scenarios/abapEnvironmentAddons.md
+++ b/documentation/docs/scenarios/abapEnvironmentAddons.md
@@ -1,9 +1,11 @@
 # Build and Publish Add-on Products on SAP BTP, ABAP Environment
 
-!!! caution Current limitations
-    Please use the long commit ID in the commit ID field in the add-on descriptor file currently, if you are using the short commit ID the build process will fail.
-    To retrieve the long commit id, go into the Manage Software Components app, navigate to the branch, select the commit in the list of commits, field "Long Commit ID" becomes available.
-    This issue is planned to be resolved ABAP Environment release 2105.
+!!! caution "Current limitations"
+
+      - [2102 only] TABU entries are currently not reflected in the object list during add-on build. With ABAP Environment release 2105 this will be supported.
+      - [2102 only] Using the short commit id in the add-on descriptor file does not work currently. Retrieve the long commit id instead by navigating to the branch in the Manage Software Components app, and selecting the commit in the list of commits.
+        This issue will be resolved with ABAP Environment release 2105.
+      - gCTS-related restrictions apply, please refer to [gCTS: restrictions in supported object types](https://launchpad.support.sap.com/#/notes/2888887)
 
 ## Introduction