# Delta Aggregation If you want your SAP Direct connector to support delta aggregation, which can speed up aggregation time by aggregating only new information, you can make certain changes on that system. For more information about aggregation, refer to [Loading Account Data](). A prerequisite to this process, as described in this document, is to copy the API Transport files to SAP. Select the link [here]() to download the files. > [!NOTE] > > SAP Direct must complete a full account aggregation before delta aggregation can be enabled. ## Supported Attributes The SAP Direct connector supports Delta Aggregation for the following attributes: - User created - User deleted - Password - User Type - Administrator lock set / IdentityIQ Disabled - Administrator lock released / IdentityIQ Enabled - Incorrect logon lock set / IdentityIQ Locked - Incorrect logon lock released / IdentityIQ Unlocked - Validity Period - Account Number - User Group - SAP Profile(s) Assigned - SAP Profile(s) Deleted - Security Policy ## Configure Delta Aggregation Use the following tasks to configure Delta Aggregation on your system. ### Importing the BAPIs This section describes how to import the transport request that contains the non-certified function modules used by SAP Direct connector to achieve the delta aggregation functionality. Function modules are imported using one of the following methods: - Using the Transport Control program manually - Using the menu-driven administration of Transport Requests via SAP GUI #### Prerequisites Copy the API Transport files to SAP. Use the following procedure to unpack and import the transport files function modules: 1. Copy the transport files. Transport request is contained in the `ImportSAPDirect.TAR` compressed file. Download the `ImportSAPDirect.TAR` file from the [Configuring Delta Aggregation TAR File]() page. The compressed file for each release contains the following files: - `RrequestNumber.sapId` - `KrequestNumber.sapId` Using WinZip or a similar utility, extract and copy each file from the appropriate compressed file to the subdirectory of the local transport directory of the target SAP system as follows: - Copy the `RrequestNumber.sapId` file to the `sapHomeDir\trans\data\RrequestNumber.sapId` directory. - Copy the `KrequestNumber.sapId` file to the `sapHomeDir\trans\cofiles\KrequestNumber.sapId` directory. > [!NOTE] > > Note the values of *requestNumber* and *sapId*. These values are required during the configuration of the Transport Control Program. #### Using the Transport Control Program Manually 1. At the command prompt (for both Microsoft Windows or UNIX systems), enter the following command to register the transport with the buffer: ```text os prompt> tp addtobuffer sapIdKrequestNumber yourSid ``` In the preceding command line, *sapId* and *requestNumber* were determined in *Prerequisites*. 2. Enter the following command to import the above transport request in to your SAP Solutions system: ```text os prompt>tp import sapIdKrequestNumber yourSid client=yourClient U126 ``` After executing the `tp` import command, the system issues a return code, indicating the status of the import. The most common return codes are described in the table below: | Return Code | Description | | --- | --- | | 0 | Successful import. The Transport imported successfully. | | 4 | Warning status. Minor version differences were detected.
The Transport Imported successfully. (No action is required.) | #### Importing the Transport Via SAP GUI If you are running SAP GUI, use the following procedure for importing the function modules: 1. Log in to SAP GUI with administrator permissions. 2. Perform one of the following: - From the Command field, run transaction `STMS` - From the menu, select **Tools \> Administration \> Transports \> Transport management system**. 3. In the **Transport Management System** window, press **F5**. 4. In the **Import Overview** window, double-click your system queue. The requests list for the system is displayed. 5. From the menu bar in the **Import Queue** window, select **Extras \> Other requests \> Add**. 6. Enter the request number and select **Yes**. 7. In the Attach to import queue message box, select **Yes**. 8. In the **Import Queue** window, select the new line, and then press **Ctrl + F11** to import the request. 9. In the **Import Transport Request** dialog box, perform the following: 1. In the **Target** client field, enter the name of the SAP client to which you want to import the transport. 2. On the **Date** tab, under **Start Date**, set the your required values. 3. On the **Execution** tab, under **Import**, ensure that **Synchronous** is selected. 4. On the **Options** tab, under **Import options**, ensure that all of the checkboxes are selected. 10. In the **Start Import** dialog box, select **Yes**. ### Verification All non-validated function modules are transported as a function group whose name starts with SailPoint's unique namespace (`"/SAILPOIN"`) To verify that the required function modules have been imported in to the SAP system, perform the following: 1. In the SAP system, execute **SE37** transaction. 2. Enter: `/SAILPOIN/*` in the Function Module field. 3. Press the **F4** key. This displays the Repository Info System window that lists all the imported functional modules currently available on the SAP system as follows: ```text SAILPOIN/USR_CHANGE_DOC_ROLES SAILPOIN/USR_CHANGE_DOC_USERS ```