Any external programs affected by the move (BSI, etc.) must be dealt with post-copy.Security profiles and user lists need to be repositioned so they can be recreated post-copy.which exist only in QAS will need to be moved elsewhere, printed out, or otherwise repositioned before the copy. Communicate to everyone that any spool data, datasets, master data, etc.Preferably, everything should be pushed through pre-copy (including LCP and CRT imports, Hot Packs, and other SAP transports associated with notes).
Identify which transports exist in QAS but not in PRD and remind the owners that all transports which have not moved to PRD before the copy will no longer exist in QAS.In addition, take a snapshot of the client change settings (SCC4), system change options (SE03), workbench organizer/transport system configuration (SE06), and any other setting that will need to be restored in the target system. Anything from the target that will need to be restored (user definitions, profiles, jobs, printers, RFC destinations, etc.) after the copy must be saved out.Perform a backup of the original QAS system to restore to in case of difficulties.The source system should be backed up (Full Backup) and the media should be accessible from the target system.(NOTE: Be certain that both the DNS name and NetBIOS name of the server are in all CAPITALS, 8 characters or less, and contain no special characters.)
Sap authorizations made easy ecc6 license#
RSTS0024 Delete job log headersĀ from TST01 that are older than jobs RSPO1043 Spool Data-Consistency check in Background (SP12) RSBTCPRIDEL Reorganization of Print Parameters for Background Jobs RSARFCDL Cleans up log file for sm58 transfers SUSR406 Regenerate SAP_ALL profile or su21 AGR_REGENERATE _SAP_ALL it will generate SAP_ALL in all client if we going to run in 000 client Documents for System/User Statuses (Table JEST)