> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/sap.md).

# SAP

### Prerequisites:

* SAP GUI Version
  1. SAP GUI version – 7.40
  2. SAP GUI for Windows 7.40 cannot be run on Windows XP and Windows 2003 Server.
* Enable Server and Client Side scripting and disable pop up

**SAP GUI Scripting** is required in order to enable UI elements recognition capabilities in SAP automation. Here are the steps for enabling it:

* **Server Side**

  1. Login to your SAP server.
  2. Run transaction RZ11. Specify the parameter name **sapgui/user\_scripting** and click Display. If "Parameter name is unknown" appears in the status bar, this indicates that you are missing the current support package. Check your installed packages. Change the value of **sapgui/user\_scripting** to TRUE.
  3. Click Save.

  <figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FegupB4pR9qZrHVaTyLhQ%2Fimage.png?alt=media&amp;token=793b520a-0076-46fb-a178-2113bc7dc022" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F9VvDNmWsNDtxbTKqF0kn%2Fimage.png?alt=media&amp;token=0e6addf8-e04a-42a8-8475-7ed0d9ad569f" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FOHx5Sq8kT2Xtz8DSyu7f%2Fimage.png?alt=media&amp;token=ecb74694-838e-4549-8278-ec2ec6958cde" alt=""><figcaption></figcaption></figure>

**Client Side**

1. Open SAP GUI Options
2. Go to Accessibility & Scripting/Scripting
3. Enable scripting : **checked**
4. Notify when a script attaches to SAP GUI: **unchecked**
5. Notify when a script opens a connection: **unchecked**

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F7EXXIriOZgrRZKrYkvm5%2Fimage.png?alt=media&amp;token=29e2b897-5dd0-416b-8391-b6a9de846cc1" alt=""><figcaption></figcaption></figure>

**Establishing SAP Connection:**

In SAP Logon 740 window, go to Connections -> Add New Entry -> User Specified System

Enter the following details in System Connection Parameters -

* Description – SL2 \[52.165.148.179]
* Application Server – 52.165.148.179
* Instance Number – 04
* System ID – SL2


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/sap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
