SAP for Public Sector Discussions
Foster conversations about citizen engagement, resource optimization, and service delivery improvements in the public sector using SAP.
cancel
Showing results for 
Search instead for 
Did you mean: 

User Restriction by Fund Group and Fund Centre

Former Member
0 Kudos

Dear Gurus,

How best can I restrict users from displaying, posting and viewing (from a drop down or drill down) a group of fund or fund centre for an FM?

Thanks

1 ACCEPTED SOLUTION

iklovski
Active Contributor
0 Kudos

Hi,

You have the following authorization objects available:

F_FICA_CTR    Funds Management Funds Center

F_FICA_FCD    Funds Management Fund

F_FICA_FCG    Funds Management: Funds Center Groups

F_FICA_FNG    Funds Management: Fund Groups

F_FICA_FOG    Funds Management: Authorization Group of Fund

F_FICA_FSG    Funds Management: Authorization Group for Funds Center

Regards,


Eli

View solution in original post

3 REPLIES 3

iklovski
Active Contributor
0 Kudos

Hi,

You have the following authorization objects available:

F_FICA_CTR    Funds Management Funds Center

F_FICA_FCD    Funds Management Fund

F_FICA_FCG    Funds Management: Funds Center Groups

F_FICA_FNG    Funds Management: Fund Groups

F_FICA_FOG    Funds Management: Authorization Group of Fund

F_FICA_FSG    Funds Management: Authorization Group for Funds Center

Regards,


Eli

Former Member
0 Kudos

Dear Eli,

Can please let us know authorization objects for Commitment items.

Regards,

Upendar Singh

0 Kudos

Look into F_FICA_CIG (Funds Management: Commitment Item Groups), F_FICA_FPG ( Funds Management: Authorization Group for Commitment Item), and F_FICB_FPS (Cash Budget Management/Funds Management Commitment Item).

You can also discover the probable authorization objects you'll need by going into PFCG for the role in question (or a dummy role if you're just exploring), choosing the Authorizations tab and clicking Change Authorization Data, then click the button for Selection criteria.  Expand the group for 'Financial Accounting' and you'll see all the related auth objects there.

Alternatively, you can either run an authorization trace while executing the relevant transactions with a superuser (via ST01) and see what objects are touched, or you can use the old 'trial and error' method, with a test user with very little authorization, letting it fail each time and then using SU53 to determine what object failed.

Best regards,

Matt