Note 1749824 - Treatment of SLT triggers during transport

IMPORTANT: When you implement this SAP Note, you MUST perform the manual pre-implementation steps. Otherwise, you can no longer log on to the SAP system after you ignore the activation errors. 

Do not deimplement this SAP Note. 

Refer to SAP Note 1809597 if you can no longer log on to the system because you ignored the manual pre-implementation steps or because you tried to deimplement this SAP Note. 

A table change terminates due to the existence of SLT replication triggers.

HANA

With SAP BASIS 7.00 and higher, the ABAP Dictionary of AS ABAP rejects all DB changes of tables with triggers. For the replication triggers created by SAP, this procedure restricts live operation. Therefore, triggers for adding non-key fields were allowed with SAP Note 1655725. However, in some cases this may still cause the termination with errors of transports with DDIC changes due to the existence of replication triggers. 

With the current versions of the replication tools, the replication triggers are in particular name spaces and can therefore be distinguished from other triggers. This allows an explicit processing of these triggers possible.

This SAP Note differentiates between manageable and unmanageable triggers. Currently, only triggers whose names begin with /1LT/ or /1CADMC/ are considered manageable. All other triggers are not manageable. 

When a table is changed using triggers, the triggers are treated as follows:

              The system rejects all change operations of the table. This means that the system behaves in the same way as before the implementation of SAP Note 1655725.

                       The triggers are retained.

                       The manageable triggers are deleted. The replication for the table must start again after the deletion of triggers.

------------------------------------------------------------------------ 
|Manual Activity                                                       | 
------------------------------------------------------------------------ 
|VALID FOR                                                             | 
|Software Component   SAP_BASIS                      SAP Basis compo...| 
| Release 700          SAPKB70007 - SAPKB70027                         | 
| Release 710          Until SAPKB71015                                | 
| Release 711          SAPKB71101 - SAPKB71110                         | 
| Release 701          Until SAPKB70112                                | 
| Release 702          SAPKB70201 - SAPKB70212                         | 
| Release 730          SAPKB73001 - SAPKB73008                         | 
| Release 720          SAPKB72002 - SAPKB72007                         | 
------------------------------------------------------------------------ 

The data element DDTRIGGERNAME must be newly created in the package SDIC. The data element uses the implemented type CHAR with the length 30 and has no further characteristics or field labels. 

The structure DDLINE must be newly created in the package SDIC. Short description: 
  DD: a line of a statement 
The structure has exactly one field LINE  of the implemented type CHAR with the length 80. The enhancement category is "Cannot Be Enhanced". 

You have to create the following messages in message class DA using transaction SE91: 
Number    Text: 
  520   Error & when determining triggers for table & 
  529   Table change: Triggers in the DB will be deleted 
  530   Trigger & of table & has already been deleted in the DB 

  531   Trigger & of Table &: Error & during deletion 
  532   Trigger & of table &: Error & during creation of 
        delete statements 
  533   Trigger & of table & deleted 
  534   Table &: Trigger not deleted.Non-manageable 
        triggers exist: 
  535   Trigger & of table & not manageable 
  536   Delete statements for triggers & of table & were 
        created 
  537   Table & has no trigger 
Check 'self-explanatory' for all messages.