Ansicht
Dokumentation

TDHC0_CUSTM_TR_TAB1 - Set Table Transfer Status

CL_GUI_FRONTEND_SERVICES - Frontend Services   CPI1466 during Backup  
This documentation is copyright by SAP AG.

All data that is transferred needs to be registered in the table that this activity calls. SAP provides the initial entries. When you define new entries, you must add them to the table. You can add them with the "Include / Exclude" value set, or left blank. If there is no entry for a table then the transfer program does not copy it. In this case, a warning message is written to the log. If an entry in the table does not have an "Include / Exclude" value set, then the transfer does not occur, and there is no warning message.

The purpose of this table is to ensure that you do not transfer new tables are not transferred before you have the opportunity to define any appropriate scrambling rules, or to decide whether the table should be transferred at all.

In contract to most other customizing activities, this activity occurs in the sender system. In this respect, this is similar to the activity Exclude Organisational Groups from Transfer (PA). Since a sender system will frequently be set to be not modifiable it will be necessary to define entries in a system that is and then to transport these changes. For this, the view V_CNVHCM_TR_TAB can be maintained using the transaction Maintain Table Views (SM30). .

When the table is delivered by SAP then you can search for the entry in the sender system and use this as a basis in the change system (entries are copied by SAP into the sender system the first time a packet is executed).

For own tables, you will need to know the table group. See the documentation for the activity Define Customer Table Transfer Groups.

This activity is optional.

The phase must be active in order to maintain customizing data. This activity occurs in the sender system. If you are unable to make changes here directly then you must make changes in another system and then transport them.

Maintain the table in the sender system, or transport it there.

If there are entries in this table for tables that contain no entries, it is best to remove them as this can improve performance. Check especially that the entries for the CLUST table grouping reflect the reality of the tables to which they refer. For example, if there is an PCL2_RD entry, this refers to the German Payroll Results. Unless you are in Germany, you are unlikely to have RD entries in your PCL2table. Such superfluous entries can increase runtimes and should be removed.

If you are experiencing performance problems in the delete function then please read the Important performance note of that activity.

.

Addresses (Business Address Services)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 3146 Date: 20240523 Time: 172708     sap01-206 ( 71 ms )