Skip to main content
After a connection with SAP ECC is made and the optimal execution order is calculated, the extraction is "queued" for several hours before it start extracting the first table. Has anyone had encountered the same issue before and knows how to handle this?

Maybe someone will answer, but may be one for support. Also have you setup real time connectivity?

 

https://docs.celonis.com/en/real-time-connectivity-to-sap-ecc-and-s-4hana-via-the-replication-cockpit.html


Thanks for your response. Already asked for support, but I am hoping to get this out of the way asap.

 

We don't use real time connectivity, but have daily delta loads in place for a few years already. It was working fine until a week ago, when this "waiting" time suddenly appeared.


Have you looked into the extractor logs? Maybe the problem is on the SAP side


Yes, I checked the logs, since the execution times worried me. That's where I noticed at what time it says "Extraction started" and when it actually starts extracting the first tables. During the period in between, it just says "queued" for all tables and is not running anything.


Yes, I checked the logs, since the execution times worried me. That's where I noticed at what time it says "Extraction started" and when it actually starts extracting the first tables. During the period in between, it just says "queued" for all tables and is not running anything.

´Did you know when started to fail? It looks like could be a change on the SAP side. If for example the problem started after a scheduled change, or a monday, etc...

Or check if Celonis made any change in your cloud around that date.

 

Of course, my guess is that you didn't change anything on the extractions... right?

 

So, if nothing changed in the extractions, it is unlikely a change in Celonis, and the extractor logs start with "Extraction started" and then nothing.... for me my first candidate is some change at the SAP side.

 

Best luck!


Indeed, we didn't change anything in the extraction. We will check if something has changed on the SAP side, thanks for the tip!


Reply