You can use this pattern to process various types of IDocs that have a single program identifier without being required to redeploy or rediscover existing message sets and adapters, even when you are adding different types of IDocs.
Use this pattern when:
The solution is to implement an IDoc Routing message flow that processes IDocs of all types by using the generic pass-through message set. Partial parsing allows the IDoc routing message flow to determine the IDoc type and put the IDoc, as a bit stream, on an appropriate WebSphere MQ queue. A single message flow is required for each IDoc type that gets this message and processes the IDoc as if the flow started with an SAPInput node. To implement these message flows, you must run the Adapter Connection wizard for the IDoc that the message flow is going to process, then you must use the DataObject domain and set the message format to IDoc. The adapter component that is created by the Adapter Connection wizard is not required when you are using the message set with an MQInput node. Subsequent IDoc types can be supported by creating a new message flow and a new queue.
Read the following section about the design of the message flows in this pattern.
Read the following section for information about how to apply and use this pattern.
Constraints on the use of the pattern