CDS View: Using join of same table twice and call it as association in the primary view

[sankar1781]

Hi Experts,

We have a primary CDS view where it has multiple associated CDS views involved (using association).

The main define view starts with one Customer CDS view (for ex: ZBP) that has Business Partner data (BUT000 and associated address data) and call it as left outer join with BUT050-PARTNER1 and BUT050-PARTNER2.

In one of the rules for a particular column as Corporate ID will be fetched based on

BUT050-PARTNER1 (as customer ID and BUT050-PARTNER2 (Group ID data) where BUT050-RELKIND is not initial. 

The above Corporate ID data logic is written as a separate CDS view and call it in the primary as associated view.

Though the above Corporate ID CDS view showing the result based on the validation but when it calls from the primary view. It writes the line of Group ID with the Customer ID where this combination doesn't exist in BUT050 since the RELKIND is initial. 

The business expectation is this line must not be written. 

I need your help, how to write and resolve this solution.

Many thanks for your time here in reading and your valuable answers, if any.

Warm Regards.

[HakanHaslaman]

Please try to resolve this issue by adding a filter condition in your primary CDS view where you call the associated view. This filter condition should ensure that the RELKIND is not initial.