Why object M_MATE_NEU?

[Former Member]

Hi together

In different Retail systems we have (now) the object M_MATE_NEU which is used o.e. in transaction mm41.

Until now we inserted the object in the roles whit mm41 because is needed to create new products, etc...

But in my opinion this object is not necessary because you can control the creation with M_MATE_MAR or M_MATE_MAT.

There you can use the ACTVT to control the authorization (01, 02, 03).

I would like to deactivate the object in the SU24 for the transactions MM41, etc.

Has anyone had experience with M_MATE_NEU?

Thank you

Best Regards

Tobias

[Colleen]

Hi Tobias

I thought that object was needed to create the new material -  assign the material number. It that the one where the only field value allowed is asterisk?  I think MM01 requires it to launch the transaction (check SE93 definition).

Regards

Colleen

[Former Member]

Hi Colleen

Right, in this object ist only field DUMMY with *

MM01 requires M_MATE_STA, MM41 requires M_MATE_NEU

But why this check for M_MATE_NEU.

Now i have to update all roles with MM41 with this "new" object, that the transaction can be started.

Check to create new material number is in M_MATE_MAR oder M_MATE_MAT

-> Has anyone deactivated the M_MATE_NEU for MM41?

-> Why this check for start the transaction?

Thanks and regards

Tobias

[Colleen]

Hi Tobias

I'm not on a system to check but I suspect it protects generating new material numbers from another transaction. You can use the "create" to extend the view of the materials but you still need the M_MATE_NEU to actually create a new material Id.

You might get more discussion by CCing in one of the functional spaces and checking there

Regards

Colleen