Data import
Connection details
| Setting | Description |
|---|---|
| Host Name Address | Type the Fully Qualified Domain Name of a valid host name. |
| Connection type | Select if the connection is to be done via HTTP or secured HTTP. |
| Client | Specify the client number from SAP to which to connect. |
| Port | Type the port number of the application server. |
| Timeout in seconds | Specify the timeout for the connection - in seconds. |
| User | Type the username of the administrative user used to access the service. |
| Password | Type the password for the administrative user. Each time you make a change to any of the settings in the Connection details dialog box, you must enter your password again. |
| Skip certificate check | Select this checkbox to ignore any certificate check when connecting using SSL. |
| Security protocol | Select the protocol used for HTTPS handshake. |
| Test connection | Enable this setting to test the specified connection details. For the Test connection to work correctly, the Company Code web service must be enabled in SAP. |
System definition: Advanced
| Setting | Description |
|---|---|
| Language | When you connect to SAP, you define a language so that the text in the user interface is provided in the required language. By default, English (E) is selected as the language of the SAP system. Optionally, you can remove this value and type the proper country code for your system, for example D (Germany). |
| Use delta | When having this checkbox selected the imports will be set to Delta mode. For Delta mode to work properly, enable the Paging option. For more information go to the Paging section of the document. Additionally, when having Delta mode enabled, be sure to periodically run a Full import. |
System definition: Queries and mappings
If you are planning an upgrade form version 14.0.8 or lower, follow these steps after the upgrade is complete, but before the first import:
- Modify the filter attribute for the Jobs query with the one below:
"#MaxRow(id, validto)#!(string.IsNullOrEmpty(validto) || validto ==
"00000000" || DateTime.ParseExact
(validto,"yyyyMMdd",null) <= DateTime.UtcNow)"
-
Enable the Distinct option for all queries.
-
Do not enable paging for Cost Centers and Positions queries.
Queries and mappings provided out of the box
| Object type | Biding/Service | Interface | Description |
|---|---|---|---|
| Identity | employee_get | omada/empl_get_resp | Employees |
| Identity owner | employee_get | omada/empl_get_resp | Managers |
| Context | orgunit_get | omada/hr_orgunit_resp | OrgUnit |
| Context owner | orgunit_get | omada/hr_orgunit_resp | Managers |
| Context | personnelarea_get | omada/hr_persarea_resp | Personnel Area |
| Context | personnelsubarea_get | omada/hr_perssubarea_resp | Personnel Subarea |
| Context | companycode_get | omada/fico_comp_code_resp | Company Codes |
| Context | costcenter_get | omada/fico_cost_center_resp | Cost Centers |
| Context | building_get | omada/hr_build_resp | Buildings |
| Context | position_get | omada/hr_orgpos_resp | Positions |
| Context | jobs_get | omada/hr_jobs_resp | Jobs |
| Context assignment | employee_get | omada/empl_get_resp | OrgUnit Assignments for Identities |
| Context assignment | employee_get | omada/empl_get_resp | Building Assignments for Identities |
| Context assignment | employee_get | omada/empl_get_resp | Personnel Area Assignments for Identities |
| Context assignment | employee_get | omada/empl_get_resp | Personnel SubArea Assignments for Identities |
| Context assignment | employee_get | omada/empl_get_resp | Company Code Assignments for Identities |
| Context assignment | employee_get | omada/empl_get_resp | Cost Center Assignments for Identities |
| Context assignment | employee_get | omada/empl_get_resp | Job Assignments for Identities |
| Context assignment | position_get | omada/hr_orgpos_resp | Position Assignments for Identities |
Edit query mappings
To edit a query mapping, click the Edit button in the Queries and mappings window.This button opens the Edit query mapping dialog box, where you can define settings for that particular mapping. The Edit query mapping dialog box consists of three tabs: Web Method, Paging, and Mappings.
Web Method
In this tab you can define the web method for the query mapping.The tab consists of the following fields:
- Binding - Enter the binding name you had used when the web services were generated in SAP via transaction SOAMANAGER.It is recommended to use the default naming convention, so you are only required to change the value if you have used a custom naming of the binding in SAP. Also refer to the 1.0.1 Generate Web Services using SOAMANAGER section.
- Service - Enter the service name you had used when the web services were generated in SAP via transaction SOAMANAGER.It is recommended to use the default naming convention, so you are only required to change the value if you have used a custom naming of the service in SAP. Also refer to the 1.0.1 Generate Web Services using SOAMANAGER section.
- Distinct - Set this option to Yes to allow the query to yield more rows with the same values.
- Filter - Provide a logical expression for each row imported, for example, Name eq 'John.' If it is evaluated to false, the row will be skipped by the collector.
- Enabled - If the query is not Enabled the collector will not perform it.
- Description - Provide a meaningful description of the query mapping.
Paging
This tab allows you to enable and define the paging method. The tab consists of the following fields:
- Use paging - Set this option to No to disable Paging for the collector.
- Request Page Number - Specify the page number from which the collector will start collecting data.
- Request Rows Per Page - Specify the number of rows that will be collected per each page.
Mappings
This tab provides standard mapping table to define Source and Destination of the mappings between the SAP system and Omada Identity.