ABAP CDS-View not really there in Eclipse ADT after transport of copies on the TEST-system

[Vlad_Ghitulescu]

Hey!

I transported the copy of a transport with a bunch (16 to be precise 😉 new ABAP CDS-Views from the DEV-System into theTEST-System (EK5.520).
The copy of the transport had a warning but nothing more than that.

Trying to access the new CDS-Views in the TEST-System in Eclipse only brought an error (see attached screenshot AND the complete text of the error at the bottom) even when the name of the "wanted" CDS-View appeared in the "Open ABAP Development Object"-window (see attached screenshot).

However alle the CDS-Views are visible in SAP GUI in SE11 (see attached screenshot).

The info-message I see for each CDS-View in the transport-log:

"Der View muss auf der Datenbank angelegt werden" = "The view must be generated on the database"

doesn't really let me know what am I suppose to do in order to actually get alle the views generated...

Any suggestions?

Thanks in advance!

Regards,
Vlad

---

2022-02-08-cds-views-not-in-k-01.png

2022-02-08-cds-views-not-in-k-02.png

2022-02-08-cds-views-not-in-k-03.png

2022-02-08-cds-views-not-in-k-04.png

---

org.eclipse.core.runtime.CoreException: Synchronize Content Result for /EK5_520/.adt/ddic/ddlsources/%2frwee%2fpm_b_ausp/%2frwee%2fpm_b_ausp.apddls<br>  at org.eclipse.core.internal.resources.semantic.SemanticFileStore.synchronizeContentWithRemote(SemanticFileStore.java:1152)<br>  at org.eclipse.core.internal.resources.semantic.SemanticResourceAdapterImpl.synchronizeContentWithRemote(SemanticResourceAdapterImpl.java:318)<br>  at com.sap.adt.tools.core.internal.sfs.AdtSfsUtil$3.run(AdtSfsUtil.java:253)<br>  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)<br>  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2338)<br>  at com.sap.adt.tools.core.internal.sfs.AdtSfsUtil.synchronize(AdtSfsUtil.java:270)<br>  at com.sap.adt.tools.abapsource.AbapSourceSfsUtil.synchronize(AbapSourceSfsUtil.java:39)<br>  at com.sap.adt.tools.abapsource.AbapSourceSfsUtil.synchronize(AbapSourceSfsUtil.java:33)<br>  at com.sap.adt.tools.abapsource.ui.sources.editors.AbapSourceEditorService$1.run(AbapSourceEditorService.java:258)<br>  at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)<br>Contains: I::000<br>com.sap.adt.communication.resources.ResourceException: Execution of request "GET /sap/bc/adt/ddic/ddl/sources/%2frwee%2fpm_b_ausp" failed: 500 Internal Server Error<br>I::000<br>------------ Request -----------------------<br>GET /sap/bc/adt/ddic/ddl/sources/%2frwee%2fpm_b_ausp HTTP/1.1<br>Cache-Control: no-cache<br>Accept: application/vnd.sap.adt.ddlSource.v2+xml, application/vnd.sap.adt.ddlSource+xml<br>User-Agent: Eclipse/4.20.0.v20210611-1600 (win32; x86_64; Java 16.0.1) ADT/3.18.0 (devedition)<br>X-sap-adt-profiling: server-time<br>------------ Response ----------------------<br>HTTP/1.1 500 Internal Server Error<br>~server_protocol: HTTP/1.1<br>X-sap-adt-profiling: server-time=72091<br>Content-Type: application/xml<br><?xml version="1.0" encoding="utf-8"?><exc:exception xmlns:exc="http://www.sap.com/abapxml/types/communicationframework"><namespace id="com.sap.adt"/><type id="ExceptionInternalServerError"/><message lang="EN">I::000</message><localizedMessage lang="DE">I::000</localizedMessage><properties/></exc:exception><br>--------------------------------------------<br>  at com.sap.adt.communication.internal.resources.RestResource.createResourceException(RestResource.java:267)<br>  at com.sap.adt.communication.internal.resources.RestResource.createResultFromResponse(RestResource.java:199)<br>  at com.sap.adt.communication.internal.resources.RestResource.invoke(RestResource.java:189)<br>  at com.sap.adt.communication.internal.resources.RestResource.get(RestResource.java:75)<br>  at com.sap.adt.tools.core.spi.sfs.AdtContentProvider.readAdtResourceInternal(AdtContentProvider.java:1666)<br>  at com.sap.adt.tools.core.spi.sfs.AdtContentProvider.synchronizeFileWithRemote(AdtContentProvider.java:1101)<br>  at com.sap.adt.tools.core.spi.sfs.AdtContentProviderForCompoundObjects.internalSynchronizeContentWithRemote(AdtContentProviderForCompoundObjects.java:145)<br>  at com.sap.adt.tools.core.spi.sfs.AdtContentProviderForCompoundObjects.synchronizeContentWithRemote(AdtContentProviderForCompoundObjects.java:103)<br>  at org.eclipse.core.internal.resources.semantic.SemanticFileStore.synchronizeContentWithRemote(SemanticFileStore.java:1150)<br>  at org.eclipse.core.internal.resources.semantic.SemanticResourceAdapterImpl.synchronizeContentWithRemote(SemanticResourceAdapterImpl.java:318)<br>  at com.sap.adt.tools.core.internal.sfs.AdtSfsUtil$3.run(AdtSfsUtil.java:253)<br>  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)<br>  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2338)<br>  at com.sap.adt.tools.core.internal.sfs.AdtSfsUtil.synchronize(AdtSfsUtil.java:270)<br>  at com.sap.adt.tools.abapsource.AbapSourceSfsUtil.synchronize(AbapSourceSfsUtil.java:39)<br>  at com.sap.adt.tools.abapsource.AbapSourceSfsUtil.synchronize(AbapSourceSfsUtil.java:33)<br>  at com.sap.adt.tools.abapsource.ui.sources.editors.AbapSourceEditorService$1.run(AbapSourceEditorService.java:258)<br>  at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)

---

[Sandra_Rossi]

500 application error

so please contact SAP support! (and check the SAP notes before contacting them)

[Vlad_Ghitulescu]

Thanks, sandra.rossi !

Could you please elaborate a little on this - because I've just contacted our "basis"-dept. and this problem is totally new for them ("500 application error? Oh, than refresh or come back later!" - no kidding! ;-))

[Sandra_Rossi]

I don't see what you want me to elaborate. It's an error from standard application, what do you want to do but asking the developers to fix the error?

[Vlad_Ghitulescu]

Sorry for not being exact enough. I meant who exactly was meant with "SAP support".

In the meantime we solved the problem: The development package for the CDS-views was not on K yet.