The update subscriber response is returned as a generic <ns2:sdsResult> response. This response returns the result of the request to provision subscriber and/or routing entities. A single result applies to all routing entities supplied. Either all subscriber and/or routing entities were successfully updated, or no updates were made.
If applying all of the provisioning changes results in no database records being modified because the database already contained the updated values, the NO_UPDATES error code is returned and the number of affected records is 0.
If a subscriber is successfully created or updated, the description field contains lists of deleted, created and changed IMSI and MSISDN values.
<ns2:sdsResult affected="affected" error="error" [description="description"]> </ns2:sdsResult>
The parameters for all of the response commands are shown in SOAP Response Messages.
| Error Code | Description |
|---|---|
| SUCCESS | The update request was successfully completed. |
| NO_UPDATES | The write transaction did not have any successful updates. |
| DEST_NOT_FOUND | Destination name does not exist. |
| DEST_TYPE_MISMATCH | Destination has a different destination type than the desired destination type. |
| MULTIPLE_SUBSCRIBERS | Specified parameters refer to multiple subscribers. |
| SUBSCRIBER_TOO_BIG | Resulting subscriber would exceed 6 IMSI or 6 MSISDN limit. |
| ACCTID_UPDATE_PROHIBITED | An attempt was made to change an accountId without specifying <deleteAccountId> tag. |
| ROUTE_TYPE_MISMATCH | Standalone and subscriber routes are not allowed in same command. |
| DEL_ROUTE_NOT_PERMITTED | Cannot delete last route from subscriber. |
| NO_ROUTES_SPECIFIED | At least one MSISDN or IMSI must be specified. |
| ROUTE_DEST_MISMATCH | Specified routes have different destinations. |