Hi Sasa, I can't help with with how the FILTER DOMAIN actually behaves, but can help you with replicating this (and probably also give possible explanation on how your predecessor generated this).

1) Make sure you have some kind of filter applied in one of your use cases.

2) right-click any empty space (no component)

3) Select 'generate documentation (HTML)

4) Go down to to 'selections' all the way at the bottom

5) You will notice the applied filters have been converted to PQL that starts with FILTER DOMAIN

6) This is a bit of workaround one can use to get around writing code.

Hope this is somewhat helpful to you.

Hi @sasa.redze12 

I have also not come across FILTER DOMAIN function documentation as such.

But from DOMAIN_TABLE function we can relate it.

The DOMAIN_TABLE  function can be used to create a temporary table from various column(s), which can be used as a target table inside all PU-functions.

Likewise FILTER DOMAIN should work.

Sharing few links which may help you in getting some idea about FILTER related function.

https://rohit-kumar103-infosys-com.training.celonis.cloud/help/display/CIBC/FILTER

https://rohit-kumar103-infosys-com.training.celonis.cloud/help/display/CIBC/DOMAIN_TABLE

Hope it helps.

Happy Learning.

Hi Bart,

thank you for your comment and your help.

The export function seems very helpful. I see now your point 5, how PU functions get converted. But this raises new questions.

Are load scripts entries also part of the HTML export selections section?

Load scripts, selects only cases where Vertriebsgesellschaft is '1000 - Some GmbH'

"FILTER DOMAIN "VBAK"."VKORG" || ' - ' || "VBAK"."VKORG_TEXT" AS "Vertriebsgesellschaft" IN ( '1000 - Some GmbH'

); "But the HTML export selections section is empty.

Does that mean that the load scripts filter is not active?

Hi @sasa.redze12 

So answer to your query.

Are load scripts entries also part of the HTML export selections section?

So the answer is yes.

Load scripts is part of sheet filter.

You can find that 'sheet Filter' detail in the HTML documentation itself.

Hope it helps.

It doesn't seem to be in my case. Could someone verify this?

Depends which version are you using, but

FILTER is a general command that supports complex filter statements.

FILTER DOMAIN only supports simple filter statements with one column which is compared to constants.

•FILTER DOMAIN has been optimized for the simple statements, making it much more efficient than FILTER.

FILTER "VBAP"."TS_ERDAT" BETWEEN {t 1514937600000} AND {t 1556575199999};

=>

FILTER DOMAIN "VBAP"."TS_ERDAT" BETWEEN {t 1514937600000} AND {t 1556575199999};

This change improves the filter evaluation performance by an order of magnitude.

In engine release 2.2 (cloud, CPM4 4.6+), FILTER automatically takes the efficient

implementation of FILTER DOMAIN if applicable