The user access specifies the identifier under which a customer consumes a service. This identifier enables SAP CC Core Server to identify the provider contract and the charge for usage rating purposes.
|
Caution: On a platform where SAP CC is integrated with SAP CRM or with another provisioning system, accesses are automatically created and maintained. Creating, modifying or deleting accesses may result in inconsistencies between these two systems. We strongly recommend that you do not modify or delete existing accesses except under support supervision. |
A user access consists of a user identifier and a service identifier. The combination of the user and service identifiers must be unique within the system. This is used by the rating process to identify the provider contract and the charge needed for rating the service.
|
Note: If you are associated to a catalog, you can only open accesses relating to this catalog. |
The pair User Service Identifier/Service Identifier identifies each user access in the database. The same user access can be divided chronologically into unique time periods. You can assign each time period of the same user access to a different or same provider contract. For example, you can divide the user access USI1/SI1 into two time periods:
First time period: From 01 January to 01 February
Second time period: From 01 February to an unspecified date
You can then assign each time period of the user access USI1/SI1 to a different provider contract.
Because user accesses are arranged into a chronological order, time periods cannot overlap but can be discontinuous. For example, you can divide the user access USI2/SI2 into third periods:
First time period: From 01 May to 01 June
Second time period: From 01 August to 01 September
Third time period: From 01 November to 01 December
|
Note: The access chronology is optional. This means that the user access can be assigned to the provider contract for an unlimited time period. |
Example
A customer wants to change a 5 free MMS plan into a 20 free MMS plan on January 1st. In this example, the price plan includes the same service (MMS). Processing possible delayed MMS messages requires to divide the same user access into time periods. This case requires January 1st as the end date of the first user access while the start date of the second access is after January 1st.
You can create or modify user accesses from the File menu.