Hi abapGit community,

with SAP_BASIS 816 a new package constraint check was introduced. This check affects the following abapGit scenarios:

• creation of sub-packages during an abapGit pull
• creation of a package via button Create Package in the “New Online Repository” screen

In both cases, the process is aborted with an error message similar to: “Change recording must be activated for package <package_name>”

Root cause
The newly introduced package constraint check validates the change recording flag (KORRFLAG) based on:

• the super package, or
• the software component (delivery unit)

If this validation determines that change recording is required, SAP enforces that all newly created packages must have KORRFLAG set.
Currently, abapGit creates packages without explicitly setting KORRFLAG, which leads to failures in SAP_BASIS 816 systems when the constraint check is triggered.

Expected behavior
abapGit should:

• evaluate whether change recording is required based on the super package or software component
• create packages with KORRFLAG = 'X' when required

This would restore compatibility with SAP_BASIS 816 and prevent pull and repository creation failures.

Best regards,
Thomas