we want to prevent showing explain plan which has contain making dirty data method which has following example. Our first problem was when consultans wants to "show view" ,they could able to see "view" which has contain dirty method. And we solved that we use two view layer.
But now we have another problem following that. Is there any way to avoid to seeing data dirty method in explain plan?
I'm not sure what you mean by a dirty data method, but it looks like you are using otranslate to encrypt and decrypt CRD_ID. This was state-of-the-art 2000 to 200 years ago but is not considered secure today: with a computer it is far too easy to crack this code even without seeing the view definition or explain. The real answer is to invest in a genuine security system, such as Protegrity, that encrypts under the covers and uses modern encryption methods.
On the other hand, if this join is the only part of the explain that reveals the otranslate, then you could remove the otranslates from the join altogether because you don't need them - just join on (right).CRD_ID=(left).CRD_ID. If the otranslated IDs match then the untranslated IDs match too.