Usage Profile 
The Enterprise Services Repository is a development environment where vast numbers of users achieve different goals based on their requirements. It represents not only the central access point for users to develop services, but also access to the development of cross-component processes based on the exchange of XML messages. As the ES Repository caters to a variety of users, it contains numerous models and design time objects. However, only a small subset of these objects may be of interest to different user groups. The ES Repository provides the functionality to adapt the environment to your needs. Depending on the goals you wish to pursue, you can have a different subset of objects from the ES Repository which helps to reduce the complexity of the tool. The usage profile defines the set of object types, software component versions and business modeling filters that you can use. They are personalized filters that enable you to view and work with only a set of object types, software component versions and modeling filters required to achieve your goals. All the other object types are hidden.
Note
The Usage Profile is referred to as Application Profile in previous versions of the product.
In the ES Builder, you can choose from a set of predefined usage profiles delivered by SAP. However, if they do not meet your requirements, then you can create your own usage profile.
Standard Usage Profiles Available in the ES Builder
Based on the common usage of various user groups or roles, SAP delivers three predefined usage profiles. You can choose from the following standard usage profiles available in the ES Builder:
Service Development
This basic selection facilitates modeling and interface development.
Process Integration
This basic selection facilitates the modeling of cross-component processes and the development of interfaces and mappings, as well as adapter objects.
Unrestricted
This basic selection contains the total amount of object types of both of the Service Development and Process Integration usage profiles.
When you log on to the ES Builder for the first time you can choose a usage profile based on your requirements. However, you can always change this selection later in the ES Builder.
More information: Choosing a Usage Profile
The above usage profiles are only available when you import the software component version SAP Basis 7.11 or higher content into the ES Repository. If you do not import the SAP Basis 7.11 content then you are assigned a default usage profile during login. This default usage profile allows you to view and edit all the objects types. However, ARIS modeling is not available for the default usage profile. Once you import the SAP Basis 7.11 content into the ES Repository, the default usage profile is deactivated and you can choose from the available usage profiles.
If the imported SAP basis content is corrupt or does not contain usage profile objects, then the login is aborted with the message No usage profiles present as part of the SAP Basis content. In such a case add the property com.sap.aii.ibrep.core.filter.defaultFallBackFilter=true to enable the default usage profile and once again import the content SAP Basis content.
Creating Personalized Usage Profiles
If the above standard selections do not meet your requirements, then you can create your own usage profile.
Note
Only system administrators can create usage profiles.
You can create a new usage profile to:
Define Personalized Filters
Based on your requirements, you can select the object types, software component versions, and business modeling filters that you want to view and work with. Only the objects you select will be visible in the navigation pane. These settings are stored as your personal settings and preserved for subsequent logins.
When you create a new usage profile, you select the object types and mark them as Visible or Editable in the usage profile editor. Based on the values specified, you can only view and edit the set of object types defined by the usage profile. If you do not mark an object type as Editable during the usage profile definition, then these objects are hidden.
Assign Modeling Filters
In ARIS there are predefined filters that restrict access to the modeling entities for users. These ARIS filters define the modeling entities that a user is allowed to view and use.
In a standalone ARIS these filters are assigned to the users. The users select a filter when logging into ARIS. Each filter defines the objects available for view and use.
However, in the integrated ARIS, these filters are available in the usage profiles. When you create a usage profile, you specify the ARIS filter that you want to assign to this usage profile. You can then assign users and roles to this usage profile to impose restrictions, this means that when users select a usage profile during login to the ES Builder, the same usage profile restricts access to users for both the object types in ES Repository and the modelling entities in ARIS. The usage profile serves as a filter that allows users direct and controlled access to all the modeling entities. This way, you can restrict the modeling users to the usage of predefined filters, as they are used to from standalone ARIS.
More information: Creating a Usage Profile
Assign Filters and Impose Restrictions on Users
You can define filter settings for other user groups or roles using the usage profiles. Based on their usage, you can specify the object types that they can view and edit. These filters are available to the users as initial setting when they log on to the ES Builder. The users can only view the objects types they are assigned to in the navigation pane. All the other objects types are hidden.
You can assign a user, user group, or role to a usage profile. Assigning users to usage profile help to:
Customize the usage profile to adapt to the needs of specific users
Restrict authorization to users via the usage profile and serves as means of imposing restrictions on users for access to objects types in the ES repository.
You can assign users even for the standard usage profiles Service Development, Process Integration and Unrestricted that is shipped with SAP Basis content.
For every usage profile, you can only assign Execute authorization to an individual user, group, or role in the ES Repository. If no users are assigned to a usage profile, then it is applicable for all users. However, if you assign users to a usage profile then it is applicable only for those users whose credentials match the assignment.
If, for example, a user is assigned to a role A, then the user can only view the usage profiles that are assigned to this role. If another user logs in with a different role (B), then only the usage profiles that are assigned to the role B are displayed. The usage profile assigned to role A will be hidden.
More information: Editing Authorizations
Note
By hiding individual object types you can further adapt the basic selection defined by the usage profile to your individual needs.
More information: Choosing Object Types
Effects of Selection of a Usage Profile
The following areas of ES are affected based on usage profile restrictions:
Navigation Path
The navigation path only displays the object types defined by the usage profile.
Create Dialog
The create dialog only displays the object types that are editable.
Object Editor
The restricted object types and software component versions are displayed in the object editor pane only when you navigate to them via references or other means. However, you can only view these objects and they are not edit them.
Deep Copy
A deep copy can not create or overwrite objects restricted by usage profiles. In such cases, these object types are excluded.
Search and F4 Help Dialog
You can only view the software component versions and object types defined by the active usage type using the search and F4 help dialog.
Source Object for Cross Reference
Cross referenced objects are displayed in the read-only mode.
Export and Release Transfer
If you select single objects for Export and Release Transfer, then you can specify only from the editable objects available. However, if you select a software component version for export, all the object types (including the hidden object types) will be exported. For release transfer, you can choose the target software component version only if it is not hidden.
Note
The object types hidden by the usage profile selection will be displayed in where-used lists, change lists, and transport lists. If you open an object from one of these lists, you can view it, but not edit it.