We are using a dedicated Segregation of Duties dashboard to analyze cases where two activities are processed by the same person (e.g. Creation of PO and Releasing the PO). In this dashboard, the viewer selects two activities, which shall not be performed by the same user to see in how many cases there is a violation. See here the PQL statement:
when PU_first(EKPO,"_CEL_P2P_ACTIVITIES".“USER_NAME”, “_CEL_P2P_ACTIVITIES”.“ACTIVITY_EN” = ‘<%=From%>’ AND “_CEL_P2P_ACTIVITIES”.“USER_TYPE” <> ‘B’) = PU_first(EKPO,"_CEL_P2P_ACTIVITIES".“USER_NAME”, “_CEL_P2P_ACTIVITIES”.“ACTIVITY_EN” = ‘<%=To%>’)
end) * 100
By checking the violations in detail, I’ve recognized that there are cases where Person A creates a PO, Person B approves the PO and afterwards Person A changes some field in the PO (e.g. Net Order Price). Due to this change, the release indicator is AUTOMATICALLY changed from “B” (release) to “R” (not released). This case is shown as a violation in the segregation of duties dashboard, since user A is changing the release indicator (not actively, but only by changing some other SAP field for this PO) and thus considered to be approving this PO even though the user is doing exactly the opposite.
Any idea how to solve this issue?