| name | abapgit-auth-object |
| description | Create an abapGit AUTH object outside SAP systems using user-defined names and repository reference files. |
Create abapGit AUTH object
abapGit docs: Supported Object Types | File Formats | Test Repo
Goal
Create an AUTH (Authorization Check Field) object directly as abapGit-serialized repository files, outside an SAP system.
abapGit serialization rules
Naming rule
- Use the exact object names provided by the user/request.
- Do not use placeholder names for implementation.
File structure
An AUTH object consists of a single file:
<name>.auth.xml — authorization field metadata
Complete sample
src/zfoo_carrier.auth.xml
<?xml version="1.0" encoding="utf-8"?>
<abapGit version="v1.0.0" serializer="LCL_OBJECT_AUTH" serializer_version="v1.0.0">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<AUTHX>
<FIELDNAME>ZFOO_CARRIER</FIELDNAME>
<ROLLNAME>ZFOO_CARRIER_ID</ROLLNAME>
<CHECKTABLE>ZFOO_FLIGHT</CHECKTABLE>
</AUTHX>
</asx:values>
</asx:abap>
</abapGit>
Key XML elements
| Element | Description |
|---|
FIELDNAME | Authorization field name (uppercase, max 10 chars) |
ROLLNAME | Referenced data element |
CHECKTABLE | Check table for the field (optional) |
Creation workflow
- Take the authorization field name and target package path from the user/request.
- Create
<name>.auth.xml in the appropriate src/ subfolder.
- Set
FIELDNAME to the uppercase object name.
- Reference the data element via
ROLLNAME and optionally a CHECKTABLE.
Done-check
- Serializer is exactly
LCL_OBJECT_AUTH.
FIELDNAME in XML matches the filename (uppercase vs lowercase).
ROLLNAME references a valid data element.
- No SAP-system-only creation step is required.