cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Data upload in Datasphere error

alvaroaguilar
Member
0 Likes
1,186

Good evening,

Currently, and due to the necessities of the project, we created a workaround alternative solution to carry out delta data loads. This workaround is carried out on the ACDOCA/BSEG remote tables. These data uploads are currently being carried out the night before the current day (the data up to yesterday will be displayed today). The problem/risk we face is that the 'posting date' date field (despite uploading the night before the current day) is currently being reflected as 2 days old (instead of 1). For example: We uploaded on December 14th the data up to December 13, but in Datasphere it only appeared data up to December 12 (two days ago instead of one). Does anyone know why the 'posting date' is not loaded correctly on date Dec.13 but is reflected on day Dec.12?

The workaround we implemented was accepted by our client, but the delay on the data upload is negatively impacting their business since the reports are not up to date. Hope someone can help us in order to figure out why is this happening or how to solve it. Regards!

Accepted Solutions (0)

Answers (1)

Answers (1)

cardoso
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi alvaroaguilar,

I'm not sure how you implemented the delta, but you might consider KBA 3155988 - Delay in real-time data replication for ABAP based connections.
In some scenarios, there might be a delay up to one day until a real-time replication reaches Datasphere.
In this blog post, I mentioned some details about the heuristic which are also mentioned in the KBA.

BR.