the metadata destination is for logging to the system which is not an useful entity for any user but the application destination which actually carries the data is for user so doing all this stuff in a single thing is not good.that's why this seperation is there...
I know what its used for, but honestly in most cases in development the metadata id is someone who has developer access so can access the bapi's etc (ie in SE37) and a lot oc client independant stuff like DDIC. In a production box the model data is mapped to the users who has to have security access to the client in question, but then doesn't that users have to have access so the metadata RFC still work?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.