01-28-2010 1:51 PM
Hi,
The Grant Master field group control settings are based on grant type settings. So you can hide fields and tabs etc based on the grant's lifecycle status.
Does anyone know if this can be configured based on authorization objects / authorization roles?
We wish certain fields to be hidden in all life cycle statuses for all general users, but for central finance users we wish those fields to be visible.
There is a customizing transaction GMS103 in the SPRO/IMG path
IMG > Public Sector Management > Grants Management > Grantee Management > Master Data > Grant > GM Grant Control : Field group for Authorizations
The documentation for this transaction says:
---
GM Grant Control: Field Group for Authorizations
It is possible to group fields together for authorization purposes. Use this step to specify such groups in Grants Management (GM).
Standard settings
We deliver the groups you can enter here, as standard.
Activities
Choose New Entries and enter the ID for the group you want to add. When you save, the system displays the longer description for the group.
Further notes
Authorization to a group allows access to all the fields in the group for users with the appropriate authorization. Only allow access to those you know need it for the whole group.
---
This table is empty on our system. Has anyone used this part of the customizing and can they let me know how it links into the basis roles / authorizations etc.
Thanks
Paul Abrahamson
01-28-2010 2:00 PM
I found this authorization object F_GMGT_FDG
The documentation for the authorization object states:
---
Definition
With this authorization object, you can define authorizations for individual field groups in grants management maintenance. You thereby define which fields in grant master maintenance can be maintained or viewed by a user.
Notes
This authorization is optional. You do not have to assign authorization if there are no field groups that require special protection and consequently no field groups requiring authorization were defined in Customizing.
Defined fields
The object consists of the fields "Field group" and "Activity":
Field group
Here you define which field groups require authorization.
Activity
Here you define which activities are permitted:
02 = Change
03 = Display
* = All activities
Procedure
Proceed as follows if you want to use this authorization:
1. Determine the field groups of the fields that you want to protect.
2. In Customizing, define that these field groups require authorization.
3. For each field group, define the authorization that you wish to assign to selected users.
4. Assign this authorization using the corresponding profile.
---
I'll try this out and update this message again later