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.

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:

• SAP BTPService / SAP Cloud Solution: SAP BTP Service or SAP Cloud Solution in which content is developed.

• 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.

• 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: Integrating SAP Cloud Transport Management with Other SAP Cloud Solutions, where more information is available.

Table: Content Supported by SAP Cloud Transport Management

SAP BTP Service / SAP Cloud Solution	Content	Content Type	Environment	Design Time Integration	Content Agent Service	Solution Export Wizard	CI Pipeline Upload	Remarks	More Information about the Integration
SAP BTP, Cloud Foundry Runtime	HTML5 apps	MTA	Cloud Foundry	No	No	n/a	Yes	Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Cloud Foundry documentation
Joule Studio in SAP Build	Joule Studio projects (including Joule skills)	MTA	Cloud Foundry	Yes	Yes (for import and export)	n/a	No		Joule Studio
SAP Analytics Cloud	Content network packages	Application Content	Cloud Foundry / Neo	Yes	No	n/a	No		SAP Analytics Cloud
SAP API Management	API artifacts	MTA	Cloud Foundry	Yes	Yes (for content selection and deployment)	n/a	No	Using API management UI	SAP API Management
SAP Asset Performance Management	Communication system configurations Coding masks Risk and criticality assessment templates Strategy assessment templates for classes, including associated recommendations	Application Content	Cloud Foundry	Yes	No	n/a	No		SAP Asset Performance Management
SAP Batch Release Hub for Life Sciences	Configuration settings	Application Content	Cloud Foundry	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 Apps (part of SAP Build)	Projects	MTA	Cloud Foundry	Yes	Yes (for export and import)	n/a	No		SAP Build Apps
SAP Build Process Automation	Projects	MTA	Cloud Foundry	Yes	Yes (for export and import)	n/a	No		SAP Build Process Automation
SAP Build Work Zone, advanced edition	Content	Application Content	Cloud Foundry	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	Application Content	Cloud Foundry	Yes	No	n/a	No		SAP Build Workzone, standard edition
SAP BTP ABAP environment	References to SAP BTP ABAP environment content	BTP ABAP	SAP BTP ABAP environment	Yes	n/a	n/a	No	Export to SAP Cloud Transport Management takes place using the Manage Software Components app.	SAP BTP, ABAP Environment
SAP BTP, Cloud Foundry Runtime	Java apps	MTA	Cloud Foundry	No	No	n/a	Yes	Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Cloud Foundry documentation
SAP BTP, Cloud Foundry Runtime	NodeJs apps	MTA	Cloud Foundry	No	No	n/a	Yes	Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Cloud Foundry documentation
SAP Datasphere	Content packages	Application Content	Cloud Foundry	Yes	No	n/a	No		SAP Datasphere
SAP Destination Service	Destinations	MTA	Cloud Foundry	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
SAP Digital Manufacturing	Production process designs	Application Content	Cloud Foundry	Yes	No	n/a	No		SAP Digital Manufacturing
SAP Entitlement Management	Configuration content	Application Content	Cloud Foundry	Yes	No	n/a	No		SAP Entitlement Management
SAP Excise Tax Management	Warehouses	Application Content	Cloud Foundry	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	Application Content	Cloud Foundry	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 HANA Deployment Infrastructure (HDI)	HDI content	MTA	Cloud Foundry	No	No	n/a	Yes
SAP Integration Suite	Integration packages (integration flows, value mappings, APIs)	MTA	Cloud Foundry	Yes	Yes (for content selection and deployment)	n/a	No	Using the SAP Integration Suite UI	SAP Integration Suite
SAP Intelligent Clinical Supply Management	Configuration settings	Application Content	Cloud Foundry	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	MTA		No	Yes	n/a	No		SAP Mobile Services
SAP Profitability and Performance Management Cloud Standard Model	Environments	Application Content	Cloud Foundry	Yes	No	n/a	No		SAP Profitability and Performance Management Cloud
SAP Risk and Assurance Management	In-house business content (controls, automated procedures, manual procedures and regulations)	Application Content	Cloud Foundry	Yes	No	n/a	No	The Manage Business Content Packages app is used to activate and transport in-house business content packages.	SAP Risk and Assurance Management
SAP BTP, Neo application runtime	Authorization groups	MTA	Neo	No	n/a	Yes	No	Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Neo documentation.
SAP BTP, Neo application runtime	Destinations	MTA	Neo	No	n/a	Yes	No	Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Neo documentation.
SAP BTP, Neo application runtime	HTML5 apps	MTA	Neo	No	n/a	Yes	Yes	Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Neo documentation.
SAP BTP, Neo application runtime	HTML 5 roles	MTA	Neo	No	n/a	Yes	No	Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Neo documentation.
SAP BTP, Neo application runtime	Java apps	MTA	Neo	No	n/a	No	No	Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Neo documentation.
SAP Integration Suite	Content	MTA	Neo	Yes	n/a	Yes	No		SAP Integration Suite
SAP BTP, Neo application runtime	SAP Fiori apps	MTA	Neo	No	n/a	Yes	Yes	Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Neo documentation.
SAP BTP, Neo application runtime	SAP Fiori Portal	MTA	Neo	No	n/a	Yes	No	Only complete Portal sites Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Neo documentation.
SAP BTP, Neo application runtime	SAP Fiori roles	MTA	Neo	No	n/a	Yes	No	Content is developed and transported as part of another application.	Specific information: See the documentation of the application. General information: Integration with Transport Management Tools in the SAP BTP, Neo documentation.
SAP HANA XS classic model	Delivery units (DU)	XSC DU	Neo	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 Integrating SAP Cloud Transport Management with Other SAP Cloud Solutions.