원클릭으로 Manus에서 모든 스킬 실행

시작하기

abapgit-devc-object

스타17

포크1

업데이트2026년 5월 18일 13:43

Create an abapGit DEVC object outside SAP systems using user-defined names and repository reference files.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

MagPasulke

MagPasulke/abap-string-interpreter

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Create abapGit DEVC object

abapGit docs: Supported Object Types | File Formats | Folders & Files

Goal

Create a DEVC (Package) object directly as abapGit-serialized repository files, outside an SAP system.

abapGit serialization rules

Files are UTF-8 with BOM, LF line endings, 2-space indentation.
Package files always use the fixed filename: package.devc.xml — one per folder.
abapGit does not store SAP package names in the repository. Folder names map to package names during import based on the folder logic setting.

The XML metadata file must start with:

<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_DEVC" serializer_version="v1.0.0">

Naming rule

The filename is always package.devc.xml (not the SAP package name).
Place it in the folder that represents the package.

File structure

A DEVC object consists of a single file per package folder:

package.devc.xml — package metadata

Complete sample

Sample A — Root package

`src/package.devc.xml`

<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_DEVC" serializer_version="v1.0.0">
 <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
  <asx:values>
   <DEVC>
    <CTEXT>My Custom Application</CTEXT>
   </DEVC>
  </asx:values>
 </asx:abap>
</abapGit>

Sample B — Sub-package

`src/model/package.devc.xml`

<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_DEVC" serializer_version="v1.0.0">
 <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
  <asx:values>
   <DEVC>
    <CTEXT>My Custom Application - Data Model</CTEXT>
   </DEVC>
  </asx:values>
 </asx:abap>
</abapGit>

Key XML elements

Element	Description
`CTEXT`	Package description text

Creation workflow

Create the folder structure under src/ matching the desired package hierarchy.
Place a package.devc.xml file in each folder.
Set CTEXT to a meaningful description of the package's purpose.
Sub-packages are represented as subdirectories, each with their own package.devc.xml.

Done-check

Serializer is exactly LCL_OBJECT_DEVC.
Filename is package.devc.xml (never the SAP package name).
Every folder under src/ that should become a package has a package.devc.xml.
CTEXT is filled with a descriptive text.
No SAP-system-only creation step is required.

이 저장소의 다른 Skills

같은 저장소

adt-checkerrors

MagPasulke/abap-string-interpreter

Run ATC syntax check on the SAP system to detect syntax errors after git pull.

2026-06-1117

adt-gitpull

MagPasulke/abap-string-interpreter

Trigger an abapGit repository pull on the SAP system to sync the current codebase.

2026-06-1117

adt-rununit

MagPasulke/abap-string-interpreter

Run ABAP Unit tests on the remote SAP system via ADT.

2026-05-3017

conventional-commit

MagPasulke/abap-string-interpreter

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.

2026-05-2817

create-tests

MagPasulke/abap-string-interpreter

Detailed guidance on which test layer(s) to update and how to write tests for different kinds of changes in the ZASIS project.

2026-05-2817

exception-handling

MagPasulke/abap-string-interpreter

Reference guide for the ZASIS exception handling pattern — class hierarchy, message class, T100 integration, how to raise exceptions, and rules for adding new exceptions.

2026-05-2617

name	abapgit-devc-object
description	Create an abapGit DEVC object outside SAP systems using user-defined names and repository reference files.

Create abapGit DEVC object

abapGit docs: Supported Object Types | File Formats | Folders & Files

Goal

Create a DEVC (Package) object directly as abapGit-serialized repository files, outside an SAP system.

abapGit serialization rules

Files are UTF-8 with BOM, LF line endings, 2-space indentation.
Package files always use the fixed filename: package.devc.xml — one per folder.
abapGit does not store SAP package names in the repository. Folder names map to package names during import based on the folder logic setting.

The XML metadata file must start with:

<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_DEVC" serializer_version="v1.0.0">

Naming rule

The filename is always package.devc.xml (not the SAP package name).
Place it in the folder that represents the package.

File structure

A DEVC object consists of a single file per package folder:

package.devc.xml — package metadata

Complete sample

Sample A — Root package

`src/package.devc.xml`

<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_DEVC" serializer_version="v1.0.0">
 <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
  <asx:values>
   <DEVC>
    <CTEXT>My Custom Application</CTEXT>
   </DEVC>
  </asx:values>
 </asx:abap>
</abapGit>

Sample B — Sub-package

`src/model/package.devc.xml`

<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_DEVC" serializer_version="v1.0.0">
 <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
  <asx:values>
   <DEVC>
    <CTEXT>My Custom Application - Data Model</CTEXT>
   </DEVC>
  </asx:values>
 </asx:abap>
</abapGit>

Key XML elements

Element	Description
`CTEXT`	Package description text

Creation workflow

Create the folder structure under src/ matching the desired package hierarchy.
Place a package.devc.xml file in each folder.
Set CTEXT to a meaningful description of the package's purpose.
Sub-packages are represented as subdirectories, each with their own package.devc.xml.

Done-check

Serializer is exactly LCL_OBJECT_DEVC.
Filename is package.devc.xml (never the SAP package name).
Every folder under src/ that should become a package has a package.devc.xml.
CTEXT is filled with a descriptive text.
No SAP-system-only creation step is required.