B2b picking wrong CPAId with Business Action Name/Service having same names
131252Sep 2 2009 — edited Oct 8 2009we are using ebms 2.0 exchange and are setup to receive documents sent from our TP with same Action Name. (env: 10.1.2.3 and on latest patchset)
Example:
From Party : TP
To Party: Host
Service: Invoice
Action: SendFile
Version 3.0.0
Business Action: SendFile
CPAId: Invoice
Document RouteID: B2BInvoiceUser
Document Type: Invoice
Revision:3.0.0
From Party : TP
To Party: Host
Service: ShipNotice
Action: SendFile
Version 3
Business Action: SendFile
CPAId: ShipNotice
Document RouteID: B2BASNUser
Document Type: ASNDoc
Revision:3
From Party : TP
To Party: Host
Service: BuldShipmentStatus
Action: SendFile
Version 4.0
Business Action: SendFile
CPAId: BulkShipmentStatus
Document RouteID: B2BBSSUser
Document Type: BulkShipmentStatus
Revision:4.0
Everytime we receive a message the first agreement gets picked (ie. CPAId: Invoice) instead of the CPAID that matches the ebms envelope and this causes the BPEL process to fail since its expecting B2BBSSuser ( in case of Bulk Shipment document) as the document routingID, the XML path is set different for the above 3 types. This is causing all kinds of issue and we are expecting 3 new documents to be setup with the same Action Name/Business Actions(SendFile). This used to work on the old release and now it fails although the Business Actions do have unique version numbers. Let me know if anyone else has has similar issue with Business Actions.
Thanks,
PT