Chat now with support
Chat with Support

Identity Manager 8.0 - Administration Guide for Connecting to SAP R/3

Managing SAP R/3 Environments Setting up SAP R/3 Synchronization Base Data for Managing SAP R/3 SAP Systems SAP Clients SAP User Accounts SAP Groups, SAP Roles and SAP Profiles SAP Products Providing System Measurement Data Reports about SAP Systems Appendix: Configuration Parameters for Managing an SAP R/3 Environment Appendix: Default Project Templates for Synchronizing an SAP R/3 Environment Appendix: Referenced SAP R/3 Tables and BAPI Calls Appendix: Example of a Schema Extension File

Users and Permissions for Synchronizing with SAP R/3

Users and Permissions for Synchronizing with SAP R/3

The following users are involved in synchronizing One Identity Manager with SAP R/3.

Table 2: Users for Synchronization
User Authorizations

One Identity Manager Service user account

The user account for the One Identity Manager Service requires access rights to carry out operations at file level (issuing user rights, adding directories and files to be edited).

The user account must belong to the group "Domain Users".

The user account must have the extended access right "Log on as a service".

The user account requires access rights to the internal web service.

NOTE: If the One Identity Manager Service runs under the network service (NT Authority\NetworkService), you can issue access rights for the internal web service with the following command line call:

netsh http add urlacl url=http://<IP address>:<port number>/ user="NT AUTHORITY\NETWORKSERVICE"

The user account needs full access to the One Identity Manager Service installation directory in order to automatically update the One Identity Manager.

In the default installation the One Identity Manager is installed under:

  • %ProgramFiles(x86)%\One Identity (on 32-bit operating systems)
  • %ProgramFiles%\One Identity (on 64-bit operating systems)
User for accessing the target system

You must provide a user account with the following authorizations for full synchronization of SAP R/3 objects with the supplied One Identity Manager default configuration.

Required authorization objects and their meanings:

  • S_TCODE with a minimum of transaction codes SU01, SU53, PFCG
  • S_ADDRESS1 with activities 01, 02, 03, 06 and valid address groups (min."BC01")
  • S_USER_AGR (role maintenance) with activities 02, 03, 22, 78 possibly with restrictions in name ranges (for example "Z*")
  • S_USER_GRP (group maintenance) with activities 02, 03, 22
  • S_USER_AUT (authorizations) with activities 03, 08
  • S_USER_PRO (profile) with activities 01, 02, 03, 22
  • S_USER_SAS (system specific assignments) with activities 01, 06, 22
  • S_RFC (authorization check by RFC access) with activity 16 at least for function groups ZVI, /VIAENET/ZVI0, /VIAENET/ZVI_L, /VIAENET/Z_HR, SU_USER, SYST, SDTX, RFC1, RFC_METADATA, SDIFRUNTIME, SYSU
  • S_TABU_DIS (use of standard tools like SM30 for maintaining tables) with activity 03

Apart from the permissions listed, the user account has to get all objects from the authorization classes "ZVIH_AUT", "ZVIA_AUT", and "ZVIL_AUT" which are installed by the transport package for synchronization.

The following authorization objects are required in addition for the child system in order to synchronize central user administration:

  • S_RFC with the function group SUU6
  • S_TCODE with the transaction code SU56
User for accessing the One Identity Manager database

The default system user "SynchronizationClosed" is available to run synchronization over an application server.

TIP: The transport file provided by default, "SAPRole.zip", includes a transport package with a role that the base authorization object already possesses. This role can be assigned to the user account. You will find the transport files on the One Identity Manager installation medium in the directory ..\Modules\SAP\dvd\AddOn\Bapi.

The named authorizations are required so that the SAP R/3 connector has read and write access to the SAP R/3 system. If only read access should be permitted, setting up a profile which has executable permission for transactions SU01 and PFCG but prevents writing at activity or field level is recommended.

The user account requires the user type "dialog", "communication" or "system" to load more information.

NOTE: In SAP R/3 versions up to and including SAP Web Application Server 6.40, the password and user input are not case sensitive. this no longer applies to the password for SAP NetWeaver Application Server 7.0 and later. The password is case sensitive.

All SAP’s own tools that are supplied up to SAP Web Application Server 6.40, apart from the SAP GUI (RFC-SDK, SAP .Net Connector), therefore change the password to capital letters before passing them to SAP R/3. You must set the password in capital letters for the user account used by the SAP .Net Connector to authenticate itself on the SAP R/3 system. If this is done, all the usual tools can be accessed on SAP NetWeaver Application Server 7.0 by RFC.

Related Topics

Installing the One Identity Manager Business Application Programing Interface

Installing the One Identity Manager Business Application Programing Interface

In order to access SAP R/3 data and business processes with the One Identity Manager, you must load the Business Application Programming Interface (BAPI) into the SAP R/3 system. You will find the required transport files on the One Identity Manager installation medium in the directory ..\Modules\SAP\dvd\AddOn\Bapi.

Install the BAPI transport in the following order:

Table 3: BAPI transport
Transport Explanation
1 SAPRepository.zip Creates the /VIAENET/ in the SAP system repository.
2 SAPTable.zip Defines the table structure for /VIAENET/USERS in the SAP system dictionary.
3 SAPTRANSPORT_70.ZIP Contains the functions defined in the /VIAENET/ environment.

Archive directory UNICODE: Transports for systems supporting unicode

Archive directory NON_UNICODE: Transports for systems not supporting unicode

NOTE: If your SAP system supports unicode, select the unicode transport file from the archive file. The archive files contain transport packages for systems not supporting unicode in the respective directories.

Set the following import options for the transport:

  • Overwrite Originals
  • Overwrite Objects in Unconfirmed Repairs
  • Ignore Non-Matching Component Versions

The SAP R/3 connector uses other SAP R/3 BAPIs in parallel. For more information, see Appendix: Referenced SAP R/3 Tables and BAPI Calls.

Setting Up the Synchronization Server

Setting Up the Synchronization Server

To setup synchronization with an SAP R/3 environment a server has to be available that has the following software installed on it:

  • Windows operating system

    Following versions are supported:

    • Windows Server 2008 (non-Itanium based 64-bit) Service Pack 2 or later
    • Windows Server 2008 R2 (non-Itanium based 64-bit) Service Pack 1 or later
    • Windows Server 2012
    • Windows Server 2012 R2
    • Windows Server 2016
  • Microsoft .NET Framework Version 4.5.2 or later

    NOTE: Microsoft .NET Framework version 4.6 is not supported.

    NOTE: Take the target system manufacturer's recommendations into account.
  • Windows Installer
  • SAP .Net Connector for .NET 4.0 on x64, with at least version 3.0.15.0
  • One Identity Manager Service, Synchronization EditorClosed, SAP R/3 connector
    • Install One Identity Manager components with the installation wizard.
      1. Select the option Select installation modules with existing database.
      2. Select the machine role Server | Job serverClosed | SAP R/3.

Further requirements

  • Following files must either be in the Global Assemblies Cache (GAC) or in the One Identity Manager installation directory.
    • libicudecnumber.dll
    • rscp4n.dll
    • sapnco.dll
    • sapnco_utils.dll
  • Following files must either be in the Global Assemblies Cache (GAC) or in C:\Windows\System32 or in the One Identity Manager's installation directory.
    • msvcp100.dll
    • msvcr100.dll

All One Identity Manager Service actions are executed against the target system environment on the synchronization server. Entries which are necessary for synchronization and administration with the One Identity Manager database are processed by the synchronization server. The synchronization server must be declared as a Job server in One Identity Manager.

NOTE: If several target system environments of the same type are synchronized under the same synchronization server, it is useful to set up a job server for each target system on performance grounds. This avoids unnecessary swapping of connection to target systems because a job server only has to process tasks of the same type (re-use of existing connections).

Use the Server Installer to install the One Identity Manager Service. This program executes the following steps.

  • Setting up a Job server.
  • Specifying machine roles and server function for the Job server.
  • Remote installation of One Identity Manager Service components corresponding to the machine roles.
  • Configures the One Identity Manager Service.
  • Starts the One Identity Manager Service.

NOTE: The program executes remote installation of the One Identity Manager Service. Local installation of the service is not possible with this program. Remote installation is only supported within a domain or a trusted domain.

To install and configure the One Identity Manager Service remotely on a server

  1. Start the program Server Installer on your administrative workstation.
  2. Enter valid data for connecting to One Identity Manager on the Database connection page and click Next.
  3. Specify on which server you want to install the One Identity Manager Service on the Server properties page.
    1. Select a job server in the Server menu.

      - OR -

      Click Add to add a new job server.

    2. Enter the following data for the Job server.
      Table 4: Job Servers Properties
      Property Description
      Server Name of the Job servers.
      Queue

      Name of queue to handle the process steps. Each One Identity Manager Service within the network must have a unique queue identifier. The process steps are requested by the job queue using exactly this queue name. The queue identifier is entered in the One Identity Manager Service configuration file.

      Full server name

      Full name of the server in DNS syntax.

      Example:

      <name of server>.<fully qualified domain name>

      NOTE: Use the Advanced option to edit other Job server properties. You can use the Designer to change properties at a later date.
  4. Specify which job server roles to include in One Identity Manager on the Machine role page. Installation packages to be installed on the Job server are found depending on the selected machine role.

    Select at least the following roles:

    • SAP R/3
  5. Specify the server's functions in One Identity Manager on the Server functions page. One Identity Manager processes are handled depending on the server function.

    The server's functions depend on which machine roles you have selected. You can limit the server's functionality further here.

    Select the following server functions:

    • SAP R/3 connector
      Windows PowerShell
  6. Check the One Identity Manager Service configuration on the Service settings page.

    NOTE: The initial service configuration is already predefined. If further changes need to be made to the configuration, you can do this later with the Designer. For more detailed information about configuring the service, see One Identity Manager Configuration Guide.
  7. To configure remote installations, click Next.
  8. Confirm the security prompt with Yes.
  9. Select the directory with the install files on the Select installation source page.
  10. Select the file with the private key on the page Select private key file.

    NOTE: This page is only displayed when the database is encrypted.
  11. Enter the service's installation data on the Service access page.
    Table 5: Installation Data
    Data Description
    Computer Server on which to install and start the service from.

    To select a server

    • Enter the server name.

      - OR -

    • Select a entry from the list.
    Service account One Identity Manager Service user account data.

    To enter a user account for the One Identity Manager Service

    • Set the option Local system account.

      This starts the One Identity Manager Service under the account "NT AUTHORITY\SYSTEM".

      - OR -

    • Enter user account, password and password confirmation.
    Installation account Data for the administrative user account to install the service.

    To enter an administrative user account for installation

      Enable Advanced
    • .
    • Enable the option Current user.

      This uses the user account of the current user.

      - OR -

    • Enter user account, password and password confirmation.
  12. Click Next to start installing the service.

    Installation of the service occurs automatically and may take some time.

  13. Click Finish on the last page of the Server Installer.

    NOTE: The is entered with the name "One Identity Manager Service" in the server's service administration.

Creating a Synchronization Project for initial Synchronization of an SAP Client

Creating a Synchronization Project for initial Synchronization of an SAP Client

Use Synchronization EditorClosed to configure synchronization between the One Identity Manager database and SAP R/3. The following describes the steps for initial configuration of a synchronization project.

After the initial configuration, you can customize and configure workflows within the synchronization project. Use the workflow wizard in the SynchronizationClosed Editor for this. The Synchronization Editor also provides different configuration options for a synchronization project.

Have the following information available for setting up a synchronization project.

Table 6: Information Required for Setting up a Synchronization Project
Data Explanation
SAP R/3 application server Name of the application server used to RFC communication.
System number Number of the SAP R/3 system for connecting the SAP connector.
System ID System ID of this SAP system.
Client Number of the client to be synchronized. You need the central system's client number to synchronize central user administration (CUAClosed).
Login name and password

The name and password of the user account used by the SAP R/3 connector to log in to the SAP R/3 system. Make a user account available with sufficient permissions.

If the network connection must be secure, you require the user account's SNC name.

Login language Login language for logging the SAP R/3 connection into the SAP R/3 system.

Synchronization serverClosed

All One Identity Manager Service actions are executed against the target system environment on the synchronization server. Entries which are necessary for synchronization and administration with the One Identity Manager database are processed by the synchronization server.

Installed components:

  • SAP .Net Connector for .NET 4.0 on x64, with at least version 3.0.15.0
  • One Identity Manager Service (started)
  • Synchronization Editor
  • SAP R/3 connector

The synchronization server must be declared as a Job server in One Identity Manager. Use the following properties when you set up the Job server.

Table 7: Additional Properties for the Job Server
Property Value
Server Function SAP R/3 connector
Machine role Server/Job server/SAP R/3

For more information, see Setting Up the Synchronization Server.

One Identity Manager Database ConnectionClosed Data

SQL Server:

  • Database server
  • Database
  • Database user and password
  • Specifies whether Windows authentication is used.

    This type of authentication is not recommended. If you decide to use it anyway, ensure that your environment supports Windows authentication.

Oracle:

  • Species whether access is direct or through the Oracle client

    Which connection data is required, depends on how this option is set.

  • Database server
  • Oracle instance port
  • Service name
  • Oracle database user and password
  • Data source (TNS alias name from TNSNames.ora)
Remote connection serverClosed

To configure synchronization with a target system, One Identity Manager must load the data from the target system. One Identity Manager communicates directly with target system to do this. If you do not have direct access on the workstation on which the Synchronization Editor is installed, because of the firewall configuration, for example, you can set up a remote connection.

The remote connection server and the workstation must be in the same Active Directory domain.

Remote connection server configuration:

  • One Identity Manager Service is started
  • RemoteConnectPlugin is installed
  • SAP R/3 connector is installed

The remote connection server must be declared as a Job server in One Identity Manager. The Job server name is required.

TIP: The remote connection server requires the same configuration (with respect to the installed software) as the synchronization server. Use the synchronization as remote connection server at the same time, by simply installing the RemoteConnectPlugin as well.

For more detailed information about setting up a remote connection, see the One Identity Manager Target System Synchronization Reference Guide.

Additional information about setting up the synchronization project may be required depending on the configuration of the SAP R/3 system.

Table 8: Information for Setting up a Synchronization Project
Data Explanation
SAP R/3 router Name of the router, which provides a network port for the SAP R/3 connector for communicating with the application server.
SAP R/3 message server Name of the message server with which the SAP R/3 connector communicates when logging in.
Login group Name of the login group used by the SAP R/3 connector for logging in when communication is working over a message server within the SAP R/3 environment.
SNC host name SNC name of the host for the secure network connection.
SNC Name SCN name of the user account with which the SAP R/3 connector logs into the SAP R/3 system if a secure network connection is required.
SNC client API API containing SNC encryption.

NOTE: The following sequence describes how you configure a synchronization project if the Synchronization Editor is both:
  • In default mode
  • Started from the launchpad

Additional settings can be made if the project wizard is run in expert mode or is started directly from the Synchronization Editor. Follow the project wizard instructions through these steps.

To set up initial synchronization project for an SAP client.

  1. Start the Launchpad and log on to the One Identity Manager database.

    NOTE: If synchronization is executed by an application server, connect the database through the application server.
  2. Select the entry SAP R/3 target system type. Click Run.

    This starts the Synchronization Editor's project wizard.

  1. Specify how the One Identity Manager can access the target system on the System access page.
    • If you have access from the workstation from which you started the Synchronization Editor, do not set anything.
    • If you do not have access from the workstation from which you started the Synchronization Editor, you can set up a remote connection.

      In this case, set the option Connect using remote connection server and select, under Job server, the server you want to use for the connection.

  1. Select a connection type on the Connection type tab.
    Table 9: Connection Types
    Property Description
    SAP R/3 Application server or SAP R/3 router Specifies whether the connection is established through an application server or a router.
    SAP R/3 message server Specifies whether the connection is established through a message server.
    • Enter the connection data for connection type "SAP R/3 application server or SAP R/3 router" on the Connection data page.
      Table 10: System Connection
      Property Description
      SAP R/3 host or router Name of the application server or router used by the SAP R/3 connector for communicating.
      System number Number of the system.SAP
      System ID System ID of the system.SAP This is used as the display name in One Identity Manager tools.
    • Enter the connection data for the connection type "SAP R/3 message server" on the Message server page.
      Table 11: System Connection
      Property Description
      SAP R/3 message server Name of the message server used to establish the connection.
      Logon group Name of the logon group used by the SAP R/3 connector.
      SAP R/3 router Name of the router if the SAP R/3 connector communicates through a router.
      System number Number of the SAP system.
      System ID System ID of the system.SAP This is used as the display name in One Identity Manager tools.
  2. Enter the network settings on Secure network communication.
    Table 12: Network Settings
    Property Description
    Program ID Identifier for the connection the SAP R/3 connector establishes with the SAP R/3 system.
    SNC login Specifies whether the SNC user account name is used when the SAP R/3 connector logs in on the SAP R/3 system.
  3. If you have enabled the option SNC login on the Secure connection page, the page SNC connection configuration is opened. Enter the data required for logging into the target system using a secure network connection.
    Table 13: SNC Configuration
    Property Description
    ClientNumber of the client to be synchronized. Enter the central system's client number if central user administration is to be synchronized.
    SNC host name Name of the SNC host for the secure network connection.
    SNC name The name and password of the user account used by the SAP R/3 connector to log in to the SAP R/3 system.
    SNC client API API containing the SCN encryption.
    Authentication Select a security level for logging into the SAP R/3 system.
    Integrity protection
    Encryption
    Highest avail. level
    Login language Login language for logging the SAP R/3 connection into the SAP R/3 system. The language selected determines the language for captions for all the client's oSAPbjects. If you select "EN", all the text from SAP groups, roles, profiles and start menus is synchronized in English.
  4. Enter data for logging into the target system on the Login data page.
    Table 14: Login Data
    Property Description
    Client Number of the client to be synchronized. Enter the central system's client number if central user administration is to be synchronized.
    Login name Name of the user account used by the SAP R/3 connector to log into the SAP R/3 system. If you have enabled the option SNC login on the Secure connection page, enter the SNC name of this user account.
    Login password User account's password the SAP R/3 connector uses to log into the SAP R/3 system.
    Login language Login language for logging the SAP R/3 connection into the SAP R/3 system. The language selected determines the language for captions for all the client's SAP objects. If you select "EN", all the text from SAP groups, roles, profiles and start menus is synchronized in English.
  5. Supply additional information about synchronizing objects and properties on the Additional settings. You can check the connection settings.
    • Specify in Central user administration (CUA) whether the connection to a central user administration's central system should be established. In this case, set CUA central system.
    • You can test the connection in Verify connection settings. Click on Verify project.

      The system tries to connect to the server. If the option CUA central system is set, the given client is tested to see if it is the central system of a CUA.

      NOTE: Checks whether the supplied BAPI is installed.
    • Click Finish, to end the system connection wizard and return to the project wizard.
  6. Click Next on the SAP HCM settings page.

    This page is only needed for synchronizing additional personnel planning data in the SAP R/3 Structural Profiles Add-on Module.

  7. Click Next on the SAP connector schema page.

    TIP: You can enter a file with additional schema types on this page. The connector schema is extended by these custom schema types. You can also enter this data after saving the synchronization project. For more information, see Adding Other Schema Types.
  1. Verify the One Identity Manager database connection data on the One Identity Manager connection page. The data is loaded from the connected database. Reenter the password.

    NOTE: Reenter all the connection data if you are not working with an encrypted One Identity Manager database and no synchronization project has been saved yet in the database. This page is not shown if a synchronization project already exists.
  2. The wizard loads the target system schema. This may take a few minutes depending on the type of target system access and the size of the target system.
  1. Select a project template on the Select project template page to use for setting up the synchronization configuration.
    Table 15: Default Project Templates
    Project template Description
    SAP R/3 (CUA subsystem) Use this project template for initially setting up the synchronization project for a CUA child system, which belongs to another SAP system than the central system.
    SAP R/3 synchronization (base administration) Use this project template for initially setting up the synchronization project for single clients of a CUA's central system.

    NOTE: A default project template ensures that all required information is added in the One Identity Manager. This includes mappings, workflows and the synchronization base object. If you do not use a default project template you must declare the synchronization base object in One Identity Manager yourself.Use a default project template for initially setting up the synchronization project. For custom implementations, you can extend the synchronization project with the .Synchronization Editor
  1. Specify how system access should work on the page Restrict target system access. You have the following options:
    Table 16: Specifying Target System Access
    Option Meaning

    Read-only access to target system.

    Specifies whether a synchronization workflow should be set up to initially load the target system into the One Identity Manager database.

    The synchronization workflow has the following characteristics:

    • Synchronization is in the direction of "One Identity Manager".
    • Processing methods in the synchronization steps are only defined in synchronization direction "One Identity Manager".

    Changes are also made to the target system.

    Specifies whether a provisioning workflow should be set up in addition to the synchronization workflow to initially load the target system.

    The provisioning workflow displays the following characteristics:

    • Synchronization in the direction of the "target system"
    • Processing methods are only defined in the synchronization steps in synchronization direction "target system".
    • Synchronization steps are only created for such schema classes whose schema types have write access.

    This page is only shown if the project template "SAP® R/3® synchronization (basic administration)" was selected. If the project template " "SAP® R/3® (child CUA system)" was selected, the option Read-only access to target system is set.

  2. Select the synchronization server to execute synchronization on the Synchronization server page.

    If the synchronization server is not declare as a job server in the One Identity Manager database yet, you can add a new job server.

    • Click to add a new job server.
    • Enter a name for the job server and the full server name conforming to DNS syntax.
    • Click OK.

      The synchronization server is declared as job server for the target system in the One Identity Manager database.

      NOTE: Ensure that this server is set up as the synchronization server after saving the synchronization project.
  1. Click Finish to complete the project wizard.

    This creates and allocates a default schedule for regular synchronization. Enable the schedule for regular synchronization.

    The synchronization project is created, saved and enabled immediately.

    NOTE: If the synchronization project is not going to be executed immediately, disable the option Activate and save the new synchronization project automatically.

    In this case, save the synchronization project manually before closing the Synchronization Editor.

    Disable this option, if you want to add your own schema types in this synchronization project.

    NOTE: The target system connection data is saved in a variable set, which you can change in the Synchronization Editor under Configuration | Variables if necessary.

To configure the content of the synchronization log

  1. To configure the synchronization log for target system connection, select the category Configuration | Target system.
  2. To configure the synchronization log for the database connection, select the category Configuration | One Identity Manager connection.
  3. Select General view and click Configure....
  4. Select the Synchronization log view and set Create synchronization log.
  5. Enable the data to be logged.

    NOTE: Certain content create a lot of log data.

    The synchronization log should only contain the data necessary for error analysis and other evaluations.

  6. Click OK.

To synchronize on a regular basis

  1. Select the category Configuration | Start up configurations.
  2. Select a start up configuration in the document view and click Edit schedule....
  3. Edit the schedule properties.
  4. To enable the schedule, click Activate.
  5. Click OK.

To start initial synchronization manually

  1. Select the category Configuration | Start up configurations.
  2. Select a start up configuration in the document view and click Execute.
  3. Confirm the security prompt with Yes.

NOTE: Following synchronization, employees are automatically created for user accounts in the default installation. If there are no account definitions for the client at the time of synchronization, user accounts are linked to employees. However, account definitions are not assigned. The user accounts are, therefore, in a "Linked" state.

To select user accounts through account definitions

  1. Create an account definition.
  2. Assign an account definition to the client.
  3. Assign the account definition and manage level to the user accounts in a "linked" state.
    1. Select the category SAP R/3 | User accounts | Linked but not configured | <client>.
    2. Select the task Assign account definition to linked accounts.
Detailed information about this topic
  • One Identity Manager Target System Synchronization Reference Guide
Related Topics
Related Documents