Share this page

# Step 5: Start the import

To import data from the interface tables, use the Import Users report.

In this topic:

## Run the Import Users report

The Import Users report performs the following tasks:

- Queries the KNTA_USERS_INT interface table for active records matching the given selection criteria.

- Queries the KNTA_USER_SECURITY_INT table.

- Validates the user information.

- Imports validated users into PPM tables. Partial imports are not allowed. Users with one or more failed fields are not imported.

- Reports on the results of the execution, listing the specified users that failed validation and the specific validation errors they encountered.

To run the Import Users report:

1. From the main menu, select Reports > Create Report.

2. On the Submit New Report page, select Administrative from the Report Category.

   The page is updated showing the list of administrative reports.

3. Select Import Users to open the Submit Report: Import Users window.

4. Complete the fields, as described in the following table.

   Required fields are marked with an asterisk. The required fields vary depending on your selections.

   The Import Users report has several parameters for controlling the behavior of the program execution. Pay special attention to the following:

   - Product Licenses

   - LDAP Import - Set this field to No

   - Search Filter

   - User Authentication Mode

   - Link User Security Groups from LDAP Groups

   - Import Modified

   Note: Although security groups can be different, all users imported in a single execution of the Import Users report must have the same user privileges. To set different attributes (security groups or product permissions) for imported users, it is necessary to run the report multiple times.

   Caution: USER_DATA for users is not validated as part of an import.

   Field | Description
   --- | ---
   Group Id | Specifies the group ID for which the interface program should be run. The interface program will only look for records with this value in the GROUP_ID column. This is useful when importing a batch of packages.
   Source Code | Indicates whether or not to set the SOURCE_CODE column of the final requests created with a free-form text code. This is used as an indicator of how the request was created for auditing or testing purposes. For an LDAP import, set to LDAP_IMPORT.
   Run Import? | If set to Yes, the program processes the records in the interface table and tries to import them. If set to No, the program reports on the records in the interface table. This option is useful when auditing prior executions of the interface.
   Show Successful Transactions? | Select Yes if you want to display the successfully imported users.
   Show Failed Transactions? | Select Yes if you want to display users who were not successfully imported.
   Default Password | Specifies a default password.
   Security Groups | Specifies security groups that can access this group of users.
   User Security Group Action | Selects the action to perform: Add/Drop Security Groups Add Security Groups Drop Security Groups Overwrite Security Groups
   Add Missing Security Groups? | Select Yes if you want to add missing security groups.
   Disable Users Not Imported | Select Yes if you want to disable users that already exist before the import process. For example, if user A and B already exist, if you specify Yes for this option, the users are disabled after you run the report. Protected users are not disabled even if this option is set to Yes. For details about protected users, see Designate protected users.
   Keep existing values for empty columns? | Select Yes if you want to keep existing values stored for empty columns.
   Product Licenses | Selects the product license for the imported users.
   Region for Resource (Override default region) | Selects the region for the imported users. If this field is not specified, and the field Keep existing values for empty columns? is set to Yes, the existing region and corresponding calendar are kept for each user. If this field is not specified, and the field Keep existing values for empty columns? is set to No, the system default region and corresponding calendar is used for each user.
   LDAP Import | Option to perform LDAP import. Set this option to Yes if the authentication mode in the server.conf file contains LDAP or an Exchange server (NTLM).
   LDAP Import PPM User Only | Select Yes to perform LDAP import of only PPM users.
   Search Filter | Specifies the search filter using syntax of the conditions on PPM commands. See Examples of search filter values.
   Search DN | Specifies the search filter using syntax of the conditions on PPM commands.
   User Authentication Mode | Selects a user authentication mode: LDAP or NTLM only.
   Link User Security Groups from LDAP Groups | Select Yes to link security groups from LDAP Groups. (LDAP or NTLM only)
   Import Modified | Option to modify the import. (LDAP or NTLM only)

5. (Optional) To test the process, set the Run Import field to No.

6. Click Submit.

For more information on the server.conf file, see the Installation and Administration Guide.

## Examples of search filter values

This section provides some examples of search filter values:

The following filter returns objects that match "Babs Jensen".

(cn=Babs Jensen)

The following filter returns objects that do not match "Tim Howes".

(!(cn=Tim Howes))

The following filter returns all people who's names match Jensen or whose name contains the string "Babs J".

(&(objectClass=Person)(|(sn=Jensen)(cn=Babs J*)))

The following filter returns objects that would help you find variations on the spelling of University of Michigan.

(o=univ*of*mich*)

This filter returns all Development objects that match: test1, test2, or test3.

(&(ou=Development)(|(uid=test1)(uid=test2)(uid=test3)))

https://admhelp.microfocus.com PPM 8942
Tips to improve your search results... OpenText™ Project and Portfolio Management Help Center PPM Help 26.2-26.3 All View Local Help Center View Online Help Center Version: