Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 
keremkoseoglu
Contributor
ABAP CDS Views are great and all; however, they don't support subqueries at this time. In this post, I would like to share a workaround which functions similar to "NOT EXISTS".


The requirement was to exclude material document items (MSEG) which were reverse posted; and the reversal documents themselves.


If I was writing a regular ABAP SQL statement, I could easily achieve this with the help of a NOT EXISTS subquery. Check the code snippet below - I have excluded unrelated WHERE conditions for simplicity.




SELECT mblnr, mjahr, zeile 
FROM mseg AS mseg1
WHERE
( sjahr EQ '0000' OR sjahr IS NULL )
AND
( NOT EXISTS (
SELECT mandt FROM mseg AS mseg2 WHERE
sjahr EQ mseg1.mjahr AND
smbln EQ mseg1.mblnr AND
smblp EQ mseg1.zeile
) )
INTO TABLE @DATA(lt_mseg).



This logic doesn't work in CDS views directly due to lack of subquery support. To get the same result using CDS views, I have split the query into two views. The first one returns a wide list where original and reversal MSEG records are listed side by side.



@AbapCatalog.sqlViewName: 'ZMMV_001'
@AbapCatalog.compiler.compareFilter: true
@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Original and reversal docs side by side'
define view ZMMV_MAT_DOC_ITEM_REV_STATUS as
select from
mseg as mseg1
left outer join mseg as mseg2 on
mseg2.sjahr = mseg1.mjahr and
mseg2.smbln = mseg1.mblnr and
mseg2.smblp = mseg1.zeile
{
mseg1.mblnr as mblnr1,
mseg1.mjahr as mjahr1,
mseg1.zeile as zeile1,
mseg1.sjahr as sjahr1,
mseg1.smbln as smbln1,
mseg1.smblp as smblp1,
mseg2.mblnr as mblnr2,
mseg2.mjahr as mjahr2,
mseg2.zeile as zeile2,
mseg2.sjahr as sjahr2,
mseg2.smbln as smbln2,
mseg2.smblp as smblp2
}



The second view filters out the reversed & reversal documents from the first view, which leaves effective material documents only.




@AbapCatalog.sqlViewName: 'ZMMV_002'
@AbapCatalog.compiler.compareFilter: true
@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'Effective material document items'
define view ZMMV_EFFECTIVE_MAT_DOC_ITEM as
select distinct from ZMMV_MAT_DOC_ITEM_REV_STATUS
{
key mblnr1 as mblnr,
key mjahr1 as mjahr,
key zeile1 as zeile
}
where
sjahr1 = '0000' and
(
mjahr2 = '0000' or
mjahr2 is null
) and
(
sjahr2 = '0000' or
sjahr2 is null
)



This approach can be implemented to replace NOT EXISTS in many other cases as well.
7 Comments
joachimrees1
Active Contributor
Nice!

While still learning about CDS, I think I greatly benefit from real live examples on what and how to achieve things with it!

Thanks a lot for sharing!

 

Joachim

 
whatsap
Participant
Great!
Jelena
Active Contributor
0 Kudos
Thanks for sharing this! Sadly, EXISTS / NOT EXISTS is still not supported by CDS views at least in 2020, so we have to get creative. This is a rather common scenario, so I hope there might be some improvements in later versions.

In the meantime, there is also an alternative suggestion for this scenario on Stackoverflow: https://stackoverflow.com/questions/60601013/how-to-achieve-not-exists-with-the-abap-cds

Maybe it helps someone too.

Thank you!
keremkoseoglu
Contributor

Yes, the association method works too. However; in my humble experience, some CDS workarounds might cause bad performance in the long run - especially when they are nested.

My approach for complex queries is to write AMDP (SqlScript) instead. It is much more flexible and powerful than vanilla CDS. Depending on the requirement, AMDP can be prepared in form of a CDS table function or an ABAP method.

Jelena
Active Contributor
0 Kudos
Yes, I've slowly reached the same conclusion that there might be over-reliance on CDS views in the scenarios that go beyond their capabilities. I feel there is a lack of guidance and general information on this and it's mostly "the devil we know" situation. Would be helpful if you could share an AMDP example as well.

Thank you!
keremkoseoglu
Contributor
Here is an AMDP code sample containing NOT EXISTS.
    open_obligations =
select * from :obligations as _obl
where not exists ( select mandt from :obligations_completed_due_to_recipient
where werks = _obl.werks and
mdvid = _obl.mdvid );

missing_plant_views =
select distinct _obl.werks, _obl.mdvid
from :open_obligations as _obl
where not exists ( select mandt from ZBCT_MDF_DRSENT as _sent
where _sent.mandt = :mandt and
_sent.reqid = :reqid and
_sent.mdvid = _obl.mdvid and
_sent.rcpnt = _obl.drrcp );
CarlosRibeiro82
Explorer
0 Kudos
Nice post! Thanks for share!