You are on page 1of 2

Architecture of GRC 10.

The component GRC is built on a Net weaver Platform.


GRC has delivered underlying Repository & also it has got some configuration data and
Transactional data delivered by GRC.
Over this Im trying to build a N/w common component which is called as BRF+

BRF+

Business rule frame work,

Example:

There is some standard procedure for a new user account creation, changing user account and
deleting user account. But as per the requirement, we are trying to build a new frame work for
creating the user or change or delete account. We are trying to build this new frame work using
a BRF+, which is a N/w Common component and nothing to do with your GRC.
o Im using this BRF+ to build my work flows. But the BRF+ is built on the N/w level not on
GRC level.

o With the help of the repository delivered by sap and the config data, we are trying to
build my own frame work which is N/W common component.

o Using this N/W common component, Im trying to build my frame work called work
flows which is at GRC level common components.

o Work Flows here are treated as common components which are used at your GRC level.

o When we talk about your AC, we talk about the master data, which is commonly used
between AC,PC, RM and this not a individual component specific.

o Using this BRF+ we are trying to build my own shared master data, HR attachments,
custom fields, dashboards,etc

o Now using this, we are trying to build the AC common components like your
(ARA,ARM,BRM,EAM).

o All this is been accessed by web-dynpro with the help of NWBC.

o To do all sort of customization, process through Diag protocol through GUI to perform
customization.
o Indirectly business user will login for requesting access to user through SAP web dynpro,
and config user will login with your SAP GUI.

o Finally, we can integrate any sort of SAP and Non SAP application with the help of
Integration frame work.

You might also like