Skip to Content

Custom Fields Behavior in GRC BRM10.1 application

There are frequent questions why “Custom Field” option is disables when the Details are not saved while creating an Role via BRM application.

  • The Details (First Phase) are becoming mandatory because the Role ID is required to initiated the BADI IF_GRFN_API_CUSTOMFIELD_BADI, then BADI can become active on the Fields that are desired by Custom Fields.

  • Logically the Post Exit method POPULATE_ROLE_ATT in ZFILL_ROLERELAT_CUSTFIELDS is not called when creating a role in BRM application. Because the Role ID is required for the second phase.
  • The functionality flows, first phase the basic attributes of the Role eg Role Name has to be defined and in second phase enhanced attributes would be defined like Owners/Approvers then BADI for Customer Fields is called.
Be the first to leave a comment
You must be Logged on to comment or reply to a post.