メニュー
Create an abapGit SUSH object outside SAP systems using user-defined names and repository reference files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run ATC syntax check on the SAP system to detect syntax errors after git pull.
Trigger an abapGit repository pull on the SAP system to sync the current codebase.
Run ABAP Unit tests on the remote SAP system via ADT.
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
Detailed guidance on which test layer(s) to update and how to write tests for different kinds of changes in the ZASIS project.
Reference guide for the ZASIS exception handling pattern — class hierarchy, message class, T100 integration, how to raise exceptions, and rules for adding new exceptions.
| name | abapgit-sush-object |
| description | Create an abapGit SUSH object outside SAP systems using user-defined names and repository reference files. |
abapGit docs: Supported Object Types | File Formats
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.
<hash><type>.sush.xml — all lowercase.<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_SUSH" serializer_version="v1.0.0">
<30-char-hash><2-char-type>.sush.xml (32 chars total before .sush.xml).USOBHASH fields (PGMID, OBJECT, OBJ_NAME).ht) corresponds to the HEAD > TYPE field.A SUSH object consists of a single file:
<hash><type>.sush.xml — authorization default values assignmentsrc/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>
| 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 |
USOBHASH fields.<hash><type>.sush.xml in the same package as the service binding.DISPLAY_NAME to R3TR <TYPE> <NAME> for readability.USOBX.LCL_OBJECT_SUSH.<30-char-hash><2-char-type>.sush.xml.HEAD > NAME matches the hash portion of the filename (uppercase).USOBHASH correctly identifies the target service.