You are right: Table 15 "CommunicationConfigurationResults Result StatusCodes" implies the existence of the field Result in the CommunicationConfigurationResults, however, the DataType Definition of CommunicationConfigurationResultDataType does not define it.

Added the missing Result to PubSubCommunicxationConfigurationResults (10.8.3)
Added clarification where to set the StatusCode in section 6.2.4.3.9.2

I agree with the updates related to the PubSubCommunicationConfigurationResultDataType to report general issues with the PubSubCommunicationConfiguration.

But to use ConnectionEndpointConfigurationResultDataType.ConnectionEndpointResult also for SetCommunicationConfiguration Cmd errors related to an endpoint is a problem.
If the creation of the endpoint succeeded but the SetCommunicationConfiguration for the endpoint in the same EstablishConnection fails, it is missleading to create the endpoint but the return an error in ConnectionEndpointConfigurationResultDataType.ConnectionEndpointResult.

According to the Abort rollback actions, the endpoint would stay created and only the communication settings are reverted.

needs discussion in a team meeting
The general error (there is just one) would not reflect, which CEP does not fit according to the Variables to the communication model.

As discussed in the prototyping meeting:
Make clear in SetCommunicationCmd where to set which StatusCode (feedback Matthias Damm, Michal Tyndal)
Add a CommunicationConfigurationResult in the ConnectionEndpointConfigurationResult and move some errors from the ConnectionEndpointResult to this one

Clarification integrated into specification, checked back with Matthias and got approval.

The name for CommunicationConfigurationResult is used twice with just a very minor difference - one should be renamed (to easy to confuse)

After some thinking I decided to have the error for a non-matching communication model included in the CommunicationLinksResult; thus no additional error needed.

By adding that to the spec, I detected a lot of inconsistent places, some status tables missing ... some status codes missing. Cleaned them up in section 6.4.2

Reviewed in in multiple call (last being today) , Agreed to all changes and closed issue