Upgrade to NW 7.01 - ST-A/PI ISSUE

[former_member633852]

Dear Expoerts,

We are upgrading BW 3.5 NW 2004s to NW 701 Ehp1, Upgrade is hanging during IS-SELECT phase and could not find ST-A/PI add-on from EPS root directory via method Upgrade with Saint Package,

Source ST-A/PI version is 01M_BCO640 Patch 1(SAPKITAB6F) and we've extracted ST-A/PI 01M_BCO700 SAPKITAB7E file to EPS directory for upgrade, but upgrade tool could not find, BI_CONT and ST-PI did not get the error, only ST-A/PI

2 ETQ096 Package queue successfully disassembled

4 ETQ399 Final decision for 'ST-PI' is: UPG WITH SAINT PACK

4 ETQ399 PI_BASIS 2005_1_640 701 INST/UPG WITH STD CD 555060

4 ETQ399 BI_CONT 353 704 UPG WITH SAINT PACK 1000822

4 ETQ399 ST-A/PI 01M_BCO640 ? UNDECIDED 69455

4 ETQ399 ST-PI 2008_1_640 2008_1_700 UPG WITH SAINT PACK 539977

4 ETQ399 Decision about Add-on ST-A/PI ...

4 ETQ399 user decision 'ST-A/PI': UPG WITH SAINT PACK

4 ETQ399 Looking for SAINT package for 'ST-A/PI' ...

4 ETQ399 R3upReadNewPackages:

4 ETQ399 patchType='U', langVect='DET'

4 ETQ359 RFC Login to: System="DTB", Nr="00", GwHost="bwdev", GwService="sapgw00"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "spda_read_new_packages" by RFC

4 ETQ399 ismovesVersion='0'

4 ETQ399 R3upReadNewPackages: exit: rc=0

4 ETQ399 ... No matching package found.

4 ETQ399 Decision about Add-on ST-A/PI ...

we are using latest SAPup version, source release kernel and spam has the latest version,

bwdev:dtbadm> ./SAPup -V

Enter the path of your root directory [/usr/sap/DTB/upg/abap]:

Root directory =

• Reexecuting ./SAPup with adapted environment and restart=3.

This is SAPup version 7.10/7, build 31.022 for UNICODE

How can we solve this problem,

Best Regards,

[former_member633852]

deleting is the solution

[former_member633852]

Dear Experts,

Note 69455 - Servicetools for Applications ST-A/PI (ST14, RTCCTOOL, ST12)

I think we found the solution, As Note 69455 do we need to delete ST-A/PI ? Have you expericend before ?

3. Upgrade behaviour

Compare your SAP Basis release before vs. after upgrade.

If SAP_BASIS makes a major change then choose "Passive deletion", case 1).

If SAP_BASIS makes only a minor change in enhancement pack, e.g. 7.00->7.02, update ST-A/PI before to the newest ST-A/PI 01M* and choose "KEEP", case 2).

For upgrade with unicode conversion see the next chapter.

For upgrade of SAP Solution Manager see the chapter after next.

a) Case 1) Major change in basis release

Choose "Passive deletion" (= "Delete the Addon. The tables are not deleted on the DB except if they are empty") whenever the upgrade asks you about ST-A/PI. Like this the addon ST-A/PI gets lost just like standard coding during system upgrade. No restrictions on upgrade target releases or similar. You do not need the files of ST-A/PI for the target release during the upgrade. You do not need to update an old ST-A/PI prior to an upgrade.

After upgrade you may find messages like "Table /SSF/.. exists without DDIC reference" concerning service tool tables in the CHK_POSTUP phase or in DB02. These are harmless and most easily solved by implementing ST-A/PI on the new release. Then run report RTCCTOOL and follow the recommendation 'Procedure after upgrade' (takes 2 clicks from inside the tool).