D.11 Design Comments and Notes

D.11.1 BAPI_USER_CHANGE (ADDRESS table)

  • The COMM-TYPE attribute in SAP has defined, acceptable values. Invalid input generates an exception and an error message stating, “The communication type <commType> is not defined.” Valid fields are the abbreviations for the supported communication types on the SAP Host.

  • The TITLE_ACA1 and TITLE_ACA2 attributes have predefined, acceptable values. Invalid input results in the value in SAP being set to a null string (“ ”).

  • The PREFIX1 and PREFIX2 attributes have predefined, acceptable values. Invalid input results in the value in SAP being set to a null string (“ ”).

  • The TEL1_NUMBR is linked to the primary, or Standard, Telephone number in the Telephone communication table.

D.11.2 BAPI_USER_CHANGE (ADDFAX table)

  • The Facsimile Telephone Number attribute in the Identity Vault is a structured attribute. An output transformation converts it to a single attribute format.

D.11.3 BAPI_USER_CHANGE (ADDTEL table)

  • Must have a CONSNUMBER (either the number of the one you want to change or a new, non-000 number.)

  • The STD_NO field must be set to X if you are synchronizing a single field or if the number is the only number present.

  • The primary data field is TELEPHONE.

D.11.4 BAPI_USER_CHANGE (ADDTLX table)

  • By default, this table is mapped to the Organizational Person; telexNumber attribute. This syntax is OCTET_STRING, which is encoded by Identity Manager into Base64 string encoding. A Java function is provided in the driver sapumshim.jar file that can decode this into the proper string format in the Output Transformation prior to submission to SAP. If you are using the driver on a remote system, place the driver shim in the same file system container with the Identity Manager library in the Input Transformation for the Publisher channel.

  • The primary data field is TELEX_NO.

  • Other rules apply as described for the ADDTEL table.

D.11.5 In BAPI_USER_CHANGE (ADDFAX table)

  • The primary data field is FAX.

  • Other rules apply as described for the ADDTEL table.

D.11.6 In BAPI_USER_CHANGE (GROUPS table)

  • The USERGROUP is the only field in this table.

D.11.7 BAPI_USER_CHANGE (ALIAS structure)

  • The USERALIAS is the only field in this table.

  • The SAP system guarantees that alias names are unique among all users. If an alias value is already assigned to another user, the modification fails.

D.11.8 BAPI_USER_CHANGE (REF_USER structure)

  • The REF_USER is the only field in this table.

  • The value specified as REF_USER must be an existing User object on the SAP client, and the Reference User’s type flag must be set to Reference (User Type L)

D.11.9 BAPI_USER_CHANGE (DEFAULTS structure)

  • The SPDB field can only be populated with a G (GO or Output Immediately), or an H (Hold output), or a null string “ ”, which sets the value to H. All other values generate an error message. This field is case sensitive.

  • The SPDA field can only be populated with a D (Delete after print), or a K (Keep), or a null string “ ”, which sets the value to K. All other values generate an error message. This field is case sensitive.

  • The KOSTL (Cost center) field is automatically truncated to 8 bytes by the SAP system.

  • The SPLG field does not appear to be utilized at all. Any value is accepted but does not relate to any attribute shown in the SAP GUI.

  • The START_MENU field can be set to any value up to 30 characters whether or not a valid menu exists for the value being set.

  • The SPLD (Output Controller) field accepts only a null string value (“ ”) or a valid output device that is available via the SAP GUI drop-down list for this field. Invalid selections return an error.

  • The LANGU field must be set to one of the one-letter language codes defined in Language Codes or to a null string (“ ”). The null string defaults to the language of the SAP system default language. This field is case sensitive. Non-defined fields result in an error.

D.11.10 BAPI_USER_CHANGE (LOGONDATA structure)

  • The USTYP field only accepts the valid User Types defined in User Types: LOGONDATA:USTYP or a null string (“ ”). Other input generates an exception and error message stating “Invalid user type<type>.”

  • The TZONE field accepts only valid, selectable fields from the SAP GUI drop-down list. Invalid input generates an exception and an error message stating “Invalid time zone.” The Time Zone setting is displayed under the Defaults tab in the SAP client Display User dialog box.

  • The CLASS field represents the User’s User Group for Authorization Check setting. Only fields that are selectable from the SAP GUI drop-down list are accepted. Invalid input generates an exception and error message stating “User group <class> does not exist.”

  • The GLTGV (Validity Begin Date) and GLTGB (Validity End Date) values exist as a set of data.

  • The Begin Date must always be less than the End date.

  • Invalid date input generates an exception and an error message stating “Invalid time interval: Begin date after end date.”

D.11.11 BAPI_USER_CHANGE (GROUPS table)

  • Only valid groups that exist in the SAP User Groups table can be added to a user. Invalid input generates an exception and an error message stating “User group<name> does not exist.”

D.11.12 BAPI_USER_CHANGE (ADDCOMREM table)

  • The LANGU and LANGU_ISO fields are set with the driver’s language parameter value.