Hierarchy
SAP_GWFND (Software Component) SAP Gateway Foundation⤷
OPU-BSE-SDE (Application Component) Gateway SAP Data Enablement⤷
/IWBEP/MGW_COF (Package) OData Channel - Configuration
IMG Activity
| ID | /IWBEP/URM_USR_CAT | Maintain User Category |
| Transaction Code | /IWBEP/92000019 | (empty) |
| Created on | 20130510 | |
| Customizing Attributes | /IWBEP/URM_USR_CAT_A | Attributes for User Category |
| Customizing Activity | /IWBEP/URM_USR_CAT_M | Maintain user category |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /IWBEP/DOCU_USR_CAT |
Use
You can maintain the list of user categories for your application using this activity. Each user category is mapped to a Reference User. Reference user should be created in the system with roles and authorization required for the application.
Note: This is a mandatory activity.
Consider a B2C application "A". The application "A" provides a self service for B2C customers to create users in the system. In case you want to restrict the user's action based on certain category (let's say "Agent" or "Normal User"), you can define categories "Agent" and "Normal User" using this IMG activity. You should also maintain a reference user for both categories.
Requirements
You can define a standard set of user categories for each application. The user category shall be part of the UserRequest entity of USERREQUESTMANAGEMENT. During the creation of user request, applications can provide the user category. Based on the user category the corresponding reference user is picked from the configuration table and users are created.
You should create and maintain the reference user for their (categories) application in the system. The reference user shall be assigned with roles and authorization required for accessing their applications. The reference user shall be used as a reference for creation of users. If reference user is not maintained in the system an error is thrown.
Activities
1. Click New Entries.
2. Enter the external service name of the OData service used for User Request Management in the External Name field.
In case if you have not extended the OData service "USERREQUESTMANGEMENT" delivered by SAP, then enter "USERREQUESTMANAGEMENT" in the External Name field.
3. Enter a version number.
In case if you have not extended the OData service "USERREQUESTMANGEMENT" delivered by SAP, then enter "0001" in the Service Version field.
4. Enter the namespace used in the User Request Management OData service in the Namespace field.
In case if you have not extended the OData service "USERREQUESTMANGEMENT" delivered by SAP, then enter "/IWBEP/" in the Namespace field.
5 Enter a three digit number for the user category in the User Category field that shall be used in the application.
6 Enter a text in the User Category Text field, for example 'Agent'.
7 Enter the reference user name (maintained in the system) in the Ref. User Name field.
Example
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| /IWBEP/C_MGWURMU | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20130510 |
| SAP Release Created in | 200 |
