Skip to main content

Hi,

 

I am trying to calculate the throughput time of each rework loop using Source- Target and failed due to no-common table errrors. My code is like below:

Minute_Betwen(

 

Source("_CEL_O2C_ACTIVITIES"."EVENTTIME", remap_values("_CEL_O2C_ACTIVITIES"."CHANGED_TO", ,'ZA','ZA'], Null)),

 

Target("_CEL_O2C_ACTIVITIES"."EVENTTIME",

remap_values ( "_CEL_O2C_ACTIVITIES"."CHANGED_FROM" , ;'ZA','ZA'], Null))

)

 

I got the errors that no common table found since both Activity table and temporary table for Souce/Target are N side.

Do you have any ideas how to work around this?

Just a shot in the dark, no idea if it will work... what if you use a PU function to put the case table in between? Like for target getting a PU_LAST(CASE, ACTIVITIES.EVENTIME)

 

Again, it is just a wild idea. Have luck!


Just a shot in the dark, no idea if it will work... what if you use a PU function to put the case table in between? Like for target getting a PU_LAST(CASE, ACTIVITIES.EVENTIME)

 

Again, it is just a wild idea. Have luck!

Thanks, @Guillermo Gost: I am afraid that such PU functions will take into account only either last or first time of rework. If a case has entered and left a loop for more than 2 times, it cannot catch how long it took for the case to leave the loop at the nth time of rework.

 

I actually used datediff in combination with filter_to_ null for this case. It worked but the filter_to_null harms the query performance. So, Im trying to find a smarter way of doing this.


If you are using same table, in both source & target table then consider using DOMAIN TABLE and then apply PU function on it.


Reply