Ansicht
Dokumentation

SCTS_HTA_ADMIN - Execute administrative tasks in HTA for HDI

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Purpose

This program allows you to perform administrative tasks in SAP HANA Transport for ABAP for SAP HANA Deployment Infrastructure (HTA for HDI).

Features

You can perform the following tasks:

Update references in projects of SAP Web IDE

With this action, the references of all projects in SAP Web IDE are updated for a given logical HDI container. Use this action, if you changed the references of a container in transaction SCTS_AMHC, and if you want to use the new references in SAP Web IDE projects that already exist.

Update User-Provided Service in XSA

With this action, the User-Provided service (external service) for a given logical HDI container, logical database schema, or the SAP_ABAP schema is recreated in XSA. This action will first delete the current external service and its users and then recreate the users and the User-Provided service. Use this action in the following situations:

• If you encounter issues with the User-Provided service in SAP Web IDE for SAP HANA.

• If the names of the physical HDI containers have changed during a downtime-minimized update (update with Software Update Manager (SUM) with Zero Downtime Option (ZDO)) and also need to be updated in SAP Web IDE.

Download HDI object

You can download an HDI object from the HTA repository to your local PC by specifying the logical HDI container, the HDI namespace, and the full object path. Input help is available for all fields. During execution you will be asked to enter the local target file. The download will then start immediately.

Upload HDI object

Usually, you should use SAP Web IDE for SAP HANA to edit HDI objects.

However, there might be reasons not to use SAP Web IDE, e.g. for urgent fixes in systems where SAP Web IDE was not set up, or because you only consume objects delivered by others and you need to fix these.

To upload an HDI object from your local PC to the HTA repository you need to specify the logical HDI container, the HDI namespace, and the full object path of the object that you want to replace. It is not possible to create new HDI objects. Input help is available for all fields.

When executing the upload, the system performs the following steps:

1. The system asks you to specify the local source file which is then uploaded to AS ABAP.
2. For non-local objects, you will be asked for a transport request to record the change.
3. HTA deploys the file to the HDI container.
4. Only if the deployment succeeds, the file is saved in the HTA repository.

After executing the steps, the system displays the deployment log.

Perform consistency check

You can choose one logical HDI container from the input help, or select the All logical HDI containers checkbox to perform the check for one HDI container, or for all containers. The system checks, for example, whether all HDI objects are active in the HTA repository, and whether exactly these object versions also exist in the physical HDI container. The system displays the result of the check in a log. If inconsistencies are found, long texts exist that will help you find the best way to remove the inconsistencies.

Perform deployability check

You can choose one logical HDI container from the input help, or select the All logical HDI containers checkbox to perform the check for one HDI container, or for all containers. The system checks whether the HDI objects can be deployed by executing a simulation make in HDI with the object versions that were already successfully deployed in the past. The system displays the result of the check in a log. If the simulation make fails, it is possible that referenced objects of a referenced container are no longer valid, or object changes are not compatible with previous versions. Execute the check for the referenced containers as well. If in doubt, contact the object owner of the object that cannot be deployed.

Lock projects of SAP Web IDE

You can lock all projects of SAP Web IDE for the specified container so that developers can no longer deploy HDI objects into the HDI container of this ABAP system from SAP Web IDE when executing a build. Usually, this action is executed automatically by Software Update Manager (SUM) before a system upgrade. However, it can be required in a scenario when the HDI object consistency check before an upgrade is negative and requires a fix of an HDI object in SAP Web IDE. In this case, an administrator can temporarily remove the lock with the Unlock projects of SAP Web IDE action so that developers can deploy HDI objects to the HDI container from SAP Web IDE. After the HDI object was fixed and deployed, the administrator can lock the projects again with the Lock projects of SAP Web IDE action.

Unlock projects of SAP Web IDE

You can unlock all projects of SAP Web IDE for the specified container so that developers can deploy HDI objects again into the HDI container of this ABAP system from SAP Web IDE when executing a build. Usually, this action is executed automatically by Software Update Manager (SUM) after a system upgrade. However, it can be required in a scenario when the HDI object consistency check before an upgrade is negative and requires a fix of an HDI object in SAP Web IDE. In this case, an administrator can temporarily remove the lock with the Unlock projects of SAP Web IDE action so that developers can deploy HDI objects to the HDI container from SAP Web IDE to fix the error. After the HDI object was fixed and deployed, the administrator can lock the projects again with the Lock projects of SAP Web IDE action.

Check and repair HDI containers

With this action, the system performs checks on all active logical HDI containers.

If the system detects any inconsistent HDI containers, it tries to repair them. This means that active logical HDI containers which exist in HTA (ABAP), but which do not exist in the database (SAP HANA) are recreated in SAP HANA. If active HDI objects exist in HTA for these logical HDI containers, the system redeploys them as well.

The system displays the result of the checks and repair actions in a log.

Find unsupported object types in SAP HANA Cloud

You want to migrate your HDI objects to SAP HANA Cloud. However, some features are either implemented differently in SAP HANA Cloud, or are not available at all. For more information, see the 'SAP HANA Cloud Migration Guide' on SAP Help Portal at https://help.sap.com/viewer/product/hana_cloud, in particular, the 'Compatibility with Other SAP HANA Versions' section.

Since some object types are no longer supported in SAP HANA Cloud, as a preparation step, this check analyzes for a given HDI container, if such an object exists in the HTA repository. If objects with unsupported object types are found, they are listed in the following categories:

• Own objects

Own objects are identified by their full transport name.

For own objects, you will have to prepare the migration yourself, by offering adjustments for all unsupported objects. For more information, see the SAP HANA Cloud Migration Guide. .

• Externally provided namespaces

Externally provided namespaces are listed together with the corresponding application component or software component.

Note: Expand an entry to get the list of objects in the namespace with unsupported object types.

For externally provided content, it is usually sufficient to contact the provider for details about how to migrate their content.

Note: You will need to execute a complete check for migration incompatibilities on HDI side (in SAP HANA). For more information, see the SAP HANA Cloud Migration Guide, 'Check for Incompatibilities' section.

ROGBILLS - Synchronize billing plans   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 9169 Date: 20240601 Time: 183910     sap01-206 ( 228 ms )