Database Reference
In-Depth Information
d. Deselect flags in order to skip replication and generation of source-dependent ob-
jects.
e. Stop RDA daemons and process chains.
f. Delete temporary/interim data used for analysis process design.
g. Delete temporary BW tables.
h. Delete entries from the DDNT and DDNF tables.
55. Execute HANA sizing program (pre-cleansing) /SDF/HANA_BW_SIZING.
56. Release all open transports for import into subsequent systems.
57. Create empty change request for SAP Notes applied during DMO.
58. Create empty change request for SPAU after upgrade.
59. Create empty change request for SPDD after upgrade.
60. Deactivate REVTRAC.
Do not skip step 0!
Before performing an SAP upgrade or importing SAP support stacks
in a development system, make sure you deactivate the Rev-Trac
field exits and BAdI. Also make sure you disable key level locking if
it is implemented in your system. Failure to disable these may leave
you unable to create transports that are required during the upgrade.
To deactivate the Rev-Trac field exits, run program RSMODPRF and deactivate field
exits for data elements TRKORR and TRORDERTXT. Deactivate the Rev-Trac BAdI
using transaction code SE19. Depending on your installation, your Rev-Trac BAdI is
named either Z_RSC_EP_TX_BADI or /RSC/DEV_EP_PLUS_TX. To disable key
level locking, ask Rev-Trac Support to supply a transport that will safely remove the
key level locking components for the development system. Import this transport into
this system. After completing your SAP upgrade, reactivate the Rev-Trac field exits
and BAdI. To re-enable key level locking, reimport the transport you originally used
to enable key level locking.
61. Request and take a backup of the interim BW (confirm with transaction code DB14).
