How can I save time for post-upgrade imports, such as release customizing, adjustments to customer-specific applications, interfaces and forms, and ABAP code modifications?
To avoid downtime when you import additional post-upgrade transports, you can include transports in the upgrade process. Use the option ‘single change request’ in the ‘BIND_PATCH’ phase of PREPARE to specify your repository-based post-upgrade transports. They are merged in the exchange repository and imported during the technical upgrade process. Customizing transports are not suitable for linking to the upgrade, since for security reasons the upgrade tools import client-dependent data into SAP’s reference client 000 only. You still need to import the transports after the upgrade directly into the target client. If you bundle a large number of single Customizing transports into one large transport, this increases the performance significantly.
Related Questions
- Manually customizing macros TLNIIS, PGMNAMES and USREDITS every time I install a new genlevel or release is time-consuming and error-prone. Isn there an easier way to do it?
- How can I save time for post-upgrade imports, such as release customizing, adjustments to customer-specific applications, interfaces and forms, and ABAP code modifications?
- Are there applications in VanS that will reduce the time required to find and access shipment folders and shipment documents?
