---
sourceDocument: Asset Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-asset-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Deploy the ABAP program for SAP

# Deploy the ABAP program for SAP {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Deploy the Advanced Business Application Programming (ABAP) program to establish a connection between your SAP system and your ServiceNow instance. Deploying the ABAP program allows data to be shared between SAP and your ServiceNow instance.

## Before you begin

Download the SAP ABAP for Software Asset Management application from the [ServiceNow Store](https://store.servicenow.com/). Download the application version that is compatible with the Brazil release.  
Note:  
The ABAP program performs only read operations on existing standard functional modules. It does not modify these modules in any way.
Role required: sam_admin, SAP Basis administrator

## About this task

To deploy the ABAP program, import the transport files that are provided through the SAP ABAP for Software Asset Management application and then configure a service provider with the service-oriented architecture (SOA) Manager.  
Note:  
If you upgrade your ServiceNow instance, you must download and deploy the version of the ABAP program that is compatible with the new release.

You must read all Release notes and Requirements under the Version details
section in the [SAP ABAP for Software Asset Management](https://store.servicenow.com/store/app/85596fae1be06a50a85b16db234bcbff)application. The download folder contains multiple transport files. Deploy only the transport requests that apply to your SAP system type and the functionality that you require.

Four different transport requests (TR) are provided in the ABAP ZIP file. Refer to the following
table to see what purpose each transport request serves depending on the system type and required functionality.  
{#import-abap-program-sap__table_sfk_mry_fjc__entry__4}

| Transport type | Purpose | Supported systems | Notes |
|-|-|-|-|
| Central Transport -- With Digital Access | Includes Digital Access logic for extracting data such as sales documents, purchase orders, financial invoices, and so on. | * SAP ERP Central Component (ECC) * SAP S/4HANA * SAP S/4HANA Cloud, Private Edition {#import-abap-program-sap__ul_iz2_h3n_kkc} | Used when Digital Access data collection is required. |
| Central Transport -- Without Digital Access | Does not include Digital Access logic for document extraction. | * SAP ECC * SAP Solution Manager * SAP GRC * SAP S/4HANA * SAP S/4HANA Cloud, Private Edition {#import-abap-program-sap__ul_vvh_t3n_kkc} | Used when Digital Access data collection is not required. |
| Satellite Transport for On-Premises | Contains SAP S/4HANA Database--specific code that is required for data extraction from satellite systems. | SAP S/4HANA | Import only if the satellite or RFC system is SAP S/4HANA. |
| Satellite Transport for Private Cloud | Contains SAP S/4HANA Database--specific code and Full Usage Equivalent (FUE) user classification code that is required for data extraction from satellite systems. | SAP S/4HANA Cloud, Private Edition | Import only if the satellite or RFC system is SAP S/4HANA Cloud, Private Edition. |
[ ]

{#import-abap-program-sap__table_sfk_mry_fjc}  
Note:  
You must deploy one of the central transport types according to your requirement. For satellite or RFC systems, deploy the satellite transport that matches your deployment: the on-premises satellite transport for SAP S/4HANA satellite systems, or the Private Cloud satellite transport for SAP S/4HANA Cloud, Private Edition satellite systems.

For further information on SAP setup, see [KB0813999](https://support.servicenow.com/kb_view.do?sysparm_article=KB0813999).

For more information on SAP and its related tools, refer to the [SAP Help Portal](https://help.sap.com/viewer/index).

## Procedure

1. In your SAP system, import all applicable transport files using the SAP Transport Management System (STMS).
2. Copy and extract the COFILE and DATA files to your directory.
3. Start STMS and select Import Overview.
4. Double-click the target system, select ExtrasOther RequestsAdd, and then enter the transport request number.
5. Highlight the request and select RequestImport.
6. From the Import Transport Request window, enter the client number in the Target Client field.
7. Select the Options tab, and then select the Ignore Invalid Component Version check box.
8. Select OK.
9. Verify the RFC connection.
{#import-abap-program-sap__steps_rbw_rx5_njc}

## What to do next

In your SAP system, configure a service provider with the SOA Manager and generate a Web Services Description Language (WSDL) URL for the SAP service definition. For details, see [Create a WSDL for the SAP service definition](https://www.servicenow.com/docs/Y27lkj7nwnQ7Axbo1tm1nA "Generate a Web Services Description Language (WSDL) URL for the SAP service definition to use when creating SAP connections on your ServiceNow instance.").

*[\>]: and then