Skip to Content
0
Former Member
Dec 23, 2014 at 09:33 PM

Material Master Data Integration (MM01, MM02, BAPI_MATERIAL_SAVEREPLICA)

462 Views

Hello SDN Experts.


I have a business scenario that I am working on & would like to gather feedback from you if you have any insight on how to accomplish the following:


Background: My company runs SAP-MDM Netweaver 7.1 (SP10) and interfaces item (aka material master) data into SAP-ECC using BAPI_MATERIAL_SAVEREPLICA. We look at SAP-MDM as the point of entry for all MRO parts. And users, under no circumstances, should update basic data or purchasing views directly in SAP-ECC (those views should only be maintained from SAP-MDM).


The question is... How can I lock the fields on the Basic Data & Purchasing views so that they are not maintainable by the online users via MM01 or MM02 but allow the BAPI to update these fields?


Solution: Currently I don't have a solution. I know that I can lock specific fields down using the field groups in config (trans code OMSR). But, typically if a field is modified to be a display field, the rule is applied to the online transaction (MM01/MM02) and the BAPI (there is an exception if the field is required in that the BAPI can update it... but once updated on a create, the changes are not considered).


Do any of you know of a BADI / User Exit that would allow me to introduce logic that states-- if running the transaction online and the material type is ERSA (Spare Part) the Field Reference is X (and I have display only ability to my MDM managed fields based on X's configuration). Meanwhile, when the BAPI is called, Field Reference Y is called. Which is configured to have change rights to my MDM sensitive fields.


This is just one of may alternatives I've considered but it seems viable. But I'm open to any & all considerations on the topic.


Notes:

The Field Reference associated to a material type is configured using OMS2.

The Field References & Field Selection Groups are configured via OMSR.


Any and all ideas are welcome. Thanks for reading & considering this post.