Use of Custom BAdis in SAP ABAP Systems 

Purpose

SAP systems with release 4.6D and higher contain default Business Add-Ins (BAdis) that implement how the SAP system creates, updates, and deletes user data upon receipt of XML documents from UME. The default BAdis create standard SU01 users. Applications running on SAP systems may have additional requirements that are not covered by the default BAdis. In this case, the default BAdis can be overriden by custom BAdis that provide an application-specific implementation for actions such as user creation, updating, and deletion.

For example, SAP Enterprise Buyer might require that users are created with additional attributes that are not contained in the standard SU01 user profile.

The process for setting up an SAP ABAP system to use custom BAdis is outlined below.

Process Flow

...

       1.      Optionally an ABAP application developer develops a custom BAdi implementation. Alternatively, one of the BAdi implementations shipped with the SAP ABAP system can be used. Each BAdi implementation has a corresponding filter value.

       2.      In UME, you maintain the properties for the SAP System, paying particular attention to the properties that you need to maintain if you are using a custom BAdi implementation.

       3.      In the ABAP system, you map the filter value of the BAdis to a receiver ID in UME. This ensures that when UME sends an XML document to the ABAP system, the correct BAdis are used. For details, see Configuring SAP ABAP System.