Skip to main content

Troubleshooting

Here you can find additional information allowing you to solve possible troubles with SAP Connectivity in Omada Identity.

tip

Omada recommends scheduling the standard SAP report PFCG_TIME_DEPENDENCY on a daily basis to cleanup and remove incomplete role and profile assignments, refer to SAP documentation for further details.

SOAMANAGER Cannot Start or Timeouts​

If SOAMANAGER cannot start, or timeouts occur when importing data, try adjusting the following parameters:

  • Icm/keep_alive_timeout (default = 60)
  • Icm/server_port_0 = PROT=HTTP,PORT=8000,TIMEOUT=?,PROCTIMEOUT=
  • Rdisp/max_wprun_time (default = 600)
  • Rdisp/PG_MAXFS (default = 32670)

Import errors about resource assignments pointing to a non-existing resource​

If you experience errors during import about resource assignments referring to non-existing resources, it is typically SAP users who had a reference to a SAP Profile which has been deleted. The import log will display the affected users and you can use transaction SU01 in the SAP system to update the user records by removing the reference to the non-existing profile. Afterward, the import can be re-started.

Setting GROUPS attribute mapping​

You can set properly the mapping for the GROUPS attribute with the following procedure.

Before you start

Add the GROUPS property to the Data Model.

<objectProperty>GROUPS</objectProperty>
<property name="GROUPS" dataType="stringType" multiValued="true" />

Procedure

  1. Go to Task mapping dialog box and open the Mappings tab.

  2. If there is no GROUPS entry in the Destination column click on the Add mapping button and choose the GROUPS value from the list.

  3. Set the appropriate value in the Operator field.

  4. Configure Source field following the USERGROUPS=ESSUSER pattern.

  5. Click on the Edit button and in the Advanced settings tab set the Action value to Add.