Database Utility

abapGitAbout 3 minreference

Database Utility is a tool for managing database entries created by abapGit. You can access the tool via the tools icon in the top right corner of the abapGit home page .

It's possible to edit database entries of type

  • USER
  • REPO

Caution: Backup all abapGit database entries, first! Be careful when you edit these entries from within abapGit. Corrupting the XML or setting invalid options might break your abapGit!

Global Settings

The SETTINGS entries contain global (not user-specific) settings for your abapGit installation. This is an example:

<?xml version="1.0" encoding="utf-16"?>
<abapGit version="v1.0.0">
 <asx:abap xmlns:asx="" version="1.0">

User Settings

A USER entry contains meta information like the favorites of an user and their repository configurations e. g. name and email address for Git. This is an example of a USER entry:

<?xml version="1.0" encoding="utf-16"?>
<asx:abap xmlns:asx="" version="1.0">
      <NAME>First and Last Name</NAME>
      <NAME>First and Last Name</NAME>

Repository Meta Data

The REPO entries contain meta data like Git repository URL, branch, and package information and information about files known and to be excluded.


Older versions of abapGit also stored local checksums under REPO. These have been migrated to REPO_CS (see below).

This is an example:

<?xml version="1.0" encoding="utf-16"?>
<asx:abap xmlns:asx="" version="1.0">
    <DISPLAY_NAME>My Test Repository</DISPLAY_NAME>

If you remove a repository entry from the database util, the repository is not shown in abapGit anymore. This is useful for example if you want to remove a repository which has a non-existing package assigned and thus can't be opened and deleted normally.

Repository Checksums

abapGit persists the checksum (SHA1) of repository files under REPO_CS. For optimized storage, these entries do not use XML but a condensed text format:

  • Repository name
  • For each object:
    • Object Type | Object Name | Package
    • Path | Filename | Checksum




The BACKGROUND entries show the method and the repository key for which the background action will be executed:

The respective XML file contains the method and optionally the credentials needed for a push:

<?xml version="1.0" encoding="utf-16"?>
<asx:abap xmlns:asx="" version="1.0">

Backup & Restore

You can backup the abapGit database entries using the menu. Entries are stored in a separate XML-file and combined into a single ZIP-archive named abapGit_Backup_<date>_<time>.zip. You can use this feature also to transfer all your settings to another system.


Emergency Mode

On rare occasions, it is necessary to edit the abapGit settings to overcome an issue.

This enhancement allows you to start abapGit in "emergency mode", which directly shows the "Database Util" for you to view or edit any setting.

How to start abapGit in "Emergency Mode":

  1. Go to transaction SU3 to maintain your user profile
  2. Maintain parameter DBT with value "ZABAPGIT" (all-caps)
  3. Start abapGit which will launch the "Database Util"
  4. Make necessary changes and save
  5. After exiting abapGit, go back to SU3 and remove parameter DBT

Package Settings

SAP does not support assigning local packages to an application component. To stay in sync with repositories that use application components (in transportable packages), abapGit persists the application component for local package separately.


<?xml version="1.0" encoding="utf-16"?>
<abapGit version="v1.0.0">
 <asx:abap xmlns:asx="" version="1.0">