<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: ABAP for Agents</title>
    <description>The latest articles on DEV Community by ABAP for Agents (@abapforagents).</description>
    <link>https://dev.to/abapforagents</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4210550%2Fab96a2bc-7c52-45c9-88c1-a6b71eac6d53.png</url>
      <title>DEV Community: ABAP for Agents</title>
      <link>https://dev.to/abapforagents</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/abapforagents"/>
    <language>en</language>
    <item>
      <title>Released CDS views for SAP S/4HANA Cloud data extraction: what you can pull, and how</title>
      <dc:creator>ABAP for Agents</dc:creator>
      <pubDate>Mon, 09 Nov 2026 09:53:22 +0000</pubDate>
      <link>https://dev.to/abapforagents/released-cds-views-for-sap-s4hana-cloud-data-extraction-what-you-can-pull-and-how-3p1c</link>
      <guid>https://dev.to/abapforagents/released-cds-views-for-sap-s4hana-cloud-data-extraction-what-you-can-pull-and-how-3p1c</guid>
      <description>&lt;p&gt;"Can we just pull the tables?" isn't an option in SAP S/4HANA Cloud Public Edition. The supported way out is a set of CDS views that SAP has released for extraction, read through SAP's extraction runtime by SAP Datasphere, SAP BW/4HANA or another consumer that SAP supports.&lt;/p&gt;

&lt;p&gt;This post covers what makes a CDS view extractable, how the public and private editions differ, the route into Datasphere, the key master and finance views, why the A_ OData APIs are the wrong tool for bulk loads, and how to find extraction views yourself. Every statement comes from SAP's documentation on the SAP Help Portal, SAP Learning and SAP's API Policy, all linked under &lt;a href="https://abapforagents.com/guides/s4hana-cloud-cds-extraction/#sources" rel="noopener noreferrer"&gt;Sources&lt;/a&gt;. &lt;strong&gt;We haven't tested this against a real SAP system.&lt;/strong&gt; View names, communication scenarios and container names change between releases, so check them in your own tenant.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;In SAP S/4HANA Cloud Public Edition you extract through C1-released CDS views annotated with @Analytics.dataExtraction.enabled. You don't get tables, SAPI extractors or SLT.&lt;/li&gt;
&lt;li&gt;Private edition and on-premise connect like classic S/4HANA. Custom CDS views and SLT are available there too.&lt;/li&gt;
&lt;li&gt;The runtime is ODP. Datasphere replication flows read these views from the CDS_EXTRACTION container through SAP_COM_0532, and the views need to be on an allowlist first.&lt;/li&gt;
&lt;li&gt;SAP's docs mark I_Product, I_Customer and I_Supplier as extraction-enabled with automatic delta. For G/L line items SAP documents I_GLAccountLineItemRawData. Check I_JournalEntryItem in your own system before you plan on it.&lt;/li&gt;
&lt;li&gt;A_ OData APIs are for documented transactional use. SAP's API Policy restricts large-scale extraction outside the pathways it provides for it.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Public edition vs private edition
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;SAP S/4HANA Cloud Public Edition&lt;/strong&gt; is the strict case. SAP Data Intelligence's documentation says it directly: "For SAP S/4HANA Cloud, only standard ABAP CDS views that are C1-released can be integrated." SAP Learning's table of Datasphere replication sources shows the same picture. For S/4HANA Cloud, the only containers are &lt;strong&gt;CDS_EXTRACTION&lt;/strong&gt; (released extraction views) and &lt;strong&gt;SQL_SERVICE&lt;/strong&gt; (views exposed through the ABAP SQL service). ODP_SAPI extractors and SLT appear only for on-premise sources.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SAP S/4HANA Cloud Private Edition&lt;/strong&gt; connects like SAP S/4HANA on-premise. SAP's Green Ledger documentation, for example, groups "SAP S/4HANA Cloud Private Edition, or SAP S/4HANA" under on-premise connections and gives public edition its own section. On those systems the Data Intelligence docs add two options that public edition lacks: you can create your own extraction-enabled CDS views, and SLT is available.&lt;/p&gt;

&lt;p&gt;Even on private edition and on-premise, released extraction views are the upgrade-safe choice. The ABAP Keyword Documentation says extraction views should be released to contract C1 "to guarantee compatibility … when the S/4HANA system is upgraded".&lt;/p&gt;

&lt;h2&gt;
  
  
  What makes a CDS view extractable
&lt;/h2&gt;

&lt;p&gt;Three things together, all from SAP's documentation:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Release.&lt;/strong&gt; The view is released with the C1 stability contract. The ABAP Keyword Documentation adds that you also choose the visibility "Use in Key User Apps", and that "Only C1-released extraction view with this visibility will be exposed in S/4HANA CE" (cloud edition).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;@Analytics.dataExtraction.enabled: true&lt;/code&gt;.&lt;/strong&gt; This marks the view as suitable for replication. SAP's Data Integration page explains that this annotation enables full loads and &lt;code&gt;@Analytics.dataExtraction.delta&lt;/code&gt; enables delta loads. Datasphere's trigger-based change data capture uses &lt;code&gt;delta.changeDataCapture.automatic&lt;/code&gt; for simple projections and &lt;code&gt;delta.changeDataCapture.mapping&lt;/code&gt; for views with joins.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Only the field list travels.&lt;/strong&gt; "Only the fields included in the field list of the view are available … Associations are not exposed via data extraction." If you need a field from an association, you need a view that projects it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;SAP also says "only a subset of the documented CDS views is enabled for data extraction". A released view isn't automatically an extraction view.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the extraction runs: ODP, CDI and the ABAP Pipeline Engine
&lt;/h2&gt;

&lt;p&gt;SAP's Architecture Overview for Data Integration names &lt;strong&gt;ODP&lt;/strong&gt; as the extraction runtime and describes two ways to call it from S/4HANA Cloud Public Edition:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Route&lt;/th&gt;
&lt;th&gt;Communication scenario&lt;/th&gt;
&lt;th&gt;Notes from SAP&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;ABAP Pipeline Engine&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;SAP_COM_0532&lt;/code&gt; (WebSocket RFC)&lt;/td&gt;
&lt;td&gt;"Recommended in most cases"&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cloud Data Integration (CDI)&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;SAP_COM_0531&lt;/code&gt; (OData V4)&lt;/td&gt;
&lt;td&gt;Slower. Datasphere's connection docs label it legacy&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;"The same set of released ABAP CDS extraction views is available for both." SAP BW/4HANA connects through &lt;code&gt;SAP_COM_0042&lt;/code&gt; (RFC/ODP). Consumers named in SAP's architecture page include SAP BW, BW/4HANA, Data Intelligence, Datasphere, HANA and HANA Cloud.&lt;/p&gt;

&lt;p&gt;The &lt;strong&gt;ABAP SQL service&lt;/strong&gt; is a separate route. SAP calls it "the strategic mechanism for exposing CDS view entities to external SQL consumers", and Datasphere's connectivity page recommends it for replication and federation. It has its own setup and isn't the ODP route this guide describes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Into SAP Datasphere, step by step
&lt;/h2&gt;

&lt;p&gt;SAP's "Integrating CDS Views Using SAP Datasphere" lists the steps for public edition with &lt;code&gt;SAP_COM_0532&lt;/code&gt;:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create a communication user.&lt;/li&gt;
&lt;li&gt;Create a communication system (inbound only) for Datasphere.&lt;/li&gt;
&lt;li&gt;Create a communication arrangement for &lt;code&gt;SAP_COM_0532&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Allowlist the views.&lt;/strong&gt; Maintain an authorization group with the CDS views you allow ("Define Allowlists for CDS View Extraction"). Views that aren't in it don't appear in the CDS_EXTRACTION folder. The ABAP SQL service doesn't use this allowlist.&lt;/li&gt;
&lt;li&gt;In Datasphere, create a connection of type SAP ABAP with protocol RFC.&lt;/li&gt;
&lt;li&gt;Build a replication flow on the CDS_EXTRACTION container. SAP Learning lists the load types: Initial Only, Initial and Delta, Delta Only.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Step 4 is where most "the view isn't there" questions end. It's a customizing step in the S/4HANA system, not in Datasphere.&lt;/p&gt;

&lt;h2&gt;
  
  
  Key views for master data and finance
&lt;/h2&gt;

&lt;p&gt;What SAP's S/4HANA Cloud Public Edition CDS documentation (release 2608) says about four views that people often ask for:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;View&lt;/th&gt;
&lt;th&gt;What it is&lt;/th&gt;
&lt;th&gt;Extraction status in SAP's docs&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;I_Product&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Product master&lt;/td&gt;
&lt;td&gt;Released. "Enabled for data extraction in full mode as well as in delta mode. Deltas are determined automatically by change data capture."&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;I_Customer&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Customer master (dimension)&lt;/td&gt;
&lt;td&gt;Same statement: full and delta, automatic CDC&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;I_Supplier&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Supplier master (dimension)&lt;/td&gt;
&lt;td&gt;Same statement: full and delta, automatic CDC&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;I_JournalEntryItem&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Journal entry items from table ACDOCA (cube)&lt;/td&gt;
&lt;td&gt;Released. Its documentation page has no data extraction section, so verify it before planning on it&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;For &lt;strong&gt;G/L line items&lt;/strong&gt;, SAP documents &lt;code&gt;I_GLAccountLineItemRawData&lt;/code&gt; with extraction type "Full" plus CDC delta on table ACDOCA. SAP's own Green Ledger content replicates that view to Datasphere. Two points from its page: it returns line items "without the ledger", so for extension ledgers you join &lt;code&gt;I_LedgerSourceLedger&lt;/code&gt;, and it includes balance carry-forward postings. &lt;code&gt;I_JournalEntryItem&lt;/code&gt;, by contrast, "does not expose technical balance carried forward items of period 000". The two views won't add up to the same balances unless you handle that.&lt;/p&gt;

&lt;p&gt;For open receivables and payables, SAP's Datasphere content builds on a replication flow of &lt;code&gt;I_OperationalAcctgDocItem&lt;/code&gt;, which is sourced from BSEG. See &lt;a href="https://abapforagents.com/guides/replace-bseg-select-acdoca/" rel="noopener noreferrer"&gt;replacing SELECT on BSEG&lt;/a&gt; for how the finance views relate.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why not the A_ OData APIs?
&lt;/h2&gt;

&lt;p&gt;The A_ entities, such as &lt;code&gt;A_Product&lt;/code&gt; or &lt;code&gt;A_BusinessPartner&lt;/code&gt;, are published OData APIs for integrating transactional processes. SAP's API Policy says published APIs are for "Documented Use". Among the possible controls, it lists "limits and preconditions for bulk extraction / replication". In section 2.2.2 it says that "except through and within the limits of SAP-endorsed architectures, data services, or service-specific pathways expressly identified and intended for such purposes, SAP prohibits API use for … scraping, harvesting, or systematic and/or large-scale data extraction or replication". The policy also allows throttling or suspension.&lt;/p&gt;

&lt;p&gt;The practical reading: use the extraction views and the ODP route above for bulk loads and deltas, and keep the A_ APIs for what they're documented for. SAP says the same about custom OData exposure in a related product: "the External API scenario is not intended for one-off mass data extraction", and calls should "limit the requested data with appropriate filters and/or paging".&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding extraction views yourself
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SAP Business Accelerator Hub.&lt;/strong&gt; SAP's Data Integration page says the Hub "shows released CDS views and also indicates whether an individual CDS view is enabled for data extraction". Look for &lt;strong&gt;Data Source for Data Extraction&lt;/strong&gt; under Supported Capabilities.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;View Browser app.&lt;/strong&gt; In the tenant, the View Browser shows whether a view is extraction-enabled.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;I_DataExtractionEnabledView&lt;/code&gt;.&lt;/strong&gt; A CDS view that lists the extraction-enabled views, with &lt;code&gt;DataExtractionViewName&lt;/code&gt;, &lt;code&gt;DeltaChgDataCaptureIsSupported&lt;/code&gt; and &lt;code&gt;IsSAPReleasedView&lt;/code&gt;. SAP documents it for S/4HANA Cloud and for S/4HANA from 2020.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SAP Help per view.&lt;/strong&gt; Each view page in the S/4HANA Cloud CDS documentation has a "Data Extraction" section when the view is extraction-enabled, as shown for &lt;code&gt;I_Product&lt;/code&gt;, &lt;code&gt;I_Customer&lt;/code&gt; and &lt;code&gt;I_Supplier&lt;/code&gt; above.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you use an AI assistant to write extraction views or queries, give it these limits up front. Assistants often suggest table reads or A_ API paging loops, which run into exactly the limits described above. &lt;a href="https://abapforagents.com/guides/ai-abap-mistakes/" rel="noopener noreferrer"&gt;The 10 mistakes AI makes in ABAP&lt;/a&gt; and &lt;a href="https://abapforagents.com/guides/claude-code-agents-md-abap/" rel="noopener noreferrer"&gt;Claude Code and AGENTS.md for ABAP&lt;/a&gt; show how to keep such rules in the agent's context, and the free &lt;a href="https://github.com/abapforagents/abap-for-agents-lite" rel="noopener noreferrer"&gt;abap-for-agents-lite&lt;/a&gt; rules are a starting point.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;ABAP Keyword Documentation 8.16: &lt;a href="https://help.sap.com/doc/abapdocu_816_index_htm/8.16/en-US/ABENCDS_2140431020_ANNO.html" rel="noopener noreferrer"&gt;Analytics.dataExtraction.enabled&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;SAP S/4HANA Cloud Public Edition (2608): &lt;a href="https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/c3a5da91691d4ebd89748d9f40af7a4c.html" rel="noopener noreferrer"&gt;Data Integration&lt;/a&gt;, &lt;a href="https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/36b7901040cb4c18b557ca9cc90a7002.html" rel="noopener noreferrer"&gt;Architecture Overview for Data Integration&lt;/a&gt; and &lt;a href="https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/f509eddda867452db9631dae1ae442a3.html" rel="noopener noreferrer"&gt;Integrating CDS Views Using SAP Datasphere&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;SAP S/4HANA Cloud Public Edition CDS views (2608): &lt;a href="https://help.sap.com/docs/SAP_S4HANA_CLOUD/c0c54048d35849128be8e872df5bea6d/af5c379f422e495c825802fcb9b0731f.html" rel="noopener noreferrer"&gt;Product&lt;/a&gt;, &lt;a href="https://help.sap.com/docs/SAP_S4HANA_CLOUD/c0c54048d35849128be8e872df5bea6d/a11849401368469fb9e7dfb34f44e9c7.html" rel="noopener noreferrer"&gt;Customer&lt;/a&gt;, &lt;a href="https://help.sap.com/docs/SAP_S4HANA_CLOUD/c0c54048d35849128be8e872df5bea6d/91c2229c60064cc1bfc621b879435174.html" rel="noopener noreferrer"&gt;Supplier&lt;/a&gt;, &lt;a href="https://help.sap.com/docs/SAP_S4HANA_CLOUD/c0c54048d35849128be8e872df5bea6d/47dce95760521070e10000000a44147b.html" rel="noopener noreferrer"&gt;Journal Entry Item&lt;/a&gt;, &lt;a href="https://help.sap.com/docs/SAP_S4HANA_CLOUD/c0c54048d35849128be8e872df5bea6d/7fe239a3f2214e2cb36e90d453eee6d3.html" rel="noopener noreferrer"&gt;G/L Account Line Item - Raw Data&lt;/a&gt; and &lt;a href="https://help.sap.com/docs/SAP_S4HANA_CLOUD/c0c54048d35849128be8e872df5bea6d/870d66c6bfc44d6c9f128c888f0c7957.html" rel="noopener noreferrer"&gt;CDS Views Enabled for Data Extraction&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;SAP Datasphere: &lt;a href="https://help.sap.com/docs/SAP_DATASPHERE/9f804b8efa8043539289f42f372c4862/abb159e027184c98a54fc1b2a88dd3f5.html" rel="noopener noreferrer"&gt;Prepare Connectivity to SAP S/4HANA Cloud&lt;/a&gt; and &lt;a href="https://help.sap.com/docs/SAP_DATASPHERE/6eb1eff34e4c4b1f90adfbfba1334240/a88ae4e56bfc1014a79e69594ccc91ad.html" rel="noopener noreferrer"&gt;Operational Accounting Document Item&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;SAP Learning: &lt;a href="https://learning.sap.com/courses/exploring-sap-datasphere-1/working-with-replication-flows_f38ca7cf-56b7-43a0-a8ae-62da2e0613b2" rel="noopener noreferrer"&gt;Working with Replication Flows&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;SAP Data Intelligence: &lt;a href="https://help.sap.com/docs/SAP_DATA_INTELLIGENCE_ON-PREMISE/1c4ff4486dd04e47b32fe406111bfee8/a8368bcec0b94ad5a5ea975167226eee.html" rel="noopener noreferrer"&gt;Enabling the Data Source&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;SAP Green Ledger: &lt;a href="https://help.sap.com/docs/SAP_Green_Ledger/275111bbd8614e939fe0a0942f81c143/0844a2c513164903848c49f85c8ab8bf.html" rel="noopener noreferrer"&gt;Integrate with SAP Datasphere&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://help.sap.com/doc/sap-api-policy/latest/en-US/API_Policy_latest.pdf" rel="noopener noreferrer"&gt;SAP API Policy&lt;/a&gt;, sections 1.1, 2.1, 2.2.2 and 3&lt;/li&gt;
&lt;li&gt;SAP Marketing Cloud: &lt;a href="https://help.sap.com/docs/SAP_MARKETING_CLOUD/e0cd7c1ecf3d4f2f9feb46ec1c5b68fb/f4dcfd6e14b54177b98d6099ddb2014e.html" rel="noopener noreferrer"&gt;External API: Exposing a Custom CDS View as OData API&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Free lite rules (MIT): &lt;a href="https://github.com/abapforagents/abap-for-agents-lite" rel="noopener noreferrer"&gt;abap-for-agents-lite on GitHub&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://abapforagents.com/guides/s4hana-cloud-cds-extraction/" rel="noopener noreferrer"&gt;abapforagents.com&lt;/a&gt;. Free MIT-licensed ABAP rules for Cursor, Claude Code and Copilot are on &lt;a href="https://github.com/abapforagents/abap-for-agents-lite" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;, and there are more guides at &lt;a href="https://abapforagents.com/guides/" rel="noopener noreferrer"&gt;abapforagents.com/guides&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>sap</category>
      <category>abap</category>
      <category>dataengineering</category>
      <category>s4hana</category>
    </item>
    <item>
      <title>Column totals in a Fiori Elements List Report with RAP: more than @Aggregation.default</title>
      <dc:creator>ABAP for Agents</dc:creator>
      <pubDate>Tue, 27 Oct 2026 10:14:45 +0000</pubDate>
      <link>https://dev.to/abapforagents/column-totals-in-a-fiori-elements-list-report-with-rap-more-than-aggregationdefault-1252</link>
      <guid>https://dev.to/abapforagents/column-totals-in-a-fiori-elements-list-report-with-rap-more-than-aggregationdefault-1252</guid>
      <description>&lt;p&gt;"How do I show the sum of a column in my Fiori List Report?" comes up again and again in ABAP forums, and the usual first answer is "add &lt;code&gt;@Aggregation.default: #SUM&lt;/code&gt;".&lt;/p&gt;

&lt;p&gt;That's only half of the answer. In SAP Fiori elements for OData V4 the total row belongs to one table type, the &lt;strong&gt;analytical table&lt;/strong&gt;. That table needs a service that supports data aggregation, and on ABAP that has its own RAP feature, its own annotation and its own release requirements.&lt;/p&gt;

&lt;p&gt;This post walks through the RAP and CDS side, the Fiori elements side, and a checklist for when the total doesn't appear. Every behaviour described here is taken from SAP's RAP documentation on the SAP Help Portal and the SAP Fiori elements documentation in the SAPUI5 SDK, linked in each section. &lt;strong&gt;The code samples are illustrative and haven't been run on a real system&lt;/strong&gt;, so adapt names and types to your own data model.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;In Fiori elements for OData V4, totals come from the analytical table. Responsive and grid tables don't calculate sums.&lt;/li&gt;
&lt;li&gt;On the RAP side, add &lt;code&gt;@OData.applySupportedForAggregation: #FULL&lt;/code&gt; to the projection view header and &lt;code&gt;@Aggregation.default: #SUM&lt;/code&gt; to each measure in the same projection view.&lt;/li&gt;
&lt;li&gt;SAP documents RAP analytical tables for read-only business objects on a list report page, and on recent releases only (SAP BTP ABAP environment and S/4HANA Cloud from 2511).&lt;/li&gt;
&lt;li&gt;Annotate amounts and quantities with &lt;code&gt;@Semantics.amount.currencyCode&lt;/code&gt; or &lt;code&gt;@Semantics.quantity.unitOfMeasure&lt;/code&gt;. Mixed currencies are totalled per currency in a popup.&lt;/li&gt;
&lt;li&gt;If the sum is missing, check &lt;code&gt;$metadata&lt;/code&gt; for &lt;code&gt;Aggregation.ApplySupported&lt;/code&gt;, the table type in &lt;code&gt;manifest.json&lt;/code&gt;, the &lt;code&gt;total&lt;/code&gt; list in your presentation variant, and the &lt;code&gt;$apply&lt;/code&gt; in the network request.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Why the sum doesn't show in a normal List Report
&lt;/h2&gt;

&lt;p&gt;The SAPUI5 documentation for SAP Fiori elements for OData V4 lists four table types: responsive table, grid table, analytical table and tree table. Responsive and analytical tables can group rows, but only the analytical table is described with data aggregation ("automatically calculate sums, averages, and other aggregate functions"), and the &lt;a href="https://ui5.sap.com/#/topic/d344c5aa5c81483482dbbed5b3abb142" rel="noopener noreferrer"&gt;Table Groupings&lt;/a&gt; page says it directly: "For analytical tables, you can also define totals."&lt;/p&gt;

&lt;p&gt;So switching a List Report to &lt;code&gt;GridTable&lt;/code&gt; does not give you a totals row. You need an analytical table, and the analytical table needs an analytical service. According to &lt;a href="https://ui5.sap.com/#/topic/b51afc2c1c9a41bb8ac6055ccce2baab" rel="noopener noreferrer"&gt;Annotating a Service as an Analytical Service&lt;/a&gt;, that means the entity set supports &lt;code&gt;@Aggregation.ApplySupported&lt;/code&gt; and, for ABAP-based services, all of these transformations: &lt;code&gt;filter&lt;/code&gt;, &lt;code&gt;identity&lt;/code&gt;, &lt;code&gt;orderby&lt;/code&gt;, &lt;code&gt;skip&lt;/code&gt;, &lt;code&gt;top&lt;/code&gt;, &lt;code&gt;groupby&lt;/code&gt;, &lt;code&gt;concat&lt;/code&gt; and &lt;code&gt;aggregate&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;In RAP you don't write &lt;code&gt;Aggregation.ApplySupported&lt;/code&gt; yourself. One CDS annotation generates it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check your release first
&lt;/h2&gt;

&lt;p&gt;SAP calls this feature &lt;strong&gt;RAP analytical tables&lt;/strong&gt;. The &lt;a href="https://help.sap.com/docs/abap-cloud/abap-rap/rap-analytical-tables" rel="noopener noreferrer"&gt;RAP documentation&lt;/a&gt; describes them as available "in read-only scenarios and on a list report page", modelled on a projection view annotated with &lt;code&gt;@OData.applySupportedForAggregation: #FULL&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;SAP's &lt;a href="https://github.com/SAP-samples/abap-platform-codejam-latest-features-2602/wiki/Analytical-Table" rel="noopener noreferrer"&gt;ABAP CodeJam material for the feature&lt;/a&gt; lists the availability as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;SAP BTP, ABAP environment as of 2511&lt;/li&gt;
&lt;li&gt;SAP S/4HANA Cloud as of 2511&lt;/li&gt;
&lt;li&gt;SAP S/4HANA and SAP S/4HANA Cloud, private edition as of 2027&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If the annotation isn't accepted in your system, the release is the first thing to check. An SAP Community thread on exactly this problem was resolved by moving from 2508 to a newer release.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: the interface view
&lt;/h2&gt;

&lt;p&gt;Model the measures in the interface (or base) view and give every amount its currency and every quantity its unit. Fiori elements needs that reference to total each currency or unit separately.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;AccessControl&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;authorizationCheck&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;#&lt;/span&gt;&lt;span class="n"&gt;NOT_REQUIRED&lt;/span&gt;
&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;EndUserText&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;label&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'Sales order items (illustrative)'&lt;/span&gt;
&lt;span class="k"&gt;define&lt;/span&gt; &lt;span class="n"&gt;root&lt;/span&gt; &lt;span class="k"&gt;view&lt;/span&gt; &lt;span class="n"&gt;entity&lt;/span&gt; &lt;span class="n"&gt;ZI_SalesItemTotals&lt;/span&gt;
  &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;zsales_item&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;key&lt;/span&gt; &lt;span class="n"&gt;item_uuid&lt;/span&gt;     &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;ItemUUID&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;sales_order&lt;/span&gt;   &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;SalesOrder&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="k"&gt;customer&lt;/span&gt;      &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="k"&gt;Customer&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;material&lt;/span&gt;      &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;Material&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;Semantics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;amount&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;currencyCode&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'Currency'&lt;/span&gt;
      &lt;span class="n"&gt;net_amount&lt;/span&gt;    &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;NetAmount&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="k"&gt;currency&lt;/span&gt;      &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="k"&gt;Currency&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;Semantics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;quantity&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;unitOfMeasure&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'OrderUnit'&lt;/span&gt;
      &lt;span class="n"&gt;order_qty&lt;/span&gt;     &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;OrderQuantity&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;order_unit&lt;/span&gt;    &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;OrderUnit&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you need two different aggregations of the same field, for example a minimum and a maximum, the documentation's reference scenario selects the field twice under different aliases. Only one aggregate function can be used per element.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: the projection view exposed by the service
&lt;/h2&gt;

&lt;p&gt;This is where the aggregation is switched on. Both annotations go on the projection view that the service definition exposes:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;AccessControl&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;authorizationCheck&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;#&lt;/span&gt;&lt;span class="n"&gt;NOT_REQUIRED&lt;/span&gt;
&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;EndUserText&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;label&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'Sales item totals (illustrative)'&lt;/span&gt;
&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;Metadata&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;allowExtensions&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;true&lt;/span&gt;
&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;OData&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;applySupportedForAggregation&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;#&lt;/span&gt;&lt;span class="n"&gt;FULL&lt;/span&gt;
&lt;span class="k"&gt;define&lt;/span&gt; &lt;span class="n"&gt;root&lt;/span&gt; &lt;span class="k"&gt;view&lt;/span&gt; &lt;span class="n"&gt;entity&lt;/span&gt; &lt;span class="n"&gt;ZC_SalesItemTotals&lt;/span&gt;
  &lt;span class="n"&gt;provider&lt;/span&gt; &lt;span class="n"&gt;contract&lt;/span&gt; &lt;span class="n"&gt;transactional_query&lt;/span&gt;
  &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;projection&lt;/span&gt; &lt;span class="k"&gt;on&lt;/span&gt; &lt;span class="n"&gt;ZI_SalesItemTotals&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;key&lt;/span&gt; &lt;span class="n"&gt;ItemUUID&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;SalesOrder&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="k"&gt;Customer&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;Material&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;Aggregation&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="k"&gt;default&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;#&lt;/span&gt;&lt;span class="k"&gt;SUM&lt;/span&gt;
      &lt;span class="n"&gt;NetAmount&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="k"&gt;Currency&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;Aggregation&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="k"&gt;default&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;#&lt;/span&gt;&lt;span class="k"&gt;SUM&lt;/span&gt;
      &lt;span class="n"&gt;OrderQuantity&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;OrderUnit&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then expose it in an OData V4 UI service:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="k"&gt;define&lt;/span&gt; &lt;span class="n"&gt;service&lt;/span&gt; &lt;span class="n"&gt;ZUI_SALES_ITEM_TOTALS&lt;/span&gt;
  &lt;span class="n"&gt;provider&lt;/span&gt; &lt;span class="n"&gt;contracts&lt;/span&gt; &lt;span class="n"&gt;odata_v4_ui&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;expose&lt;/span&gt; &lt;span class="n"&gt;ZC_SalesItemTotals&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;SalesItem&lt;/span&gt;&lt;span class="err"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What SAP's &lt;a href="https://help.sap.com/docs/abap-cloud/abap-rap/annotating-aggregate-functions-in-cds" rel="noopener noreferrer"&gt;Annotating Aggregate Functions in CDS&lt;/a&gt; page says about these annotations:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The supported functions are &lt;code&gt;#SUM&lt;/code&gt;, &lt;code&gt;#MIN&lt;/code&gt;, &lt;code&gt;#MAX&lt;/code&gt;, &lt;code&gt;#AVG&lt;/code&gt; and &lt;code&gt;#COUNT_DISTINCT&lt;/code&gt;. &lt;code&gt;#MIN&lt;/code&gt; and &lt;code&gt;#MAX&lt;/code&gt; also work on dates.&lt;/li&gt;
&lt;li&gt;Only measures can carry an aggregation annotation, and only elements with numerical data types (plus dates for min and max).&lt;/li&gt;
&lt;li&gt;For &lt;code&gt;#SUM&lt;/code&gt;, use a numeric type large enough for the total.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;#COUNT_DISTINCT&lt;/code&gt; needs &lt;code&gt;@Aggregation.referenceElement: ['...']&lt;/code&gt;. SAP recommends a dedicated element for it, because a single row always counts as 1.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Elements without &lt;code&gt;@Aggregation.default&lt;/code&gt; become groupable automatically in a service with &lt;code&gt;@OData.applySupportedForAggregation: #FULL&lt;/code&gt;, as the SAPUI5 page &lt;a href="https://ui5.sap.com/#/topic/9062f11fb94f4781a61a7437a70e62fe" rel="noopener noreferrer"&gt;Defining Groupable Properties&lt;/a&gt; notes. You don't annotate dimensions separately.&lt;/p&gt;

&lt;p&gt;The base view in this example has no behavior definition, so the business object is read-only, which is the scenario SAP documents. SAP's &lt;a href="https://help.sap.com/docs/abap-cloud/abap-rap/developing-read-only-rap-analytical-tables" rel="noopener noreferrer"&gt;Developing Read-Only RAP Analytical Tables&lt;/a&gt; follows the same pattern with the &lt;code&gt;/DMO/C_TRAVEL_ANA&lt;/code&gt; reference objects from the ABAP Flight Reference Scenario. The same page notes that CDS entities annotated for RAP analytical tables aren't enabled for extensibility.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: grouping and the totals list
&lt;/h2&gt;

&lt;p&gt;By default, Fiori elements groups the records by the columns the user sees, because those are the elements in &lt;code&gt;$select&lt;/code&gt;. If you want every row to stay at item level, SAP's documentation suggests requesting the technical key in the presentation variant:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;UI&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;presentationVariant&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="n"&gt;requestAtLeast&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="s1"&gt;'ItemUUID'&lt;/span&gt; &lt;span class="p"&gt;],&lt;/span&gt;
                            &lt;span class="n"&gt;visualizations&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="k"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;#&lt;/span&gt;&lt;span class="n"&gt;AS_LINEITEM&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt;
&lt;span class="n"&gt;annotate&lt;/span&gt; &lt;span class="n"&gt;entity&lt;/span&gt; &lt;span class="n"&gt;ZC_SalesItemTotals&lt;/span&gt; &lt;span class="k"&gt;with&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;UI&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;lineItem&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="k"&gt;position&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt;  &lt;span class="n"&gt;SalesOrder&lt;/span&gt;&lt;span class="err"&gt;;&lt;/span&gt;
  &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;UI&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;lineItem&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="k"&gt;position&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;20&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt;  &lt;span class="k"&gt;Customer&lt;/span&gt;&lt;span class="err"&gt;;&lt;/span&gt;
  &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;UI&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;lineItem&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="k"&gt;position&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;30&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt;  &lt;span class="n"&gt;NetAmount&lt;/span&gt;&lt;span class="err"&gt;;&lt;/span&gt;
  &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;UI&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;lineItem&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="k"&gt;position&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;40&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt;  &lt;span class="n"&gt;OrderQuantity&lt;/span&gt;&lt;span class="err"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The presentation variant also decides which columns get a total. From &lt;a href="https://ui5.sap.com/#/topic/d344c5aa5c81483482dbbed5b3abb142" rel="noopener noreferrer"&gt;Table Groupings&lt;/a&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Without a presentation variant, every column with an aggregatable property gets a total.&lt;/li&gt;
&lt;li&gt;With a presentation variant, only the properties in its &lt;code&gt;total&lt;/code&gt; list get a total. If &lt;code&gt;total&lt;/code&gt; is missing, all aggregatable columns get one. If &lt;code&gt;total&lt;/code&gt; is defined but empty, none do.&lt;/li&gt;
&lt;li&gt;The presentation variant must have a &lt;code&gt;visualizations&lt;/code&gt; entry, or it is ignored.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So a presentation variant copied from another app with &lt;code&gt;total: []&lt;/code&gt; silently removes your sums. You can also set default groups and totals explicitly, for example &lt;code&gt;groupBy: [ 'Customer' ], total: [ 'NetAmount' ]&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Currencies and units
&lt;/h2&gt;

&lt;p&gt;Totals across currencies don't make sense, and Fiori elements doesn't add them up. The same Table Groupings page explains that if a group contains several units or currencies, the table shows a &lt;strong&gt;Show Details&lt;/strong&gt; link that opens a popup with the total or subtotal per unit or currency.&lt;/p&gt;

&lt;p&gt;On the model side, the &lt;a href="https://ui5.sap.com/#/topic/7d914317c0b64c23824bf932cc8a4ae1" rel="noopener noreferrer"&gt;OData V4 data aggregation documentation&lt;/a&gt; describes how each aggregatable property can carry its unit or currency, which returns a single value when there's only one, and &lt;code&gt;null&lt;/code&gt; in a "multi-unit situation". In RAP that reference comes from &lt;code&gt;@Semantics.amount.currencyCode&lt;/code&gt; and &lt;code&gt;@Semantics.quantity.unitOfMeasure&lt;/code&gt;. Without it, the framework can't tell 100 EUR from 100 USD.&lt;/p&gt;

&lt;p&gt;If users need one grand total in a single currency, the totals have to be converted in the back end first. SAP Fiori elements also documents analytical parameters for converting to a target currency at runtime, which is beyond the scope of this post.&lt;/p&gt;

&lt;h2&gt;
  
  
  The table type in manifest.json
&lt;/h2&gt;

&lt;p&gt;With an analytical service, you usually don't need to configure anything. &lt;a href="https://ui5.sap.com/#/topic/3fd4c37ff7964db9b00f80841f7a7bce" rel="noopener noreferrer"&gt;Determining the Default Table Type&lt;/a&gt; says the List Report defaults to the analytical table when the entity set has &lt;code&gt;Aggregation.ApplySupported&lt;/code&gt; with all the transformations listed above, and to a responsive table otherwise.&lt;/p&gt;

&lt;p&gt;If the app was generated earlier with an explicit table type, it may still say &lt;code&gt;ResponsiveTable&lt;/code&gt; or &lt;code&gt;GridTable&lt;/code&gt;. Set it as described in &lt;a href="https://ui5.sap.com/#/topic/7f844f1021cd4791b8f7408eac7c1cec" rel="noopener noreferrer"&gt;Setting the Table Type&lt;/a&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="nl"&gt;"targets"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"SalesItemList"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Component"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"sap.fe.templates.ListReport"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"options"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"settings"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="nl"&gt;"controlConfiguration"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
          &lt;/span&gt;&lt;span class="nl"&gt;"@com.sap.vocabularies.UI.v1.LineItem"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
            &lt;/span&gt;&lt;span class="nl"&gt;"tableSettings"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"AnalyticalTable"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
          &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
        &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The documented catch: if you set &lt;code&gt;AnalyticalTable&lt;/code&gt; and the entity set has no analytical capabilities, the result is an &lt;strong&gt;empty table&lt;/strong&gt;. So a List Report that shows no rows right after a table-type change usually means the service side isn't done yet.&lt;/p&gt;

&lt;p&gt;A few documented restrictions of analytical tables that are worth knowing before you promise them to users:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The table only displays properties that are groupable or aggregatable. Anything else isn't requested and stays empty.&lt;/li&gt;
&lt;li&gt;Navigation properties aren't supported. A &lt;code&gt;LineItem&lt;/code&gt; column pointing to one stays empty.&lt;/li&gt;
&lt;li&gt;Micro charts, multi-line content such as &lt;code&gt;FieldGroup&lt;/code&gt; columns, and multi-input fields aren't supported.&lt;/li&gt;
&lt;li&gt;With &lt;code&gt;aggregationOnLeafLevel: true&lt;/code&gt;, navigation and bound actions are only enabled when all key properties are visible in the table (&lt;a href="https://ui5.sap.com/#/topic/d230e371357b402fba3c3af8dfd0538e" rel="noopener noreferrer"&gt;Aggregation Based on Visible Properties&lt;/a&gt;).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Draft and transactional apps
&lt;/h2&gt;

&lt;p&gt;This is the most common disappointment. RAP's documentation scopes RAP analytical tables to read-only business objects. The SAPUI5 SDK does describe &lt;a href="https://ui5.sap.com/#/topic/8ad8d795e0b14ce79325cc0a4b383dcc" rel="noopener noreferrer"&gt;analytical tables with a draft-enabled service&lt;/a&gt;: only active entities are shown, the Editing Status filter is hidden, and the combination isn't available in the flexible column layout. Those are general Fiori elements rules, though, and they don't change what RAP supports for your ABAP service.&lt;/p&gt;

&lt;p&gt;In practice, if your users need both an editable List Report and totals, plan for a separate read-only projection and service for the analytical list, and keep the transactional app as it is. Check the ABAP platform roadmap and the release notes for your system before you design around anything newer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the service before you blame the UI
&lt;/h2&gt;

&lt;p&gt;Two checks take a few minutes and settle most cases.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. The $metadata document.&lt;/strong&gt; Open the service URL with &lt;code&gt;/$metadata&lt;/code&gt; (from the service binding in ADT, or from the browser's network tab). On the entity set or entity type, look for the &lt;code&gt;Aggregation.ApplySupported&lt;/code&gt; annotation and its &lt;code&gt;Transformations&lt;/code&gt; collection. It should contain all of &lt;code&gt;filter&lt;/code&gt;, &lt;code&gt;identity&lt;/code&gt;, &lt;code&gt;orderby&lt;/code&gt;, &lt;code&gt;skip&lt;/code&gt;, &lt;code&gt;top&lt;/code&gt;, &lt;code&gt;groupby&lt;/code&gt;, &lt;code&gt;concat&lt;/code&gt; and &lt;code&gt;aggregate&lt;/code&gt;. If it's missing, &lt;code&gt;@OData.applySupportedForAggregation: #FULL&lt;/code&gt; isn't on the projection view that is actually exposed, or the release doesn't support it. The SAPUI5 SDK's &lt;a href="https://ui5.sap.com/#/topic/564ac6e999a04097b227dd469c4a4d4f" rel="noopener noreferrer"&gt;Defining Aggregatable Properties&lt;/a&gt; shows how an aggregatable property looks in metadata, with &lt;code&gt;Aggregation.CustomAggregate&lt;/code&gt; qualified by the property name.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. The data request.&lt;/strong&gt; Open the browser's developer tools, go to the Network tab, filter for &lt;code&gt;$batch&lt;/code&gt;, and look at the GET request for your entity set inside the batch. An analytical table doesn't send a plain &lt;code&gt;$select&lt;/code&gt;. The OData V4 model derives a &lt;code&gt;$apply&lt;/code&gt; system query option from the grouping and aggregation, so you should see &lt;code&gt;$apply&lt;/code&gt; with &lt;code&gt;groupby&lt;/code&gt; and &lt;code&gt;aggregate&lt;/code&gt;. If you see a normal &lt;code&gt;$select ... $top&lt;/code&gt; request with no &lt;code&gt;$apply&lt;/code&gt;, the app isn't using the analytical table.&lt;/p&gt;

&lt;h2&gt;
  
  
  OData V2
&lt;/h2&gt;

&lt;p&gt;Most new RAP development uses OData V4 UI services, and the RAP analytical table described above is documented for OData V4. If you maintain a Fiori elements app for OData V2, the logic for the table type is different. According to the V2 page &lt;a href="https://ui5.sap.com/#/topic/5d270547f113468e83e06dd7ee408a45" rel="noopener noreferrer"&gt;Setting the Table Type&lt;/a&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Without a configured type, an aggregate-based service gets an analytical table, and any other service gets a responsive table.&lt;/li&gt;
&lt;li&gt;For an analytical table on the List Report, the entity type must have &lt;code&gt;sap:semantics="aggregate"&lt;/code&gt;. That is a back-end setting.&lt;/li&gt;
&lt;li&gt;If you configure &lt;code&gt;AnalyticalTable&lt;/code&gt; and the entity set has no analytical capabilities, the V2 template falls back to a grid table instead of showing an empty table.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The RAP documentation has a separate topic on the &lt;a href="https://help.sap.com/docs/abap-cloud/abap-rap/odata-v2-interpretation-of-aggregation-annotations" rel="noopener noreferrer"&gt;OData V2 interpretation of aggregation annotations&lt;/a&gt;. Check it for your release rather than assuming the V4 behaviour.&lt;/p&gt;

&lt;h2&gt;
  
  
  Troubleshooting checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Release.&lt;/strong&gt; Does your system support &lt;code&gt;@OData.applySupportedForAggregation&lt;/code&gt;? On BTP ABAP environment and S/4HANA Cloud it's 2511 or later.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Right view.&lt;/strong&gt; Are both annotations on the projection view that the service definition exposes, not only on the interface view?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Read-only.&lt;/strong&gt; Is the business object read-only? RAP analytical tables are documented for that scenario.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Numeric measures.&lt;/strong&gt; Is the summed element numeric, with a type big enough for the total?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Currency and unit.&lt;/strong&gt; Do amounts and quantities have &lt;code&gt;@Semantics.amount.currencyCode&lt;/code&gt; or &lt;code&gt;@Semantics.quantity.unitOfMeasure&lt;/code&gt;? Mixed currencies show "Show Details" instead of one total, which is the expected behaviour.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;$metadata.&lt;/strong&gt; Is &lt;code&gt;Aggregation.ApplySupported&lt;/code&gt; present with all eight transformations?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Table type.&lt;/strong&gt; Is &lt;code&gt;manifest.json&lt;/code&gt; forcing &lt;code&gt;ResponsiveTable&lt;/code&gt; or &lt;code&gt;GridTable&lt;/code&gt;? Remove the setting or set &lt;code&gt;AnalyticalTable&lt;/code&gt;. An empty table after this change points back to the service.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Presentation variant.&lt;/strong&gt; Is there a &lt;code&gt;total: []&lt;/code&gt;, or a presentation variant without &lt;code&gt;visualizations&lt;/code&gt;?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Network.&lt;/strong&gt; Does the list request contain &lt;code&gt;$apply&lt;/code&gt;?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Columns.&lt;/strong&gt; Are the columns groupable or aggregatable properties, not navigation properties?&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why AI assistants get this wrong
&lt;/h2&gt;

&lt;p&gt;Ask a general-purpose AI assistant how to sum a column in a Fiori List Report and you'll often get &lt;code&gt;@Aggregation.default: #SUM&lt;/code&gt; on its own, &lt;code&gt;@DefaultAggregation&lt;/code&gt; from older analytical CDS views, or advice to switch to a grid table. None of these produces a totals row in an OData V4 RAP app by itself. The feature is new, depends on the release, and is spread across the RAP documentation and the SAPUI5 SDK, so it's thin in the code that models learn from.&lt;/p&gt;

&lt;p&gt;The fix is the same as for other ABAP topics: tell the assistant your release and your OData version, and keep the rule where it reads it on every request, for example "Totals in a Fiori elements V4 List Report need a read-only RAP analytical table: &lt;code&gt;@OData.applySupportedForAggregation: #FULL&lt;/code&gt; on the exposed projection view, plus &lt;code&gt;@Aggregation.default&lt;/code&gt; on the measures." For more patterns like this one, see &lt;a href="https://abapforagents.com/guides/ai-abap-mistakes/" rel="noopener noreferrer"&gt;ABAP mistakes AI coding assistants make&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Free MIT-licensed ABAP rules for Cursor, Claude Code and Copilot are on &lt;a href="https://github.com/abapforagents/abap-for-agents-lite" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;, and there are more guides at &lt;a href="https://abapforagents.com/guides/" rel="noopener noreferrer"&gt;abapforagents.com/guides&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>abap</category>
      <category>sap</category>
      <category>fiori</category>
      <category>odata</category>
    </item>
    <item>
      <title>9 ABAP mistakes AI coding assistants keep making (and how to prevent them)</title>
      <dc:creator>ABAP for Agents</dc:creator>
      <pubDate>Tue, 27 Oct 2026 10:14:31 +0000</pubDate>
      <link>https://dev.to/abapforagents/9-abap-mistakes-ai-coding-assistants-keep-making-and-how-to-prevent-them-35nm</link>
      <guid>https://dev.to/abapforagents/9-abap-mistakes-ai-coding-assistants-keep-making-and-how-to-prevent-them-35nm</guid>
      <description>&lt;p&gt;AI coding assistants are great at languages with millions of public examples. ABAP isn't one of them, and it trips them up in two specific ways:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The language changes a lot between releases.&lt;/strong&gt; Code that activates on S/4HANA 2023 can be a syntax error on an ECC system running SAP_BASIS 7.50.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Most of what you call lives inside SAP systems, not on GitHub.&lt;/strong&gt; Function modules, BAPIs, CDS views and tables aren't public, so the model can't check whether they exist. It guesses, and the guesses look convincing.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The result is a small set of mistakes that come back again and again, whether you use Cursor, Claude Code or GitHub Copilot. Here are nine of them, with the fix for each.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Tell the assistant your language version, product and SAP_BASIS release first. Most wrong ABAP is valid syntax from a different release.&lt;/li&gt;
&lt;li&gt;Guard every &lt;code&gt;FOR ALL ENTRIES&lt;/code&gt; with &lt;code&gt;IF itab IS NOT INITIAL&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Plausible names prove nothing. Verify every SAP object the assistant uses.&lt;/li&gt;
&lt;li&gt;Table expressions don't set &lt;code&gt;sy-subrc&lt;/code&gt;, BAPIs report errors in &lt;code&gt;RETURN&lt;/code&gt;, and RAP owns the LUW.&lt;/li&gt;
&lt;li&gt;Put these points in a short rules file and keep ATC and ABAP Unit as the real gate.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  1. Syntax from the wrong release
&lt;/h2&gt;

&lt;p&gt;The assistant doesn't know which system you're on, so it writes the newest syntax it has seen. Some availability dates worth knowing (from SAP's ABAP Keyword Documentation release notes):&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Feature&lt;/th&gt;
&lt;th&gt;Available from&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Inline declarations &lt;code&gt;DATA(...)&lt;/code&gt;, &lt;code&gt;NEW&lt;/code&gt;, &lt;code&gt;VALUE&lt;/code&gt;, table expressions&lt;/td&gt;
&lt;td&gt;7.40 SP02&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ABAP SQL &lt;code&gt;@&lt;/code&gt; host variables, comma-separated lists (strict mode)&lt;/td&gt;
&lt;td&gt;7.40 SP05&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Inline target &lt;code&gt;INTO TABLE @DATA(...)&lt;/code&gt; in ABAP SQL&lt;/td&gt;
&lt;td&gt;7.40 SP08&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;xsdbool( )&lt;/code&gt;, &lt;code&gt;REDUCE&lt;/code&gt;, &lt;code&gt;FILTER&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;7.40 SP08&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;RAISE EXCEPTION NEW&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;7.52&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Calculation assignments &lt;code&gt;+=&lt;/code&gt;, &lt;code&gt;-=&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;7.54&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CDS view entities &lt;code&gt;define view entity&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;7.55&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;ECC 6.0 runs on SAP_BASIS 7.50 at most (EHP8), so &lt;code&gt;x += 1.&lt;/code&gt; won't compile there, and neither will a view entity. On 7.40 SP05 to SP07, this is a syntax error:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="n"&gt;vbeln&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;erdat&lt;/span&gt; &lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="n"&gt;vbak&lt;/span&gt;
  &lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;erdat&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;date_from&lt;/span&gt;
  &lt;span class="k"&gt;INTO&lt;/span&gt; &lt;span class="k"&gt;TABLE&lt;/span&gt; &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="k"&gt;DATA&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;orders&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;   &lt;span class="c1"&gt;" needs 7.40 SP08&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The SP05-safe version declares the target first:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="k"&gt;TYPES&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="k"&gt;BEGIN&lt;/span&gt; &lt;span class="k"&gt;OF&lt;/span&gt; &lt;span class="n"&gt;ty_order&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
         &lt;span class="n"&gt;vbeln&lt;/span&gt; &lt;span class="k"&gt;TYPE&lt;/span&gt; &lt;span class="n"&gt;vbak&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;vbeln&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
         &lt;span class="n"&gt;erdat&lt;/span&gt; &lt;span class="k"&gt;TYPE&lt;/span&gt; &lt;span class="n"&gt;vbak&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;erdat&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
       &lt;span class="k"&gt;END&lt;/span&gt; &lt;span class="k"&gt;OF&lt;/span&gt; &lt;span class="n"&gt;ty_order&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
&lt;span class="k"&gt;DATA&lt;/span&gt; &lt;span class="n"&gt;orders&lt;/span&gt; &lt;span class="k"&gt;TYPE&lt;/span&gt; &lt;span class="k"&gt;STANDARD&lt;/span&gt; &lt;span class="k"&gt;TABLE&lt;/span&gt; &lt;span class="k"&gt;OF&lt;/span&gt; &lt;span class="n"&gt;ty_order&lt;/span&gt; &lt;span class="k"&gt;WITH&lt;/span&gt; &lt;span class="k"&gt;EMPTY&lt;/span&gt; &lt;span class="k"&gt;KEY&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;

&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="n"&gt;vbeln&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;erdat&lt;/span&gt; &lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="n"&gt;vbak&lt;/span&gt;
  &lt;span class="k"&gt;INTO&lt;/span&gt; &lt;span class="k"&gt;TABLE&lt;/span&gt; &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;orders&lt;/span&gt;
  &lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;erdat&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;date_from&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prevention:&lt;/strong&gt; give the assistant three facts before it writes a line: language version (ABAP for Cloud Development or Standard ABAP), product (S/4HANA or ECC) and release. If you can't, tell it to assume the lowest plausible release and never mix syntax from different releases in one answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. FOR ALL ENTRIES on an empty table
&lt;/h2&gt;

&lt;p&gt;This one activates fine and passes a quick test, which is why it's dangerous. If the internal table after &lt;code&gt;FOR ALL ENTRIES IN&lt;/code&gt; is empty, the whole &lt;code&gt;WHERE&lt;/code&gt; clause is ignored and every row of the database table is read.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="k"&gt;IF&lt;/span&gt; &lt;span class="k"&gt;keys&lt;/span&gt; &lt;span class="k"&gt;IS&lt;/span&gt; &lt;span class="k"&gt;NOT&lt;/span&gt; &lt;span class="k"&gt;INITIAL&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
  &lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="n"&gt;vbeln&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;erdat&lt;/span&gt; &lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="n"&gt;vbak&lt;/span&gt;
    &lt;span class="k"&gt;FOR&lt;/span&gt; &lt;span class="k"&gt;ALL&lt;/span&gt; &lt;span class="k"&gt;ENTRIES&lt;/span&gt; &lt;span class="k"&gt;IN&lt;/span&gt; &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="k"&gt;keys&lt;/span&gt;
    &lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;vbeln&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="k"&gt;keys&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;vbeln&lt;/span&gt;
    &lt;span class="k"&gt;INTO&lt;/span&gt; &lt;span class="k"&gt;TABLE&lt;/span&gt; &lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="k"&gt;DATA&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;orders&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;
&lt;span class="k"&gt;ENDIF&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;FOR ALL ENTRIES&lt;/code&gt; also removes duplicate result rows, so select all key fields or you lose data silently. There's a full walkthrough in &lt;a href="https://abapforagents.com/guides/for-all-entries-empty-table/" rel="noopener noreferrer"&gt;FOR ALL ENTRIES with an empty table&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Invented function modules, BAPIs and CDS views
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;Z_GET_ORDER_STATUS&lt;/code&gt;, &lt;code&gt;I_SomethingView&lt;/code&gt;, &lt;code&gt;BAPI_WHATEVER&lt;/code&gt;: invented names follow SAP's naming conventions, so they read as real. A model will also invent parameter names for function modules that do exist.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prevention:&lt;/strong&gt; require the assistant to name every SAP object it relies on and to flag the ones it isn't sure about. Then check them yourself: "Open ABAP Development Object" in ADT, SE37/SE24/SE11 in SAP GUI, or SAP's Cloudification Repository for the release state. In ABAP Cloud only released objects are allowed, and an &lt;code&gt;I_&lt;/code&gt; prefix is not proof of either existence or release.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Checking sy-subrc after a table expression
&lt;/h2&gt;

&lt;p&gt;Models trained on classic &lt;code&gt;READ TABLE&lt;/code&gt; code write this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="k"&gt;DATA&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;item&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;items&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="k"&gt;id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;key&lt;/span&gt; &lt;span class="p"&gt;].&lt;/span&gt;
&lt;span class="k"&gt;IF&lt;/span&gt; &lt;span class="n"&gt;sy&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;subrc&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;       &lt;span class="c1"&gt;" never reached on a miss&lt;/span&gt;
  &lt;span class="p"&gt;...&lt;/span&gt;
&lt;span class="k"&gt;ENDIF&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A table expression doesn't set &lt;code&gt;sy-subrc&lt;/code&gt;. If the line isn't found it raises &lt;code&gt;CX_SY_ITAB_LINE_NOT_FOUND&lt;/code&gt;, and without a &lt;code&gt;TRY&lt;/code&gt; block the program dumps. Use one of these instead:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="k"&gt;IF&lt;/span&gt; &lt;span class="nb"&gt;line_exists&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="n"&gt;items&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="k"&gt;id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;key&lt;/span&gt; &lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;).&lt;/span&gt;
  &lt;span class="p"&gt;...&lt;/span&gt;
&lt;span class="k"&gt;ENDIF&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;

&lt;span class="c1"&gt;" 7.40 SP08+: initial value instead of an exception&lt;/span&gt;
&lt;span class="n"&gt;item&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;VALUE&lt;/span&gt; &lt;span class="o"&gt;#&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="n"&gt;items&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="k"&gt;id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;key&lt;/span&gt; &lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="k"&gt;OPTIONAL&lt;/span&gt; &lt;span class="p"&gt;).&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;(The exception: &lt;code&gt;ASSIGN items[ id = key ] TO &amp;lt;item&amp;gt;.&lt;/code&gt; does set &lt;code&gt;sy-subrc&lt;/code&gt; and raises nothing.)&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Java, C# and JavaScript habits
&lt;/h2&gt;

&lt;p&gt;ABAP looks enough like other languages for the model to slip:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="k"&gt;IF&lt;/span&gt; &lt;span class="n"&gt;a&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="kt"&gt;b&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;          &lt;span class="c1"&gt;" wrong: ABAP uses &amp;lt;&amp;gt;&lt;/span&gt;
&lt;span class="k"&gt;i&lt;/span&gt;&lt;span class="o"&gt;++&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;                &lt;span class="c1"&gt;" wrong: no ++ operator&lt;/span&gt;
&lt;span class="kt"&gt;s&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="c1"&gt;"text".         " wrong: " starts a comment&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The correct forms are &lt;code&gt;IF a &amp;lt;&amp;gt; b.&lt;/code&gt;, &lt;code&gt;i = i + 1.&lt;/code&gt; (or &lt;code&gt;i += 1.&lt;/code&gt; from 7.54) and &lt;code&gt;s = `text`.&lt;/code&gt; with backquotes or single quotes. There is no &lt;code&gt;null&lt;/code&gt; either: use &lt;code&gt;IS INITIAL&lt;/code&gt; or &lt;code&gt;IS NOT BOUND&lt;/code&gt;. And &lt;code&gt;RETURN value.&lt;/code&gt; only exists in functional methods from 7.58 (ABAP Cloud 2211); below that, assign the returning parameter and then &lt;code&gt;RETURN.&lt;/code&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  6. boolc( ) instead of xsdbool( )
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;boolc( )&lt;/code&gt; returns a &lt;code&gt;string&lt;/code&gt;, not &lt;code&gt;abap_bool&lt;/code&gt;, which can surprise you in comparisons. &lt;code&gt;xsdbool( )&lt;/code&gt; returns type &lt;code&gt;c&lt;/code&gt; length 1 and works with &lt;code&gt;abap_true&lt;/code&gt; / &lt;code&gt;abap_false&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="k"&gt;DATA&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;is_late&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;xsdbool&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="n"&gt;due_date&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="n"&gt;today&lt;/span&gt; &lt;span class="p"&gt;).&lt;/span&gt;
&lt;span class="k"&gt;IF&lt;/span&gt; &lt;span class="n"&gt;is_late&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;abap_true&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
  &lt;span class="p"&gt;...&lt;/span&gt;
&lt;span class="k"&gt;ENDIF&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  7. Classic ABAP inside ABAP Cloud
&lt;/h2&gt;

&lt;p&gt;In ABAP for Cloud Development, &lt;code&gt;sy-datum&lt;/code&gt;, &lt;code&gt;WRITE&lt;/code&gt;, &lt;code&gt;SUBMIT&lt;/code&gt;, &lt;code&gt;CALL TRANSACTION&lt;/code&gt;, direct reads of SAP tables like &lt;code&gt;VBAK&lt;/code&gt; and non-released function modules are not allowed. Assistants reach for them first because that's what most public ABAP looks like. For the date, use the released class:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="k"&gt;DATA&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;today&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;cl_abap_context_info&lt;/span&gt;&lt;span class="o"&gt;=&amp;gt;&lt;/span&gt;&lt;span class="n"&gt;get_system_date&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="p"&gt;).&lt;/span&gt;   &lt;span class="c1"&gt;" UTC&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That returns the system date in UTC. For the user's local date, SAP points to the XCO library with the user time zone.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. COMMIT WORK inside a RAP handler
&lt;/h2&gt;

&lt;p&gt;In the ABAP RESTful Application Programming Model (RAP), the framework owns the logical unit of work. &lt;code&gt;COMMIT WORK&lt;/code&gt;, &lt;code&gt;ROLLBACK WORK&lt;/code&gt;, &lt;code&gt;COMMIT ENTITIES&lt;/code&gt; and &lt;code&gt;ROLLBACK ENTITIES&lt;/code&gt; don't belong in behavior handler or saver methods. Errors go back through the &lt;code&gt;failed&lt;/code&gt; and &lt;code&gt;reported&lt;/code&gt; structures, not through &lt;code&gt;MESSAGE&lt;/code&gt; or exceptions. Many classic BAPIs commit internally, so they must not be called in the interaction phase either.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. Ignoring the BAPI RETURN table
&lt;/h2&gt;

&lt;p&gt;BAPIs don't raise exceptions or set &lt;code&gt;sy-subrc&lt;/code&gt; for business errors. They fill a &lt;code&gt;RETURN&lt;/code&gt; table, so read it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight abap"&gt;&lt;code&gt;&lt;span class="k"&gt;DATA&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="k"&gt;TYPE&lt;/span&gt; &lt;span class="k"&gt;STANDARD&lt;/span&gt; &lt;span class="k"&gt;TABLE&lt;/span&gt; &lt;span class="k"&gt;OF&lt;/span&gt; &lt;span class="n"&gt;bapiret2&lt;/span&gt; &lt;span class="k"&gt;WITH&lt;/span&gt; &lt;span class="k"&gt;EMPTY&lt;/span&gt; &lt;span class="k"&gt;KEY&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
&lt;span class="c1"&gt;" ... call the BAPI, passing return ...&lt;/span&gt;
&lt;span class="k"&gt;IF&lt;/span&gt; &lt;span class="nb"&gt;line_exists&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="k"&gt;type&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'E'&lt;/span&gt; &lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;OR&lt;/span&gt; &lt;span class="nb"&gt;line_exists&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="k"&gt;type&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'A'&lt;/span&gt; &lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;).&lt;/span&gt;
  &lt;span class="c1"&gt;" handle the error, do not commit&lt;/span&gt;
&lt;span class="k"&gt;ENDIF&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Commit separately with &lt;code&gt;BAPI_TRANSACTION_COMMIT&lt;/code&gt;, and not once per record inside a loop.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to stop repeating these corrections
&lt;/h2&gt;

&lt;p&gt;You can paste these reminders into every prompt, but it's easier to put them in the file your tool reads automatically:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Cursor:&lt;/strong&gt; project rules in &lt;code&gt;.cursor/rules/*.mdc&lt;/code&gt; (&lt;a href="https://abapforagents.com/guides/cursor-rules-sap-abap/" rel="noopener noreferrer"&gt;setup guide&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Claude Code, Codex and other agents:&lt;/strong&gt; &lt;code&gt;AGENTS.md&lt;/code&gt;, imported from &lt;code&gt;CLAUDE.md&lt;/code&gt; (&lt;a href="https://abapforagents.com/guides/claude-code-agents-md-abap/" rel="noopener noreferrer"&gt;guide&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GitHub Copilot:&lt;/strong&gt; &lt;code&gt;.github/copilot-instructions.md&lt;/code&gt; plus path-specific instructions (&lt;a href="https://abapforagents.com/guides/github-copilot-instructions-abap/" rel="noopener noreferrer"&gt;guide&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep these files short. Every always-on line costs context, and long instruction files are followed less reliably. A good rules file states the target release, forbids invented objects, lists the traps above and ends with a self-check the assistant runs before answering.&lt;/p&gt;

&lt;p&gt;Rules are guidance, not enforcement. The assistant can still ignore them, so keep the syntax check, ATC and ABAP Unit as your gate, and run them on everything AI-generated before it reaches a transport.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Free MIT-licensed ABAP rules for Cursor, Claude Code and Copilot are on &lt;a href="https://github.com/abapforagents/abap-for-agents-lite" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;, and there are more guides at &lt;a href="https://abapforagents.com/guides/" rel="noopener noreferrer"&gt;abapforagents.com/guides&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>abap</category>
      <category>sap</category>
      <category>ai</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
