From df441683f7b5c58b4fe9b1ee625eed00515b7f7e Mon Sep 17 00:00:00 2001
From: Peter Persiel <6087940+peterpersiel@users.noreply.github.com>
Date: Thu, 11 Nov 2021 13:56:05 +0100
Subject: [PATCH] Update abapEnvironmentAddons.md: Further version limitations
 (#3263)

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

diff --git a/documentation/docs/scenarios/abapEnvironmentAddons.md b/documentation/docs/scenarios/abapEnvironmentAddons.md
index 0eef4c282..d22d68a71 100644
--- a/documentation/docs/scenarios/abapEnvironmentAddons.md
+++ b/documentation/docs/scenarios/abapEnvironmentAddons.md
@@ -3,7 +3,7 @@
 !!! caution "Current limitations"
     gCTS-related restrictions apply, please refer to [gCTS: restrictions in supported object types](https://launchpad.support.sap.com/#/notes/2888887)
 
-!!! caution Required project "Piper" library version
+!!! caution "Required project "Piper" library version"
     SAP BTP ABAP environment releases might require certain versions of the project "Piper" Library. More Information can be found in [SAP Note 3032800](https://launchpad.support.sap.com/#/notes/3032800).
 
 ## Introduction
@@ -204,6 +204,11 @@ Invalid increase:
 - 2.1.0 to 2.3.0 (version 2.2.0 is missing; therefore, a support package level is missing)
 - 2.1.1 to 2.1.3 (version 2.1.2 is missing; therefore, a patch level is missing)
 
+Technically, the allowed number range for add-on product version and software component version is 1.0.0 to 9999.9999.9999.
+
+The support package level of software component version can only go up until 369 because of technical limitations.
+For the patch level, there is a technical limit of 36³, limited to 9999.
+
 ### Example
 
 Please have a look at the configuration example to [build and publish add-on products using a transient assembly system](https://github.com/SAP-samples/abap-platform-ci-cd-samples/tree/addon-build).