Users 
Description
Attribute Names for USERS
Attribute |
Required/ Optional/ Multiple |
Description |
[User] |
Required |
Delimiter to separate user records. Empty lines are skipped and are not treated as delimiters. |
Org_ID |
Optional |
Name of the |
UID |
Required |
ID that the user uses to log on. |
Password |
Optional |
If you do not specify a password for import, the application generates a password. User creation may fail if the password does not conform to the security policy. This attribute is only available for import. It cannot be exported. |
Role |
Optional, multiple |
List of roles assigned to the user, separated by semi colons. If the role does not exist, a warning will be generated. |
$usermapping$:<system |
Optional |
User ID to which the user is mapped in the system <system_alias>. <system_alias> is the system alias as defined in the portal
system landscape editor. See This attribute is only available for import. It cannot be exported. |
$usermapping$:<system |
Optional |
Password of mapped user in system <system_alias>. <system_alias> is the system alias as defined in the portal
system landscape editor. See This attribute is only available for import. It cannot be exported. |
$usermapping$:<system |
Optional |
Any other attribute value required by an external system <system_alias> to which the user is mapped. <system_alias> is the system alias as defined in the portal
system landscape editor. See This attribute is only available for import. It cannot be exported. |
<namespace>:<name> |
Optional |
Additional field in the form: namespace:name=<text_value> By default the value is interpreted as a text value. If you want to use a binary value, you must use the base64 encoded value with the prefix {BINARY}. Examples:
myApplication:largeUserPhoto= com.sap.security.core .usermanagement:department=Team |
Email_Address |
Required |
The user’s email address |
First_Name |
Required |
self-explanatory |
Last_Name |
Required |
self-explanatory |
Job_Title |
Optional |
self-explanatory |
Department |
Optional |
self-explanatory |
Country |
Optional |
Two-character ISO code for country. For example, enter JP and not Japan. |
Language |
Optional |
Two-character ISO code for language. For example, enter DE and not German. |
Time_Zone |
Optional |
The time zone, either as an abbreviation such as PST or a full name such as America/Los_Angeles. Do not enter GMT+09:00 (Asia/Tokyo). |
Currency |
Optional |
Free text. |
Street |
Optional |
self-explanatory |
City |
Optional |
self-explanatory |
State |
Optional |
self-explanatory |
ZIP |
Optional |
self-explanatory |
Telephone |
Optional |
See rules below. |
Fax |
Optional |
See rules below. |
Mobile |
Optional |
See rules below. |
company
For the telephone, fax and mobile phone fields, the following rules apply:
· Valid characters are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, (, ), +, /, -, SPACE
· Open bracket ‘(‘ and closed bracket ‘)’ must be in pairs
· If included, ‘+’ must be the first or second character (after a leading open bracket ‘(‘). For example:
· +1 650 123-4567
· (+1) 650 123-4567
· 1+ 650 123-4567 is not valid
Example
The following is an example of users in standard format.
[User] |
The following example shows how you can change the user mapping data of an existing user, user2. When you import the data, choose the option Overwrite Existing Data in the import tool.
The user user2 is mapped to the user ID ext_user2 in the system BCE, where BCE is the system alias of the system defined in the portal system landscape.
[User] |