Did you check for the first case whether the sum in Celonis also comes to 704?

My approach would be to break down the problem (as you did) and then gradually build it back up to see where it goes wrong.

An issue that could be in play is the auto-join feature of Celonis. If youre accessing only one table in a component/calculation, no join is done. If you use multiple tables then joins are executed as indicated in the data model. This is performed in a left join way from the parent table. In some cases this might result in less records and hence different calculations.

See

https://help.celonis.de/pages/viewpage.action?spaceKey=PQL45&title=Join+functionality for more details

Hi there,

Joosbuijs is right, this is most probably connected to joins in your table, which joosbuijs described as auto-joins.

Not every entry in EKPO also has an entry in the EBAN table or in business words, not every purchase order item also has had a purchase requisiton item. When you combine these two tables in one formula, an inner join will be performed and only those items recognized which have entries in both tables, so only purchases with a purchase requisition.

This behaviour is very much wanted in the most cases, but for the few which are left we have our PU formulas. There is a beautiful entry on what they do and how they work here in this forum, just have a quick search for it.

Basically what PU_Formulas do is an (aggregated) left join of one column of a table to another, or in your case, left join EBAN.MENGE to the EKPO table by doing a PU_SUM(EKPO, EBAN."MENGE) / (EKPO.MENGE) for CASE 1 and a

CASE WHEN ISNULL(PU_FIRST(EKPO, EBAN.FLIEF)) = 0 AND PU_FIRST(EKPO, EBAN.FLIEF) != EKKO.LIFNR

for the second case, this should do the job.

Important Disclaimer: Please read up and inform yourself about PU_ Functions as these have special attributes and ways they work (e.g. analysis filter dont usually filter them) and if they make sense in your situation.

Best Regards,

Benedict