Create and activate a Subnetwork Connection. 

Operation Exceptions:
1. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
2. INVALID_INPUT - Raised when any input parameter is syntactically incorrect (e.g. an attribute of SNCCreateData is
    invalid), or in case a bundled SNC is requested, the GTP endpoints of the SNC do not match, i.e., the GTPs do not
    have the same number of CTPs and in a particular order with respect to their layerRates or are not of the same layer
    rate.
3. ENTITY_NOT_FOUND - Raised when attribute values of sncCreateData or tpsToModify refer to an object that does
    not exist.
4. OBJECT_IN_USE - Raised when the SNC can not be created and activated because of CC or TP 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. UNABLE_TO_COMPLY - Raised when the EMS is unable to find an appropriate route for the SNC.
    Raised when the EMS can not meet the tolerableImpact requested by the NMS.
    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 the 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.
    Raised when the SNC cannot be activated because the EMS cannot comply for a reason different than the ones above.
    When the EMS cannot determine the reason it could not comply, it is also allowed to throw UNABLE_TO_COMPLY. 
6. TIMESLOT_IN_USE (Obsolete - OBJECT_IN_USE should be used)
      - Raised when the SNC can not be created and activated because of timeslot conflicts with other SNCs.
7. PROTECTION_EFFORT_NOT_MET - Raised when the NMS requests an SNC with a static protection level and
    protection effort that cannot be met by the EMS.
8. USERLABEL_IN_USE - Raised when the userLabel uniqueness constraint is not met.
9. UNSUPPORTED_ROUTING_CONSTRAINTS - Raised when the EMS does not support the routing constraints specified.
10. NE_COMM_LOSS - Raised when communication to managed element is lost and this prevents creation of the SNC.
11. 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.
      (Obsolete usage - OBJECT_IN_USE should be used instead for the case where an exception is raised when the SNC
      is in conflict with another active or partial SNC and can not be created.)
