Filling Missing Date Records in CDS Views: Calendar View vs ABAP Variable

Sara Kim breaks down what you need to know

I’ve lost count of how many times a “complete” daily sales report showed blank rows for weekends or holidays—until someone asked why the monthly total didn’t match the ledger. Missing date records in ABAP CDS views are a classic silent bug: they don’t throw errors, they just quietly distort aggregates and averages.

The core problem is simple: your source CDS view only contains rows for dates where something happened. But business users need a continuous timeline, even if the value is zero or null. You can’t just tell them “no data” for those days. So how do you fill the gaps? In the SAP ecosystem, two approaches dominate: joining with a calendar CDS view or generating the missing rows using ABAP logic (usually via AMDP or table functions). Let me break down what actually works.

The Real Story: Declarative vs. Procedural

ABAP CDS views are declarative—you define what to select, not how to loop and insert. That means you cannot directly write procedural ABAP code (like DO loops with variables) inside a plain CDS view definition. When developers ask about “using an ABAP variable to populate missing records,” they usually mean one of two things:

1. Using input parameters on a CDS view, then filling those parameters from ABAP at runtime. This doesn’t create new rows by itself; it just filters existing data differently.
2. Using a table function (AMDP) that executes procedural ABAP to generate a complete date series, which is then exposed as a CDS view entity. This does create new rows.

But before you dive into procedural code, ask yourself: Do I actually need AMDP, or can I solve this with a join? In 90% of cases, a calendar CDS view is the cleaner, more maintainable solution—if such a view exists or can be built once.

What This Means for You

Option 1: Join with a Calendar CDS View (Recommended)

If you’re on S/4HANA, you likely already have the standard I_CalendarDate CDS view. It provides a row for every date in a wide range, with helpful attributes like CalendarYear, CalendarMonth, Weekday, and IsHoliday. If you don’t have that, you can create your own reusable calendar view using a table function or a database-specific date generation technique.

The pattern is straightforward: left outer join from the calendar to your source view. The calendar is the left side because you want every date, even when no source record exists. Then use COALESCE to fill missing measures with zero or another default.

Here’s a practical example. Suppose you have a sales order count view ZI_SalesOrders with OrderDate and OrderCount. To get a complete daily series:

@AbapCatalog.sqlViewName: 'ZI_SALES_DAILY'
@AbapCatalog.compiler.compareFilter: true
@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: 'Daily Sales with Complete Dates'
define view ZI_SalesDaily as
  select from I_CalendarDate as cal
    left outer join ZI_SalesOrders as so
      on cal.CalendarDate = so.OrderDate
{
  cal.CalendarDate as OrderDate,
  coalesce(so.OrderCount, 0) as OrderCount
}

The key insight: the calendar side drives the output. This ensures no gaps, and the COALESCE fills numeric zeros. For character or amount fields, you might use coalesce(so.CustomerName, 'Unknown') or just leave null if the consumer prefers.

Pros: Reusable across many views, declarative, easy to read, no procedural code. Cons: You need a calendar view with all required dates. If your date range is dynamic (e.g., filter by user input), you may need to restrict the calendar join with an additional where clause, which still works fine.

Option 2: Generate Dates in ABAP (Table Function / AMDP)

Sometimes the calendar view approach isn’t enough—for example, you need to generate dates based on a parameter that isn’t a simple range, or you want to include complex business logic for default values. In that case, use a table function with AMDP

References

• Populate records in a cds view with abap variable- ABAP Development Guide
• SAP AI Core Documentation

References

• ABAP Development Guide
• SAP AI Core Documentation
• Populate records in a cds view with abap variable