B2B Deployment overrides the Business Action Selection for Inbound

Question

Hi,
Following is the scenario, please let me know what configuration mistake I am doing and give me any possible Fix or Work around.
a. Host_TP_AS2_ID_1 & External_TP_1 ---> Agreement_A --> BusinessAction_A --> Document Rev. Protocol_A --> DocumentType_A --> DocumentDefinition_A
b. Host_TP_AS2_ID_2 & External_TP_2 ---> Agreement_B --> BusinessAction_B --> Document Rev. Protocol_B --> DocumentType_B --> DocumentDefinition_B
Document Definition for both A and B as follows...
DD for A:
To Role: Host_TP_AS2_ID_1 (host)
From Role: External_TP_1
Identification Expression (XPath) for XML Document: /*[local-name()='Pip3B12ShippingOrderConfirmation']
Document Routing ID: DT_Pip3B12ShipOrderConf
DD for B:
To Role: Host_TP_AS2_ID_2 (host)
From Role: External_TP_2
Identification Expression (XPath) for XML Document: /*[local-name()='Pip3B12ShippingOrderConfirmation']
Document Routing ID: DT_Pip3B12ShipOrderConf
When I create a new deployment for "a" and deploy, the inbound finds the right Agreement for the incoming Trading Partner Identifiers, Business Action and successfully processing it.
When I create a new deployment for "b" and deploy, the inbound cannot find the right Business Action, It error out saying that for Host_TP_AS2_ID_2 & External_TP_2, not able to find the "BusinessAction_A".
Now the question, for the second set of Trading Partner combination ("b"), why is it looking for Business Action of "a".
The Interesting part is, if I deploy the "b" first and "a" second, the Error is the other way.
Did anybody B2B customer encountered any kind of issue like this. Is there any solution, patch or work around for this kind of issue.
Thanks
Bala

Answer 1

Use case still remains the same -
Following is the scenario, please let me know what configuration mistake I am doing and give me any possible Fix or Work around.
a. Host_TP_AS2_ID_1 & External_TP_1 ---> Agreement_A --> BusinessAction_A --> Document Rev. Protocol_A --> DocumentType_A --> DocumentDefinition_A
b. Host_TP_AS2_ID_2 & External_TP_2 ---> Agreement_B --> BusinessAction_B --> Document Rev. Protocol_B --> DocumentType_B --> DocumentDefinition_B
Document Definition for both A and B as follows...
DD for A:
To Role: Host_TP_AS2_ID_1 (host)
From Role: External_TP_1
Identification Expression (XPath) for XML Document: /*[local-name()='Pip3B12ShippingOrderConfirmation']
Document Routing ID: DT_Pip3B12ShipOrderConf
DD for B:
To Role: Host_TP_AS2_ID_2 (host)
From Role: External_TP_2
Identification Expression (XPath) for XML Document: /*[local-name()='Pip3B12ShippingOrderConfirmation']
Document Routing ID: DT_Pip3B12ShipOrderConf
The only additional complexity is we need to route the documents we receive from different trading partners to different bpel processes so that trading partner specific logic can be applied to the processing in bpel.