We are experiencing a critical data consistency issue with the Stock on Posting Date report. The report shows different closing stock values when executed simultaneously across multiple user sessions, despite no manual entries being passed by the team.
Observations
Scenario 1: Sequential Retrievals (Same Login)
First retrieval: 1,433,243,957 units
Second retrieval: 1,433,223,314 units
Difference: 20,643 units
Time interval: 2 minutes
No manual entries were posted between retrievals
Scenario 2: Simultaneous Multi-Session Execution
Ran the same report simultaneously on 3-4 different (or same) user logins
Each session returned different stock values from the same report
No parameter variations were made
Questions & Concerns
Why does the same report show different values when run simultaneously across different sessions? This suggests either a data consistency issue or query execution problem rather than timing-related variance.
What could cause a 20,643 unit variance within a 2-minute interval when no manual transactions have been posted?
Is this expected behavior in SAP S/4HANA Cloud, or does this indicate:
Database lock contention or transaction isolation issues?
Uncommitted transactions being read differently by different sessions?
Cache synchronization problems?
Authorization/User Exit filtering differences?
Investigation Performed
Confirmed no manual journal entries or goods movements were posted by the team during the test period
Verified that all report executions used identical parameters and variant settings
Confirmed the issue occurs consistently across multiple simultaneous sessions
#SAP-S4HANA-Cloud #Inventory #Stock-Management #Data-Consistency #Reporting
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.