--- title: "SAP" slug: "sap" updated: 2023-01-03T11:51:44Z published: 2023-01-03T11:51:44Z canonical: "help.pillir.io/sap" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.pillir.io/llms.txt > Use this file to discover all available pages before exploring further. # SAP The SAP database requires a plugin and adapter to be configured in the **Administration**->**Integrations** tab. For servers like Salesforce, the data retrieval is query-related. Whereas, in the SAP server, data is fetched using **Functions** and not queries. A unique feature of EdgeReady Platform is that the user can access the non-remote functions through the SAP block. The data is not retrieved in the form of tables. They are fetched in **Key-value** pairs. The SAP action blocks are: | - **BAPI/RFC** - **Commit** - **Rollback** - **Start Transaction** - **Stop Transaction** | ![SAP-blocknew](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SAP-blocknew.png) | | --- | --- | There is a select plugin option for the SAP block. The [plugin](https://help.pillir.io/docs/integrations-plugins) is mandatory for SAP blocks. NoteIf RFC connection is enabled in the adapter configuration, the password is not required in the plugin lane. All the SAP operations are carried out in the plugin lane. They are explained below: | SAP Block Description | SAP Blocks on Canvas | | --- | --- | | ## BAPI / RFC It is a standard application interface that enables the EdgeReady server to access SAP. The user provides the following details: - When the plugin and adapter are selected by the user, the username is displayed in the first oval box and the user is prompted to enter the password in the second oval box. - Select **yes/no** for **Include Non-Remote FM**(*yes-Enables user to access Non-Remote BAPI functions*) - Select the required function from the **BAPI/RFC** dropdown list. - Select the **Input** and **Output** parameters from the respective dropdown lists. - Drag and drop the input and output variables in the oval boxes. 
Note
The BAPI block does not accept table variables in its Input and Output parameters. Each column from the table must be copied into a variable and then added to the parameters field.
| ![SAP-BAPI](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SAP-BAPI.png) | | ## Commit Commit saves data permanently to the database after a set of tentative changes. A commit ends a transaction and allows all other users to see the changes. | ![SAP-commit1](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SAP-commit1.png) | | ## Roll Back Rollback helps to restore values to previous values by negating recent changes. It undoes all recent changes and restores the database and updates. | ![SAP-Rollback1](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SAP-Rollback1.png) | | ## Start/Stop Transaction: A function call can be started or stopped using the Start/Stop Transaction Blocks. NoteIf a Start Transaction is used, then a Stop Transaction must also be used. | ![SAP-start-stop transaction-new](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SAP-start-stop%20transaction-new.png) | **EXAMPLE:** How does a typical SAP block function in real-time? | - For a given function, the plugin and adapter are selected and credentials are entered. - BAPI/RFC is included for non-remote FM and the BAPI/RFC is selected. - The respective input and output variables with their functional properties and values (table column values) are dragged and dropped. - The values are parsed into the respective input and output columns of the table. | BAPI/RFC: ![Sample_BAPI](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/Sample_BAPI.png) | | --- | --- |