SAP Datasphere - Replication Flow - Started failing with Partitions' Error

[Mandar_Damle]

Hello Experts,

I am getting the the below error messages while extracting the data via replication flows from S/4HANA. These extractions were working fine and suddenly, these errors have started appearing to many replication flows since last couple of days. All are "Initial" loads (Full loads). Deltas are working fine. Source for these replication flows are CDS views.

Error -

One or more partitions have encountered an error.

Error while accessing object queue / Calculation not finished but ACD doesn't exists for object ZCDS_VIEW_NAME (type DDLS)

Thanks!

Regards,

Mandar Damle

[ClemSteich · Accepted solution]

Hello,

Apply latest notes from Note Analyzer (program CNV_NOTE_ANALYZER_DI) in your S/4 system.

That fixed the partition error for us.

Best regards

[Mandar_Damle · Accepted solution]

Hello, We have already implemented these notes. Thanks!

[ClemSteich · Accepted solution]

Hello, you could try one of these notes:

3360383 - SAP Data Intelligence - ABAP Integraion (S/4HANA) - Access plan calculation for client ind...

3450435 - SAP Datasphere - ABAP Integration - Restart of replication flow fails if previous run fail...

3424305 - SAP Datasphere - ABAP Integration - Errors during data transfer after restart of the repli... 

Regards

[madhvi_pai]

Hi Mandar,

Please see SAP Note https://launchpad.support.sap.com/#/notes/3450435

Thanks

[Mandar_Damle]

Hello Madhvi, It seems this note is not implemented. I will ask BASIS to implement this note and I will provide you the feedback. Thanks!

[n_gaertner]

Hi Mandar,

the root cause cannot be tracked down by this error message.
You can check the application log in SLG1 on the source S/4 HANA System (Log Object DH*), if you get further errors that help you to understand the problem.
Otherwise please raise a ticket on CA-DI-IS-ABA and let the SAP support check.

Best Regards,

Nico

[Mandar_Damle]

Hello Nico, In general, SLG1 seems to be very handy to figure out the root cause but in this case, I get the same error message in SLG1 as well.