How to do user mapping in portal users and backend users

[Former Member]

Hi exports.

i have 100 users in portal but i have to mapped portal 100 users to R3 system . how?  please tell me

Br

Svreddy

[Former Member · Accepted solution]

First we have to create text file like notepad

Then upload text file into portal

Go to user admin then import

Standard Format 

Description

You can define user, group, and role data in standard format. Each data field appears on a separate line in name=value form. User records are separated by the [User] tag. Group records are separated by the [Group] tag. Role records are separated by the [Role] tag These tags must appear on the first line of each record.

You cannot mix user, group, and role records in the same import runs.

Optional attributes can either be omitted or assigned no value (for example, by specifying Country=). The equal sign (‘=’) must always appear after an attribute name, even if the attribute is not assigned any value.

If the program encounters an invalid line, the corresponding user or group will not be created, an error message will occur for this entry, and the batch process will continue. All valid user and group records will be processed and the corresponding objects created. Invalid records can be corrected and uploaded separately.

All attribute names (but not attribute values) are case insensitive.

For a description of the possible name-value pairs that can be included in user, group, and role records, see:

·        Users

·        Groups

·        Roles

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 company to which the user belongs. The company must exist.
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	Semi-colon-separated list of roles assigned to the user. If the role does not exist, a warning will be generated.
$usermapping$:<system _alias>:user	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 System Landscape. This attribute is only available for import. It cannot be exported.
$usermapping$:<system _alias>:mappedpassword	Optional	Password of mapped user in system <system_alias>. <system_alias> is the system alias as defined in the portal system landscape editor. See System Landscape. This attribute is only available for import. It cannot be exported.
$usermapping$:<system _alias>:<attribute_name>	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 System Landscape. 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= {BINARY}h&%AShja4zu8923h(=!&62h345kljhs 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 PSTor 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.

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

Example

The following is an example of users in standard format.

[User]
UID=user1
Password=user1
Email_Address=user1@mycompany.com
First_Name=John
Last_Name=Smith

[User]
UID=user2
Password=user2
Email_Address= user2@mycompany.com
First_Name=Jane
Last_Name=Miller

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]
uid=user2
$usermapping$:BCE:user=ext_user2
$usermapping$:BCE:mappedpassword=password

Groups 

Description

Attribute Names for GROUPS

Attribute	Required / Optional / Multiple	Description
[Group]	Required	Group delimiter.
gid	Required	Name of the group.
gdesc	Optional	Description of the group.
user	Optional	List of users that are assigned to this group, separated by semi-colons. These users must already exist. They are not automatically created during the import of the group.
group	Optional	List of groups that are assigned to this group, separated by semi-colons. These groups must already exist. They are not automatically created during the import of the group.

Example

The following is an example of a file containing a group in standard format. The users MarcPeters, JackSmith, and Alan_Fox must already exist, otherwise an error occurs. Similarly, the groups HappyBuyersOf2003and HappyBuyersOf2002 must already exist, or be created during the import before the groupHappyBuyers.

[Group]
gid=HappyBuyers
gdesc=This is a group of all satisfied buyers
user=MarcPeters;JackSmith;Alan_Fox
group=HappyBuyersOf2003;HappyBuyersOf2002

Roles 

Description

If no role exists with the role ID defined in the import data, a new UME role with this role ID is created. If a role already exists with the role ID defined in the import data and you choose Overwrite Existing Data, the role is updated regardless of whether it is a portal role or a UME role.

If you choose to update the user assignments of an existing role, the existing user assignments of that role are overwritten.

Attribute Names for ROLES

Attribute	Required / Optional / Multiple	Description
[Role]	Required	Role delimiter.
rid	Required	Name of the UME role.
rdesc	Optional	Description of the role.
action	Optional	List of actions assigned to the role, separated by semi-colons. These actions must already exist.
user	Optional	List of users that are assigned to this role, separated by semi-colons. These users must already exist. They are not automatically created during the import of the group.
group	Optional	List of groups that are assigned to this role, separated by semi-colons. These groups must already exist. They are not automatically created during the import.

Example

The following is an example of a file containing a role in standard format. The users MarcPeters, JackSmith, and Alan_Fox must already exist, otherwise an error occurs. Similarly, the groups HappyBuyersOf2003and HappyBuyersOf2002 must already exist.

[Role]
rid=Role1
rdesc=Role description
user=MarcPeters;JackSmith;Alan_Fox;
group=HappyBuyersOf2003;HappyBuyersOf2002