How do queues / mappings work internally?
I have some experience in mapping tools outside XI which are "source oriented". This is quite simpy as the source message is "read" top -> down and you can define at each field which action should be done.
So as you all knwo XI message mappings are "target oriented". There is the queue concept which seems to be one of the most complicated and frustrating issue in XI I have some experience in XI message mappings, but I really would like to understand more in detail how queues and message mappings in general work internally. How does the XI mapper "read" the target structure which actually contains the mapping code? What happens internally for example when you watch the queue of the PARVW field of the E1EDKA1 segment using a "removeContext" function afterwards? What happens without the removeContext function?
Any information, link to blogs etc. is appreciated.
Message was edited by: