Upgrade stopped in TABIMP_UPG phase

[former_member245712]

Hello.

We're currently upgrading our BW system from 7.00 ( with SEM-BW 6.00

and FINBASIS 6.00 ) to 7.01 SPS 10( with SEM-BW 6.04 and FINBASIS

6.04 ).

We generated the stack.xml with SOLMAN, and added the SEM-BW, FINBASIS

and SAP_BS_FND as required in note 1326576.

Unfortunately, the upgrade failed during the DOWNTIME - TABIMP_UPG

phase with the following error message:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

MAIN IMPORT ERRORS and RETURN CODE in SAPIA70017.BW7

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2EETW109 table "CRMC_IC_XMLSTORE" does not exist in nametab.

Long text:

Cause

Table &V#& does not exist and therefore cannot be transported.

System Response

INCLUDE R3TRANS-OBJTP

What to do

Export: Ensure that the table has been entered correctly.

Import: Find out why the table is not active. An error may have

occurred when activating the table, or the table description may

not

have been transported.

2EETW109 table "CRMC_IC_XMLSTORE" does not exist in nametab.

2EETW109 table "CRMC_IC_XMLSTORT" does not exist in nametab.

2EETW109 table "CRMC_SAF_MODELS" does not exist in nametab.

2EETW109 table "CRMD_IC_XMLCOM" does not exist in nametab.

2EETW109 table "CRMD_IC_XMLCOM_T" does not exist in nametab.

We didn't find any useful note.

Could you please help us ?

Best regards.

Sébastien

[Reagan · Accepted solution]

And this is the SAP note

1705333  - Error in TABIM_UPG phase of Upgrade/Update - Table "CRMC_IC_XMLSTORT" does not exist in n...

Regards

RB

[valeriocicchiel]

Hello community,

same problem here, the only difference is that SEM-BW, FINBASIS, SAP_BS_FND not installed.

Does anybody have a workaround or an official reply from SAP?

Valerio

[former_member245712]

Hello Valerio.

SAP was not able to help us solving our issue.

In our case, we finally found how to proceed. In fact, the issue is on the stack file generated by the MOPZ.

The MOPZ added the support packages 7.00 level 17 and higher, but you don't need it in your upgrade.

As we didn't receive any helpful answer from the SAP support, we decided to regenerate the stack file but without these unnecessary support packages. ( Unthick the boxes manually in MOPZ )

Unfortunately, we had to restore the instance and restart the upgrade.

We were able to go further in the upgrade and everything finished well. We're currently upgrading our third system with this procedure.

I guess there's still something wrong in the MOPZ but I didn't have enough time to troubleshoot it yet.

Hope it could help you.

Best regards.

Sebastien.

[valeriocicchiel]

Hello Sebastien,

SAP just released the official SAP Note 1689053 which address our issue. Maybe this can help other people facing the same problem.

Valerio

[former_member245712]

Thanks for your answer, for us it's too late, but the note seems to correct the issue.

I'll try to implement it later and I'll see the improvements.

I think it's better to update the SPAM rather to deselect manually the support packages.

Good luck for your upgrade !

Sébastien.

[Former Member]

Sebastian,

Make sure you have below two CRT's are in EPS/in and try again.

SAPK-52006INCRMUIF CRMUIF 520: patch 0006, CRT for SAPKA70017

SAPK-60005INCRMUIF CRMUIF 600: patch 0005, CRT for SAPKA70017

Note 1074019 - Support Packages for CRMUIF 520

[former_member245712]

Thanks for your answer.

My source system components are:

BI_CONT 703 0008

FINBASIS 600 0011

PI_BASIS 2005_1_700 0014

SAP_ABA 700 0014

SAP_BASIS 700 0014

SAP_BW 700 0016

SEM-BW 600 0011

ST-A/PI 01M_BCO700 0001

ST-PI 2008_1_700 0003

And the target release will be:

BI_CONT 705 0003

FINBASIS 604 0010

PI_BASIS 701 0010

SAP_ABA 701 0010

SAP_BASIS 701 0010

SAP_BW 701 0010

SEM-BW 604 0010

ST-A/PI 01M_BCO700 0001

ST-PI 2008_1_700 0003

SAP_BS_FND701 0010

So there's no CRM components installed.

Best regards.

Sébastien.

[Former Member]

Sebastian,

Those two components are CRT - Conflict Resolution Transport (CRT) for ABAP SAPKA70017. You need to include CRT's along with SP's.

A CRT that is valid for an add-on release also contains all adjustments for earlier releases of this add-on. A CRT can also contain other quality improvements for the add-on in question. A CRT can also be a special Component Support Package for an add-on software component

Refer to below links

http://forums.sdn.sap.com/thread.jspa?threadID=1614565

http://help.sap.com/saphelp_46c/helpdata/en/3d/ad5d044ebc11d182bf0000e829fbfe/content.htm

[former_member245712]

Arjun,

As far as I know, a CRT is used to solve a conflict between two components.

In the case you mentioned, the CRTs are used for solving issues between SAPKA70017 and CRMUIF520 on one hand, SAPKA70017 and CRMUIF600 on the other one.

However, in my case, I've no CRMUIF add-on to maintain, so no CRT to add in the queue.

Moreover, I'm already in the DOWNTIME phase of the upgrade, so my SP queue has already been validated by the EHPI program ( which is up-to-date).

Sébastien.