Show TOC

Background documentationUser Data Import Format Locate this document in the navigation structure

 

This section describes the attributes used to import user records into SAP NetWeaver Application Server (AS) Java. User records consist of optional and required attributes.

Required Attributes for Importing Users

Attribute

Description

Field Name in User Interface

[User]

Delimiter to separate user records.

The UME skips empty lines.

Not applicable

uid

ID the user uses to log on.

Logon ID

last_name

Self-explanatory

Last Name

Optional Attributes for Importing Users

Attribute

Description

Field Name in User Interface

accessibility

Used to enable the accessibility of Web Dynpro interfaces for users with special needs.

For more information, see Accessibility

Activate Accessibility Feature

city

Self-explanatory

City

cert

You can import the user certificate. Enter the certificate encoded in Base 64.

Not applicable

com.sap.security.core.usermanagement:orgunit

Organizational unit

Organizational Unit

country

ISO 3166 code for the country.

Country

department

Self-explanatory

Department

email_address

The user's e-mail address.

E-Mail Address

fax

Self-explanatory. See also the note below the table.

Fax

first_name

Self-explanatory

First Name

group

List of groups to which to the user is assigned, separated by semicolons (;).

Not applicable

job_title

Self-explanatory

Position

language

Java locale for the country. These are formed by the ISO 639 code for the language followed optionally by an underscore (_) and the ISO 3166 code for the country.

Language

mobile

Self-explanatory. See also the note below the table.

Mobile

org_id

Name of the company to which the user belongs. The company must already exist.

For more information, see Configuring Delegated User Administration Using Companies

Company

password

If you do not include a password for import, the application generates a password.

If the password does not conform to the security policy or if you leave the password attribute empty, the application does not import that user.

If the user already exists and has a password, the application updates the password so long as it conforms to the security policy.

Note Note

This attribute is only available for import. It cannot be exported.

End of the note.

Not applicable

role

List of roles to which the user is assigned, separated by semicolons (;).

Note Note

There is limited support for portal role assignments.

For more information, see Import Format for UME Principals

End of the note.

Not applicable

salutation

How the user is addressed.

Form of Address

state

Self-explanatory

State/Province

street

Self-explanatory

Street

telephone

Self-explanatory. See also the note below the table.

Telephone

time_zone

The time zone, either as an abbreviation such as PST or a full name such as America/Los_Angeles.

Caution Caution

Do not enter GMT+09:00 (Asia/Tokyo).

End of the caution.

Time Zone

zip

Self-explanatory

ZIP/Postal Code

<namespace>:<name>

Syntax Syntax

Custom field with the syntax:

  1. <namespace>:<name>=<text_value>
End of the code.

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}.

Example Example

myApplication:largeUserPhoto={BINARY}h&%AShja4zu8923h(=!&62h345kljhscom.sap.security.core.usermanagement:department=Team

End of the example.

Same as the custom field namespace and name.

$usermapping$:<system_alias>:<attribute_name>

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.

Note Note

This attribute is only available for import. It cannot be exported.

End of the note.

Not applicable

$usermapping$:<system_alias>:mappedpassword

Password of mapped user in system <system_alias>.

<system_alias> is the system alias as defined in the portal system landscape editor.

Note Note

This attribute is only available for import. It cannot be exported.

End of the note.

Not applicable

$usermapping$:<system_alias>:user

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.

Note Note

This attribute is only available for import. It cannot be exported.

End of the note.

Not applicable

Note Note

For the telephone, fax, and mobile phone fields, the following rules apply:

  • Valid characters are: the numbers 0–9, parentheses ((…)), plus sign (+), minus sign (-), and space ( )

  • Opening and closing parentheses ((…)) must be in pairs

  • If included, the plus sign (+) must be the first or second character after a leading opening parenthesis (()

    Example Example

    • Valid: +1 650 123-4567

    • Valid: (+1) 650 123-4567

    • Invalid: 1+ 650 123-4567

    End of the example.
End of the note.

Example

The following is an example of users in the import format.

Syntax Syntax

  1. [User]
    UID=user0001
    Password=initial1
    Email_Address=user0001@example.com
    First_Name=Teresa
    Last_Name=Ruiz
    
    [User]
    UID=user0002
    Password=initial1
    Email_Address=user0002@example.com
    First_Name=Mikhail
    Last_Name=Komarov
    
End of the code.

The following example shows how you can change the user mapping data of an existing user, user0002. When you import the data, choose the option Overwrite Existing Data in the import tool.

The user user0002 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.

Syntax Syntax

  1. [User]
    uid=user0002
    Last_Name=Komarov
    $usermapping$:BCE:user=ext_user0002
    $usermapping$:BCE:mappedpassword=initial1
    
End of the code.