Skip to content

Add "Source System" to repo settings#291

Merged
mbtools merged 1 commit into
mainfrom
mbtools/repo-sett-source-sys
Mar 16, 2026
Merged

Add "Source System" to repo settings#291
mbtools merged 1 commit into
mainfrom
mbtools/repo-sett-source-sys

Conversation

@mbtools

@mbtools mbtools commented Mar 16, 2026

Copy link
Copy Markdown
Member

No description provided.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds documentation for the new “Source System” repository setting in the .abapgit.xml user guide, explaining how TADIR-SRCSYSTEM is determined by default and how to override it.

Changes:

  • Document default SRCSYSTEM assignment behavior for customer namespaces vs. repair-key-only namespaces.
  • Explain how configuring a “Source System” affects modifiability after import, with example system IDs.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

Comment on lines +172 to +176
When importing objects in the default customer namespace (Y- or Z-packages), objects are assigned to the current system (`TADIR-SRCSYSTEM = SY-SYSID`). It works the same way, when importing objects into a namespace that has a producer key. This means you can freely create and modify objects in this namespace. However, if the namespace only has a repair key, abapGit will assign the importing objects to "SAP" (`TADIR-SRCSYSTEM = 'SAP'`). As a result, you will not be able to modify the objects.

#### Setting a Source System

If you want to allow modifying objects even if only a repair key is present (or part of the NSPC object in the repo), then you can set the source system in the repository settings to "SID". During import, abapGit will assign objects to the current system (`SY-SYSID`), which makes them modifiable. The typical use case is open-source projects using a namespace.

#### Setting a Source System

If you want to allow modifying objects even if only a repair key is present (or part of the NSPC object in the repo), then you can set the source system in the repository settings to "SID". During import, abapGit will assign objects to the current system (`SY-SYSID`), which makes them modifiable. The typical use case is open-source projects using a namespace.

If you want to allow modifying objects even if only a repair key is present (or part of the NSPC object in the repo), then you can set the source system in the repository settings to "SID". During import, abapGit will assign objects to the current system (`SY-SYSID`), which makes them modifiable. The typical use case is open-source projects using a namespace.

If you want to preserve the original system, you can set the source system accordingly. For example, your repository originates in system "DEV". Set source system in your repository settings to "DEV". When you import the repository to system "ABC" objects will be assigned to "DEV" and therefore will not be modifiable. The typical use case is landscapes with multiple development systems where you want to share common packages (but keep the link to the original).
@mbtools mbtools merged commit b6989ad into main Mar 16, 2026
5 checks passed
@mbtools mbtools deleted the mbtools/repo-sett-source-sys branch March 16, 2026 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants