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

Configuring a Schema Extension File

Define all the schema types you want to use to extend the connector schema in the schema extension file. The schema extension file is an XML file with a structure identical to the connector schema. It describes the definitions for table queries and BAPI calls for the new schema types. If a new schema type has the same name as an already existing schema type, the extension is ignored.

The file is divided into three main sections:

• Table section
• Functions section
• SchemaData model of a connected system. The schema describes all the master data from the connected system. see target system schema; see One Identity Manager schema; see connector schema; see extended schema types section

Basically, tables and functions required to access data for defined schema types, must be declared first. Then, after this, you can define new schema types in the schema types section. You can use functions and tables in different schema type definitions in this case. A schema type definition must contain at least one call for an object list.

Schema Extension File Structure

Predefined Variables

You can use variables in the table and function sections. These can be all the system variables known to the SAP module RFC_READ_TABLE.

You can also use variables known to the SAP R/3 connector, for example, from the process parameter definition.

Detailed information about this topic

• Defining Tables
• Defining Functions
• Defining Schema Types
• Appendix: Example of a Schema Extension File

Defining Tables

In the section for tables (Tables), you can select tables and columns required for accessing the data for the schema types, which will be defined. The SAP R/3 connector requires a definition for each table to load the slim object list. To do this, you define exactly those columns the SAP R/3 connector required when it loaded the synchronization objects. All columns in the table are loaded when single objects are accessed.

Advice

• Several table definitions with different symbolic names can be defined that refer to the same table in the SAP database.
• Key columns are always loaded. They should not, therefore, be given in the Load attribute.
• The Load attribute only works when loading the object list. All columns of the table are always loaded for When single object access
• The following operators are valid in the WHERE clause:

  Table 20: Permitted operators in the SQL attribute

  Operator	Function/Example
  EQ	=
  NE	<>
  GT	>
  LT	<
  GE	>=
  LE	<=
  BETWEEN	ENDDA BETWEEN '20090101' AND '20090131'

• A table definition can also contain a mapping block. This block is used to replace parameters that are supposed to be used in WHERE clauses but were selected with another name in the object list.

  In the example, every occurrence of the variable $BNAME$ was replaced with the value in the column USERNAME when single objects were loaded from the table RSECUSERAUTH before SQL selection was run. The column USERNAME must be loaded into an object list beforehand.

  Table definitions with a mapping are used primarily to load single objects.

• Predefined variables can be used as well as custom defined parameters in the WHERE clause. For more information, see Configuring a Schema Extension File.

Example:

Defining Functions

In the section for functions (Functions), you can describe the interfaces to BAPI functions required for accessing the data for the schema types, which will be defined.

In the optional mapping block, you define how the values are passed to the function call parameters. To do this, an object list must be created before the function call. The parameters for the function call can be filled from this object list's properties. In the example below, BNAME is a property, which is determined from the object list of the table USR02.

Predefined variables can be passed to the parameters. For more information, see Configuring a Schema Extension File. Apart from that, it is possible to pass a fixed value to a function parameter. The following notation is provided for this.

<Data ParameterName = "<Name>" PropertyName = "VALUE=<fixed value>" />

Example:

Related Topics

• Appendix: Example of a Schema Extension File

Defining Schema Types

In the section for schema types (SAPExtendedSchematypes), you can define schema types that exist in the SAP schema and can be used to extend the connector schema. The identifier given in the attribute Name is used as the name. This identifier must be unique in the extended connector schema.

Table 22: Schema typeDefines an object type within a schema. Refers to exactly one table or view of the database based schema or exactly one object type of the non-database based schema. definition

Attribute	Description
Bem	Internal description
Name	Name of the schema type in the extended connector schema.
DisplayPattern	Definition of a display pattern for displaying objects in the Synchronization EditorOne Identity Manager tool for configuring target system synchronization. (for example, in the target system browser or defining schema classes). (Optional) Only columns that are loaded in the table definition (attribute Key or Load) can be used. IMPORTANT: Each column, which must be additionally loaded when the object list is loaded, creates extra load for One Identity Manager. This can make synchronization much slower if there is a lot of data. Only enter columns that you really need for further object processing.
RevisionProperty	Name of a property contain the revision counter. (Optional)
ListObjectsDefinition	Function or table definition for calling an object list.
ReadObjectDefinition	Function or table definition for calling a single object.
WriteObjectDefinition	Function definition for writing an object. (Optional)
DeleteObjectDefinition	Function definition for deleting an object. (Optional)
ParentType	Context of the schema type. (Optional) By default, the schema types are client related (ParentType="SAPMANDANT"). If the new schema type is valid in all SAP R/3 system clients, enter the ParentType with the value "SAPSYSTEM". If this attribute is not defined, the schema type is client related.

A schema type definition must contain at least one object list call (attribute ListObjectsDefinition). In this case, you can enter a table or a function definition. To call a single object (attribute ReadObjectDefinition), the object list must have been loaded previously. The list call and single object call can refer to different tables, however the key columns for identifying single objects must either have the same name or have been mapped in the table definition for the single object call. In the example below, the single objects from table RSECUSERAUTH are determined for an object from the table USR02. The key columns for identifying the objects are USR02.BNAME and RSECUSERAUTH.UNAME. The columns have different names and are therefore mapped using the parameter $BNAME$.

If is possible to define a Properties block for declaring any number of other object properties and the types of access to them.P One single property is defined by the Property tag, which can have the following attributes.

Example:

Explanation:

The list of schema type objects UserFunctionTable is created by using the table USR02. Reading, writing and deleting is done with USER-BAPI functions, which each have been declared as a Function.

The schema type has a properties block. Two properties are defined here that are neither returned through the list call's table definition nor through the single object call's function definition. A multi-value property SAPBWP is defined, whose value is taken from the table RSECUSERAUTH. The single objects are identified by the columns USR02.BNAME and RSECUSERAUTH.UNAME. BAPI calls, which are defined as functions, are used for inserting and deleting values.

The property Userprofile is an example of a multi-value property, which has values read from a table (USER04) and a Replace function. Therefore, all values that need to remain in the property must always be given when changes are made. The write function is the original USER-BAPI function for setting profiles in the user (function definition for BAPI_USER_PROFILES_ASSIGN). Single objects are identified using the columns USR02.BNAME and USR04.BNAME. There is no mapping required for the table definition because the key columns have the same name.