2131961 - Import of HOTx objects ends with RC 12 in SAP HANA repository deployment step

Symptom

This SAP Note applies to the following cases:

1. The import of SAP HANA repository objects (R3TR HOTA, LIMU HOTO) ends with return code (RC) 12 in step C for SAP HANA repository deployment. In the log for this step, you find the information "Program canceled (...) See job log".  If you click on the icon before "See job log", you branch to the job log. The job log contains one of the following errors:
1. "Internal session terminated with a runtime error OBJECTS_OBJREF_NOT_ASSIGNED (see ST22)".
   By double-clicking this line, you navigate to transaction ST22 and receive more information about this runtime error in the ABAP program RDDHANADEPLOYMENT. In the section "Source Code Extract", you can see that the error occurs in line 1011 for SAP_BASIS 7.40 SP 10 and in line 1138 for SAP_BASIS 7.40 SP 12 and SAP_BASIS 7.50 SP 0.
2. "Internal session terminated with a runtime error ITAB_ILLEGAL_SORT_ORDER (see ST22)".
   By double-clicking this line, you navigate to transaction ST22 and receive more information about this runtime error in the ABAP program RDDHANADEPLOYMENT. In the section "Source Code Extract", you can see that the error occurs in line 579 for SAP_BASIS 7.40 SP 12 and SAP_BASIS 7.50 SP 0, in line 622 for SAP_BASIS 7.40 SP 13, and in line 618 for SAP_BASIS 7.50 SP 1.
2. The import of SAP HANA repository objects (R3TR HOTA/LIMU HOTO) ends with RC 4 and only deploys some of the objects to be imported into the SAP HANA repository. Objects that only consists of a suffix (such as .xsapp or .xsaccess) are not deployed. These objects are output as "skipped transport objects" with the error category "Warning" in the log, in step 'C', SAP HANA repository deployment.
3. Implementing an SAP Note with automatic correction instructions with HOTx objects terminates with the runtime error ITAB_ILLEGAL_SORT_ORDER. The error occurs in the program RDDHANADEPLOYMENT. In the section "Source Code Extract", you can see that the error occurs in line 579 for SAP_BASIS 7.40 SP 12 and SAP_BASIS 7.50 SP 0, in line 622 for SAP_BASIS 7.40 SP 13, and in line 618 for SAP_BASIS 7.50 SP 1.

Other Terms

SAP HANA transport for ABAP (HTA), RDDHANADEPLOYMENT

Reason and Prerequisites

You use AS ABAP 7.40 SP 10, SP 11, SP 12, SP 13 or 7.50 SP 0, SP 1. During the import of the SAP HANA repository objects of the type R3TR HOTA or LIMU HOTO, you observe the system behavior described in the "Symptom" section.

Solution

For cases 1 and 3 described under "Symptom"
Make sure that the error occurs in the exact same rows that are mentioned in the "Symptom" section. If this is the case, implement the relevant correction instructions. If the error occurs in a different line, create a customer incident under the component BC-CTS-HTA.
For case 2
Check whether the skipped objects consist only of a suffix. You can do this either directly in the log or in transaction SCTS_HTA. To do so, call transaction SCTS_HTA, enter the SAP HANA package name, and choose "Execute". The "Object Name" column should be blank for the skipped objects, the status should be gray, and the corresponding tooltip should be "Package/object cannot be synchronized". When you double-click one of these objects, you see that the "Status in ABAP" with "I - Inactive. Not yet been deployed into the SAP HANA repository" is issued. If this is the case, implement the relevant correction instructions.

Header Data

Released On	30.12.2015 15:53:49
Release Status	Released for Customer
Component	BC-CTS-HTA SAP HANA object transport for ABAP
Priority	Correction with medium priority
Category	Program error