A client has added a bunch of custom fields to MARC, many of which have dictionary-based validations via value ranges on domains, checktables, etc.
To extend materials to plants in MARC, the client uses a custom function that calls the usual BAPI (material save data or whatever it’s called – I can’t remember.)
In the index to the extension for the BAPI, only one of the many custom fields is “X’d” to tell SAP to consider it.
So, the end result is that materials can be extended to plants without the new MARC records satisfying the rules for data in all but one of the custom fields.
Should this be allowed?
If not, whose responsibility is to stop it?
I mean SAP could easily check the non-X’d extension fields against the dictionary validations for the corresponding custom table columns, and blow off if a validation wasn’t met by an empty (non-X’d) field.
Or, customers could do this themselvesvia implicit enhancments.
Or, customers could enforce clean data via a posteriori or a priori auditing procedures.
What do you think?
Is this a problem anyone should worry about (empirically, as opposed to theoretically)?
Or should everyone just go on their merry way?