메뉴
Create an abapGit SRVB 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-srvb-object |
| description | Create an abapGit SRVB object outside SAP systems using user-defined names and repository reference files. |
abapGit docs: Supported Object Types | File Formats
Create a SRVB (Service Binding) object directly as abapGit-serialized repository files, outside an SAP system.
<object_name>.srvb.xml — all lowercase.<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_SRVB" serializer_version="v1.0.0">
A SRVB object consists of a single file:
<name>.srvb.xml — service binding metadatasrc/zfoo_ui_flight_o4.srvb.xml<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_SRVB" serializer_version="v1.0.0">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<SRVB>
<METADATA>
<NAME>ZFOO_UI_FLIGHT_O4</NAME>
<TYPE>SRVB/SVB</TYPE>
<DESCRIPTION>Flight Management - OData V4 UI Service</DESCRIPTION>
</METADATA>
<CONTENT>
<BIND_TYPE_IMPL>
<NAME>ZFOO_UI_FLIGHT_O4</NAME>
</BIND_TYPE_IMPL>
<BIND_TYPE>ODATA</BIND_TYPE>
<BIND_TYPE_VERSION>V4</BIND_TYPE_VERSION>
<SERVICES>
<item>
<SERVICE_NAME>ZFOO_UI_FLIGHT</SERVICE_NAME>
<SERVICE_CONTENT>
<item>
<SERVICE_VERSION>0001</SERVICE_VERSION>
<RELEASE_STATE>NOT_RELEASED</RELEASE_STATE>
<SRVD_REF>
<URI>/sap/bc/adt/ddic/srvd/sources/zfoo_ui_flight</URI>
<TYPE>SRVD/SRV</TYPE>
<NAME>ZFOO_UI_FLIGHT</NAME>
</SRVD_REF>
<BIND_TYPE_DATA>
<CONTENT>
<ENCODING>base64</ENCODING>
</CONTENT>
</BIND_TYPE_DATA>
</item>
</SERVICE_CONTENT>
</item>
</SERVICES>
</CONTENT>
<CONTRACT>C1</CONTRACT>
<RELEASE_SUPPORTED>true</RELEASE_SUPPORTED>
<PUBLISHED>true</PUBLISHED>
<BINDING_CREATED>true</BINDING_CREATED>
</SRVB>
</asx:values>
</asx:abap>
</abapGit>
| Element | Description |
|---|---|
NAME | Service binding name (uppercase) |
TYPE | Always SRVB/SVB |
DESCRIPTION | Short description |
BIND_TYPE | ODATA |
BIND_TYPE_VERSION | V2 or V4 |
SERVICE_NAME | Referenced service definition name |
SRVD_REF > NAME | Service definition name (uppercase) |
SRVD_REF > URI | /sap/bc/adt/ddic/srvd/sources/<lowercase_srvd_name> |
CONTRACT | C1 = SAP standard contract |
PUBLISHED | true = service is published |
Service bindings typically follow: <srvd_name>_O2 (OData V2) or <srvd_name>_O4 (OData V4).
<name>.srvb.xml with the full binding metadata.BIND_TYPE_VERSION to V2 or V4.SRVD_REF.SRVD_REF > URI using the lowercase service definition name.LCL_OBJECT_SRVB.NAME in XML matches the filename (uppercase vs lowercase).SRVD_REF correctly references an existing service definition.BIND_TYPE_VERSION is valid (V2 or V4).