Find the Prepaid Accounts related to a User Technical Identifier

Service Operation (WS)

Definition

To find all the prepaid accounts related to a User Technical Identifier (UTI) in customer master data

Technical Data

Software Product and Version	SAP Convergent Charging 2022
Technical Details	prepaidAccountFindFromUserTechnicalIdentifier
Namespace	http://refilling.v1.ws.highdeal.com/ http://refilling.ws.highdeal.com/
Proxy Instance in SAP CC System	Updater
Service Operation Version	0
Application Area	IS-CC
Direction	inbound
Mode	synchronous
Idempotency	false

Business Context and Use

This service operation enables you to find a prepaid account stored in SAP Convergent Charging from a Customer Relationship Management (CRM) application. Note that you specify at least which is the User Technical Identifier (UTI) related to the searched prepaid account.

Related Service Operations

You can use the following operations to perform actions on prepaid accounts:

Features

This service operation enables you to find a prepaid account relating to an end customer specified by his User Technical Identifier (UTI). This UTI can be a phone number or an email address. You implement this service operation in your connected application or system to search for this prepaid account stored in SAP CC.

You must specify the technical identifier of the end customer who may have registered a prepaid account. The result of the operation is a list of non distinct prepaid accounts.

Options

Optionally, you can specify the Service Identifier (SID) and the date. If so, the result is zero or one prepaid account.

Note

If you do not specify the date, the SAP CC system uses the current date to process the operation request.

Authorizations

To know the role that is expected in the user profile of the SAP CC user specified in your request messages, refer to the SAP CC Security Guide .

Error Handling

The SAP CC system may return an error classified into a category and an error stack detailing the issue and its cause.

Categories and Treatments to Implement

Consider the following error categories to design and implement the appropriate behavior of your connected application or system:

Error Category	Description	Error Handling
Already Exists	The data has to be created but another data already exists in the connected SAP CC system with the same type and the same identifier.	Applicable for this service operation: You implement the logging of this error to enable a system administrator or a consultant to investigate and resolve the issue. Data replication or data synchronization mechanisms may fail.
Does Not Exist	The data to be modified or deleted does not exist in the connected SAP CC system.	Applicable for this service operation:
Invalid	The request or the data is invalid.	Applicable for this service operation: Next follows a non-exhaustive list of errors related to the Invalid category: The User Technical Identifier (UTI) is not set in the operation request
Incompatible Configuration	The configuration of the connected SAP CC system is not compatible with the data specified in the operation request and the scope of the request. Creating or correcting the prerequisite configuration data (master data, business data) has to be done in the SAP CC system with the Core Tool user interface or within your connected application or system.	Applicable for this service operation:
Prerequisite Missing	Another data mandatory for the operation is not available or is not compatible with the data specified in the operation request. Create a prerequisite for the data.	Applicable for this service operation: The prerequisite data is managed outside the SAP CC system.
Illegal State	The operation request is valid but was rejected because of the current state of the data in the connected SAP CC system which prevents the execution of the request. The current state of the complete system can be also the origin of the error.	Applicable for this service operation: The request will not succeed without a required manual correction or change in the SAP CC system. You implement error logging and manual retry mechanisms.
Temporary Illegal State	The valid request was rejected because of the temporary illegal state of the data in the connected SAP CC system. The data state may automatically change without any further notification. This is a subcategory of the Illegal State category. The state of a data is temporary illegal but the operation request can be sent again after a waiting period. The current state of the complete system can be also the origin of the error.	Applicable for this service operation: You can implement an automated resend function.

Note

This list of errors is not exhaustive: consider the technical details of the operation response.

Troubleshooting

Refer to the SAP CC Error Code Reference for more information about a returned error code and the corrective actions necessary for troubleshooting your implementation project.

Message Types

Consult the structures of the message types related to this service operation :

Prerequisites

At least one subscriber account and one prepaid account included in this subscriber account must exist.

Integration

You can use this service operation to identify the prepaid account to be refilled (see the Refill a prepaid account operation).

Constraints and Integrity Conditions

There is no specific constraint.

Notes on SAP CC Implementation

You must have installed and configured the SAP CC Core Server system.

Configuration

Consult the SAP CC Configuration and Implementation Guide to know the necessary configuration or Customizing of the SAP CC system.

Before implementing SAP Convergent Charging in your SAP system landscape, you must configure the systems and the data (master data, business data).