Hello team,
We recently began implementing a First Time Right analysis for SAP ECC using the most recent template from the App Store. One item we noticed was that the KPIs included in the analysis all filtered to only cases that included the Clear Invoice activity:
Affected Net Order Value:
SUM(CASE
WHEN PU_COUNT(VBAP, CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %>,CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %> = <%= clear_invoice_activity %> ) = 0
THEN NULL
WHEN PU_COUNT(VBAP, CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %> ) - PU_COUNT_DISTINCT(VBAP,CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %> ) = 0
AND PU_COUNT(VBAP, CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %>,CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %> IN (<%=rework_activities%>) ) = 0
THEN 0.0
ELSE VBAP.NETWR_CONVERTED
END)
FTR Ratio:
AVG(CASE
WHEN PU_COUNT(VBAP, CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %>,CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %> = <%= clear_invoice_activity %> ) = 0
THEN NULL
WHEN PU_COUNT(VBAP, CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %> ) - PU_COUNT_DISTINCT(VBAP,CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %> ) = 0
AND PU_COUNT(VBAP, CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %>,CEL_O2C_ACTIVITIES"."ACTIVITY<%= language %> IN (<%=rework_activities%>) ) = 0
THEN 1.0
ELSE 0.0
END)*100.0
Id like to understand what the concerns would be with removing this statement and considering all cases instead. I ask in part because we are having a problem with the Clear Invoice activity pulling in consistently, but also because we would want to include items that never go through that activity (such as cancelled orders).
Can you help me understand why the Clear Invoice filtering logic was included on the First Time Right analysis provided by Celonis?
Thank you!
Page 1 / 1
Hi Alex,
the Clear Invoice filtering was added because a desired process would ideally contain a Clear Invoice activity.
Whether or not removing the activity totally depends on how you define the FTR Rate from business perspective. In case you would like to remove it, you could just remove the first PU function
Using the same logic, you could also exclude certain activities using WHEN
Best,
Viana
the Clear Invoice filtering was added because a desired process would ideally contain a Clear Invoice activity.
Whether or not removing the activity totally depends on how you define the FTR Rate from business perspective. In case you would like to remove it, you could just remove the first PU function
PU_COUNT(VBAP, *CEL_O2C_ACTIVITIES"."ACTIVITY* <%= language %>, *CEL_O2C_ACTIVITIES"."ACTIVITY* <%= language %> = <%= clear_invoice_activity %> ) = 0Using the same logic, you could also exclude certain activities using WHEN
PU_COUNT(VBAP, *CEL_O2C_ACTIVITIES"."ACTIVITY* <%= language %>, *CEL_O2C_ACTIVITIES"."ACTIVITY* <%= language %> IN (<%=excludedActivities%>)) = 0 THEN NULLBest,
Viana
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.