Menu
Create an abapGit SUSO object outside SAP systems using user-defined names and repository reference files.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-suso-object |
| description | Create an abapGit SUSO object outside SAP systems using user-defined names and repository reference files. |
abapGit docs: Supported Object Types | File Formats
Create a SUSO (Authorization Object) object directly as abapGit-serialized repository files, outside an SAP system.
<object_name>.suso.xml — all lowercase.<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_SUSO" serializer_version="v1.0.0">
A SUSO object consists of a single file:
<name>.suso.xml — authorization object metadatasrc/zfoo_flght.suso.xml<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_SUSO" serializer_version="v1.0.0">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<TOBJ>
<OBJCT>ZFOO_FLGHT</OBJCT>
<FIEL1>ZFOO_CARRIER</FIEL1>
<FIEL2>ACTVT</FIEL2>
<OCLSS>ZFOO</OCLSS>
</TOBJ>
<TOBJT>
<LANGU>E</LANGU>
<OBJECT>ZFOO_FLGHT</OBJECT>
<TTEXT>Flight Management: Read and Write Access</TTEXT>
</TOBJT>
<TOBJVORFLG>
<OBJCT>ZFOO_FLGHT</OBJCT>
<FLAG3>N</FLAG3>
<FLAG4>A</FLAG4>
<FLAG5>A</FLAG5>
</TOBJVORFLG>
<TACTZ>
<TACTZ>
<BROBJ>ZFOO_FLGHT</BROBJ>
<ACTVT>01</ACTVT>
</TACTZ>
<TACTZ>
<BROBJ>ZFOO_FLGHT</BROBJ>
<ACTVT>02</ACTVT>
</TACTZ>
<TACTZ>
<BROBJ>ZFOO_FLGHT</BROBJ>
<ACTVT>03</ACTVT>
</TACTZ>
<TACTZ>
<BROBJ>ZFOO_FLGHT</BROBJ>
<ACTVT>06</ACTVT>
</TACTZ>
</TACTZ>
</asx:values>
</asx:abap>
</abapGit>
| Element | Description |
|---|---|
TOBJ > OBJCT | Authorization object name (uppercase, max 10 chars) |
TOBJ > FIEL1..FIEL10 | Authorization fields (AUTH objects) |
TOBJ > OCLSS | Authorization object class (SUSC, max 4 chars) |
TOBJT > TTEXT | Description text |
TOBJVORFLG | Default field flags (N=no check, A=all values) |
TACTZ > ACTVT | Permitted activities (01=Create, 02=Change, 03=Display, 06=Delete) |
<name>.suso.xml in the appropriate src/ subfolder.OBJCT to the uppercase object name.FIEL1, FIEL2, etc.) — these must be AUTH objects.OCLSS.TACTZ.LCL_OBJECT_SUSO.OBJCT in XML matches the filename (uppercase vs lowercase).OCLSS references an existing SUSC authorization class.FIEL* values reference existing AUTH fields.