Business roles that are not in 'Complete' status is blank in ad-hoc Risk Analysis

[rubens_muller]

Hello friends

NWBC> Access Management> Access Risk Analysis > Role Level:

- Adhoc Risk Analysis in Business Role, the report appears blank. This problem occurs only in roles that do not have the "Complete" or "Provisioning" (BRM) Status.

- Adhoc Risk Analysis in a Technical Role, the report appears with risks regardless of the Role Status in the BRM.

NWBC> Access Request> Risk Violation:

The Business Role presents risks regardless of the Role Status in the BRM.

Note 2466129 reflects exactly what we are facing, but the version is not applicable to our environment. Our version is GRC-AC 12 SP06. The note version is for GRC-AC 10 SP27.

The problem occurs only in the production environment. Development and Quality are ok.

------------------------------------------------------------------------------------

Business Role with "Complete" Status

-------------------------------------------------------------------------------------

Business Role with "Authorization" Status

Regards, Friends

[rubens_muller]

Friends,

We identified that the roles that present the issue, have no history of a generation. When we downloaded GRC10 e and uploaded it to GRC12 and when, due to some partial adjustment, the Risk Analysis does not recognize the Role because there is no history.

Scroll without "Complete" or "Provisioned" Status, it will only appear in the risk analysis if there is at least one Generated version in BRM.

Tks

[rubens_muller · Accepted solution]

Friends.

We have identified the cause.

The roles were extracted from GRC-AC 10 to 12 using a template.

If the Business Role has no Generation and Approval history, without Completed or Provisioned status, when analyzing its risks, the report appears blank.

Roles without completed or Provisioned status will only be considered in the risk analysis if it has already been generated, approved and completed / provisioned at least once.

Tanks

[vijayakumarsuth]

I would suggest your to review and apply note 2871033 because this is latest update on same code logic, in case issue not fixed it is good to raise incident to SAP

[rubens_muller]

Hi, Vijayakumar

Thank you very much for your support.

I just applied the note in question. Didn't solve it. 😞

A incident already exists at SAP. 2 weeks. SAP did not return with this note.

Tanks.