BAPI_MATERIAL_BOM_GROUP_CREATE requires C_STUE_NOH

[Former Member]

Hi all,

couple of facts before I get to the point:

- Our customization does not require ECM for BOM create.

- By default our users do not have permission to modify BOM w/o ECM (C_STUE_NOH NOHIS=X is not granted).

With all said above, following the standard process using CS01, a user w/o C_STUE_NOH object assigned is able to create a new alternative BOM w/o ECM required even if there exist other alternatives for this BOM that have already been modified with an ECM. This reflects our configuration mentioned above.

Except for standard CS01 we are using custom program for BOM upload that utilizes BAPI_MATERIAL_BOM_GROUP_CREATE. Our issue is that BAPI_MATERIAL_BOM_GROUP_CREATE requires C_STUE_NOH authorization object whenever we create an alternative BOM if given BOM has other alternatives already modified with ECM.

In other words for the same activity - new alternative BOM create - SAP requires C_STUE_NOH if we use the BAPI and it does not when we use standard CS01.

Giving C_STUE_NOH to all the users is not an option. Using ECM during BOM create is not a valid option either for us.

Can anybody propose a solution how could we stay using BAPI_MATERIAL_BOM_GROUP_CREATE and overcome the C_STUE_NOH requirement at the same time?

Regards,

Jacek

[Former Member]

I tried debugging the FM but its quite large. What you could do is be a little cowboyish and enhance the standard FM. Look for an authorisation call for the object you are mentioning and see if you can place an enhancement before or after the authorisation call to frig that you have it.

Of course you would need to export a flag to memory to only active this enhancement when you actually wanted to use it and prevent any other SAP standard calls getting broken, i.e.

import lv_frig from memory id 'my_frigg'.

if lv_frig = 'X'.

     " code to reflect the fact you have authorisation

     clear lv_frig;

      export lv_frig to memory id 'my_frigg'.

endif.

Cheers,

Adam

[Former Member]

I hope you are not going to create BoM on regular basis. BoM creation may happen once in a while.

Even Master Data creation can be controlled by having only with Master Data Specialist who can create / change the Master data.

And you can assign that authorization object only to specific user(s).