| name | abapgit-sush-object |
| description | Create an abapGit SUSH object outside SAP systems using user-defined names and repository reference files. |
Create abapGit SUSH object
abapGit docs: Supported Object Types | File Formats
Goal
Create a SUSH (Authorization Default Values Assignment) object directly as abapGit-serialized repository files, outside an SAP system. SUSH maps services/applications to their required authorization objects.
abapGit serialization rules
Naming rule
- SUSH uses a hash-based filename, not a semantic name.
- The filename is
<30-char-hash><2-char-type>.sush.xml (32 chars total before .sush.xml).
- The hash is derived from
USOBHASH fields (PGMID, OBJECT, OBJ_NAME).
- The type suffix (e.g.
ht) corresponds to the HEAD > TYPE field.
File structure
A SUSH object consists of a single file:
<hash><type>.sush.xml — authorization default values assignment
Complete sample
src/a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3ht.sush.xml
<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_SUSH" serializer_version="v1.0.0">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<HEAD>
<NAME>A1B2C3D4E5F6A1B2C3D4E5F6A1B2C3</NAME>
<TYPE>HT</TYPE>
<DISPLAY_NAME>R3TR G4BA ZFOO_UI_FLIGHT_O4</DISPLAY_NAME>
</HEAD>
<USOBX>
<USOBX>
<NAME>A1B2C3D4E5F6A1B2C3D4E5F6A1B2C3</NAME>
<TYPE>HT</TYPE>
<OBJECT>S_START</OBJECT>
<OKFLAG>X</OKFLAG>
</USOBX>
</USOBX>
<USOBHASH>
<PGMID>R3TR</PGMID>
<OBJECT>G4BA</OBJECT>
<OBJ_NAME>ZFOO_UI_FLIGHT_O4</OBJ_NAME>
</USOBHASH>
</asx:values>
</asx:abap>
</abapGit>
Key XML elements
| Element | Description |
|---|
HEAD > NAME | 30-character hash (uppercase) |
HEAD > TYPE | Type suffix (HT = hash type) |
HEAD > DISPLAY_NAME | Human-readable name: R3TR <OBJTYPE> <OBJNAME> |
USOBX > OBJECT | Authorization object checked (e.g. S_START) |
USOBX > OKFLAG | X = check is active |
USOBHASH > PGMID | Program ID (R3TR) |
USOBHASH > OBJECT | Object type of the assigned service (e.g. G4BA, IWSG) |
USOBHASH > OBJ_NAME | Name of the service being assigned |
Creation workflow
- SUSH objects are typically generated by the system when publishing a service binding.
- If creating manually, determine the hash from
USOBHASH fields.
- Create
<hash><type>.sush.xml in the same package as the service binding.
- Set
DISPLAY_NAME to R3TR <TYPE> <NAME> for readability.
- List all required authorization checks in
USOBX.
Done-check
- Serializer is exactly
LCL_OBJECT_SUSH.
- Filename format is
<30-char-hash><2-char-type>.sush.xml.
HEAD > NAME matches the hash portion of the filename (uppercase).USOBHASH correctly identifies the target service.- No SAP-system-only creation step is required.
