2938979 - NetWeaver AS Java upgrade determines UPDATE scenario instead of SWITCH_UPGRADE

During a release upgrade of a NetWeaver AS Java system, SUM determines an UPDATE scenario during CONFIRM-TARGET phase:

CONFIRM-TARGET_01.LOG

Jun 18, 2020 8:56:50 PM [Info ]: The parsed source products are: 
Jun 18, 2020 8:56:50 PM [Info ]: The parsed target products are: 
Jun 18, 2020 8:56:50 PM [Info ]: The detected system topology is DUAL_STACK
Jun 18, 2020 8:56:50 PM [Info ]: Dialog eliminator BatchModeDialogEliminator does not allow to omit dialog ConfirmTargetDialog
Jun 18, 2020 8:57:45 PM [Info ]: The update scenario will be determined based on the scenarios configuration file ScenariosDefinition.xml
Jun 18, 2020 8:57:45 PM [Info ]: The scenario is: UPDATE
Jun 18, 2020 8:57:45 PM [Info ]: The Business Suite version will be determined based on the BS configuration file BSVersionDefinition.xml
Jun 18, 2020 8:57:45 PM [Info ]: No Business Suite Version is detected.
Jun 18, 2020 8:57:45 PM [Info ]: The detected Bs version is written into the data model
Jun 18, 2020 8:57:45 PM [Info ]: The scenario is UPDATE and is written in the SharedInputCatalog.xml
Jun 18, 2020 8:57:45 PM [Info ]: Saving data model JUP.J2EE.DataModel.xml ...
Jun 18, 2020 8:57:45 PM [Info ]: Data model JUP.J2EE.DataModel.xml saved.

Read more...

SAP NetWeaver AS Java 7.x

SAP NetWeaver 7.0 ; SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP Solution Manager 7.1 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0

wrong, incorrect , KBA , BC-UPG-TLS-TLJ , Upgrade tools for Java , Problem