In case of preserve key annotation, At 8:53 , when you said , only cust will be the key field, but in the table , sales order was the key field and not customer. Even when i tried it , in version 757, it gave me warning when i tried to activate it and it remained inactive. i am confused why do we even have this annotation. please check and help me understand the working of this preservekey annotation. as usual good video, thanks for sharing!
Hi Karishma, as per my understanding. I hope it will help. 1. If we didn't define any key field while selecting value it will take key field from source table automatically as initially we have key field as VBELN. Because in VBAK table key field is VBELN. 2. As per our requirement we need to make cust as key field instead of VBELN. Here we need annotation preservekey : true. If we set preserve key true then we can set cust as key field and VBELN will not be key field anymore. 3. If we set preserve key as false then we can set cust as key field and VBELN will remain key field. @SAPTECHNOMANIAC Kindly correct if I am wrong.
Hi Ram. What is the use of dbHint dbSystem annotation? We can specify the database system. But I have already logged to a system and defining this CDS view. That logged in system will have its own database system which will be used for this CDS view. Then what is the use of specifying it explicitely. If my DB is ORA and I give HDB in this annotation what will happen?
Dear Ram, CDS DDIC-based views are obsolete as of Application Server ABAP 7.57. Use a template for a CDS view entity instead. Can you share some of your experience upgrading system where DDIC Based cds are converted to CDS View entity ?
However, I have explained the CDS entity in the next video, Using the CDS entity only next video and onwards. For your second Q, you can refer to below blog it will help:- blogs.sap.com/2021/10/16/a-new-generation-of-cds-views-how-to-migrate-your-cds-views-to-cds-view-entities/#:~:text=No%20new%20features%20will%20be,However%2C%20this%20is%20optional.
