SAP Business Technology Platform, Neo environment will sunset on December 31, 2028, subject to terms of customer or partner contracts.
For more information, see SAP Note 3351844.
This documentation refers to SAP Business Technology Platform, Neo environment. If you are looking for documentation about other environments, see SAP Business Technology Platform
↗️ .
In the context of SAP BTP, a solution is comprised of various application types and configurations, designed to serve a certain scenario or task flow. Typically the comprised parts of the solution are interconnected and have a common lifecycle. They are explicitly deployed, updated, deleted, configured, and monitored together.
A solution allows you to easily manage complex deployable artifacts. You can compose a solution by yourself, or you can acquire one from a third-party vendor. Furthermore, you can use the solutions to deploy artifacts that are comprised by entities external to SAP BTP, such as SAP SuccessFactors entities. This allows you to have a common management and lifecycle of artifacts spread across various SAP platforms and systems.
The following entities are required for creating a solution:
- A Multitarget Application (MTA) archive, which contains all required application types and configurations as well as a deployment descriptor file. It is intended to be used as a generic artifact that can be deployed and managed on several SAP BTP subaccounts. For example, you can reuse one MTA archive on your development and productive subaccounts.
- (Optionally) An МТА extension descriptor file that contains a deployment-specific data. It is intended to be used as a specific data source for a given SAP BTP subaccount. For example, you can have different extension descriptors for your development and productive subaccounts. Alternatively, you can also provide this data manually during the solution deployment.
You model the supported entities according to the MTA specification so that they can be deployed as a solution.
Related Information