supported-content-types-8961dcb.md

Supported Content Types

SAP Cloud Transport Management service can be used to transport the following entities, called content types:

• Multitarget Application archives (MTAs -.mtar files) between different spaces in SAP BTP subaccounts

  MTAs can consist of a cloud application itself, or content created in a cloud application, which you want to transport between two subaccounts. For example, SAP Cloud Integration content is packaged and transported as an MTA.

  Restriction:

  Transporting MTAs without modules is not supported.

• BTP ABAP: references to ABAP objects in a Git repository between different SAP BTP, ABAP environment instances. A reference can consist of the name of the software component, the commit ID, the branch name, and the tag name. When a reference of type BTP ABAP is imported, the referenced content of the Git repository is pulled to the target instance.

• Application content transported in an application-specific format between different cloud subaccounts and tenants

  In general, application content is packed in archive files, for example, .zip files, or .rar files. The archives can contain any kind of application-specific content. The application that has created such an archive file must provide a method to deploy the application-specific content into the target environment. This means, such an archive file can only be used for transport if the application-specific deployment service in the target environment is able to handle it. For more information, see the documentation of the individual applications.

• Delivery units (DUs) of SAP HANA XS classic model between different SAP HANA instances that are assigned to cloud subaccounts

These content types (files or references) can be transported in one of the following scenarios:

• Directly from within another application
• They are uploaded from a Continuous Integration pipeline.
• They are available on local file systems.

For more information, see SAP Cloud Transport Management Scenarios.

Overview: Supported Content

The table contains a list of development artifacts and application-specific content that can be transported using SAP Cloud Transport Management service.

The table contains the following information:

• Content: Application-specific content and development artifacts to be transported.

• Environment: SAP BTP environment where the content is created, either SAP BTP, ABAP environment, Cloud Foundry, or Neo.

• Content Type: Entity to transport that you can select when you create a new node in SAP Cloud Transport Management. See Supported Content Types.

• Design Time Integration: Can the transport be triggered directly in the design time tool of the application where the content is produced?

• Content Agent Service: Is the integration with SAP Cloud Transport Management realized using SAP Content Agent service? (Cloud Foundry only)

• Solution Export Wizard: Is the integration with SAP Cloud Transport Management realized using Solution Export Wizard? (Neo only)

• Continuous Integration (CI) Pipeline Upload: Is there a CI pipeline template available with the option of uploading content to SAP Cloud Transport Management?

  For more information about integration into CI pipelines, see the links to More Information listed in the Integration Scenario: Receiving transports comprising release candidates qualified by automated pipelines in SAP Continuous Integration and Delivery service, in particular the series of tutorial videos.

• More Information about the Integration: Link to more information about the integration with SAP Cloud Transport Management in the relevant section of:Integration in Development and Change Management Processes and with Other Services, where more information is available.

Table: Content Supported by SAP Cloud Transport Management

Content	Environment	Content Type	Design Time Integration	Content Agent Service	Solution Export Wizard	CI Pipeline Upload	Remarks	More Information about the Integration
Reference to SAP BTP, ABAP environment content	SAP BTP, ABAP environment	BTP ABAP	Yes	n/a	n/a	No	Export to SAP Cloud Transport Management takes place using the Manage Software Components app.	SAP BTP, ABAP Environment
API Management content	Cloud Foundry	MTA	Yes	Yes (for content selection and deployment)	n/a	No	Using API management UI	SAP API Management
Destination	Cloud Foundry	MTA	No	Yes	n/a	No	Using the integration of SAP Destination Service in SAP Content Agent service. Note that secrets and passwords are not transported.	SAP Content Agent Service
HTML5 app	Cloud Foundry	MTA	No	No	n/a	Yes
Java app	Cloud Foundry	MTA	No	No	n/a	Yes
NodeJs app	Cloud Foundry	MTA	No	No	n/a	Yes
SAP Build Apps projects	Cloud Foundry	MTA	Yes	Yes (for export and import)	n/a	No		SAP Build Apps
SAP Build Process Automation projects	Cloud Foundry	MTA	Yes	Yes (for export and import)	n/a	No		SAP Build Process Automation
SAP Cloud Integration content	Cloud Foundry	MTA	Yes	Yes (for content selection and deployment)	n/a	No	Using SAP Cloud Integration UI	SAP Cloud Integration
SAP HANA Deployment Infrastructure (HDI) content	Cloud Foundry	MTA	No	No	n/a	Yes
SAP Analytics Cloud (content network packages)	Cloud Foundry / Neo	Application Content	Yes	No	n/a	No		SAP Analytics Cloud
SAP Batch Release Hub for Life Sciences (configuration settings)	Cloud Foundry	Application Content	Yes	No	n/a	No	Export to SAP Cloud Transport Management takes place using the Transport Configuration Settings app.	SAP Batch Release Hub for Life Sciences
SAP Build Work Zone, advanced edition content	Cloud Foundry	Application Content	Yes	No	n/a	No	Using the integration of SAP Build Work Zone, standard edition in SAP Build Work Zone, advanced edition	SAP Build Workzone, advanced edition
SAP Build Work Zone, standard edition content	Cloud Foundry	Application Content	Yes	No	n/a	No		SAP Build Workzone, standard edition
SAP Datasphere (content packages)	Cloud Foundry	Application Content	Yes	No	n/a	No		SAP Datasphere
SAP Entitlement Management (configuration content)	Cloud Foundry	Application Content	Yes	No	n/a	No		SAP Entitlement Management
SAP Excise Tax Management (warehouses)	Cloud Foundry	Application Content	Yes	No	n/a	No	Warehouse address details are not transported with a warehouse. They must be maintained in the Address Types for Warhouses app.	SAP Excise Tax Management
SAP Group Reporting Data Collection (forms and folders)	Cloud Foundry	Application Content	Yes	No	n/a	No	In the Manage Packages app, forms and folders can be exported to SAP Cloud Transport Management.	SAP Group Reporting Data Collection for SAP S/4HANA
SAP Intelligent Clinical Supply Management (configuration settings)	Cloud Foundry	Application Content	Yes	No	n/a	No	Export to SAP Cloud Transport Management takes place using the Transport Configuration Settings app.	SAP Intelligent Clinical Supply Management
SAP Mobile Services application configurations	Cloud Foundry	MTA	No	Yes	n/a	No		SAP Mobile Services
Authorization group	Neo	MTA	No	n/a	Yes	No
Destination	Neo	MTA	No	n/a	Yes	No
HTML5 app	Neo	MTA	No	n/a	Yes	Yes
HTML 5 role	Neo	MTA	No	n/a	Yes	No
Java app	Neo	MTA	No	n/a	No	No
SAP Cloud Integration content	Neo	MTA	Yes	n/a	Yes	No		SAP Cloud Integration
SAP Fiori app	Neo	MTA	No	n/a	Yes	Yes
SAP Fiori Portal	Neo	MTA	No	n/a	Yes	No	Only complete Portal sites
SAP Fiori role	Neo	MTA	No	n/a	Yes	No
Delivery unit (DU) of SAP HANA XS classic model	Neo	XSC DU	No	n/a	No	No	On Delivery Unit (DU) level

More Information

• Multitarget Applications in the Cloud Foundry Environment
• Multitarget Applications for the Neo Environment
• For more information about the integration of specific content in SAP Cloud Transport Management, see Integration in Development and Change Management Processes and with Other Services.