The following step by step instructions guides you through the process of setting up a SAPMA configuration using the ERP Configuration Tool.

The approach

The approach is to first flow the create-user-data from the FIM attributes onto the corresponding function/parameters for the 1st function (BAPI_USER_CREATE). Next, assign a profile to the user account (allowing the user to log onto the SAP) by calling a 2nd function (BAPI_USER_PROFILES_ASSIGN).

Using the ERP MA Configuration Tool to create ERP MA configuration files is a three step process. These steps are:

  • Identifying what BAPI's must be called to get/set the data of interest (you may need an SAP administrator to assist).

  • Configuring a CS object, CS attributes, and the data flow between function/parameters and CS attributes

  • Saving the configuration to the FIMInstallDirectory/Extensions folder.

To create a configuration using the config tool
  1. Identify the BAPIs that will used to manipulate object within SAP.In most cases a SAP administrator will provide the appropriate BAPI's and parameter information needed to manipulate data within your SAP environment. If you will be using custom BAPIS, make sure the discovery filter is expanded appropriately. See the section on How to Configure a New Discovery Cache File for more information.

  2. Configure a CS object, CS attributes, and the data flow between function/parameters and CS attributes. This is mapping (or connecting) a CS attribute to function/parameter(s) which holds the data of interest. The mappings are created via the Add/Edit attributes wizard which can be access from the Main screen action button "Add Attribute" or "Edit."

  3. Saving the configuration to the FIMInstallDirectory/Extensions folder.By default configurations are saved to the FIMInstallDirectory/Extensions folder. At runtime the ERP MA expects to find the files in this location. The same name should be used when saving outputs through the ERP MA Configuration Tool and when creating the ERP MA in FIM.

    Note
    You cannot simply rename these files once created. This is because a dynamic .NET assembly is generated during the save process and the file names and the generated assembly info names must be in sync. Once you have generated all the needed files, you will then need to create a new ERP MA in FIM. This process is explained in details in the How To Create ERP MA in FIM topic.
[an error occurred while processing this directive]