Note that the SUM does not explicitely mention this behavior on the dialog, only in the log files. If the source has just one instance, no specific handling happens. The source system has more than one instance.The source system does not yet has a separate ASCS.The SUM maintenance activity (like an upgrade) is targeting NW 7.50.The SUM will create a separate ASCS instance for the following condition (all have to apply together): Further one, there is no non-unicode load for the load-based procedure for NW 7.50. But the SUM procedure to create a shadow system requires the non-unicode kernel for a non-unicode source system. For NW 7.50, we do not have a non-unicode kernel.
NW 7.50 is unicode-only, and SAP has announced long time ago that the successor of SAP NetWeaver 7.40 will only by offered as Unicode system, and that the path to the successor of SAP NetWeaver 7.40 can only be reached from a unicode system … what was that again? I mean to say that you have to start from a Unicode system to reach NW 7.50 (and to reach EHP 8). – with SUM 1.0 SP 19 and higher, the Report RSUPG_TADIR_COMPONENT_CHECK (attached in SAP Note 2318321) will be executed by SUM automatically. – the load-based approach does not allow any inactive objects, see SAP Note 2435892. You may check the following SAP notes: SAP Note 2318321, SAP Note 530335. It is an upgrade, as the shadow system is created from DVDs, not cloned from the customer system (compare my outdated SCN blog on shadow system: SUM: introduction to shadow system).
It is not an update in the sense of the Enhancement Packages (EHPs) until now. SAP Business Suite 7 Innovations 2016 with SAP ECC 6.0 EHP 8 (6.18) is based on SAP NetWeaver 7.50 (NW 7.50), and the procedure is load-based.
These are the aspects that I am aware of: I guess you know: Enhancement Package 8 for SAP ECC 6.0 is different, from our technical perspective of Software Logistics.
0 kommentar(er)
