Idoc Serialization for multiple idoc types

[former_member189558]

Hello,

We have a requirement that we need to serialize two different idoc Types -- purchase Order Create and Purchase Order Change (for each PO Number) flowing from Process Orchestration to SAP Backend System.

Now, we can populate the Queue Name based on PO Number by generating the que name dynamically. Ref blog: http://scn.sap.com/community/pi-and-soa-middleware/blog/2015/02/06/adapter-module-development-set-qo...

We can use the above approach to populate the que name for both the PO Create Interface and PO change Interface --  the same que id can be populated if we use Purchase Order number as a part of the queue name.

However, if we do so:

• Will these remain serialized in the SAP backend System as well after the idocs reach ECC?
• Every different Purchase Order will have a different Queue Name -- then how would that impact the system since we would have a large number of queues building up in the system? Is there any limitation on the number of queues in the system?
• My understanding is if an Idoc fails in ECC, then the others in same queue will be delivered to ECC from PO and will be stuck up with ECC(IF serialization is still maintained in ECC). Then that would require manual intervention. Is this understanding correct?

Thanks and Regards,

Himadri

[former_member187587]

Can you please clarify the business requirement rather than specifying a technical solution?

Why do you need to serialize these two IDocs?

Are you having a case where a PO update is reaching the ECC before a PO creation?

Which application is sending the messages?

[ravicarpenter]

Hi,

From your scenario I understand that you require to serialize the idocs PO Creation + Change in a single interface (might be using multimapping) - Is this correct ?

If so, then in the receiver IDoc channel you need to tick the Queued option

I don't think you need any mechanism to populate the  queue name - Its generated by ECC with SAP_ALE_XXXX

On the ECC side if the first idoc in the queue let's say creation ends up in error then the corresponding change idoc will fail. However the next pair of idoc will continue to process.

You can simulate above and check the behaviour yourselves.