This operation modifies the route of the addressed SNC.

If the EMS does preserve the SNC name, the addressed SNC route is modified. If the SNC was in PENDING or PARTIAL state, then the state is unchanged. If the SNC was in ACTIVE state, then the output state is PARTIAL. In case the SNC has several routes, then the administrative state of the addressed route will always transit to LOCKED state.

If the EMS does not preserve the SNC name, then the operation creates a new pending SNC from an existing pending or active SNC. It is similar to createSNC except that the created SNC is made based on an existing one.
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 if the SNC can not be created because of CC or CTP conflicts with other SNCs (e.g.
    because of timeslot conflicts).
5. ENTITY_NOT_FOUND - Raised when fields of input parameters (e.g. sncModifyData) reference objects that do
    not exist.
6. PROTECTION_EFFORT_NOT_MET - Raised if the NMS requests a new SNC with a static protection level and
    protection effort that cannot be met by the EMS.
7. UNABLE_TO_COMPLY - Raised if the SNC cannot be created because it cannot comply with any of the input
    parameter contraints 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.
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.
