一键导入
abapgit-ddlx-object
Create an abapGit DDLX object outside SAP systems using user-defined names and repository reference files.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Create an abapGit DDLX 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-ddlx-object |
| description | Create an abapGit DDLX object outside SAP systems using user-defined names and repository reference files. |
abapGit docs: Supported Object Types | File Formats | Test Repo
Create a DDLX (CDS Metadata Extension) object directly as abapGit-serialized repository files, outside an SAP system.
<object_name>.ddlx.<extension> — all lowercase.<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_DDLX" serializer_version="v1.0.0">
A DDLX object consists of two files:
<name>.ddlx.asddlxs — CDS metadata extension source<name>.ddlx.xml — metadatasrc/zfoo_c_flight.ddlx.asddlxs@Metadata.layer: #CUSTOMER
@UI.headerInfo: {
typeName: 'Flight',
typeNamePlural: 'Flights',
description.value: 'FlightId'
}
annotate entity ZFOO_C_FLIGHT with
{
@UI.facet: [{
id: 'FlightDetails',
purpose: #STANDARD,
type: #IDENTIFICATION_REFERENCE,
label: 'Flight Details',
position: 10
}]
@UI.hidden: true
FlightId;
@UI.selectionField: [{ position: 10 }]
@UI.lineItem: [{ position: 10 }]
@UI.identification: [{ position: 10 }]
Carrier;
@UI.lineItem: [{ position: 20 }]
@UI.identification: [{ position: 20 }]
Connection;
@UI.lineItem: [{ position: 30 }]
@UI.identification: [{ position: 30 }]
FlightDate;
}
src/zfoo_c_flight.ddlx.xml<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_DDLX" serializer_version="v1.0.0">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<DDLX>
<METADATA>
<NAME>ZFOO_C_FLIGHT</NAME>
<DESCRIPTION>ZFOO_C_FLIGHT - Metadata Extension</DESCRIPTION>
<MASTER_LANGUAGE>EN</MASTER_LANGUAGE>
</METADATA>
</DDLX>
</asx:values>
</asx:abap>
</abapGit>
| Element | Description |
|---|---|
NAME | Metadata extension name (uppercase, matches annotated CDS view) |
DESCRIPTION | Short description |
MASTER_LANGUAGE | EN = English |
| Annotation | Purpose |
|---|---|
@Metadata.layer | #CUSTOMER, #PARTNER, #INDUSTRY, #CORE |
@UI.headerInfo | List report / object page header |
@UI.facet | Object page facets (sections) |
@UI.lineItem | Columns in list report |
@UI.selectionField | Filter bar fields |
@UI.identification | Fields on object page |
@UI.hidden | Hide technical fields |
<name>.ddlx.asddlxs with the annotate entity source.<name>.ddlx.xml with DDLX metadata.NAME typically matches the CDS consumption view being annotated.LCL_OBJECT_DDLX.NAME in XML matches the filename (uppercase vs lowercase)..asddlxs file uses annotate entity <CDS_VIEW> with syntax.@Metadata.layer is set.