WRFMASSMAT does not work properly

[Former Member]

Hello,

this is my first post in this forum.

I have a problem regarding the Transaction WRFMASMAT. This transaction should be available to users without the permission to access the transcation MM42. I have added all neccessary objects from the MM42 to the WRFMASSMAT and there is no error message in the transaction. But the data, which was changed by this transaction, was not written to the master data table. MM43 shows still shows the unchanged data. The SLG1 reports an error, but there are no objects oder transactions, for which i could give permissions.

What can i do ? Is there a possibility to make the WRFMASSMAT available to users without granting permission to the MM42 ?

Thanks for your help.

Greetings

Ingo Schroeder

[paul_gendreau]

You asked: "Is there a possibility to make the WRFMASSMAT available to users without granting permission to the MM42?"

The answer is Yes.

There are primarily two transactions that are relevant for this process:

WRFMGROUP - Maintenance Group Management

WRFMASSMAT - Integrated Mass Change

When using WRFMGROUP to create Maintenance Groups, youu2019re able to choose from a long list of preconfigured field

groups, each of which includes a short list of related Article Master fields.

By adding preconfigured field groups to a Maintenance Group, in mere minutes youu2019ll enable users to mass maintain a

limited list of fields.

If standard field groups fail to meet your requirements, then you can configure a custom field group and then reassign

fields from standard field groups to your custom field group. As a final step, youu2019ll add the custom field group to a

Maintenance Group.

No matter whether youu2019re using standard field groups or rolling your own, you may encounter this error message while

using WRFMGROUP to add a field group to a Maintenance Group: Field group XXX is not allowed for mainenance group.

This error is presented because thereu2019s a substantial list of fields that are not allowed for use with Maintenance Groups,

no matter that these fields are included in standard field groups. The list of not-authorized fields is determined by function

module WRF_GEN_HIER_CHECK_FGROUP.

Please note that if you havec customer defined fields then these will not be updated. Fore this, see SAP Note 1024725 WRFMASSMAT: How to support customer defined fields

[Former Member]

Hello Mr. Gendreau,

Thank you for your answer.

We have defined this groups and we used the WRFMGROUP to do this. The Problem is, that the WRFMASSMAT says, that the Transaction was sucessfully, but in the master data there were no changes made. SU53 reported no errors, everything is green.

For example, in the field length we made an update and WRFMASSMAT reports, that the change was successfully done. But the SLG1 of this user reports an error : No permission on this transaction. But there is no transaction named.

Could it be, that WRFMASSMAT needs database access to write the changes ?

Greetings

Ingo Schröder

[paul_gendreau]

Then this sounds like a security issue for the user. While the user does not need authorization for MM41/MM42/MM43, the user does require correct authorizations to maintain the objects.

You should make use of transaction ST01 to check the AUTH objects and activities that are being accessed and are failing. This will inform you of the required authorization objects and activities that must be maintained for the user / role.

[Former Member]

Hello Mr. Gendreau,

Thank you for your fast answers.

I tried the ST01 and i found only one row with an Return code <>0.

10:36:47:413 AUTH - - - M_MATE_WRK RC=4 tcode= ;ACTVT=03;WERKS=Z100;

How can i integrate this issue in the role ? What do i need to do ?

Best regards

Ingo Schröder

[paul_gendreau]

Please work with your security administrator to solve this issue. An understanding of Authorization Profiles and how Authorization Profiles are maintained in your own system is required.

Transation PFCG can be used to maintain Roles and Authorization Profiles.

Perhaps a strategy is to create a new role, assign the required Authorizations (e.g. Authorization Object M_MATE_WRK, Materials Management: Master Data), Activities, and Organization Levels to the new role, and then add your WRFMASSMAT users to the new Role.