Добрый день.
https://launchpad.support.sap.com/#/notes/70547Import postprocessing:
The import postprocessing must be carried out directly after importing the
transport requests. Every activity in the target client prior to the execution
of the import postprocessing can lead to inconsistencies. It is recommended to
wait a few minutes before you start the SCC7 to ensure that the buffer
synchronization is completed.
The import postprocessing is essential (except for a copy with SAP_USR before Release 4.0B), because important functions are only carried out there:
• Tables that have not been transported are deleted. These are in general tables of delivery class 'L' and 'W' and - depending on the copy profile - also those of delivery class 'A'.
• The runtime environment is adjusted to the current Customizing. For
this, postprocessing actions are started by the import postprocessing
(client validation exits) which are used - among other things - to
adjust data, reports, screens and number ranges.
• The texts are imported (up to and including Release 4.0)
• Depending on the copy profile address data is copied or deleted as of Release 4.0B.
• For copy profile SAP_USER, only the addresses of the user and of the company are generated.
• 3.0D,3.0E: For the text import, start report 'RSTXR3TR' with request <SId>KXnnn and for the generation, report 'RSCLIIMP' with request <SId>KTnnn. Report 'RSCLIIMP' starts several postprocessing reports in succession which end with a log each. Confirm every single log with 'F3' until the final log of 'RSCLIIMP' is displayed. Also refer to the documentation of the report.
• 3.0F: You can use both, the method for 3.0D/E (RSTXR3TR und RSCLIIMP) or Transaction SCC2. On the initial screen of SCC2, select the action 'Import'. Press 'Enter', and enter transport request <SId>KTnnn on the new screen. In Transaction SCC3 you can only find an import log after having successfully completed the postprocessing. By mistake, the log is stored with the logs of the transport requests. Therefore, you must select the button 'Transport requests'.
If import postprocessing using SCC2 terminates without obvious reason, you must
import request <SId>KTnnn again and start report 'RSCLIIMP' afterwards. At this
time the texts have already been imported and the tables have already been
deleted.
• As of 3.1G: Start Transaction SCC7. The old reports are no longer complete. The corresponding transport request is selected automatically. Also refer to Note 92770.
The import postprocessing can only be performed once. You start it with the
request <SId>KTnnn.