released-abap-object-types-b31aa03.md

Released ABAP Object Types

The following table contains all the released ABAP object types that can be imported into your ABAP environment tenant.

Note:

If you try to import or export objects that are not supported, you receive a warning during the transport operation. The objects that are not released are skipped and not transported. To avoid this, you have to manually copy the ABAP objects to the target system. Note that you have to create these objects using the same name in the target system, unless they already exist. Afterwards, you either have to manually copy the code or reconfigure the objects identically in the target system.

APIS	API Release State of Objects
APLO	Application Log Object
AUTH	Authorization Check Fields
BDEF	Behavior Definition
BGQC	Background Processing Context
CDBO	Customer Data Browser Object
CFDF	Custom Field
CHDO	Change Document
CHKC	ATC Check Category
CHKO	ATC Check Object
CHKV	ATC Check Variant
CLAS	Class
COTA	Connection Target Transport Object
DCLS	ABAP Data Control Language Sources
DDLS	Data Definition Language Source
DDLX	Core Data Services Metadata Extensions
DEVC	Package
DESD	Logical External Schema
DOMA	Domain
DRAS	CDS Aspects
DRTY	Dictionary: CDS Type Definitions
DSFD	CDS Scalar Function Definition
DSFI	CDS Scalar Function Implementation Reference
DTEB	Dictionary Tuning: Entities Buffer
DTEL	Data Element
EEEC	Event Consumption Modell
ENHO	Enhancement Implementation Object
ENHS	Enhancement Spot Object
EVTB	Event Binding
ENQU	Lock Object
FUGR	Function Group
FUNC	Function Module
GSMP	Metric Provider
HTTP	HTTP Service
INTF	Interface
INTM	Intelligent Scenario Model
INTS	Intelligent Scenario
MSAG	Message Class
NONT	SAP Object Node Type
NTTY	Note Type
NROB	Number Range Object
RONT	SAP Object Type
SAJC	Application Job Catalog Entry
SAJT	Application Job Template
SCO1	Communication: Communication Scenario
SCO2	Communication: Inbound Service
SCO3	Outbound Service
SIA1	IAM: Business Catalog
SIA2	IAM: Restriction Type
SIA3	IAM: Authorization Object Extension
SIA5	IAM: Restriction Field
SIA6	IAM: App
SIA7	IAM: Business Catalog App Assignment
SIA8	IAM: Business Role Template
SIA9	IAM: Business Role Templ. Bus. Catalog Assignment
SIAD	Business Role Template Fiori Space Assignment
SKTD	Knowledge Transfer Document
SMBC	Maintainable Business Configuration
SMTG	OM: Email Template
SOD1	API Package
SOD2	API Package Assignment
SRVD	Service Definition
SUSH	Assignment: Service --> Authorization Objects
SUSO	Authorization Object
SWCR	Software Component Relations
TABL	Table Definition
TTYP	Table Type
UIAD	Application Descriptors for the Fiori Launchpad Enviornment
UIPG	Fiori Launchpad Page Template
UIST	Fiori Launchpad Space Template
XSLT	Transformation

Restrictions

• All objects imported with abapGit are imported as inactive, except the ones that don’t have an inactive state. Therefore, you have to activate all the imported objects after the import.

  Note:

  During the activation process, some objects may depend on other objects which need to be activated beforehand. For instance, the newly enabled DSFI objects depend on a corresponding DSFD, that needs to be activated beforehand.

  Also note that mass activation is not supported.

• All local changes to ABAP objects that are not saved are overwritten by the import.

• Open transport requests for any of the imported ABAP objects must be released before they can be changed. Otherwise, they get locked.

Known Issues

• Changes in table definitions could lead to data loss.