4 Replies
-
The best model type I have found for mapping data to data connections is the Technical Terms Model. Most of the other model types want data to be connected to a function or application which transforms it into other data.
Rick
-
Yes, Rick is right, Technical Term model is a very good solution, the two alternatives I used being Program Flow Chart and EPC, the latter used in a non-conventional way: Data Object > Function > Data Object w/o connections between functions. So, in the first alternative the ïntermediary is Application System Type and in the second - Function. The Data Object could be Cluster/Data model, ERM attribute, Class or Technical Term. However, if you expect to syncronise such models with Solution manager, that might be a problem.
I have no experience with SAP SERM and as far as I know it is also not supported for synchronisation with Solution Manager.
-
Yes, we use as well technical term -model as the CONCEPT -model that can be discussed with business. Based at this one we create the logical ERM -model that is a formal design of information independently of physical databases and information resources. This is the "canonical" model that ESB (enterprise service bus) is using for routing, transformation, etc ...
Only then the designer do the mapping to the ohysical models that application interfaces require.
The content of the effort to make this extensive modelling is to manage external integration, and cross-application integration.
How to model relationships is a story of it own ....
-
I would assume the right way to model such request would be the "data flow diagram" in ARIS. My problem is that I can't find any information about it or how to access it. Maybe I have the wrong lisences.