...

The NEXUSe2e developers interpreted this to mean that the scope of any CPAId's uniqueness may be in the context of two trading partners, as long as the parties agree. Developers of one or more other messaging systems require globally unique CPAId values, regardless of a mutually agreed more narrow namespace. For some connectivity scenarios, these two implementations are incompatible when CPAId values are the same across two or more trading partner pairs.

Work-Around

Work-Around Description, Submitted by Simplot

...

AgGateway does not utilize the ebXML CPA specification to form an agreementagreement between Trading Partners, so the convention to identify the from and to party inin the CPAID element is not necessary. The AgGateway convention for naming thethe CPAId is to use the Document message name unless the business message is usedused to close a conversation, in which case it would use the name of the message toto which the response is being made (See Table 1 below). An example is below:

<eb:MessageHeader eb:version="2.0" SOAP-ENV:mustUnderstand="1">
<eb:From>
<eb:PartyId eb:type="DUNS">878542765</eb:PartyId>
</eb:From>
<eb:To>
<eb:PartyId eb:type="DUNS+4">0503651210000</eb:PartyId>
</eb:To>
<eb:CPAId>OrderCreate</eb:CPAId>

...