Grant Master field group control based on authorization - hide fields

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

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

Similar Messages

GL account master data creation control based on Account group

While creating GL account in FS00 we need to control to select P&L account or Balance sheet account. At present after selecting P&L accunt group it is allowing to check Balance sheet account. If we select account group belongs to Balance sheet but it is allowing to check P&L. How to control to select P&L or Balance based on account group.
For example: If we select account group beongs to P&L it should allow to check P&L statement account.
If we select account group belongs to BS it should allow to check Balance sheet account

I don't there is any control for this at 'Account Group' level, please use userexit EXIT_SAPMF02H_001 for this.
Regards,
Ganesh

Vendor Master Field Group Authorizations

Hi guys,
I want to give the authorization to specific users for only changing a few fields in the Vendor Master.
There is an authorization field in the vendor master ( XK02 ) under control Tab. But how do we create this authorization ?
There is also define vendor field groups where we can restrict which fields to be changeable by the user. But how do we link these field groups to the vendor master?
Please suggest.
Thanks,
Srikanth.

HI,
You can use dual control to provide more security when changes are made to sensitive data in your customer and vendor master records. This function can be used for changing customer master records (FI-AR) and vendor master records (FI-AP).
Prerequisites: You must define the required sensitive fields in the customer or vendor master record in Customizing (IMG) for Financial Accounting. To do so, choose Financial Accounting->Accounts Receivable and Accounts Payable->Customer Accounts-> Master Records->Preparations for Creating Customer Master Records->Define Sensitive Fields for Dual Control.
You must be authorized to change master records. You also define authorizations in Customizing (IMG) for Financial Accounting. To do so, choose Financial Accounting->Financial Accounting Global Settings->Maintain Profiles. The person who makes the changes is never allowed to confirm his or her own changes.
Features: You can define the required master data fields as sensitive in Customizing.
When an authorized accounting clerk changes a sensitive field in the customer or vendor master record (such as Alternative Payee), the relevant account is blocked for the payment run. The changes take effect immediately. The account remains blocked until a second authorized person confirms the master data changes. However, it is still possible to make a further change to an account that is already blocked. The second authorized person is informed of the changes by mail or by other means, and then uses the function Master records->Confirmation of change->Single (or->List) to edit the changes.
If the second authorized person does not confirm the master data change, the relevant account continues to be blocked for the payment run. The changes are likewise not reset.
Hope this helps you. Let me know if you need anyother information.
Rgds
Manish

Different field groups in the different account groups

Dear IT Experts,
I´m working on restructuring authorization in roles concerning the IC and TP customers.
The goal of this changes is be able to have different field groups in the different account groups (TP and IC), for give you some more detail a good example can be, the same AMS user should be able to change general data and sales views for TP customers but for IC he should only be allowed to change the sales views, however when the changes are made in the roles they are being ignored because as far as I could check the system does not have as a rule that the field groups are or can be dependent from the account group...
I can give you a clear example:
Role A
F_KNA1_AEN -> VGRUP = 10-16
F_KNA1_GRP -> ACTVT = 01, 02, 03
F_KNA1_GRP -> KTOKD = INTR
Role B
F_KNA1_AEN -> VGRUP = 16
F_KNA1_GRP -> ACTVT = 01, 02, 03
F_KNA1_GRP -> KTOKD = THIR
Despite it looks fine, the system is not validating the account group with the correspondent field group in each role, so the field groups that the system use is unique, it means it the content of the object F_KNA1_AEN in total independently of used account group!
So my question is, can we apply any other object that makes the field group being directly depending of the account group, as we can see for example activities for each account group having something similar for field group and account group?
Can someone please explain me step-by-step how I can do this work even if by another method?
I´m quite new on this issues and I really need your wisdom to find a solution for this.
Many thanks
Katjia

Hi Manoj
The debate is each inidividual business unit has defined different account groups for the same vendor in their respective systems.
The question is : What is the best practice-- Should we keep Vendor account group as main table field and define Vendors with one unique account groups OR we maintain the account group in qualified table each pointing to different business unit.
In my opinion this is going to be very complex solution. Ideally we need to define all the Harmonization rules before syndicating data to different target systems.
Is this possibel that the same vendor record which is existing as vendor of different account groups in different systems have same set of attributes. If yes then enabling the remote key for Account group Lookup field is one option and defining a unique Account group 'AG" (which is mapped to say AG1 from remote system1, AG2 from remote system2 and so on..)..
Managing this via Qualified table will be very complex and not advisabel. As Rajesh also mentioned Account Group in MDM should be considered as Global attribute and all such harmonization rules should be defined in your project. AG1=AG2=AG in above exmaple.
Hope this clarifies.
Thanks-Ravi

Make fields un-editable based on condition in Relationship tab of ACCOUNTS

Hi Friends,
Iam working in CRM 5.0. Application: ZCRMMACCOUNT View: Z*ACC
I want to make the fields in the relationship tab of Accounts application to read only based on some condition (when the relationship is contact person).
I have tried all the ways:
1. In the READ method of Access Class, set the field property as 'A' in the et_field_attribute.
2. Use the method set_field_attr of class cl_bsp_bp_global_service.
But still the fields are in the editable mode. And here i cant use the Field Group Customization, because i want to make the fields read only based on some condition. I tried using field group variants, but while debugging, the method GET_FIELDGROUP_VARIANT is not called.
Can you please suggest me your ideas and how to work with this?
Regard,
Raju

Dear Raju,
I am new to CRM, if i am wrong in explaing the things dont consider it.
We to had the almost the same requirement then we went to the field groups level and chekced the following field groups and changed them to display only feature by checking the box in the field groups....
ADR_DETAIL_COMM_DATA
ADR_DETAIL_COMM_DATA_CAM1
and generated the layout for the following parent field groups....
ADR_DETAIL_COMM_ALL
ADR_DETAIL
BUP_ADR_DETAIL
ADR_DETAIL_2
and also check the field groups under the following parent field groups which matches to your requirement...by checking box of the related field group to display mode
BUP_GENERAL_DATA
BUP_BUS1006_SRES

Ad-hoc Query - Travel Privilege Field Group

Hi am new to this Ad-hoc Query...
can any body tel me this.
Asia HR is currently using/assigned to AQB : ZHR_UG_01 ABAP Query: User group and AQS: ZHR_PA_ASIA SAP Query: InfoSet which does not include the Travel Privilege Field Group. The same Travel Privilege Field Group is already included in the Global infoset AQB - ZHR_UG_01 - ABAP Query: User group and AQS - ZHR_UG_01 - SAP Query: InfoSet
Please tel me how to create ASIA HR as per the requirement.
Thanks in advance..
Regards,
kalam A.

Hi Kalam,
seems that you simply have to add this field to the use InfoSet in transaction SQ02.
Regards,
Michael

Field Symbols, Field String, and Field Group.

Hi,
Can you differentiate between filed symbols, field strings and field groups,
With regards,
Bharath Mohan B

Hi,
Field Symbols
Field symbols are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field symbols are similar to dereferenced pointers in C (that is, pointers to which the content operator * is applied). However, the only real equivalent of pointers in ABAP, that is, variables that contain a memory address (reference) and that can be used without the contents operator, are reference variables in ABAP Objects.
All operations programmed with field symbols are applied to the field assigned to it. For example, a MOVE statement between two field symbols moves the contents of the field assigned to the first field symbol to the field assigned to the second field symbol. The field symbols themselves point to the same fields after the MOVE statement as they did before.
You can create field symbols either without or with type specifications. If you do not specify a type, the field symbol inherits all of the technical attributes of the field assigned to it. If you do specify a type, the system checks the compatibility of the field symbol and the field you are assigning to it during the ASSIGN statement.
Field symbols provide greater flexibility when you address data objects:
If you want to process sections of fields, you can specify the offset and length of the field dynamically.
You can assign one field symbol to another, which allows you to address parts of fields.
Assignments to field symbols may extend beyond field boundaries. This allows you to address regular sequences of fields in memory efficiently.
You can also force a field symbol to take different technical attributes from those of the field assigned to it.
The flexibility of field symbols provides elegant solutions to certain problems. On the other hand, it does mean that errors can easily occur. Since fields are not assigned to field symbols until runtime, the effectiveness of syntax and security checks is very limited for operations involving field symbols. This can lead to runtime errors or incorrect data assignments.
While runtime errors indicate an obvious problem, incorrect data assignments are dangerous because they can be very difficult to detect. For this reason, you should only use field symbols if you cannot achieve the same result using other ABAP statements.
For example, you may want to process part of a string where the offset and length depend on the contents of the field. You could use field symbols in this case. However, since the MOVE statement also supports variable offset and length specifications, you should use it instead. The MOVE statement (with your own auxiliary variables if required) is much safer than using field symbols, since it cannot address memory beyond the boundary of a field. However, field symbols may improve performance in some cases.
check the below links u will get the answers for your questions
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/field_sy.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci920484,00.html
Syntax Diagram
FIELD-SYMBOLS
Basic form
FIELD-SYMBOLS <fs>.
Extras:
1. ... TYPE type
2. ... TYPE REF TO cif
3. ... TYPE REF TO DATA
4. ... TYPE LINE OF type
5. ... LIKE s
6. ... LIKE LINE OF s
7. ... TYPE tabkind
8. ... STRUCTURE s DEFAULT wa
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Untyped Field Symbols ad Cannot Use Field Symbols as Components of Classes.
Effect
This statement declares a symbolic field called <fs>. At runtime, you can assign a concrete field to the field symbol using ASSIGN. All operations performed with the field symbol then directly affect the field assigned to it.
You can only use one of the additions.
Example
Output aircraft type from the table SFLIGHT using a field symbol:
FIELD-SYMBOLS <PT> TYPE ANY.
DATA SFLIGHT_WA TYPE SFLIGHT.
ASSIGN SFLIGHT_WA-PLANETYPE TO <PT>.
WRITE <PT>.
Addition 1
... TYPE type
Addition 2
... TYPE REF TO cif
Addition 3
... TYPE REF TO DATA
Addition 4
... TYPE LINE OF type
Addition 5
... LIKE s
Addition 6
... LIKE LINE OF s
Addition 7
... TYPE tabkind
Effect
You can define the type of the field symbol using additions 2 to 7 (just as you can for FORM parameters (compare Defining the Type of Subroutine Parameters). When you use the ASSIGN statement, the system carries out the same type checks as for USING parameters of FORMs.
This addition is not allowed in an ABAP Objects context. See Cannot Use Obsolete Casting for FIELD SYMBOLS.
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. See Defining Types Using STRUCTURE.
Effect
Assigns any (internal) field string or structure to the field symbol from the ABAP Dictionary (s). All fields of the structure can be addressed by name: <fs>-fieldname. The structured field symbol points initially to the work area wa specified after DEFAULT.
The work area wa must be at least as long as the structure s. If s contains fields of the type I or F, wa should have the structure s or at least begin in that way, since otherwise alignment problems may occur.
Example
Address components of the flight bookings table SBOOK using a field symbol:
DATA SBOOK_WA LIKE SBOOK.
FIELD-SYMBOLS <SB> STRUCTURE SBOOK
DEFAULT SBOOK_WA.
WRITE: <SB>-BOOKID, <SB>-FLDATE.
Related
ASSIGN, DATA
Additional help
Declaring Field Symbols
FIELD GROUPS
are used to hold/handle large amount of data when the internal table are not useful
we use EXTRACT statement, HEADER structure in them
see the example
REPORT demo_extract.
NODES: spfli, sflight.
FIELD-GROUPS: header, flight_info, flight_date.
START-OF-SELECTION.
INSERT: spfli-carrid spfli-connid sflight-fldate
            INTO header,
          spfli-cityfrom spfli-cityto
            INTO flight_info.
GET spfli.
EXTRACT flight_info.
GET sflight.
EXTRACT flight_date.
END-OF-SELECTION.
SORT STABLE.
LOOP.
    AT FIRST.
      WRITE / 'Flight list'.
      ULINE.
    ENDAT.
    AT flight_info WITH flight_date.
      WRITE: / spfli-carrid , spfli-connid, sflight-fldate,
               spfli-cityfrom, spfli-cityto.
    ENDAT.
    AT flight_date.
      WRITE: / spfli-carrid , spfli-connid, sflight-fldate.
    ENDAT.
    AT LAST.
      ULINE.
      WRITE: cnt(spfli-carrid), 'Airlines'.
      ULINE.
    ENDAT.
ENDLOOP.
FIELD STRING is nothing but a string with one row of records.
Reward points if useful
regards
Anji

Difference between Field symbols and field group

Hi experts,
Can you please advice me what is the difference between field symbols and field groups.
Thanks in advance,
Logu.

Field symbols: are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field Groups:
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
A field group combines several existing fields together under one name
like
FIELD-GROUPS: fg.
then you can use one insert statement to insert values in fields of field-group.
INSERT f1 f2 ... INTO fg.
Field symbols
If u have experience with 'C', then understand this to be similar to a pointer.
It is used to reference another variable dynamically. So this field symbol will simply point to some other variable. and this pointer can be changed at runtime.
FIELD-SYMBOLS <FS>.
DATA FIELD VALUE 'X'.
ASSIGN FIELD TO <FS>.
WRITE <FS>.
Field symbols: are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field Groups:
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
example :
DATA: BEGIN OF SPTAB OCCURS 0,
line(1000), " or type string
END OF SPTAB.
DATA: IDX LIKE SY-INDEX.
field-symbols <FS1>.
split tb_sip AT ';' INTO table sptab.
LOOP AT SPTAB.
IDX = IDX + 1.
ASSIGN COMPONENT IDX OF STRUCTURE tb_detsip TO <FS1>.
If sy-subrc = 0.
<FS1> = SPTAB-line.
Endif.
Endloop.
append tb_detsip.
clear idx.
Field Groups / Extracts
http://help.sap.com/saphelp_46c/helpdata/EN/9f/db9ede35c111d1829f0000e829fbfe/frameset.htm
Field Symbols
http://help.sap.com/saphelp_46c/helpdata/EN/fc/eb387a358411d1829f0000e829fbfe/frameset.htm
Reward points if useful.

Dynamic screen layout - Hide Field Group until user selects country

Hi.
Does anyone in the PCUI commuity know how to hide a particular reference field group (field group that contains several fields) and only make it visible when the user selects a particular value from a dropdown in a differen field group on the same screen.
Regards
Sergio

Hi,
I am trying to do something similar in Advance search area of Opportunity. I want to hide few fields for non managers. I created field group variant and added that to field group and all the fields. I modified method if_crm_bsp_model_access_il~get_fieldgroup_variant. I put breakpoint at this method and it does get executed but the page doesnt load correct variant. Did you get this to work? if so can you please share your experience on what else do I need to change to make it work.
I have separate thread going regarding this issue. Here is the URL for that:
[SAP CRM: People Centric UI (Read Only Archive);
Thank you,
AP

Field Group Modification

Hi,
   I have created a ZACC_VW for the CRMM_ACCOUNT Application. I have maintained the customizing Entries for the following: (on view ZACC_VW)
Application
Toolbar Group
Tab Group
All of these work fine when I use the BLVIEW parameter.
   Now, I am trying to hide certain fields on the Detail Tab. I found that the ACC_SRES_01_V1 is the field group being used. In CRMC_BLUEPRINT_C - Field Group Structure, I maintained the entries for ACC_SRES_01_V1 (Instead of 5 reference groups, I have left only 3). I then generate the layout for ACC_SRES_01_V1/ZACC_BMG.
   When I view the application again, I still see all the fields. I am not able to figure out what am I missing?
Thanks,
Ranjan

Hi Arun,
         Yes, I am viewing the application for the ZACC_VIEW (the BLVIEW querystring).
         In CRMC_BLUEPRINT_C - Field Group - Field Group Structure, I have maintained the following entries for ACC_SRES_01_V1:
ZACC_VW 10   ACC_SRES_NAME_V1     SCGR Screengroup
ZACC_VW 20   ACC_SRES_ADDRESS_V1     SCGR Screengroup
ZACC_VW 30   ACC_SRES_COMM_V1     SCGR Screengroup
ZACC_VW 40   ACC_SRES_CONTACT_V1     SCGR Screengroup
then I go to Layout Generation and generate the layout for ACC_SRES_01_V1/ZACC_VW.
When I try the application on ZACC_VW, I still see the fields in ACC_LOG_SALES_CLASS (which is the group I excluded in the ZACC_VW)
Thanks,
Ranjan

Field Group Layout Generation Error

Hi Experts,
I have Created a custom field group using Tr EEWB. now i want to do PCUI customization.
I Have created custom field group and Field Group Structure in tr CRMC_BLUEPRINT_C. now when i am going to create layout for the field group msg coming-
"Program CRM_BSP_LAYOUTC_GENERATE
No field group was selected in the blueprint table"
Please guide me.
Regards!!

Have you included the field group as part of the application layout? Also have you assigned a MAC to the structure referenced by the field group?
Once you have done those steps, then the field group should normally generate.
Take care,
Stephen

Controlling material master access through field groups

Hello SAP Gurus,
We want to control the material master access (MM01/02) using field groups. I am unable to find any authorization object provided by SAP which can control access at field group level.
My scenarios is that certain group of people should be able to only display the fields in MM02 tcode and certain group of people should be able to change it. Please suggest if there is any config which will enable me to do this.
Thanks and Regards
Amit Gupta

Dear usen the following authorization object to contol the field entry on view level,
I donot think at field group level it is there
M_MATE_STA
status are nothiong but views
A     Work scheduling
B     Accounting
C     Classification
D     MRP
E     Purchasing
F     Production resources/tools
G     Costing
K     Basic data
L     Storage
P     Forecasting
Q     Quality management
S     Warehouse management
V     Sales
X     Plant stocks
Z     Storage location stocks

Search help for a field in table control based on another field value

Hi,
I want to attach the Search help for a field in table control based on another field value.
Please help me asap.
Will be highly rewarded

HI,..
Check these links
search help in table control
Re: How to create Search Help for a field in Table control !!
How to create Search Help for a field in Table control !!
F4 Help In Table Control
Control table F4 help
Problem in F4 help in screen field
check this code
DATA: BEGIN OF it_value4 OCCURS 0,
         TEXTCODE LIKE ZXX-TEXTCODE,
         TEXTDESC LIKE ZXX-TEXTDESC,
       END OF it_value4.
progname = sy-repid.
dynnum   = sy-dynnr.
         SELECT TEXTCODE TEXTDESC
           FROM xxxx
           INTO CORRESPONDING FIELDS OF TABLE<b> it_value4</b>
          WHERE LOSS_CODE =<b> IT_VALUE1 .</b>
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield    = 'TEXTCODE'
      dynpprog    = progname
      dynpnr      = dynnum
      dynprofield = 'ITVALUE-TEXTCODE' "-->UR 4 th filed value in screen
      value_org   = 'S'
    TABLES
      value_tab   = it_value4.
endmodule.
Message was edited by:
        veereshbabu ponnada

How to create new field groups in AA master data screen layout?

Hello,
We are using ECC 6.0
We have created bunch of new fields for asset master data, but we want to make them visible only for particular asset class. So we need to customize in SPRO Asset Master Data Screen Layout, but there no specific field groups that we can customize. So how to create and add new field groups to manage them by radiobuttons Required, Optional, No or Display?

hi,
think, it's not possible.
look here:
http://help.sap.com/saphelp_47x200/helpdata/en/4f/71e05a448011d189f00000e81ddfac/frameset.htm
"The field groups and their respective fields are defined in system tables"
kind regards
Andreas

Trading Partner field in control view of Vendor Master

what is the use of Trading Partner field in control view of Vendor Master.
In which business scenario it is used.

I searched the Forum and found many threads on this topic in ERP financial.
This field is connected to FI.
Since I was not aware of this so I posted in MM forum after searching in MM forum. I apologize but this happened due to ignorance.
Below threads will give insight into this
Re: Use of trading partner field in GL Master, Vendor and Customer Master
Trading Partner ??
trading partner
Thanks to all

Grant Master field group control based on authorization - hide fields

Similar Messages

Maybe you are looking for