on 10-07-2021 11:25 AM
Hello SAP ABAP Community, Hi thomasfiedler,
I want to find CDS Views based on an SAP Standard Table e.g. T179. So I go into SE11, enter the table name and hit the where-used-list icon. This dialog appears:
and is defaulted also with "Data Definitions". I uncheck the options for Programs, Classes and Web Dynpro Components. When I now start the search I only get the info message:
"Database table T179 was not found in DDL Sources"
But as you can see from the following screenshot there is the View I_ProductHierarchy based exactly on this Table:
I've reached out with this problem to Twitter. In the Meantime our Basis Admin found the Report SAPRSEUB that is mentioned in SAP Note 28022 - Customer system: Where-used list for SAP Objects but according to this Twitter thread from christian.punz starting this report is not enough. You also have to start SDDIC_DDLS_INDEX_ALL_SOURCES according to SAP Note 2833335 - DDLS object missing in the where-used result list.
So my question is: Why are the DDLS sources not indexed using the report SAPRSEUB directly?
Best Regards
Gregor
Hi Gregor,
according to my colleagues the SAPRSEUB is calling the SDDIC_DDLS_INDEX_ALL_SOURCES.
So it should work.
The benefit of the SDDIC_DDLS_INDEX_ALL_SOURCES is that only CDS sources are re-indexed which is much quicker than re-indexing the whole system for all objects.
Regards,
Thomas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas,
I have tried SAPRSEUB on S/4HANA 2020 on premise Initial shipment stack. No, it did not fix the CDS-View-index. It was worse: before SAPRSEUB I activated some views which yielded particular entries in Where-Used-List. The run of SAPRSEUB wiped them all away.
<edit Oct. 8 2021>
at #SAPStammtisch Vienna yesterday we did a code review and found that SDDIC_DDLS_INDEX_ALL_SOURCES is built into SAPRSEUB as "step 8". That means, your colleagues told you a correct story.
And we found the log section regarding SDDIC_DDLS_INDEX_ALL_SOURCES in the log of the SAPRSEUB-run. All indicators show that you are right and code should be ok.
But as I checked the situation in the last weeks I found that SAPRSEUB wiped my WUL-entries from the manual activation and the CDS-views are NOT in WUL. Is there a "data destroyer" somewhere after "step 8"?
</edit>
br
christian
Hi Thomas,
our Basis Admin did run SAPRSEUB on our S/4HANA 2020 FPS 01 sandbox system. It was not enough to index also the CDS views. Another issue that we catched on our development system with the same release is that now after the weekend the CDS views are not found anymore. Can EU_REORG have any influence on that?
I think it's getting worth rasing an incident via the SAP Support?
Best Regards
Gregor
hi!
here is mine:
706803 / 2021 Where-Used-List does not show certain objects
br
christian
Hi, we were facing the same issue. Our basis team thinks the cause of "after the weekend the CDS views are not found anymore" is the job: ATO_REPAIR_OR_REBUILD_INDEX. But we didn't find much information about it. After we stopped it, seems to work correctly.
A first correction is available:
3109997 - DDLS Where-Used: No deletion of DDLS index for SAPRSEUC
indexing still running here. Can report results tomorrow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you check this, Hope our program helps
https://blogs.sap.com/2020/04/28/abap-cds-view-object-flow-program/
Thank you for sharing this report. But this question is about the SAP Standard where-used functionality for CDS Views. The issue seems to be fixed with Note 3109997 - DDLS Where-Used: No deletion of DDLS index for SAPRSEUC.
User | Count |
---|---|
98 | |
12 | |
10 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.