Skip to Content
0
Former Member
May 20, 2010 at 03:59 PM

RAR for BCS

39 Views

Hi Guys,

I am working on a ruleset for BCS and as part of this there is an SoD between Submission and Signoff for a particular company code.

This is all related to a single authorisation object (R_UC_TASK).

Submission is made up of the following:

Tcode Auth Obj Field Value

UCMON R_UC_TASK ACTVT 16

UCMON R_UC_TASK TASK SUBMITGRP

UCMON R_UC_TASK TASK_FLD2 Company code

Signoff is made up of the following:

Tcode Auth Obj Field Value

UCMON R_UC_TASK ACTVT 16

UCMON R_UC_TASK TASK ZSIGN*

UCMON R_UC_TASK TASK_FLD2 Company code

The SOD is only an issue when the person can perform both functions for the SAME Company code.

In ERP, this could be generated into an ORG unit and we could configure RAR to consider this via the Org Rules. The only way I can think of to do this for BW is to effectively create a function for Submit for every company code and also a function for every Sign off. These can then be configured individually as risks.

I have no desire to be hard coding in the Company code into the rules as that will have massive maintenance efforts and duplication of effort not to mention the potential performance impact on running the risk analysis.

If you can think of a better way of achieving this, I'm open to suggestions.

Simon