Deploy Mode in SAP HANA Transport for ABAP
The deploy mode in SAP HANA Transport for ABAP specifies whether SAP HANA content (SAP HANA repository packages and associated objects) are deployed, either directly or after prework.
In ABAP for SAP HANA applications, it may be the case that SAP HANA content cannot yet be deployed in transports, updates, or upgrades. This can happen, for example, because it references objects (such as tables or schemata) that are not yet known at transport, update, or upgrade time. The missing referenced objects are usually created in the technical configuration of the application. In the configuration, for example, schemata can be created or tables replicated from other systems. Only then can the SAP HANA content be deployed. The deploy mode in SAP HANA Transport for ABAP is available for performing deployments after completed prework. This mode can be specified by the software provider for each SAP HANA package. It can have one of the following values:
Value |
Description |
|---|---|
A |
SAP HANA packages and associated objects are deployed directly in the import. (This is the default value.) |
P |
The SAP HANA packages and associated objects are deployed in the import only if prework was completed. If this is not the case, the non-deployed packages and objects are entered in the import log with a warning. |
If SAP HANA content is not deployed directly in the import due to missing prework, it is usually deployed automatically after the technical configuration. It is also possible, however, that the SAP HANA content in question may need to be deployed manually. Information about this process can be obtained from your software provider. For information about manual deployment, see Manually Deploying SAP HANA Objects and Packages.