A Routing Key is used to store the routing information for an IDoc. Creating Routing Keys prevents defining the routing each time an IDoc is generated. Instead, an IDoc type can be associated with its Routing Key, which then sends it on to its defined destination. For example, a Routing Key (named "KEY01") is created in which is stored the information for routing the IDoc "INVOIC01". When an IDoc is generated with the name "INVOIC01", and is submitted to either the IDoc Handler or the Application Integration Component (AIC), it is automatically sent to the destination defined in the Key. Routing Keys can also be renamed.
When a Routing Key is created, it is associated with a valid MSMQ Queue. If the Queue is then deleted, the routing is broken.
To create a routing key
After the routing keys are created, you must associate a routing key with an R/3 destination or a queue.
To associate a routing key with an R/3 destination or Messaging Queue
Click the arrow to move it to the Selected Routing Keys section. Clicking the arrow moves all available routing keys to the Selected Routing Keys section.
A valid destination must be associated with a routing key for the key to successfully transfer the IDoc. If two or more routing keys are created for the same IDoc type but the first key does not have a destination, the IDoc will be transferred using the first routing key in the list with a valid destination.