Menu
Create an abapGit MSAG object outside SAP systems using user-defined names and repository reference files.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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-msag-object |
| description | Create an abapGit MSAG object outside SAP systems using user-defined names and repository reference files. |
abapGit docs: Supported Object Types | File Formats | Test Repo
Create a MSAG (Message Class) object directly as abapGit-serialized repository files, outside an SAP system.
<object_name>.msag.xml — all lowercase.<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_MSAG" serializer_version="v1.0.0">
A MSAG object consists of a single file:
<name>.msag.xml — message class with all messagessrc/zfoo_messages.msag.xml<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_MSAG" serializer_version="v1.0.0">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<T100A>
<ARBGB>ZFOO_MESSAGES</ARBGB>
<MASTERLANG>E</MASTERLANG>
<STEXT>Application Messages</STEXT>
</T100A>
<T100>
<T100>
<SPRSL>E</SPRSL>
<ARBGB>ZFOO_MESSAGES</ARBGB>
<MSGNR>001</MSGNR>
<TEXT>Operation completed successfully</TEXT>
</T100>
<T100>
<SPRSL>E</SPRSL>
<ARBGB>ZFOO_MESSAGES</ARBGB>
<MSGNR>002</MSGNR>
<TEXT>Entry &1 already exists</TEXT>
</T100>
<T100>
<SPRSL>E</SPRSL>
<ARBGB>ZFOO_MESSAGES</ARBGB>
<MSGNR>003</MSGNR>
<TEXT>Entry &1 not found</TEXT>
</T100>
<T100>
<SPRSL>E</SPRSL>
<ARBGB>ZFOO_MESSAGES</ARBGB>
<MSGNR>004</MSGNR>
<TEXT>Invalid input: &1 &2</TEXT>
</T100>
</T100>
</asx:values>
</asx:abap>
</abapGit>
| Element | Description |
|---|---|
| T100A | Message class header |
ARBGB | Message class ID (uppercase, max 20 chars) |
MASTERLANG | Master language (E = English) |
STEXT | Message class description |
| T100 | Individual message entries |
SPRSL | Language key (E = English) |
MSGNR | Message number (3-digit, zero-padded: 001–999) |
TEXT | Message text. Use &1–&4 for placeholders (XML-encoded as &1) |
<name>.msag.xml in the appropriate src/ subfolder.ARBGB in both T100A and all T100 entries to the uppercase message class name.001.&1 through &4 for message placeholders (XML encoding of &1).LCL_OBJECT_MSAG.ARBGB in XML matches the filename (uppercase vs lowercase).ARBGB is consistent across T100A and all T100 entries.&1 (XML-encoded ampersand).