Merge pull request #55 from tobiashofmann/voting-2025.12

tobiashofmann · web-flow · commit f1184121c8f8 · 2025-12-01T08:21:24.000+01:00
Release 2025.12
diff --git a/definitions/frameworks/adobeforms.toml b/definitions/frameworks/adobeforms.toml
@@ -0,0 +1,20 @@
+[page]
+title = "Adobe Forms"
+description = "Adobe Forms is the latest forms solutions for SAP. It enables form-based processing of business data. Forms are designed using the Adobe LifeCycle Designer and rendered on the ADS. Forms can be static, interactive as well as online or offline enabled."
+reason = "Currently recommended forms technology. Available for on-premise and cloud solutions. Default forms solution for S/4HANA public cloud."
+support = "Supported."
+
+[links]
+"SAP Forms Service by Adobe" = "https://www.sap.com/germany/products/technology-platform/forms-service-by-adobe.html"
+"SAP Help Adobe Forms BTP" = "https://help.sap.com/docs/CP_FORMS_BY_ADOBE?locale=en-US"
+"SAP Help Forms Service by Adobe" = "https://help.sap.com/docs/forms-service-by-adobe/sap-forms-service-cf/sap-forms-service-by-adobe?locale=en-US"
+"Discovery Center" = "https://discovery-center.cloud.sap/serviceCatalog/forms-service-by-adobe?region=all"
+"ADS Configuration NW Java" = "https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/cc3e2153b8504419bc7114f5ae2f693c/69a633254b6e47e6aa379e68e36eb66d.html?locale=en-US"
+"SAP Help SAP Interactive Forms by Adobe" = "https://help.sap.com/docs/ABAP_PLATFORM_NEW/6f3c61a7a5b94447b80e72f722b0aad7/a9b128543eaa4a508b5120b695e29391.html?locale=en-US"
+
+[config]
+label = "Adobe Forms"
+ring = "USE"
+quadrant = "Frameworks"
+active = true
+moved = 0
diff --git a/definitions/frameworks/bor.toml b/definitions/frameworks/bor.toml
@@ -0,0 +1,18 @@
+[page]
+title = "BOR"
+description = "The Business Object Repository (BOR) contains object types that are created using the Business Object Builder. Events is a object type component for an object type. Events are status changes that are published across the system and that can be used in a workflow."
+reason = "Legacy framework. Originally made for SAP Workflow. Successor is RAP Events."
+support = "Not available in SAP S/4HANA Cloud public or SAP BTP ABAP Environment."
+
+[links]
+"SAP Help Business Workflow" = "https://help.sap.com/docs/ABAP_PLATFORM_NEW/4400bdc8dd4648a5a2e5c1c8e05198d7/4f41effddd89535be10000000a421937.html?locale=en-US"
+"SAP Help BOR" = "https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/a602ff71a47c441bb3000504ec938fea/4f344cbf0a7b5542e10000000a421937.html?locale=en-US"
+"SAP Help RAP Business Events" = "https://help.sap.com/docs/abap-cloud/abap-rap/business-events?locale=en-US"
+"SAP Note 3478579" = "https://me.sap.com/notes/3478579"
+
+[config]
+label = "BOR"
+ring = "HOLD"
+quadrant = "Frameworks"
+active = true
+moved = 0
diff --git a/definitions/frameworks/cleanabap.toml b/definitions/frameworks/cleanabap.toml
@@ -5,7 +5,7 @@ reason = "Clean code guidelines for ABAP"
 support = "No real support. Best practice for writing ABAP code."
 
 [links]
-"Homepage" = "https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md"
+Homepage = "https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md"
 "Blog: ABAP Tools for Clean ABAP" = "https://community.sap.com/t5/technology-blogs-by-sap/abap-tools-for-clean-abap/ba-p/13577378"
 
 [config]
diff --git a/definitions/frameworks/nast.toml b/definitions/frameworks/nast.toml
@@ -0,0 +1,17 @@
+[page]
+title = "NAST"
+description = "NAST Output Management is the standard solution for output management for Business Suite applications. NAST supports several channels like Print, FAX, E-Mail, EDI or ALE. It is used widely by modules like SD or MM. Uses a table driven architecture and offers customization options, while integration other technologies like Smart Forms. NAST stands for Nachrichtensteuerung."
+reason = "Successor for new S/4HANA applications is available. NAST is available and supported in S/4HANA. No switch to S/4HANA Output Management mandatory for existing applications."
+support = "Use only for existing Business Suite applications that already used NAST. For new S/4HANA application, S/4HANA Output Management is recommended."
+
+[links]
+"SCN Blog Post Output Management vs NAST" = "https://community.sap.com/t5/supply-chain-management-blog-posts-by-sap/s-4hana-output-management-vs-nast-when-to-choose-which/ba-p/13889623"
+"SCN Blog Post Storing Output Documents in SAP S/4HANA" = "https://community.sap.com/t5/technology-blog-posts-by-sap/storing-output-documents-in-sap-s-4hana/ba-p/13552587"
+"SCN Blog Post Determining the Right Tool: NAST vs. BRF+ for SAP Output Management" = "https://community.sap.com/t5/technology-blog-posts-by-sap/determining-the-right-tool-nast-vs-brf-for-sap-output-management/ba-p/13734107"
+
+[config]
+label = "NAST"
+ring = "USE"
+quadrant = "Frameworks"
+active = true
+moved = 0
diff --git a/definitions/frameworks/outputmanagement.toml b/definitions/frameworks/outputmanagement.toml
@@ -0,0 +1,19 @@
+[page]
+title = "S/4HANA Output Management"
+description = "Output management is the framework for all functions and processes related to the output of documents in SAP S/4HANA. It comprises activities related to business documents and provides functions like printing, sending e-mails or maintaining form templates. The on-premise and private cloud versions of S/4HANA support EDI as an channel. The public cloud version depends on Adobe Document Services for form rendering. The reuse service used is S/4HANA Output Control. S/4HANA Output Management is the successor to NAST which was the framework used in the Business Suite for output management."
+reason = "S/4HANA Output Management is part of the S/4HANA standard. It is the standard solution for output management for new applications. For applications that existed before S/4HANA, NAST is recommended. A switch from NAST to S/4HANA Output Management is not mandatroy."
+support = "Supported. Standard output management solution for new applications in S/4HANA."
+
+[links]
+"SAP Help S4 Public Cloud" = "https://help.sap.com/docs/SAP_S4HANA_CLOUD/a630d57fc5004c6383e7a81efee7a8bb/d7bd4b5d70d94f09bcf99b221a7a1688.html?locale=en-US"
+"SAP Help S4 Private Cloud" = "https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/8308e6d301d54584a33cd04a9861bc52/d736578415a340cba84b944798a699b5.html?locale=en-US"
+"SCN Blog Post Output Management" = "https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/output-management-in-sap-s-4hana/ba-p/13492419"
+"SCN Blog Post Output Management vs NAST" = "https://community.sap.com/t5/supply-chain-management-blog-posts-by-sap/s-4hana-output-management-vs-nast-when-to-choose-which/ba-p/13889623"
+"SAP Learning Getting Started with SAP Forms service by Adobe" = "https://learning.sap.com/learning-journeys/getting-started-with-sap-forms-service-by-adobe"
+
+[config]
+label = "Output Management"
+ring = "USE"
+quadrant = "Frameworks"
+active = true
+moved = 0
diff --git a/definitions/technology/clustertable.toml b/definitions/technology/clustertable.toml
@@ -0,0 +1,19 @@
+[page]
+title = "Cluster Table"
+description = "Cluster tables and table pools are special table types in the ABAP Dictionary. Data from several tables is stored in a table pool / table cluster. These tables are used exclusively for storing internal control information (parameters, screen sequences, temporary data, documentation, etc). Data stored in a custer table is compressed using a proprietory format and can only be accessed by the SAP kernel. With S/4HANA, cluster tables are obsolete."
+reason = "Deprecated technology. Not supported by S/4HANA and ABAP as of release 7.53."
+support = "Not supported as of ABAP release 7.53."
+
+[links]
+"SAP Help Pooled and Cluster Tables" = "https://help.sap.com/docs/SAP_NETWEAVER_AS_ABAP_752/ec1c9c8191b74de98feb94001a95dd76/cf21f083446011d189700000e8322d00.html?locale=en-US"
+"ABAP Keyword Documentation" = "https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/index.htm?file=abencluster_table_glosry.htm"
+"1892354 - SAP Strategy for Cluster and Pool Tables" = "https://me.sap.com/notes/1892354"
+"2634739 - How to get a list about the existing pool and cluster tables in the system?" = "https://me.sap.com/notes/0002634739"
+"YouTube: Do Cluster Tables Exist in SAP S/4HANA?" = "https://www.youtube.com/watch?v=NNG4izOk7CQ"
+
+[config]
+label = "Cluster Table"
+ring = "STOP"
+quadrant = "Technology"
+active = true
+moved = 0
diff --git a/definitions/technology/sapscript.toml b/definitions/technology/sapscript.toml
@@ -2,7 +2,7 @@
 title = "SAPscript"
 description = "The oldest SAP forms technology. Dating back to 1992, this forms technology is still available and used. Allows to create forms that contain custom logic and layout. Via the usage of standard texts and symbols, flexible forms can be created."
 reason = "Not recommended. Legacy technology with restrictions regarding modern layout like barcodes or pictures.<br>Once the dominant forms technology, SAPscript is superseded by SmartForms or Adobe Forms.<br>Being a legacy technology means that its usage share is declining, making it also complicated to maintain SAPscript based forms. General recommendation is to migrate SAPscript forms or to rewrite them in newer technology. "
-support = "Supported untill 2040 (follows S/4HANA maintenance strategy)"
+support = "Supported until 2040 (follows S/4HANA maintenance strategy)"
 
 [links]
 "SAP Help" = "https://help.sap.com/docs/ABAP_PLATFORM_NEW/bb9551032d3046c98c2b251ae486085f/4e12dc40e1905707e10000000a42189e.html?locale=en-US"
diff --git a/definitions/technology/smartforms.toml b/definitions/technology/smartforms.toml
@@ -0,0 +1,19 @@
+[page]
+title = "Smart Forms"
+description = "Smart Forms are used to create and maintain forms in SAP Systems. Several output channels like printer or HTML can be used. SAP Smart Forms offers tools that allow to create, maintain and adopt forms. The architecture of SAP Smart Forms separates application data retrieval from the form definition. "
+reason = "Not recommended. Smart Forms successor to SAPscript and is succeeded by Adobe Forms, introducced in 2005. New forms should be created using Adobe Forms."
+support = "Supported."
+
+[links]
+"SAP Help" = "https://help.sap.com/docs/ABAP_PLATFORM_NEW/e0ef07e1f76b4370b1baa502eace5ece/4e50b68d95e14dd2e10000000a42189b.html?locale=en-US"
+"SAP Help 4.7" = "https://help.sap.com/saphelp_470/helpdata/en/a5/de6838abce021ae10000009b38f842/frameset.htm"
+
+
+[config]
+label = "Smart Forms"
+ring = "STOP"
+quadrant = "Technology"
+active = true
+moved = 0
+
+
diff --git a/definitions/tools/fioritools.toml b/definitions/tools/fioritools.toml
@@ -0,0 +1,19 @@
+[page]
+title = "Fiori Tools"
+description = "The SAP Fiori tools provide functionalities to simplify the process of writing or modifying SAP Fiori Elements apps. They are a set of several tools that efficiently support the developer during the app development process: Application Wizard, Application Modeler, Guided Development, Service Modeler, XML Annotation Language Server, XML Toolkit. The Fiori tools are available for BAS and VS Code."
+reason = "The recommended tooling for Fiori Elements apps. Available for both BAS and VS Code, the tooling is being made (in progress) as open source. For developers working with Fiori Elements apps in the frontend, the tools offer valuable help at all development phases, and specially when working with annotations."
+support = "Supported"
+
+[links]
+Documentation = "https://help.sap.com/docs/SAP_FIORI_tools"
+GitHub = "https://github.com/SAP/open-ux-tools"
+Capabilities = "https://help.sap.com/docs/SAP_FIORI_tools/17d50220bcd848aa854c9c182d65b699/f540ae1961914bf783cd266f3c0d8530.html"
+"VS Code Marketplace" = "https://marketplace.visualstudio.com/items?itemName=SAPSE.sap-ux-fiori-tools-extension-pack"
+SCN = "https://pages.community.sap.com/topics/fiori-tools"
+
+[config]
+label = "Fiori tools"
+ring = "USE"
+quadrant = "Tools"
+active = true
+moved = 0
diff --git a/definitions/tools/ui5cli.toml b/definitions/tools/ui5cli.toml
@@ -1,15 +1,15 @@
 [page]
-title = "UI5 tooling"
+title = "UI5 CLI"
 description = "An open and modular toolchain to develop state-of-the-art applications based on the UI5 framework."
 reason = "Tooling for UI5 apps. For Fiori apps the usage of UX tooling / wizards for BAS and VS Code is recommended."
 support = "Supported"
 
 [links]
-Documentation = "https://sap.github.io/ui5-tooling/v3/"
-GitHub = "https://github.com/SAP/ui5-tooling"
+Documentation = "https://ui5.github.io/cli/stable/"
+GitHub = "https://github.com/UI5/cli"
 
 [config]
-label = "UI5 tooling"
+label = "UI5 CLI"
 ring = "USE"
 quadrant = "Tools"
 active = true
diff --git a/definitions/ui/crmwebclientui.toml b/definitions/ui/crmwebclientui.toml
@@ -1,11 +1,12 @@
 [page]
 title = "CRM-WebClient-UI"
 description = "The CRM WebClient UI is based on the WebClient UI framework. It is designed for business users, and presents a role-based workspace with a navigation area from which you can start different functions, applications, and processes."
-reason = "Currently only usage is for Solution Manager"
-support = "EOL with SolMan in 2027/30. Successor is Fiori UX"
+reason = "Currently only usage is for standard SAP apps (CRM, Solution Manager). It is not available in the public cloud for custom extensions."
+support = "Only available in S/4HANA on premise and private cloud. Successor is Fiori UX."
 
 [links]
 "SAP Help" = "https://help.sap.com/docs/SAP_NETWEAVER_700/129f88c06c531014aa4eb568cafe09ea/69f5bc3d42f46c33e10000000a11405a.html?locale=en"
+"SAP Note 3591718" = "https://me.sap.com/notes/3591718"
 
 [config]
 label = "CRM-WebClient-UI"
diff --git a/definitions/ui/nwbc.toml b/definitions/ui/nwbc.toml
@@ -7,8 +7,8 @@ support = "Supported"
 [links]
 "SAP Help" = "https://help.sap.com/docs/ABAP_PLATFORM_NEW/9737050ef01843f19572591b42128f1b/03ecbafb844b450a9314a5683b75ed80.html?locale=en-US"
 "SAP Note 3220574" = "https://me.sap.com/notes/3220574"
-"SCN" = "https://pages.community.sap.com/topics/business-client"
-"FAQ" = "https://pages.community.sap.com/topics/business-client/faq"
+SCN = "https://pages.community.sap.com/topics/business-client"
+FAQ = "https://pages.community.sap.com/topics/business-client/faq"
 
 [config]
 label = "NWBC"
diff --git a/package.json b/package.json
@@ -26,7 +26,7 @@
   "scripts": {
     "start": "browser-sync radar -w",
     "conv": "node index.js",
-    "lint": "npm run lint:js && npm run lint:html",
+    "lint": "npm run lint:js && npm run lint:html && npm run lint:toml",
     "lint:js": "eslint convert.js index.js",
     "lint:toml": "eslint definitions/**/*.toml",
     "lint:html": "eslint radar/**/*.html"
diff --git a/radar/index.html b/radar/index.html
@@ -41,9 +41,9 @@
     ],
     rings: [
       { name: "ADOPT", color: "#198754" },
-      { name: "USE",   color: "#0c6efd" },
-      { name: "HOLD",  color: "#ffc107" },
-      { name: "STOP",  color: "#dc3545" }
+      { name: "USE", color: "#0c6efd" },
+      { name: "HOLD", color: "#ffc107" },
+      { name: "STOP", color: "#dc3545" }
     ],
     print_layout: true,
     links_in_new_tabs: true,
@@ -83,12 +83,12 @@ <h3>What is the purpose?</h3>
       Therefore, the tech radar aims to help SAP developers in positioning themselves and give them the tool needed to justify and defend their choice of technology.
       </p>
       <p>
-      The SAP development tech radar aims to provide a plattform for SAP developers to exchange on the community driven technology recommendation, to reflect and make make technology decisions transparent.
-      In a borader scope, it aims to continuously evolve the overall SAP developer technology. 
+      The SAP development tech radar aims to provide a platform for SAP developers to exchange on the community driven technology recommendation, to reflect and make make technology decisions transparent.
+      In a broader scope, it aims to continuously evolve the overall SAP developer technology. 
       </p>
 
       <p>
-        The information is not tailored to a specific version, e.g. NetWeaver 7.50 or S/4HANA 2023. The recommendations are generic and give guidance on what you should be used, independent of the current available technology stack. If the recommendation is to use RAP with OData v4 or CDS View Entity and your sytem does not support this, see this as an oppurtunity to drive change in your stack. Innovation from SAP will not stop, and the longer it takes you to be able to use the technology in the ring USE, the higher the risk to stay outdated: once you as a developer, but also your company. If your tech stack shows that you are mostly in the HOLD and STOP ring because USE implies an update, do the update.
+        The information is not tailored to a specific version, e.g. NetWeaver 7.50 or S/4HANA 2023. The recommendations are generic and give guidance on what should be used, independent of the current available technology stack. If the recommendation is to use RAP with OData v4 or CDS View Entity and your system does not support this, see this as an oppurtunity to drive change in your stack. Innovation from SAP will not stop, and the longer it takes you to be able to use the technology in the ring USE, the higher the risk to stay outdated: once you as a developer, but also your company. If your tech stack shows that you are mostly in the HOLD and STOP ring, try to update to technology in ring USE.
       </p>
       <p>
       Based on the <a href="https://www.thoughtworks.com/radar">pioneering work of ThoughtWorks</a>, the SAP development Tech Radar is based on the Zalando Tech Radar for visualization.
@@ -117,10 +117,10 @@ <h3>What technology is included in the SAP Development Tech Radar?</h3>
       <h3>How to maintain it?</h3>
       
       <p>
-      The Tech Radar is maintained by <em>Tobias Hofmann</em>. The idea is to continuously improve the tech radar by adding, removing and adjusting the listed technologies. The latest version of the tech radar will be published every quarter.
+      The Tech Radar is maintained by <em>Tobias Hofmann</em>. The idea is to continuously improve the tech radar by adding, removing and adjusting the listed technologies. The latest version of the tech radar will be published every 6 months.
       </p>
       <p>
-      To ensure that the tech radar stays relevant, contributions from the SAP development community are welcomed. The contribution can span the task of adding a new technology, as well as adjusting the ring of a listed technology, or to adjust the information provided. Assignment of technologies to rings is the outcome of ring change proposals, which are discussed and voted on. 
+      To ensure that the tech radar stays relevant, contributions from SAP developers and architects are welcomed. The contribution can span the task of adding a new technology, as well as adjusting the ring of a listed technology, or to adjust the information provided. Assignment of technologies to rings is the outcome of ring change proposals, which are discussed and voted on. 
       </p>
 
     </td>
