Menu
Create an abapGit G4BA 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-g4ba-object |
| description | Create an abapGit G4BA object outside SAP systems using user-defined names and repository reference files. |
abapGit docs: Supported Object Types | File Formats
Create a G4BA (OData V4 Backend Service Group) object directly as abapGit-serialized repository files, outside an SAP system. G4BA is the OData V4 service catalog entry generated when a service binding is published.
<object_name>.g4ba.xml — all lowercase.<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_G4BA" serializer_version="v1.0.0">
A G4BA object consists of a single file:
<name>.g4ba.xml — OData V4 service group metadatasrc/zfoo_ui_flight_o4.g4ba.xml<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_G4BA" serializer_version="v1.0.0">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<_-IWBEP_-I_V4_MSGA>
<_-IWBEP_-I_V4_MSGA>
<GROUP_ID>ZFOO_UI_FLIGHT_O4</GROUP_ID>
<SERVICE_ID>/IWBEP/COMMON</SERVICE_ID>
<REPOSITORY_ID>DEFAULT</REPOSITORY_ID>
<GWBEP_VERSION>031</GWBEP_VERSION>
</_-IWBEP_-I_V4_MSGA>
</_-IWBEP_-I_V4_MSGA>
<_-IWBEP_-I_V4_MSGR>
<_-IWBEP_-I_V4_MSGR>
<GROUP_ID>ZFOO_UI_FLIGHT_O4</GROUP_ID>
<GWBEP_VERSION>031</GWBEP_VERSION>
<ASSIGNMENT_REPO_ID>SADL</ASSIGNMENT_REPO_ID>
<EXTERNAL_GROUP_ID>ZFOO_UI_FLIGHT_O4</EXTERNAL_GROUP_ID>
</_-IWBEP_-I_V4_MSGR>
</_-IWBEP_-I_V4_MSGR>
<_-IWBEP_-I_V4_MSGT>
<_-IWBEP_-I_V4_MSGT>
<GROUP_ID>ZFOO_UI_FLIGHT_O4</GROUP_ID>
<LANGUAGE>E</LANGUAGE>
<DESCRIPTION>Flight Management - OData V4 UI Service</DESCRIPTION>
</_-IWBEP_-I_V4_MSGT>
</_-IWBEP_-I_V4_MSGT>
</asx:values>
</asx:abap>
</abapGit>
| Element | Description |
|---|---|
GROUP_ID | Service group name (uppercase, matches SRVB name) |
SERVICE_ID | /IWBEP/COMMON (standard IWBEP service) |
REPOSITORY_ID | DEFAULT |
GWBEP_VERSION | Gateway version (031 typical for current systems) |
ASSIGNMENT_REPO_ID | SADL (Service Adaptation Description Language) |
EXTERNAL_GROUP_ID | External name, typically same as GROUP_ID |
DESCRIPTION | Human-readable description |
_-IWBEP_-I_V4_MSGA, _-IWBEP_-I_V4_MSGR, _-IWBEP_-I_V4_MSGT._- prefix/suffix) represent the /IWBEP/ namespace in XML.<name>.g4ba.xml in the same package as the corresponding SRVB.GROUP_ID and EXTERNAL_GROUP_ID to the uppercase object name.SERVICE_ID as /IWBEP/COMMON and REPOSITORY_ID as DEFAULT.LCL_OBJECT_G4BA.GROUP_ID in XML matches the filename (uppercase vs lowercase)._-IWBEP_- escaped format.