The operation is used to put an already created SNC into the ACTIVE state.
More precisely, all the SNC routes, intended and backup, if any, are unlocked. The restoration process will take control of the unlocked routes and activate the proper one.
Note: The behavior of sncState is not dependend on the number of routes associated to the SNC.
The operation also applies to bundled SNCs.

Operation Exceptions:
1. NOT_IMPLEMENTED - Raised when an EMS does not provide this operation; this is only allowed if the EMS does not
    support the PENDING state and if the PARTIAL state is unreachable.
2. INTERNAL_ERROR - Raised in case of non-specific EMS internal failure.
3. INVALID_INPUT - Raised when any input parameter is syntactically incorrect (e.g sncName does not refer to an SNC
    object, or any field in tpsToModify is invalid).
4. ENTITY_NOT_FOUND - Raised when sncName or tpsToModify reference an SNC/TP object that does not exist.
5. OBJECT_IN_USE - Raised when the SNC can not be 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.
6. TIMESLOT_IN_USE (Obsolete - OBJECT_IN_USE should be used)
     - Raised when the SNC can not be activated because of timeslot conflicts with other SNCs.
7. NE_COMM_LOSS - Raised when communication to managed element is lost and this prevents any change to the SNC.
8. UNABLE_TO_COMPLY - Raised when the SNC is in PENDING state and is in conflict with another active or partial SNC.
    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; 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.
    If the EMS cannot determine the reason it could not comply, it is also allowed to throw UNABLE_TO_COMPLY.
9. 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.)
