Ansicht
Dokumentation

TDHC0_UTIL_MSCRAMB1 - View Tables Required to be Scrambled

ROGBILLS - Synchronize billing plans   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

In this optional activity, you can list the tables that can be transferred because of customizing definitions but where the selection field is no key field. If these tables are to be included in the transfer then it is necessary to define scrambling rules.

An example is the SAP time event table TEVEN. This table will be selected because it contains a PERNR field. This is not a key field though. The key field here is the PDSNR. If the table was selected according to the PERNR and simply copied without any scrambling changes, then there is a risk that the PDSNR would already exist in the target system.

Both SAP and customer-own tables can be listed. The SAP ones will be delivered with scrambling content and they will be defined as "included" (see the activity for further information). The customer must explicitly define scrambling rules and then create an entry in the Transfer Status table for the affected tables.

Run the activity and determine whether the listed customer tables need to be transferred. If so, then create scrambling rules and then maintain the Transfer Status table using the activity Table Transfer Status (Optional).

NOTE: tables that contain a key field that is derived from a number range must always be scrambled. These will only be listed here though if the defined selection field is not a key field. Thus TEVEN will be listed because PERNR is its non-key selection field.

Note also, that even if scrambling rules exist for a table such as the TEVEN, they must be activated. If rules exist but aren't active then a check occurs in the transfer program which stops transfer of these tables and makes log entries. The following sequence of checks is made to each tables. The Table Transfer Statustable is read (which can be maintained in the above mentioned activity) and the run-time checks are made:

is the selected table in the Table Transfer Statustable?

If "No"then it's checked if the selection field of the table is a key field or not. If it is not a key field then scrambling must be defined for it and an entry made in the table to indicate that it is to be "included" in transfers (assuming it is required and should not simply be entered in the table to be excluded). Tables that aren't in the Table Transfer Statustable are considered "new" and will be recorded in the transfer program's log.

If "Yes"then it is asked whether it should be included or excluded. If excluded then nothing will be logged.

If the table is registered as being "included" a check will still be made to see if the selection field is a key field and, if it is, then scrambling must be defined and active for this table. If it is not then the table will be excluded from the transfer and an entry written in the log.

CPI1466 during Backup   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 3150 Date: 20240523 Time: 165300     sap01-206 ( 77 ms )