Our Fiori analytical apps for order-to-cash cycle are showing outdated data after billing documents are posted. The KPI tiles on the launchpad display revenue and invoice counts that are 2-4 hours behind actual postings in VF01/VF04. We’re on S/4HANA 1809 and using standard Fiori apps for sales analytics.
I’m trying to understand if this is a data replication issue versus a live CDS view problem. When I check the billing tables directly in SE16, the data is there immediately, but the analytics don’t reflect it. Could this be related to how the billing document tables are joined in the underlying CDS views, or is there some kind of analytics cache that needs refreshing?
Our business users are complaining because they make decisions based on these dashboards, and the delay is causing issues with credit management and collections follow-up.
Have you checked if accounting documents are being created in real-time or in background? Sometimes billing posts immediately but the FI document creation is scheduled, which can cause analytics delays if your KPIs include revenue recognition data that depends on accounting postings.
I had a similar issue and it turned out the CDS views weren’t using the right billing tables. Standard S/4HANA billing uses VBRK/VBRP, but some custom scenarios write to different tables first. Check your CDS view definition - is it reading directly from VBRK or going through intermediate views? If there are multiple view layers with associations, data might not propagate immediately. Also look at whether @Analytics.dataCategory is set correctly on the consumption view.
In 1809, the order-to-cash Fiori apps can use either live CDS views or replicated data depending on configuration. The fact that you see data in SE16 immediately but not in analytics suggests the CDS views might be using buffering or there’s a scheduled job that updates analytical snapshots. Check transaction RSANWB_CDS to see if your billing CDS views are registered for analytical queries and what their refresh mode is. You might have delta queue processing that runs periodically rather than real-time updates. For true real-time analytics, you need CDS views with @Analytics.query: true and no intermediate buffering layers.
This sounds like a CDS view cache issue to me. Fiori apps cache analytical queries for performance reasons. Try transaction /IWFND/MAINT_SERVICE and check your OData service cache settings. You might need to reduce the cache expiration time or force a refresh after billing posts. Also verify the $metadata of your OData service to see if it’s marked as cacheable.