Restrict Customer Master Maintenance

[Former Member]

I would like to restrict the tabs available on the customer master maintnenace screen XD02 for a specific group of users? Specifically I want to limit a group of users to maintenance of contact persons-general data. Is there a way to do this with either security or configuration? I would like to avoid creating custom code.

Thank you in advance for your assistance.

[Former Member]

I think you can achieve this by creating a new Account group and maintaining the field status for required fields and assigning the account group to the customers.

Reward points if it helps.

[Former Member]

Hi,

You may use authorisation techniques also for this.

The ABAP authorization concept protects transactions, programs, and services in SAP systems from unauthorized access. On the basis of the authorization concept, the administrator assigns authorizations to the users that determine which actions a user can execute in the SAP system, after he or she has logged on to the system and authenticated himself or herself.

To access business objects or execute SAP transactions, a user requires corresponding authorizations, as business objects or transactions are protected by authorization objects. The authorizations represent instances of generic authorization objects and are defined depending on the activity and responsibilities of the employee. The authorizations are combined in an authorization profile that is associated with a role. The user administrators then assign the corresponding roles using the user master record, so that the user can use the appropriate transactions for his or her tasks.

For details refer to:

http://help.sap.com/saphelp_nw70/helpdata/en/52/671285439b11d1896f0000e8322d00/content.htm

Regards,

Renjith Michael.

[Former Member]

Not working completely

[Former Member]

I have defined the field groups and set the authorization using "F_KNA1_AEN". This seems to work for all the standard SAP fields. But I have also appended several fields to KNVV and created the pushbutton and screen (screen group - ZP) to maintain these append fields.

The appended fields have be added to the field groups, but are not protected as expected.

When I debug this process, I do not see the custom screen group (ZP) being processed.

I have looked at OSS note 577502, but after reviewing this note, I still an unclear how to proceed.

Is there a badi that needs to be implemented to have these fields protected?

Thanks in advance.

[Former Member]

We coded the authorization check and validation against t055 in the PBO of our custom subscreen