This operation modifies and activates a SNC on the network. If the EMS does not preserve the SNC name, then newSNC will have a different name than formerly addressed SNC, which is deactivated and deleted.
Behavior as createModifiedSNC to find the route and swapSNC to set it on the network.
This operation also applies to bundled SNCs.

Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when operation is not supported.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. INVALID_INPUT - Raised when a field of input parameters is invalid.
4. OBJECT_IN_USE - Raised when the SNC can not be created or activated because of CC, or TP conflicts (e.g.
    because of timeslot conflicts) or conflicts between the active route (with equal or higher priority) of this and other
    SNCs or when CC creation would involve a TP that has an existing fixed CC that does not match that required for
    the SNC.
5. ENTITY_NOT_FOUND - Raised when fields of input parameters (e.g. sncModifyData) reference objects that does
    not exist.
6. PROTECTION_EFFORT_NOT_MET - Raised when the NMS requests an new SNC with a static protection level
    and protection effort that cannot be met by the EMS.
7. UNABLE_TO_COMPLY - Raised when the SNC cannot be created /activated because it cannot comply with any of
    the input parameter (e.g. sncModifyData) contraints for a reason different than the ones above. 
    Raised when the EMS is unable to execute the request because at least one of the parameters although valid can
    not be set and that parameter is identified as "not best effort" in the supporting document LayeredParameters.pdf
    associated to the TransmissionParameters object or in additionalInfo; i.e. the whole operation will be rejected
    if one parameter fails that must be set. This is potentially usable for cases where a parameter must be set for
    the SNC to be valid.
    If the EMS cannot determine the reason it could not comply, it is also allowed to throw UNABLE_TO_COMPLY.
8. UNSUPPORTED_ROUTING_CONSTRAINTS - Raised if the EMS does not support the routing constraints specified.
9. USERLABEL_IN_USE - Raised when the userLabel uniqueness constraint is not met.
10. NOT_IN_VALID_STATE - Raised where the SNC would involve a CTP that is not connectable due to the state of
      the server TP or in the case of inverse multiplexing where the SNC would involve a CTP that is not connectable due
      to the state of the client TP.
11. NE_COMM_LOSS - Raised when communication to managed element is lost and this prevents any change to the SNCs.
