---
title: "ABAP Extension via gCTS for Administrators - Payhawk Help Center"
slug: "installing-the-payhawk-abap-extension-via-gcts"
description: "Install the Payhawk ABAP Extension on SAP S/4HANA Cloud Public Edition with gCTS: set up Git credentials, link the repository, and pull the extension objects."
updated: 2026-08-04T12:18:09Z
published: 2026-08-04T12:18:09Z
canonical: "payhawk.com/installing-the-payhawk-abap-extension-via-gcts"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://payhawk.com/help/llms.txt
> Use this file to discover all available pages before exploring further.

# Installing the Payhawk ABAP Extension via gCTS (SAP S/4HANA Public Edition)

This article provides step-by-step instructions on how to install the Payhawk ABAP Extension onto your SAP S/4HANA® Cloud Public Edition system.

Payhawk uses the native Git-enabled Change and Transport System (gCTS) to deliver updates securely and directly to your environment. To complete the installation, you use the fine-grained Git access token and repository URL provided by Payhawk.

## Prerequisites

Before you begin the installation, make sure you have the following in place:

- **System landscape**: access to your SAP S/4HANA Cloud Public Edition development/test tenant (typically a 3-system landscape setup).
- **User authorizations**: your business user must be assigned a role containing Lifecycle Management business catalogs (such as `SAP_CORE_BC_COM` or the standard `SAP_BR_ADMINISTRATOR` template) to access gCTS and software component apps.
- **Extension details**:
  - Target package: `ZPARTNER`.
  - Git repository URL: `[provided by Partner]`.
  - Fine-grained access token: `[provided by Partner]`.

## Step-by-step installation guide

### Step 1: Configure your Git credentials

SAP S/4HANA Cloud processes Git credentials on a strict, client-specific basis. Maintain your token within the specific client where you intend to pull the repository.

1. Log in to your SAP S/4HANA Cloud Fiori launchpad.
2. Open the **Git-Enabled CTS** app (or **Manage Software Components**, depending on your administrative configuration).
3. Go to the **User Settings** or **Credentials** section.
4. Choose **Create** or **Add Credentials** and enter the following details:
  - **Authentication Type**: Personal Access Token / Token.
  - **Username**: the username or Git identity provided to you.
  - **Token/Password**: paste the fine-grained access token exactly as provided.
5. Save your changes.

> [!WARNING]
> Treat this fine-grained token as a secure password. It is scope-limited specifically to grant your system read-only access to pull the `ZPARTNER` repository.

### Step 2: Link the repository to your system

Next, map the Payhawk hosted repository to your local cloud environment.

1. In the gCTS/Software Components interface, go to the **Repositories** tab and select **Create** or **Clone**.
2. Enter the Git repository URL provided by Payhawk support.
3. Configure the following parameters during the repository setup:
  - **Software Component / Package**: `ZPARTNER`.
  - **Repository Role**: **"Provided"**
4. Choose the default deployment branch: Production.
5. Click **Clone** or **Save**. The system authenticates using the credentials saved in Step 1.

### Step 3: Pull the extension objects

Once the link is initialized, you can deploy the ABAP objects directly into your tenant.

1. Select your newly created `ZPARTNER` repository from the list.
2. Go to the **Branches** or **Commits** tab.
3. Locate the latest commit, version tag, or active release branch.
4. Click **Pull** (or **Update**).
5. The system triggers a background deployment job. You can monitor the progress, logs, and object transport steps through the **Jobs** or **History** tab.

## Troubleshooting and support

- **Authentication errors (**`401 Unauthorized`**)**: ensure the fine-grained token was pasted without trailing spaces and has not expired. Remember that credentials must be maintained within the specific client you are operating in.